Systems and methods for selecting which power transmitter should deliver wireless power to a receiving device in a wireless power delivery network
The embodiments described herein include a transmitter that transmits a power transmission signal (e.g., radio frequency (RF) signal waves) to create a three-dimensional pocket of energy. At least one receiver can be connected to or integrated into electronic devices and receive power from the pocket of energy. A wireless power network may include a plurality of wireless power transmitters each with an embedded wireless power transmitter manager, including a wireless power manager application. The wireless power network may include a plurality of client devices with wireless power receivers. Wireless power receivers may include a power receiver application configured to communicate with the wireless power manager application. The wireless power manager application may include a device database where information about the wireless power network may be stored.
Latest Energous Corporation Patents:
- Power wave transmission techniques to focus wirelessly delivered power at a location to provide usable energy to a receiving device
- Small form-factor devices with integrated and modular harvesting receivers, and shelving-mounted wireless-power transmitters for use therewith
- Near-field antenna for wireless power transmission with antenna elements that follow meandering patterns
- Systems and methods for machine learning based foreign object detection for wireless power transmission
- Systems and methods for controlling and managing operation of one or more power amplifiers to optimize the performance of one or more antennas
This application is a continuation-in-part of U.S. Non-Provisional patent application Ser. No. 14/272,124, filed May 7, 2014, entitled “System and Method for Controlling Communication Between Wireless Power Transmitter Managers,” which is herein fully incorporated by reference in its entirety.
This application relates to U.S. Non-Provisional patent application Ser. No. 13/891,430, filed May 10, 2013, entitled “Methodology For Pocket-forming;” U.S. Non-Provisional patent application Ser. No. 13/925,469, filed Jun. 24, 2013, entitled “Methodology for Multiple Pocket-Forming;” U.S. Non-Provisional patent application Ser. No. 13/946,082, filed Jul. 19, 2013, entitled “Method for 3 Dimensional Pocket-forming;” U.S. Non-Provisional patent application Ser. No. 13/891,399, filed May 10, 2013, entitled “Receivers for Wireless Power Transmission;” U.S. Non-Provisional patent application Ser. No. 13/891,445, filed May 10, 2013, entitled “Transmitters for Wireless Power Transmission;” U.S. Non-Provisional patent application Ser. No. 14/336,987, filed Jul. 21, 2014, entitled “System and Method for Smart Registration of Wireless Power Receivers in a Wireless Power Network,” U.S. Non-Provisional patent application Ser. No. 14/286,289, filed May 23, 2014, entitled “System and Method for Generating a Power Receiver Identifier in a Wireless Power Network,” U.S. Non-Provisional patent application Ser. No. 14/583,625, filed Dec. 27, 2014, entitled “Receivers for Wireless Power Transmission,” U.S. Non-Provisional patent application Ser. No. 14/583,630, filed Dec. 27, 2014, entitled “Methodology for Pocket-Forming,” U.S. Non-Provisional patent application Ser. No. 14/583,634, filed Dec. 27, 2014, entitled “Transmitters for Wireless Power Transmission,” U.S. Non-Provisional patent application Ser. No. 14/583,640, filed Dec. 27, 2014, entitled “Methodology for Multiple Pocket-Forming,” U.S. Non-Provisional patent application Ser. No. 14/583,641, filed Dec. 27, 2014, entitled “Wireless Power Transmission with Selective Range,” U.S. Non-Provisional patent application Ser. No. 14/583,643, filed Dec. 27, 2014, entitled “Method for 3 Dimensional Pocket-Forming,” all of which are incorporated herein by reference in their entirety.
TECHNICAL FIELDThe present disclosure relates generally to wireless power transmission.
BACKGROUNDPortable electronic devices such as smart phones, tablets, notebooks and other electronic devices have become an everyday need in the way we communicate and interact with others. The frequent use of these devices may require a significant amount of power, which may easily deplete the batteries attached to these devices. Therefore, a user is frequently needed to plug in the device to a power source, and recharge such device. This may require having to charge electronic equipment at least once a day, or in high-demand electronic devices more than once a day.
Such an activity may be tedious and may represent a burden to users. For example, a user may be required to carry chargers in case his electronic equipment is lacking power. In addition, users have to find available power sources to connect to. Lastly, users must plugin to a wall or other power supply to be able to charge his or her electronic device. However, such an activity may render electronic devices inoperable during charging.
Current solutions to this problem may include devices having rechargeable batteries. However, the aforementioned approach requires a user to carry around extra batteries, and also make sure that the extra set of batteries is charged. Solar-powered battery chargers are also known, however, solar cells are expensive, and a large array of solar cells may be required to charge a battery of any significant capacity. Other approaches involve a mat or pad that allows charging of a device without physically connecting a plug of the device to an electrical outlet, by using electromagnetic signals. In this case, the device still requires to be placed in a certain location for a period of time in order to be charged. Assuming a single source power transmission of electro-magnetic (EM) signal, an EM signal gets reduced by a factor proportional to 1/r2 in magnitude over a distance r, in other words, it is attenuated proportional to the square of the distance. Thus, the received power at a large distance from the EM transmitter is a small fraction of the power transmitted. To increase the power of the received signal, the transmission power would have to be boosted. Assuming that the transmitted signal has an efficient reception at three centimeters from the EM transmitter, receiving the same signal power over a useful distance of three meters would entail boosting the transmitted power by 10,000 times. Such power transmission is wasteful, as most of the energy would be transmitted and not received by the intended devices, it could be hazardous to living tissue, it would most likely interfere with most electronic devices in the immediate vicinity, and it may be dissipated as heat.
In yet another approach such as directional power transmission, it would generally require knowing the location of the device to be able to point the signal in the right direction to enhance the power transmission efficiency. However, even when the device is located, efficient transmission is not guaranteed due to reflections and interference of objects in the path or vicinity of the receiving device.
SUMMARYThe embodiments described herein include a transmitter that transmits a power transmission signal (e.g., radio frequency (RF) signal waves) to create a three-dimensional pocket of energy. At least one receiver can be connected to or integrated into electronic devices and receive power from the pocket of energy. The transmitter can locate the at least one receiver in a three-dimensional space using a communication medium (e.g., Bluetooth technology). The transmitter generates a waveform to create a pocket of energy around each of the at least one receiver. The transmitter uses an algorithm to direct, focus, and control the waveform in three dimensions. The receiver can convert the transmission signals (e.g., RF signals) into electricity for powering an electronic device. Accordingly, the embodiments for wireless power transmission can allow powering and charging a plurality of electrical devices without wires.
A wireless power network may include wireless power transmitters each with an embedded wireless power transmitter manager. The wireless power transmitter manager may include a wireless power manager application, which may be a software application hosted in a computing device. The wireless power transmitter manager may include a GUI which may be used by a user to perform management tasks.
The wireless power network may include a plurality of client devices with wireless power receivers built in as part of the device or adapted externally. Wireless power receivers may include a power receiver application configured to communicate with the power transmitter manager application in a wireless power transmitter. The wireless power manager application may include a device database where information about the wireless power network may be stored.
In one embodiment, a system for providing simultaneous communication in a wireless power delivery network, comprises: a plurality of power transmitters communicatively coupled to at least one transmitter manager; and at least one power receiver communicatively coupled to at least one user device; wherein the at least one transmitter manager receives from the at least one user device a selection indicator indicative of at least one of signal strength or proximity of the at least one user device relative to ones of the plurality of power transmitters; and wherein the transmission of controlled power transmission signals to produce a plurality of pockets of energy by ones of the plurality of power transmitters to the at least one power receiver is controlled by the at least one transmitter manager in accordance with the selection indicator.
In another embodiment, a method for providing simultaneous communication in a wireless power delivery network, comprises: transmitting, by at least one of a plurality of power transmitters, controlled power transmission signals to produce a plurality of pockets of energy to at least one power receiver communicatively coupled to at least one user device; and receiving, by at least one transmission manager of the at least one the plurality of power transmitters, a selection indicator indicative of signal strength or proximity of the at least one user device relative to the at least one of the plurality of power transmitters; wherein the transmitting by the at least one of the plurality of power transmitters to the at least one power receiver is controlled by the at least one transmitter manager in accordance with the selection indicator.
In a further embodiment, a system for providing simultaneous communication in a wireless power delivery network, comprises: a plurality of power transmitters communicatively coupled to at least one transmitter manager; and at least one power receiver communicatively coupled to at least one user device; wherein the at least one transmitter manager receives from the at least one user device a selection indicator indicative of at least one of signal strength or proximity of the at least one user device relative to ones of the plurality of power transmitters; and wherein the transmission of controlled power transmission signals to produce a plurality of pockets of energy by ones of the plurality of power transmitters to the at least one power receiver is controlled by the at least one transmitter manager in accordance with the selection indicator.
In another embodiment, a system for providing contemporaneous communication in a wireless power delivery network, comprises: a plurality of power transmitters communicatively coupled to at least one transmitter manager; and a power receiver communicatively coupled to a user device, wherein at least two of the plurality of power transmitters are available to generate pocket-forming energy in three dimensional space at the power receiver to charge or power the user device; wherein the at least one transmitter manager coordinates contemporaneous communication of the plurality of power transmitters with the power receiver via time division multiplexing (TDM) of such communication; wherein the at least one transmitter manager controls the transmission of controlled power transmission signals to produce a plurality of pockets of energy at the power receiver is in accordance with the time division multiplexing (TDM) of the contemporaneous communication.
In a further embodiment, a method for providing contemporaneous communication in a wireless power delivery network, comprises: transmitting, by at least one of a plurality of power transmitters, controlled power transmission signals to produce a plurality of pockets of energy to at least one power receiver communicatively coupled to at least one user device; and coordinating, by the at least one transmitter manager of the plurality of power transmitters, contemporaneous communication of the plurality of power transmitters with the power receiver via time division multiplexing (TDM) of such communication; wherein the at least one transmitter manager controls the transmission of controlled power transmission signals to produce a plurality of pockets of energy at the power receiver in accordance with the time division multiplexing (TDM) of the contemporaneous communication.
Additional features and advantages of an embodiment will be set forth in the description which follows, and in part will be apparent from the description. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the exemplary embodiments in the written description and claims hereof as well as the appended drawings.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
Non-limiting embodiments of the present disclosure are described by way of example with reference to the accompanying figures which are schematic and are not intended to be drawn to scale. Unless indicated as representing the background art, the figures represent aspects of the disclosure.
The present disclosure is here described in detail with reference to embodiments illustrated in the drawings, which form a part here. Other embodiments may be used and/or other changes may be made without departing from the spirit or scope of the present disclosure. The illustrative embodiments described in the detailed description are not meant to be limiting of the subject matter presented here. Furthermore, the various components and embodiments described herein may be combined to form additional embodiments not expressly described, without departing from the spirit or scope of the invention.
Reference will now be made to the exemplary embodiments illustrated in the drawings, and specific language will be used here to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Alterations and further modifications of the inventive features illustrated here, and additional applications of the principles of the inventions as illustrated here, which would occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the invention.
I. Systems and Methods for Wireless Power Transmissions
A. Components System Embodiment
1. Transmitters
The transmitter 101 may transmit or broadcast power transmission signals to a receiver 103 associated with a device 105. Although several of the embodiments mentioned below describe the power transmission signals as radio frequency (RF) waves, it should be appreciated that the power transmission may be physical media that is capable of being propagated through space, and that is capable of being converted into a source of electrical energy 103. The transmitter 101 may transmit the power transmission signals as a single beam directed at the receivers 103. In some cases, one or more transmitters 101 may transmit a plurality of power transmission signals that are propagated in a multiple directions and may deflect off of physical obstructions (e.g., walls). The plurality of power transmission signals may converge at a location in a three-dimensional space, forming a pocket of energy 104. Receivers 103 within the boundaries of an energy pocket 104 may capture and covert the power transmission signals into a useable source of energy. The transmitter 101 may control pocket-forming based on phase and/or relative amplitude adjustments of power transmission signals, to form constructive interference patterns.
Although the exemplary embodiment recites the use of RF wave transmission techniques, the wireless charging techniques should not be limited to RF wave transmission techniques. Rather, it should be appreciated that possible wireless charging techniques may include any number of alternative or additional techniques for transmitting energy to a receiver converting the transmitted energy to electrical power. Non-limiting exemplary transmission techniques for energy that can be converted by a receiving device into electrical power may include: ultrasound, microwave, resonant and inductive magnetic fields, laser light, infrared, or other forms of electromagnetic energy. In the case of ultrasound, for example, one or more transducer elements may be disposed so as to form a transducer array that transmits ultrasound waves toward a receiving device that receives the ultrasound waves and converts them to electrical power. In the case of resonant or inductive magnetic fields, magnetic fields are created in a transmitter coil and converted by a receiver coil into electrical power. In addition, although the exemplary transmitter 101 is shown as a single unit comprising potentially multiple transmitters (transmit array), both for RF transmission of power and for other power transmission methods mentioned in this paragraph, the transmit arrays can comprise multiple transmitters that are physically spread around a room rather than being in a compact regular structure. The transmitter includes an antenna array where the antennas are used for sending the power transmission signal. Each antenna sends power transmission waves where the transmitter applies a different phase and amplitude to the signal transmitted from different antennas. Similar to the formation of pockets of energy, the transmitter can form a phased array of delayed versions of the signal to be transmitted, then applies different amplitudes to the delayed versions of the signal, and then sends the signals from appropriate antennas. For a sinusoidal waveform, such as an RF signal, ultrasound, microwave, or others, delaying the signal is similar to applying a phase shift to the signal.
2. Pockets of Energy
A pocket of energy 104 may be formed at locations of constructive interference patterns of power transmission signals transmitted by the transmitter 101. The pockets of energy 104 may manifest as a three-dimensional field where energy may be harvested by receivers 103 located within the pocket of energy 104. The pocket of energy 104 produced by transmitters 101 during pocket-forming may be harvested by a receiver 103, converted to an electrical charge, and then provided to electronic client device 105 associated with the receiver 103 (e.g., laptop computer, smartphone, rechargeable battery). In some embodiments, there may be multiple transmitters 101 and/or multiple receivers 103 powering various client devices 105. In some embodiments, adaptive pocket-forming may adjust transmission of the power transmission signals in order to regulate power levels and/or identify movement of the devices 105.
3. Receivers
A receiver 103 may be used for powering or charging an associated client device 105, which may be an electrical device coupled to or integrated with the receiver 103. The receiver 103 may receive power transmission waves from one or more power transmission signals originating from one or more transmitters 101. The receiver 103 may receive the power transmission signals as a single beam produced by the transmitter 101, or the receiver 103 may harvest power transmission waves from a pocket of energy 104, which may be a three-dimensional field in space resulting from the convergence of a plurality of power transmission waves produced by one or more transmitters 101. The receiver 103 may comprise an array of antennas 112 configured to receive power transmission waves from a power transmission signal and harvest the energy from the power transmission signals of the single beam or pocket of energy 104. The receiver 103 may comprise circuitry that then converts the energy of the power transmission signals (e.g., the radio frequency electromagnetic radiation) to electrical energy. A rectifier of the receiver 103 may translate the electrical energy from AC to DC. Other types of conditioning may be applied, as well. For example, a voltage conditioning circuit may increase or decrease the voltage of the electrical energy as required by the client device 105. An electrical relay may then convey the electrical energy from the receiver 103 to the client device 105.
In some embodiments, the receiver 103 may comprise a communications component that transmits control signals to the transmitter 101 in order to exchange data in real-time or near real-time. The control signals may contain status information about the client device 105, the receiver 103, or the power transmission signals. Status information may include, for example, present location information of the device 105, amount of charge received, amount of charged used, and user account information, among other types of information. Further, in some applications, the receiver 103 including the rectifier that it contains may be integrated into the client device 105. For practical purposes, the receiver 103, wire 111, and client device 105 may be a single unit contained in a single packaging.
4. Control Signals
In some embodiments, control signals may serve as data inputs used by the various antenna elements responsible for controlling production of power transmission signals and/or pocket-forming. Control signals may be produced by the receiver 103 or the transmitter 101 using an external power supply (not shown) and a local oscillator chip (not shown), which in some cases may include using a piezoelectric material. Control signals may be RF waves or any other communication medium or protocol capable of communicating data between processors, such as Bluetooth®, RFID, infrared, near-field communication (NFC). As detailed later, control signals may be used to convey information between the transmitter 101 and the receiver 103 used to adjust the power transmission signals, as well as contain information related to status, efficiency, user data, power consumption, billing, geo-location, and other types of information.
5. Detectors
A detector 107 may comprise hardware similar to receivers 103, which may allow the detector 107 to receive power transmission signals originating from one or more transmitters 101. The detector 107 may be used by users to identify the location of pockets of energy 104, so that users may determine the preferable placement of a receiver 103. In some embodiments, the detector 107 may comprise an indicator light 108 that indicates when the detector is placed within the pocket of energy 104. As an example, in
6. Client Device
A client device 105 may be any electrical device that requires continuous electrical energy or that requires power from a battery. Non-limiting examples of client devices 105 may include laptops, mobile phones, smartphones, tablets, music players, toys, batteries, flashlights, lamps, electronic watches, cameras, gaming consoles, appliances, GPS devices, and wearable devices or so-called “wearables” (e.g., fitness bracelets, pedometers, smartwatch), among other types of electrical devices.
In some embodiments, the client device 105a may be a physical device distinct from the receiver 103a associated with the client device 105a. In such embodiments, the client device 105a may be connected to the receiver over a wire 111 that conveys converted electrical energy from the receiver 103a to the client device 105a. In some cases, other types of data may be transported over the wire 111, such as power consumption status, power usage metrics, device identifiers, and other types of data.
In some embodiments, the client device 105b may be permanently integrated or detachably coupled to the receiver 103b, thereby forming a single integrated product or unit. As an example, the client device 105b may be placed into a sleeve that has embedded receivers 103b and that may detachably couple to the device's 105b power supply input, which may be typically used to charge the device's 105b battery. In this example, the device 105b may be decoupled from the receiver, but may remain in the sleeve regardless of whether or not the device 105b requires an electrical charge or is being used. In another example, in lieu of having a battery that holds a charge for the device 105b, the device 105b may comprise an integrated receiver 105b, which may be permanently integrated into the device 105b so as to form an indistinct product, device, or unit. In this example, the device 105b may rely almost entirely on the integrated receiver 103b to produce electrical energy by harvesting pockets of energy 104. It should be clear to someone skilled in the art that the connection between the receiver 103 and the client device 105 may be a wire 111 or may be an electrical connection on a circuit board or an integrated circuit, or even a wireless connection, such as inductive or magnetic.
B. Method of Wireless Power Transmission
In a first step 201, a transmitter (TX) establishes a connection or otherwise associates with a receiver (RX). That is, in some embodiments, transmitters and receivers may communicate control data over using a wireless communication protocol capable of transmitting information between two processors of electrical devices (e.g., Bluetooth®, Bluetooth Low Energy (BLE), Wi-Fi, NFC, ZigBee®). For example, in embodiments implementing Bluetooth® or Bluetooth® variants, the transmitter may scan for receiver's broadcasting advertisement signals or a receiver may transmit an advertisement signal to the transmitter. The advertisement signal may announce the receiver's presence to the transmitter, and may trigger an association between the transmitter and the receiver. As described herein, in some embodiments, the advertisement signal may communicate information that may be used by various devices (e.g., transmitters, client devices, sever computers, other receivers) to execute and manage pocket-forming procedures. Information contained within the advertisement signal may include a device identifier (e.g., MAC address, IP address, UUID), the voltage of electrical energy received, client device power consumption, and other types of data related to power transmission. The transmitter may use the advertisement signal transmitted to identify the receiver and, in some cases, locate the receiver in a two-dimensional space or in a three-dimensional space. Once the transmitter identifies the receiver, the transmitter may establish the connection associated in the transmitter with the receiver, allowing the transmitter and receiver to communicate control signals over a second channel.
In a next step 203, the transmitter may use the advertisement signal to determine a set of power transmission signal features for transmitting the power transmission signals, to then establish the pockets of energy. Non-limiting examples of features of power transmission signals may include phase, gain, amplitude, magnitude, and direction among others. The transmitter may use information contained in the receiver's advertisement signal, or in subsequent control signals received from the receiver, to determine how to produce and transmit the power transmission signals so that the receiver may receive the power transmission signals. In some cases, the transmitter may transmit power transmission signals in a way that establishes a pocket of energy, from which the receiver may harvest electrical energy. In some embodiments, the transmitter may comprise a processor executing software modules capable of automatically identifying the power transmission signal features needed to establish a pocket of energy based on information received from the receiver, such as the voltage of the electrical energy harvested by the receiver from the power transmission signals. It should be appreciated that in some embodiments, the functions of the processor and/or the software modules may be implemented in an Application Specific Integrated Circuit (ASIC).
Additionally or alternatively, in some embodiments, the advertisement signal or subsequent signal transmitted by the receiver over a second communications channel may indicate one or more power transmission signals features, which the transmitter may then use to produce and transmit power transmission signals to establish a pocket of energy. For example, in some cases the transmitter may automatically identify the phase and gain necessary for transmitting the power transmission signals based on the location of the device and the type of device or receiver; and, in some cases, the receiver may inform the transmitter the phase and gain for effectively transmitting the power transmission signals.
In a next step 205, after the transmitter determines the appropriate features to use when transmitting the power transmission signals, the transmitter may begin transmitting power transmission signals, over a separate channel from the control signals. Power transmission signals may be transmitted to establish a pocket of energy. The transmitter's antenna elements may transmit the power transmission signals such that the power transmission signals converge in a two-dimensional or three-dimensional space around the receiver. The resulting field around the receiver forms a pocket of energy from which the receiver may harvest electrical energy. One antenna element may be used to transmit power transmission signals to establish two-dimensional energy transmissions; and in some cases, a second or additional antenna element may be used to transmit power transmission signals in order to establish a three-dimensional pocket of energy. In some cases, a plurality of antenna elements may be used to transmit power transmission signals in order to establish the pocket of energy. Moreover, in some cases, the plurality of antennas may include all of the antennas in the transmitter; and, in some cases, the plurality of antennas may include a number of the antennas in the transmitter, but fewer than all of the antennas of the transmitter.
As previously mentioned, the transmitter may produce and transmit power transmission signals, according to a determined set of power transmission signal features, which may be produced and transmitted using an external power source and a local oscillator chip comprising a piezoelectric material. The transmitter may comprise an RFIC that controls production and transmission of the power transmission signals based on information related to power transmission and pocket-forming received from the receiver. This control data may be communicated over a different channel from the power transmission signals, using wireless communications protocols, such as BLE, NFC, or ZigBee®. The RFIC of the transmitter may automatically adjust the phase and/or relative magnitudes of the power transmission signals as needed. Pocket-forming is accomplished by the transmitter transmitting the power transmission signals in a manner that forms constructive interference patterns.
Antenna elements of the transmitter may use concepts of wave interference to determine certain power transmission signals features (e.g., direction of transmission, phase of power transmission signal wave), when transmitting the power transmission signals during pocket-forming. The antenna elements may also use concepts of constructive interference to generate a pocket of energy, but may also utilize concepts of deconstructive interference to generate a transmission null in a particular physical location.
In some embodiments, the transmitter may provide power to a plurality of receivers using pocket-forming, which may require the transmitter to execute a procedure for multiple pocket-forming. A transmitter comprising a plurality of antenna elements may accomplish multiple pocket-forming by automatically computing the phase and gain of power transmission signal waves, for each antenna element of the transmitter tasked with transmitting power transmission signals the respective receivers. The transmitter may compute the phase and gains independently, because multiple wave paths for each power transmission signal may be generated by the transmitter's antenna elements to transmit the power transmission signals to the respective antenna elements of the receiver.
As an example of the computation of phase/gain adjustments for two antenna elements of the transmitter transmitting two signals, say X and Y where Y is 180 degree phase shifted version of X(Y=−X). At a physical location where the cumulative received waveform is X−Y, a receiver receives X−Y=X+X=2X, whereas at a physical location where the cumulative received waveform is X+Y, a receiver receives X+Y=X−X=0.
In a next step 207, the receiver may harvest or otherwise receive electrical energy from power transmission signals of a single beam or a pocket of energy. The receiver may comprise a rectifier and AC/DC converter, which may convert the electrical energy from AC current to DC current, and a rectifier of the receiver may then rectify the electrical energy, resulting in useable electrical energy for a client device associated with the receiver, such as a laptop computer, smartphone, battery, toy, or other electrical device. The receiver may utilize the pocket of energy produced by the transmitter during pocket-forming to charge or otherwise power the electronic device.
In next step 209, the receiver may generate control data containing information indicating the effectiveness of the single beam or energy pockets providing the receiver power transmission signals. The receiver may then transmit control signals containing the control data, to the transmitter. The control signals may be transmitted intermittently, depending on whether the transmitter and receiver are communicating synchronously (i.e., the transmitter is expecting to receive control data from the receiver). Additionally, the transmitter may continuously transmit the power transmission signals to the receiver, irrespective of whether the transmitter and receiver are communicating control signals. The control data may contain information related to transmitting power transmission signals and/or establishing effective pockets of energy. Some of the information in the control data may inform the transmitter how to effectively produce and transmit, and in some cases adjust, the features of the power transmission signals. Control signals may be transmitted and received over a second channel, independent from the power transmission signals, using a wireless protocol capable of transmitting control data related to power transmission signals and/or pocket-forming, such as BLE, NFC, Wi-Fi, or the like.
As mentioned, the control data may contain information indicating the effectiveness of the power transmission signals of the single beam or establishing the pocket of energy. The control data may be generated by a processor of the receiver monitoring various aspects of receiver and/or the client device associated with the receiver. The control data may be based on various types of information, such as the voltage of electrical energy received from the power transmission signals, the quality of the power transmission signals reception, the quality of the battery charge or quality of the power reception, and location or motion of the receiver, among other types of information useful for adjusting the power transmission signals and/or pocket-forming.
In some embodiments, a receiver may determine the amount of power being received from power transmission signals transmitted from the transmitter and may then indicate that the transmitter should “split” or segment the power transmission signals into less-powerful power transmission signals. The less-powerful power transmission signals may be bounced off objects or walls nearby the device, thereby reducing the amount of power being transmitted directly from the transmitter to the receiver.
In a next step 211, the transmitter may calibrate the antennas transmitting the power transmission signals, so that the antennas transmit power transmission signals having a more effective set of feature (e.g., direction, phase, gain, amplitude). In some embodiments, a processor of the transmitter may automatically determine more effective features for producing and transmitting the power transmission signals based on a control signal received from the receiver. The control signal may contain control data, and may be transmitted by the receiver using any number of wireless communication protocols (e.g., BLE, Wi-Fi, ZigBee®). The control data may contain information expressly indicating the more effective features for the power transmission waves; or the transmitter may automatically determine the more effective features based on the waveform features of the control signal (e.g., shape, frequency, amplitude). The transmitter may then automatically reconfigure the antennas to transmit recalibrated power transmission signals according to the newly determined more-effective features. For example, the processor of the transmitter may adjust gain and/or phase of the power transmission signals, among other features of power transmission feature, to adjust for a change in location of the receiver, after a user moved the receiver outside of the three-dimensional space where the pocket of energy is established.
C. System Architecture of Power Transmission System
Antenna elements 306 of the transmitter 302 may operate in single array, pair array, quad array, or any other suitable arrangement that may be designed in accordance with the desired application. Pockets of energy may be formed at constructive interference patterns where the power transmission waves 342 accumulate to form a three-dimensional field of energy, around which one or more corresponding transmission null in a particular physical location may be generated by destructive interference patterns. Transmission null in a particular physical location-may refer to areas or regions of space where pockets of energy do not form because of destructive interference patterns of power transmission waves 342.
A receiver 320 may then utilize power transmission waves 342 emitted by the transmitter 302 to establish a pocket of energy, for charging or powering an electronic device 313, thus effectively providing wireless power transmission. Pockets of energy may refer to areas or regions of space where energy or power may accumulate in the form of constructive interference patterns of power transmission waves 342. In other situations there can be multiple transmitters 302 and/or multiple receivers 320 for powering various electronic equipment for example smartphones, tablets, music players, toys and others at the same time. In other embodiments, adaptive pocket-forming may be used to regulate power on electronic devices. Adaptive pocket-forming may refer to dynamically adjusting pocket-forming to regulate power on one or more targeted receivers.
Receiver 320 may communicate with transmitter 302 by generating a short signal through antenna elements 324 in order to indicate its position with respect to the transmitter 302. In some embodiments, receiver 320 may additionally utilize a network interface card (not shown) or similar computer networking component to communicate through a network 340 with other devices or components of the system 300, such as a cloud computing service that manages several collections of transmitters 302. The receiver 320 may comprise circuitry 308 for converting the power transmission signals 342 captured by the antenna elements 324, into electrical energy that may be provided to and electric device 313 and/or a battery of the device 315. In some embodiments, the circuitry may provide electrical energy to a battery of receiver 335, which may store energy without the electrical device 313 being communicatively coupled to the receiver 320.
Communications components 324 may enable receiver 320 to communicate with the transmitter 302 by transmitting control signals 345 over a wireless protocol. The wireless protocol can be a proprietary protocol or use a conventional wireless protocol, such as Bluetooth®, BLE, Wi-Fi, NFC, ZigBee, and the like. Communications component 324 may then be used to transfer information, such as an identifier for the electronic device 313, as well as battery level information, geographic location data, or other information that may be of use for transmitter 302 in determining when to send power to receiver 320, as well as the location to deliver power transmission waves 342 creating pockets of energy. In other embodiments, adaptive pocket-forming may be used to regulate power provided to electronic devices 313. In such embodiments, the communications components 324 of the receiver may transmit voltage data indicating the amount of power received at the receiver 320, and/or the amount of voltage provided to an electronic device 313b or battery 315.
Once transmitter 302 identifies and locates receiver 320, a channel or path for the control signals 345 can be established, through which the transmitter 302 may know the gain and phases of the control signals 345 coming from receiver 320. Antenna elements 306 of the transmitter 302 may start to transmit or broadcast controlled power transmission waves 342 (e.g., radio frequency waves, ultrasound waves), which may converge in three-dimensional space by using at least two antenna elements 306 to manipulate the power transmission waves 342 emitted from the respective antenna element 306. These power transmission waves 342 may be produced by using an external power source and a local oscillator chip using a suitable piezoelectric material. The power transmission waves 342 may be controlled by transmitter circuitry 301, which may include a proprietary chip for adjusting phase and/or relative magnitudes of power transmission waves 342. The phase, gain, amplitude, and other waveform features of the power transmission waves 342 may serve as inputs for antenna element 306 to form constructive and destructive interference patterns (pocket-forming). In some implementations, a micro-controller 310 or other circuit of the transmitter 302 may produce a power transmission signal, which comprises power transmission waves 342, and that may be may split into multiple outputs by transmitter circuitry 301, depending on the number of antenna elements 306 connected to the transmitter circuitry 301. For example, if four antenna elements 306a-d are connected to one transmitter circuit 301a, the power transmission signal will be split into four different outputs each output going to an antenna element 306 to be transmitted as power transmission waves 342 originating from the respective antenna elements 306.
Pocket-forming may take advantage of interference to change the directionality of the antenna element 306 where constructive interference generates a pocket of energy and destructive interference generates a transmission null. Receiver 320 may then utilize pocket of energy produced by pocket-forming for charging or powering an electronic device and therefore effectively providing wireless power transmission.
Multiple pocket-forming may be achieved by computing the phase and gain from each antenna 306 of transmitter 302 to each receiver 320.
D. Components of Systems Forming Pockets of Energy
1. Transmitters
Transmitters 402 may be any device capable of broadcasting wireless power transmission signals, which may be RF waves 442, for wireless power transmission, as described herein. Transmitters 402 may be responsible for performing tasks related to transmitting power transmission signals, which may include pocket-forming, adaptive pocket-forming, and multiple pocket-forming. In some implementations, transmitters 402 may transmit wireless power transmissions to receivers 420 in the form of RF waves, which may include any radio signal having any frequency or wavelength. A transmitter 402 may include one or more antenna elements 406, one or more RFICs 408, one or more microcontrollers 410, one or more communication components 412, a power source 414, and a housing that may allocate all the requested components for the transmitter 402. The various components of transmitters 402 may comprise, and/or may be manufactured using, meta-materials, micro-printing of circuits, nano-materials, and the like.
In the exemplary system 400, the transmitter 402 may transmit or otherwise broadcast controlled RF waves 442 that converge at a location in three-dimensional space, thereby forming a pocket of energy 444. These RF waves may be controlled through phase and/or relative amplitude adjustments to form constructive or destructive interference patterns (i.e., pocket-forming). Pockets of energy 444 may be fields formed at constructive interference patterns and may be three-dimensional in shape; whereas transmission null in a particular physical location may be generated at destructive interference patterns. Receivers 420 may harvest electrical energy from the pockets of energy 444 produced by pocket-forming for charging or powering an electronic client device 446 (e.g., a laptop computer, a cell phone). In some embodiments, the system 400 may comprise multiple transmitters 402 and/or multiple receivers 420, for powering various electronic equipment. Non-limiting examples of client devices 446 may include: smartphones, tablets, music players, toys and others at the same time. In some embodiments, adaptive pocket-forming may be used to regulate power on electronic devices.
2. Receivers
Receivers 420 may include a housing where at least one antenna element 424, one rectifier 426, one power converter 428, and a communications component 430 may be included.
Housing of the receiver 420 can be made of any material capable of facilitating signal or wave transmission and/or reception, for example plastic or hard rubber. Housing may be an external hardware that may be added to different electronic equipment, for example in the form of cases, or can be embedded within electronic equipment as well.
3. Antenna Elements
Antenna elements 424 of the receiver 420 may comprise any type of antenna capable of transmitting and/or receiving signals in frequency bands used by the transmitter 402A. Antenna elements 424 may include vertical or horizontal polarization, right hand or left hand polarization, elliptical polarization, or other polarizations, as well as any number of polarization combinations. Using multiple polarizations can be beneficial in devices where there may not be a preferred orientation during usage or whose orientation may vary continuously through time, for example a smartphone or portable gaming system. For devices having a well-defined expected orientation (e.g., a two-handed video game controller), there might be a preferred polarization for antennas, which may dictate a ratio for the number of antennas of a given polarization. Types of antennas in antenna elements 424 of the receiver 420, may include patch antennas, which may have heights from about ⅛ inch to about 6 inches and widths from about ⅛ inch to about 6 inches. Patch antennas may preferably have polarization that depends upon connectivity, i.e., the polarization may vary depending on from which side the patch is fed. In some embodiments, the type of antenna may be any type of antenna, such as patch antennas, capable of dynamically varying the antenna polarization to optimize wireless power transmission.
4. Rectifier
Rectifiers 426 of the receiver 420 may include diodes, resistors, inductors, and/or capacitors to rectify alternating current (AC) voltage generated by antenna elements 424 to direct current (DC) voltage. Rectifiers 426 may be placed as close as is technically possible to antenna elements A24B to minimize losses in electrical energy gathered from power transmission signals. After rectifying AC voltage, the resulting DC voltage may be regulated using power converters 428. Power converters 428 can be a DC-to-DC converter that may help provide a constant voltage output, regardless of input, to an electronic device, or as in this exemplary system 400, to a battery. Typical voltage outputs can be from about 5 volts to about 10 volts. In some embodiments, power converter may include electronic switched mode DC-DC converters, which can provide high efficiency. In such embodiments, the receiver 420 may comprise a capacitor (not shown) that is situated to receive the electrical energy before power converters 428. The capacitor may ensure sufficient current is provided to an electronic switching device (e.g., switch mode DC-DC converter), so it may operate effectively. When charging an electronic device, for example a phone or laptop computer, initial high-currents that can exceed the minimum voltage needed to activate operation of an electronic switched mode DC-DC converter, may be required. In such a case, a capacitor (not shown) may be added at the output of receivers 420 to provide the extra energy required. Afterwards, lower power can be provided. For example, 1/80 of the total initial power that may be used while having the phone or laptop still build-up charge.
5. Communications Component
A communications component 430 of a receiver 420 may communicate with one or more other devices of the system 400, such as other receivers 420, client devices, and/or transmitters 402. Different antenna, rectifier or power converter arrangements are possible for a receiver as will be explained in following embodiments.
E. Methods of Pocket Forming for a Plurality of Devices
In a first step 501, a transmitter (TX) establishes a connection or otherwise associates with a receiver (RX). That is, in some embodiments, transmitters and receivers may communicate control data over using a wireless communication protocol capable of transmitting information between two processors of electrical devices (e.g., Bluetooth®, BLE, Wi-Fi, NFC, ZigBee®). For example, in embodiments implement Bluetooth® or Bluetooth® variants, the transmitter may scan for receiver's broadcasting advertisement signals or a receiver may transmit an advertisement signal to the transmitter. The advertisement signal may announce the receiver's presence to the transmitter, and may trigger an association between the transmitter and the receiver. As described later, in some embodiments, the advertisement signal may communicate information that may be used by various devices (e.g., transmitters, client devices, sever computers, other receivers) to execute and manage pocket-forming procedures. Information contained within the advertisement signal may include a device identifier (e.g., MAC address, IP address, UUID), the voltage of electrical energy received, client device power consumption, and other types of data related to power transmission waves. The transmitter may use the advertisement signal transmitted to identify the receiver and, in some cases, locate the receiver in a two-dimensional space or in a three-dimensional space. Once the transmitter identifies the receiver, the transmitter may establish the connection associated in the transmitter with the receiver, allowing the transmitter and receiver to communicate control signals over a second channel.
As an example, when a receiver comprising a Bluetooth® processor is powered-up or is brought within a detection range of the transmitter, the Bluetooth processor may begin advertising the receiver according to Bluetooth® standards. The transmitter may recognize the advertisement and begin establishing connection for communicating control signals and power transmission signals. In some embodiments, the advertisement signal may contain unique identifiers so that the transmitter may distinguish that advertisement and ultimately that receiver from all the other Bluetooth® devices nearby within range.
In a next step 503, when the transmitter detects the advertisement signal, the transmitter may automatically form a communication connection with that receiver, which may allow the transmitter and receiver to communicate control signals and power transmission signals. The transmitter may then command that receiver to begin transmitting real-time sample data or control data. The transmitter may also begin transmitting power transmission signals from antennas of the transmitter's antenna array.
In a next step 505, the receiver may then measure the voltage, among other metrics related to effectiveness of the power transmission signals, based on the electrical energy received by the receiver's antennas. The receiver may generate control data containing the measured information, and then transmit control signals containing the control data to the transmitter. For example, the receiver may sample the voltage measurements of received electrical energy, for example, at a rate of 100 times per second. The receiver may transmit the voltage sample measurement back to the transmitter, 100 times a second, in the form of control signals.
In a next step 507, the transmitter may execute one or more software modules monitoring the metrics, such as voltage measurements, received from the receiver. Algorithms may vary production and transmission of power transmission signals by the transmitter's antennas, to maximize the effectiveness of the pockets of energy around the receiver. For example, the transmitter may adjust the phase at which the transmitter's antenna transmit the power transmission signals, until that power received by the receiver indicates an effectively established pocket energy around the receiver. When an optimal configuration for the antennas is identified, memory of the transmitter may store the configurations to keep the transmitter broadcasting at that highest level.
In a next step 509, algorithms of the transmitter may determine when it is necessary to adjust the power transmission signals and may also vary the configuration of the transmit antennas, in response to determining such adjustments are necessary. For example, the transmitter may determine the power received at a receiver is less than maximal, based on the data received from the receiver. The transmitter may then automatically adjust the phase of the power transmission signals, but may also simultaneously continues to receive and monitor the voltage being reported back from receiver.
In a next step 511, after a determined period of time for communicating with a particular receiver, the transmitter may scan and/or automatically detect advertisements from other receivers that may be in range of the transmitter. The transmitters may establish a connection to the second receiver responsive to Bluetooth® advertisements from a second receiver.
In a next step 513, after establishing a second communication connection with the second receiver, the transmitter may proceed to adjust one or more antennas in the transmitter's antenna array. In some embodiments, the transmitter may identify a subset of antennas to service the second receiver, thereby parsing the array into subsets of arrays that are associated with a receiver. In some embodiments, the entire antenna array may service a first receiver for a given period of time, and then the entire array may service the second receiver for that period of time.
Manual or automated processes performed by the transmitter may select a subset of arrays to service the second receiver. In this example, the transmitter's array may be split in half, forming two subsets. As a result, half of the antennas may be configured to transmit power transmission signals to the first receiver, and half of the antennas may be configured for the second receiver. In the current step 513, the transmitter may apply similar techniques discussed above to configure or optimize the subset of antennas for the second receiver. While selecting a subset of an array for transmitting power transmission signals, the transmitter and second receiver may be communicating control data. As a result, by the time that the transmitter alternates back to communicating with the first receiver and/or scan for new receivers, the transmitter has already received a sufficient amount of sample data to adjust the phases of the waves transmitted by second subset of the transmitter's antenna array, to transmit power transmission waves to the second receiver effectively.
In a next step 515, after adjusting the second subset to transmit power transmission signals to the second receiver, the transmitter may alternate back to communicating control data with the first receiver, or scanning for additional receivers. The transmitter may reconfigure the antennas of the first subset, and then alternate between the first and second receivers at a predetermined interval.
In a next step 517, the transmitter may continue to alternate between receivers and scanning for new receivers, at a predetermined interval. As each new receiver is detected, the transmitter may establish a connection and begin transmitting power transmission signals, accordingly.
In one exemplary embodiment, the receiver may be electrically connected to a device like a smart phone. The transmitter's processor would scan for any Bluetooth devices. The receiver may begin advertising that it's a Bluetooth device through the Bluetooth chip. Inside the advertisement, there may be unique identifiers so that the transmitter, when it scanned that advertisement, could distinguish that advertisement and ultimately that receiver from all the other Bluetooth devices nearby within range. When the transmitter detects that advertisement and notices it is a receiver, then the transmitter may immediately form a communication connection with that receiver and command that receiver to begin sending real time sample data.
The receiver would then measure the voltage at its receiving antennas, send that voltage sample measurement back to the transmitter (e.g., 100 times a second). The transmitter may start to vary the configuration of the transmit antennas by adjusting the phase. As the transmitter adjusts the phase, the transmitter monitors the voltage being sent back from the receiver. In some implementations, the higher the voltage, the more energy may be in the pocket. The antenna phases may be altered until the voltage is at the highest level and there is a maximum pocket of energy around the receiver. The transmitter may keep the antennas at the particular phase so the voltage is at the highest level.
The transmitter may vary each individual antenna, one at a time. For example, if there are 32 antennas in the transmitter, and each antenna has 8 phases, the transmitter may begin with the first antenna and would step the first antenna through all 8 phases. The receiver may then send back the power level for each of the 8 phases of the first antenna. The transmitter may then store the highest phase for the first antenna. The transmitter may repeat this process for the second antenna, and step it through 8 phases. The receiver may again send back the power levels from each phase, and the transmitter may store the highest level. Next the transmitter may repeat the process for the third antenna and continue to repeat the process until all 32 antennas have stepped through the 8 phases. At the end of the process, the transmitter may transmit the maximum voltage in the most efficient manner to the receiver.
In another exemplary embodiment, the transmitter may detect a second receiver's advertisement and form a communication connection with the second receiver. When the transmitter forms the communication with the second receiver, the transmitter may aim the original 32 antennas towards the second receiver and repeat the phase process for each of the 32 antennas aimed at the second receiver. Once the process is completed, the second receiver may getting as much power as possible from the transmitter. The transmitter may communicate with the second receiver for a second, and then alternate back to the first receiver for a predetermined period of time (e.g., a second), and the transmitter may continue to alternate back and forth between the first receiver and the second receiver at the predetermined time intervals.
In yet another implementation, the transmitter may detect a second receiver's advertisement and form a communication connection with the second receiver. First, the transmitter may communicate with the first receiver and re-assign half of the exemplary 32 the antennas aimed at the first receiver, dedicating only 16 towards the first receiver. The transmitter may then assign the second half of the antennas to the second receiver, dedicating 16 antennas to the second receiver. The transmitter may adjust the phases for the second half of the antennas. Once the 16 antennas have gone through each of the 8 phases, the second receiver may be obtaining the maximum voltage in the most efficient manner to the receiver.
F. Wireless Power Transmission with Selective Range
1. Constructive Interference
Continuing with
In contrast, as shown in
G. Exemplary System Embodiment Using Heat Maps
As user may seem to be obstructing the path between receivers 920A, 920B and transmitters 902A, 902B, RF waves may not be easily aimed to the receivers 920A, 920B in a linear direction. However, since the short signals generated from receivers 920A, 920B may be omni-directional for the type of antenna element used, these signals may bounce over the walls 944A, 944B until they reach transmitters 902A, 902B. A hot spot 944A, 944B may be any item in the room which will reflect the RF waves. For example, a large metal clock on the wall may be used to reflect the RF waves to a user's cell phone.
A micro controller in the transmitter adjusts the transmitted signal from each antenna based on the signal received from the receiver. Adjustment may include forming conjugates of the signal phases received from the receivers and further adjustment of transmit antenna phases taking into account the built-in phase of antenna elements. The antenna element may be controlled simultaneously to steer energy in a given direction. The transmitter 902A, 902B may scan the room, and look for hot spots 944A, 944B. Once calibration is performed, transmitters 902A, 902B may focus RF waves in a channel following a path that may be the most efficient paths. Subsequently, RF signals 942A, 942B may form a pocket of energy on a first electronic device and another pocket of energy in a second electronic device while avoiding obstacles such as user and furniture.
When scanning the service area, the room in
The transmitters 902A, 902B, may use the Bluetooth connection to determine the location of the receivers 920A, 920B, and may use different non-overlapping parts of the RF band to channel the RF waves to different receivers 920A, 920B. In some implementations, the transmitters 902A, 902B, may conduct a scan of the room to determine the location of the receivers 920A, 920B and forms pockets of energy that are orthogonal to each other, by virtue of non-overlapping RF transmission bands. Using multiple pockets of energy to direct energy to receivers may inherently be safer than some alternative power transmission methods since no single transmission is very strong, while the aggregate power transmission signal received at the receiver is strong.
H. Exemplary System Embodiment
Multiple pocket forming 1000A may be achieved by computing the phase and gain from each antenna of transmitter 1002A to each receiver 1020A. The computation may be calculated independently because multiple paths may be generated by antenna element from transmitter 1002A to antenna element from receivers 1020A.
I. Exemplary System Embodiment
Once transmitter 1002B identities and locates receiver, a channel or path can be established by knowing the gain and phases coming from receiver. Transmitter 1002B may start to transmit controlled RF waves 1042B that may converge in three-dimensional space by using a minimum of two antenna elements. These RF waves 1042B may be produced using an external power source and a local oscillator chip using a suitable piezoelectric material. RF waves 1042B may be controlled by RFIC that may include a proprietary chip for adjusting phase and/or relative magnitudes of RF signals, which may serve as inputs for antenna elements to form constructive and destructive interference patterns (pocket-forming). Pocket-forming may take advantage of interference to change the directionality of the antenna elements where constructive interference generates a pocket of energy and deconstructive interference generates a null in a particular physical location. Receiver may then utilize pocket of energy produced by pocket-forming for charging or powering an electronic device, for example a laptop computer and a smartphone and thus effectively providing wireless power transmission.
Multiple pocket-forming 1000B may be achieved by computing the phase and gain from each antenna of transmitter to each receiver. The computation may be calculated independently because multiple paths may be generated by antenna elements from transmitter to antenna elements from receiver.
An example of the computation for at least two antenna elements may include determining the phase of the signal from the receiver and applying the conjugate of the receive parameters to the antenna elements for transmission.
In some embodiments, two or more receivers may operate at different frequencies to avoid power losses during wireless power transmission. This may be achieved by including an array of multiple embedded antenna elements in transmitter 1002B. In one embodiment, a single frequency may be transmitted by each antenna in the array. In other embodiments some of the antennas in the array may be used to transmit at a different frequency. For example, ½ of the antennas in the array may operate at 2.4 GHz while the other ½ may operate at 5.8 GHz. In another example, ⅓ of the antennas in the array may operate at 900 MHz, another ⅓ may operate at 2.4 GHz, and the remaining antennas in the array may operate at 5.8 GHz.
In another embodiment, each array of antenna elements may be virtually divided into one or more antenna elements during wireless power transmission, where each set of antenna elements in the array can transmit at a different frequency. For example, an antenna element of the transmitter may transmit power transmission signals at 2.4 GHz, but a corresponding antenna element of a receiver may be configured to receive power transmission signals at 5.8 GHz. In this example, a processor of the transmitter may adjust the antenna element of the transmitter to virtually or logically divide the antenna elements in the array into a plurality patches that may be fed independently. As a result, ¼ of the array of antenna elements may be able to transmit the 5.8 GHz needed for the receiver, while another set of antenna elements may transmit at 2.4 GHz. Therefore, by virtually dividing an array of antenna elements, electronic devices coupled to receivers can continue to receive wireless power transmission. The foregoing may be beneficial because, for example, one set of antenna elements may transmit at about 2.4 GHz and other antenna elements may transmit at 5.8 GHz, and thus, adjusting a number of antenna elements in a given array when working with receivers operating at different frequencies. In this example, the array is divided into equal sets of antenna elements (e.g., four antenna elements), but the array may be divided into sets of different amounts of antenna elements. In an alternative embodiment, each antenna element may alternate between select frequencies.
The efficiency of wireless power transmission as well as the amount of power that can be delivered (using pocket-forming) may be a function of the total number of antenna elements 1006 used in a given receivers and transmitters system. For example, for delivering about one watt at about 15 feet, a receiver may include about 80 antenna elements while a transmitter may include about 256 antenna elements. Another identical wireless power transmission system (about 1 watt at about 15 feet) may include a receiver with about 40 antenna elements, and a transmitter with about 512 antenna elements. Reducing in half the number of antenna elements in a receiver may require doubling the number of antenna elements in a transmitter. In some embodiments, it may be beneficial to put a greater number of antenna elements in transmitters than in a receivers because of cost, because there will be much fewer transmitters than receivers in a system-wide deployment. However, the opposite can be achieved, e.g., by placing more antenna elements on a receiver than on a transmitter as long as there are at least two antenna elements in a transmitter 1002B.
II. Wireless Power Software Management System
A. System and Method for Smart Registration of Wireless Power Receivers in a Wireless Power Network
Wireless power transmitter manager 1102 may transmit controlled RF waves that act as power transmission signals that may converge in 3-d space to a wireless power receiver 1104 for charging or powering a customer device 1106. Although the exemplary embodiment recites the use of RF waves as power transmission signals, the power transmission signals may include any number of alternative or additional techniques for transmitting energy to a wireless power receiver converting the transmitted energy to electrical power. These RF waves may be controlled through phase and/or relative amplitude adjustments to form constructive and destructive interference patterns (pocket-forming). Pockets of energy may form at constructive interference patterns and can be 3-dimensional in shape, whereas null-spaces may be present outside the constructive interference patterns.
Wireless power receiver 1104 may be paired with customer device 1106 or may be built into customer device 1106. Examples of customer devices 1106 may include laptop computer, mobile device, smartphones, tablets, music players, and toys, among other. Wireless power transmitter manager 1102 may receive customer device's signal strength from advertisement emitted by wireless power receiver 1104 for the purpose of detecting if wireless power receiver 1104 is nearer to wireless power transmitter manager 1102 than to any other wireless power transmitter manager 1102 in system 1100.
Customer device 1106 may include a graphical user interface 1112 (GUI). Graphical user interface 1112 (GUI) may receive customer device's signal strength from advertisement emitted by wireless power receiver 1104 for the purpose of detecting if wireless power receiver 1104 is paired with graphical user interface 1112 (GUI).
According to some aspects of this embodiment, wireless power transmitter manager 1102 may include a device database 1116, where device database 1116 may store information about all network devices, such as universally unique identifier (UUID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer device's past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others. Device database 1116 may also stores information about all system devices such as wireless power transmitter managers, wireless power receivers, end user hand-held devices, and servers, among others
Under control of wireless power transmitter manager 1102, wireless power system 1100 may send power in a range up to 30 feet.
Wireless power transmitter manager 1102, with control over wireless power receiver's power record, may allow sending power to a specific wireless power receiver 1104. In one embodiment, wireless power transmitter managers 1102 may need to fulfill two conditions to control wireless power receiver's power record in device database 1116; customer device's signal strength threshold has to be significantly greater than 50% (for example 55%) of the signal strength measured by all other wireless power transmitter managers 1102 and has to remain significantly greater than 50% for a minimum amount of time.
Wireless power transmitter manager 1102 may use, but is not limited to, Bluetooth low energy (BLE) to establish a communication link 1108 with wireless power receiver 1104 and a control link 1110 with customer device's graphical user interface (GUI). Wireless power transmitter manager 1102 may use control link 1110 to receive commands from and receive pairing information from customer device's graphical user interface (GUI).
Wireless power transmitter manager 1102 may include antenna manager software 1114 to track customer device 1106. Antenna manager software 1114 may use real time telemetry to read the state of the power received in customer device 1106.
Wireless power transmitter manager 1102 may create a wireless energy area model which includes information about all the movements in the system. This information may be stored in device database 1116.
In other situations, there can be multiple wireless power transmitter managers 2902 and/or multiple wireless power receivers 1104 for powering multiple and various customer devices 1106.
In a wireless power network, one or more wireless power transmitter managers and/or one or more wireless power receivers may be used for powering various customer devices.
Each wireless power device in the wireless power network may include a universally unique identifier (UUID). Examples of wireless power devices may include wireless power transmitter manager, wireless power receiver, end user hand-held or mobile devices, and servers, among others.
A wireless power transmitter manager 1202 may include a processor with computer-readable medium, such as a random access memory (RAM) (not shown) coupled to the processor. Examples of processor may include a microprocessor, an application specific integrated circuit (ASIC), and a field programmable object array (FPOA), among others.
According to some aspects of this embodiment, each wireless power device bought by a customer may be registered at the time of purchase, or registered later by the customer using public accessible web page or smart device application that communicates to energy domain service 1214. The device may registered with the wireless power network, via a registry stored in an energy domain service 1214.
Energy domain service 1214 may be one or more cloud-based servers and each cloud-based servers may include a database that may store a registry for each wireless power device purchased by a customer. Cloud-based servers may be implemented through known in the art database management systems (DBMS) such as, for example, MySQL, PostgreSQL, SQLite, Microsoft SQL Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice Base, FileMaker Pro and/or any other type of database that may organize collections of data. The registry may include customer's name, customer's credit card, Pay Pal account, or any other method of payment, address, and wireless power device UUID, among others. The registry may indicate whether wireless power transmitter manager 1202 is for business, commercial, municipal, government, military, or home use. The registry may also include different access policies for each wireless power transmitter manager 1202, depending on it use, for example if wireless power transmitter manager 1202 will be for businesses use, the customer may need to define whether the power transfer will be charged or not.
In a different aspect of this embodiment, a wireless power receiver 1204 may include a nonvolatile memory for storing wireless power transmitter manager 1202 universally unique identifier (UUID). Examples of nonvolatile memory may include read-only memory, flash memory, ferroelectric RAM (F-RAM) hard disks, floppy disks, and optical discs, among others. Wireless power receiver 1204 may be paired with customer device 1206 or may be built into customer device 1206. Examples of customer devices 1206 may include laptop computer, mobile device, smartphone, tablet, music player, and toys, among other. Customer device 1206 may include a graphical user interface 1208 (GUI) as part of wireless power system software downloaded and installed from public application store.
According to some aspects of this embodiment, wireless power transmitter manager 1202 may include a device database 1210, where device database 1210 may store information about all network devices such as universally unique identifier (UUID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer device's past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others.
Wireless power transmitter manager 1202 may send power in a range up to 30 feet.
According to some aspects of this embodiment, wireless power transmitter manager 1202 may detect customer device's signal strength from advertisement emitted graphical user interface 1208 (GUI) for the purpose of detecting if wireless power receiver 1204 is paired with graphical user interface 1208 (GUI). Wireless power transmitter manager 1202 may also detect if wireless power receiver 1204 is nearer to wireless power transmitter manager 1202 than to any other wireless power transmitter manager 1202 in the wireless power network through an analysis of each device database records in the wireless power system 1200. Each record may include a list of each wireless power receiver 1204 and its signal strength relative to and detected by wireless power transmitter manager 1202. Then wireless power receiver 1204 may be assigned to wireless power transmitter manager 1202, which may have exclusive control and authority to change the wireless power receiver's record in distributed system device database 1210 until wireless power receiver 1204 moves to a new location closer to another wireless power transmitter manager 1202. If wireless power receiver 1204 change to new location closer to another wireless power transmitter manager 1202, then wireless power transmitter manager 1202 (with control over wireless power receiver 1204) may update wireless power receiver's record with its UUID.
If wireless power receiver 1204 tries to charge using wireless power transmitter manager 1202, then wireless power transmitter manager 1202 may verify with energy domain service 1214 if it is authorized to send power to wireless power receiver 1204. Therefore wireless power transmitter manager 1202 may establish a communication connection with wireless power receiver 1204 to request its universally unique identifier (UUID). Wireless power receiver 1204 may send UUID to wireless power transmitter manager 1202. Wireless power transmitter manager 1202 may establish communication connection with energy domain service 1214 and then send its UUID and wireless power receiver 1204 UUID to energy domain service 1214 through an internet cloud 1212, where internet cloud 1212 may be any suitable connections between computers such as, for example, intranets, local area networks (LAN), virtual private networks (VPN), wide area networks (WAN) and the internet among others. Once energy domain service 1214 receives wireless power transmitter UUID and wireless power receiver 1204 UUID, it may inspect the registry for wireless power transmitter manager 1202 using UUID. Registry may include access policy for wireless power transmitter manager 1202. Energy domain service 1214 may determine through the access policy whether wireless power transmitter manager 1202 needs to pay to receive power. If wireless power transmitter manager 1202 access policy states that wireless power receiver 1204 with UUID needs to pay to receive power, energy domain service 1214 may verify whether a credit card, Pay Pal, or other payment method, may be denoted within wireless power receiver 1204 registry. If a payment method is associated with wireless power receiver 1204, energy domain service 1214 may send a message to wireless power transmitter manager 1202 authorizing the power transfer to wireless power receiver 1204. Wireless power transmitter manager 1202 may report energy consumption statistics to energy domain service 1214 for subsequent billing of wireless power receiver's owner. Energy consumption statistics may be stored in device database 1210 and also may be sent to energy domain service 1214 and saved in wireless power receiver's registry.
If no payment method is associated with wireless power receiver 1204, energy domain service 1214 may send a message to wireless power transmitter manager 1202 denying the power transfer to wireless power receiver 1204.
In the case wireless power transmitter manager 1202 access policy states that no charge will be applied to certain wireless power receivers 1204, then energy domain service 1214 may confirm if wireless power receiver 1204 is allowed to receive power from wireless power transmitter manager 1202. If wireless power receiver 1204 is allowed to receive power from wireless power transmitter manager 1202, then, energy domain service 1214 may send a message to wireless power transmitter manager 1202 authorizing the power transfer to wireless power receiver 1204. Otherwise energy domain service 1214 may send a message to wireless power transmitter manager 1202 denying the power transfer to wireless power receiver 1204.
According to some aspect of this embodiment, a customer, may be able to select through a GUI device, which wireless power receivers 1204 may receive charge from wireless power transmitter manager 1202. In the GUI device, customer may be able to visualize each wireless power receiver 1204 near wireless power transmitter manager 1202, then, customer may select which wireless power receivers 1204 are allowed to receive charge from wireless power transmitter manager 1202. This information may be stored in device database 1210 and also may be sent to energy domain service 1214.
In a different aspect of this embodiment, a proprietor or clerk of a commercial or retail business establishment that owns a wireless power system may be able to select through the GUI device a wireless power receiver 1204 to receive power from one or more wireless power transmitter managers 1202 within power range of wireless power receiver 1204. The customer may be provided with a pre-authorized wireless power receiver 1204 at business establishment by proprietor or clerk. The wireless power receiver 1204 may be attached to customer's device. The proprietor or clerks may specify to GUI device the customer's method of payment (credit card, Pay Pal, cash, among others.). Immediately the wireless power transmitter manager 1202 that belong to business establishment may start sending power to the customer device that is attached to pre-authorized wireless power receiver 1204. Customer may be billed on behalf of business establishment for power provided. Also in the GUI device, proprietor or clerk may be able to visualize power received by wireless power receiver 1204 and the amount to bill for power received. This information may be stored in distributed system device database 1210 and also may be sent to energy domain service 1214.
In a wireless power network, one or more wireless power transmitter managers and/or one or more wireless power receivers may be used for powering various customer devices. Each wireless power device in the wireless power network may include a universally unique identifier (UUID). Examples of wireless power devices may include wireless power transmitter manager, wireless power receiver, end user hand-held or mobile devices and servers, among others.
The method may start at step 1302 when a wireless power transmitter manager detects a customer device. Customer device may be paired with wireless power receiver or wireless power receiver may be built in a customer device. Example of customer devices may include smartphones, mobile device, tablets, music players, toys and others at the same time. Customer device may include a graphical user interface (GUI) as part of wireless power system software downloaded and installed from public application store.
Wireless power transmitter manager may detect customer device's signal strength from advertisement emitted graphical user interface (GUI) for the purpose of detecting if wireless power receiver is paired with graphical user interface (GUI). Wireless power transmitter manager may also detect if wireless power receiver is nearer to wireless power transmitter manager than to any other wireless power transmitter manager in the wireless power network through an analysis of each device database records in the wireless power system. Each record may include a list of each wireless power receiver and its signal strength relative to and detected by wireless power transmitter manager. Then wireless power receiver may be assigned to wireless power transmitter manager, which may have exclusive control and authority to change the wireless power receiver's record in distributed system device database until wireless power receiver moves to a new location closer to another wireless power transmitter manager.
According to some aspects of this embodiment, Device database may store information about all network devices such as universally unique identifier (UUID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer device's past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others.
Wireless power transmitter manager may establish a communication connection with wireless power receiver indicating is within range to receive charge. Wireless power transmitter manager may send power in a range up to 30 feet.
If wireless power receiver tries to obtain charge from wireless power transmitter manager, wireless power transmitter manager may verify with energy domain service if it is authorized to send power to wireless power receiver. Therefore wireless power transmitter may establish a communication connection with wireless power receiver to request universally unique identifier (UUID). Wireless power receiver may send UUID to wireless power transmitter manager. Wireless power transmitter manager may read wireless power receiver UUID, at step 1904.
Energy domain service may be one or more cloud-based servers and each cloud-based servers may include a database that may store a registry for each wireless power device purchased by a customer. Cloud-based servers may be implemented through known in the art database management systems (DBMS) such as, for example, MySQL, PostgreSQL, SQLite, Microsoft SQL Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice Base, FileMaker Pro and/or any other type of database that may organize collections of data. The registry may include customer's name, customer's credit card, address, and wireless power device UUID, among others. The registry may indicate whether wireless power transmitter manager is for business, commercial, municipal, government, military, or home use. The registry may also include different access policies for each wireless power transmitter manager, depending on it use, for example if wireless power transmitter manager will be for businesses use, the customer may need to define whether the power transfer will be charged or not.
According to some aspects of this embodiment, each wireless power device bought by a customer may be registered at the time of purchase, or registered later by the customer using public accessible web page or smart device application that communicates to energy domain service.
Wireless power transmitter manager may send its UUID and also wireless power receiver UUID to an energy domain service through the internet cloud, at step 1306. Internet cloud may be any suitable connections between computers such as, for example, intranets, local area networks (LAN), virtual private networks (VPN), wide area networks (WAN) and the internet among others.
Energy domain service may inspect the registry for wireless power transmitter manager using UUID, at step 1308. Registry may include access policy for wireless power transmitter manager.
Energy domain service may determine through the access policy whether wireless power transmitter manager needs to pay to receive power, at step 1310.
If wireless power transmitter manager access policy states that wireless power receiver with UUID needs to pay to receive power, energy domain service may verify whether a credit card, Pay Pal, or other payment method, may be denoted within wireless power receiver registry, at step 1312.
If a payment method is associated with wireless power receiver registry, energy domain service may send a message to wireless power transmitter manager authorizing the power transfer to wireless power receiver, at step 1314.
Wireless power transmitter manager may report energy consumption statistics to energy domain service for subsequent billing of wireless power receiver's owner, at step 1316. Energy consumption statistics may be stored in device database and also may be sent to energy domain service and saved in wireless power receiver's registry.
In the case no payment method is associated with wireless power receiver, energy domain service may send a message to wireless power transmitter manager denying the power transfer to wireless power receiver, at step 1318.
Else, if wireless power transmitter manager access policy states that no charge will be applied to a certain wireless power receiver which may be trying to obtain power from wireless power transmitter manager, energy domain service may confirm whether wireless power receiver is allowed to receive power from wireless power transmitter manager, at step 1320.
If wireless power receiver is allowed to receive power from wireless power transmitter manager. Energy domain service may send a message to wireless power transmitter manager authorizing the power transfer to wireless power receiver, at step 1314.
Wireless power transmitter manager may report energy consumption statistics to energy domain service, at step 1316. Energy consumption statistics may be stored in device database and also may be sent to energy domain service and saved in wireless power receiver's registry.
Otherwise if wireless power receiver is not allowed to receive power from the wireless power transmitter, energy domain service may send a message to wireless power transmitter manager denying the power transfer to wireless power receiver, at step 1322.
According to some aspect of this embodiment, a customer may be able to select through a GUI device which wireless power receivers may receive charge from wireless power transmitter manager. In the GUI device, customer may be able to visualize each wireless power receiver near to wireless power transmitter manager, then customer may select which wireless power receivers are allowed to receive charge from wireless power transmitter manager. This information may be stored in device database and also may be sent to energy domain service.
ExamplesExample #1 is a wireless power network with components similar to those described in
Example #2 is a wireless power network with components similar to those described in
III. Managing Power Transfer from Multiple Transmitters
A. System and Method for Controlling Communication Between Wireless Power Transmitter Managers
In a wireless power transmission system, multiple wireless power transmitter managers and/or multiple wireless power receivers may be used for powering various customer devices 1402. A wireless power receiver 1404 may be paired with customer device 1402 or may be built into customer device 1402. Example of customer devices 1402 may include smartphones, tablets, music players, toys and others at the same time. Customer device 1402 may include a graphical user interface (GUI)
Each wireless power transmitter manager in the wireless power transmission system may receive customer device's signal strength from ads emitted by wireless power receiver 1404 and graphical user interface (GUI).
Each wireless power transmitter manager in the wireless power transmission system may include a device database 1410. Device database 1410 may store customer device's power schedules, customer device's status, names, customer's sign names, and details running the system, among others, for each customer device 1402 in the wireless power transmission system near to a wireless power transmitter manager. Device database 1410 may also stores information about all system devices such as wireless power transmitter managers, wireless power receivers, end user hand-held devices, and servers, among others.
A Wi-Fi connection 1412 may be established between a wireless power transmitter manager one 1406 and a wireless power transmitter manager two 1408 to share between system devices: device database's power records, quality control information, statistics, and problem reports, among others
Each wireless power transmitter manager may create a wireless energy area model which includes information about all the movements in the system. Also this information may be stored at device database 1410. Wireless energy area model may be used in transmitter communications transitions, i.e. in transitioning communications and power transfer from wireless power transmitter manager one 1406 to wireless power transmitter manager two 1408. For example if a customer device 1402 moves away from wireless power transmitter manager one 1406 and nearer to wireless power transmitter manager two 1408, this movement may be registered in the wireless energy area model.
In another aspect of this embodiment, wireless power transmitter managers may transfer power in a range between 175 feet to 30 feet, but only wireless power transmitter manager with control over wireless power receiver's power record, may be allowed sending power to a specific wireless power receiver. Furthermore wireless power transmitter managers may share wireless power receiver's power record, but only the wireless power transmitter manager, with control over wireless power receiver's power record, can change the information stored for that power record in the device database 1410.
According to some aspects of this embodiment, wireless power transmitter managers may need to fulfill two conditions to control power transfer over a customer device; customer device's signal strength threshold has to be significantly greater than a predetermined percentage of the signal strength measured by all the other wireless power transmitter managers for a minimum amount of time, where the predetermined percentage is generally well above 1700%. For example, in the case of a predetermined percentage of 400%, the signal strength threshold has to be greater than 405%. If multiple wireless power transmitter managers are within range to communicate with and transfer power to a given wireless power receiver, then only the closest wireless power transmitter manager or the last wireless power transmitter manager closest to wireless power receiver, has control of the wireless power receiver's power record in device database 1410, however each wireless power transmitter manager may individually and simultaneously transfer power to the power record. In this case, communication with the wireless power receiver is time-phased (shared) between the multiple wireless power transmitter managers so that each can track the 3-D location of the wireless power receiver, in case it is in movement.
In another aspect of this embodiment, wireless power transmitter manager one 1406 and wireless power transmitter manager two 1408 may share customer device's information through a cloud 1414. Both wireless power transmitter managers may be connected to cloud 1414 through network connections (not shown in
According to some aspects of this embodiment, a server 1416 may be connected to cloud 1414 as a backup of device database 1410 shared by every wireless power transmitter manager in the wireless power transmission system.
In a wireless power transmission system with two wireless power transmitter managers the process may start when a wireless power receiver moves away from a wireless power transmitter manager and nearer to another, at step 1502. A customer device may be paired with the wireless power receiver. Example of customer devices may include smartphones, tablets, music players, and toys, among others. Customer device may include a graphical user interface (GUI).
Wireless power transmitter managers may receive customer device's signal strength from ads emitted by wireless power receiver and graphical user interface (GUI).
Subsequently, both wireless power transmitter managers may update a device database with the customer device's signal strength measured by each transmitter manager, at step 1504.
Each wireless power transmitter manager in the wireless power transmission system may include a device database. Device database may store customer device's power schedules, customer device's status, names, customer's sign names, and details running the system, among others, for each customer device in the power transmission system near to a given wireless power transmitter manager. Device database also may store information about all system devices such as wireless power transmitter managers, wireless power receivers, end user hand-held devices, and servers, among others.
According to some aspects of this embodiment, only the wireless power transmitter manager with control over wireless power receiver's power record, may be allowed sending power to a specific wireless power receiver. Also wireless power transmitter managers in the system may share wireless power receiver's power records but only the wireless power transmitter manager with control over wireless power receiver's power record, can change the information stored for that power record in the device database.
Both wireless power transmitter managers may decide which one of them first receives the strongest signal strength from customer device, at step 1506.
According to some aspects of this embodiment, wireless power transmitter managers may need to fulfill two conditions to control power transfer over a customer device; customer device's signal strength threshold has to be significantly greater than a predetermined percentage of the signal strength measured by all the other wireless power transmitter managers for a minimum amount of time, where the predetermined percentage is generally well above 1700%. For example, in the case of a predetermined percentage of 400%, the signal strength threshold has to be greater than 405%. If multiple wireless power transmitter managers are within range to communicate with and transfer power to a given wireless power receiver, then only the closest wireless power transmitter manager or the last wireless power transmitter manager closest to wireless power receiver, has control of the wireless power receiver's power record in the device database, however each wireless power transmitter manager may individually and simultaneously transfer power to the power record. In this case, communication with the wireless power receiver is time-phased (shared) between the multiple wireless power transmitter managers so that each can track the 3-D location of the wireless power receiver, in case it is in movement.
The wireless power transmitter manager that first receives the strongest signal strength from customer device, it may verify if the signal strength of customer device has been significantly greater than predetermined percentage (for example greater than 405%, for a predetermined percentage of 400%) for a minimum amount of time, at step 1508.
The wireless power transmitter manager that first receives the strongest signal strength from customer device for a minimum amount of time may take control of wireless power receiver's power records and power transfer, at step 1510.
In a wireless power transmission system 1608, multiple wireless power transmitter managers and/or multiple wireless power receivers may be used for powering various customer devices.
As an exemplary embodiment 1600, two wireless power transmitter managers may be in different rooms. Wireless power transmitter manager one 1602 may be located in room B and wireless power transmitter manager two 1604 may be located in room A. Room A and B may be next to each other.
Wireless power receiver 1606 may be located in room B and may receive power transfer from wireless power transmitter manager one 1602. A customer device may be paired with a wireless power receiver 1606. Example of customer devices may include smartphones, tablets, music players, toys and others at the same time. Customer device may include a graphical user interface (GUI).
Each wireless power transmitter manager near to customer device may receive customer device's signal strength from ads emitted by wireless power receiver 1606 and graphical user interface (GUI).
Each wireless power transmitter manager in the power transmission system 1608 may have a device database. Device database may store customer device's power schedules, customer device's status, names, customer sign names, and details running the system, among others, for each customer device in the power transmission system 1608 near to any wireless power transmitter manager. Device database also may store information about all system devices such as wireless power transmitter managers, wireless power receivers, end user hand-held devices, and servers, among others.
Each wireless power transmitter manager may create a wireless energy area model which includes information about all the movements in the system. This information may be used to effect a transmitter communications transition involving control of power transfer from wireless power transmitter manager one 1602 to wireless power transmitter manager two 1604. Wireless energy area model may be stored in the corresponding device database for each wireless power transmitter manager.
If wireless power receiver 1606 starts moving from room B to room A, wireless power transmitter manager one 1602 may take control over power transfer for wireless power receiver 1606 and wireless power transmitter's power records if customer device's signal strength threshold is significantly greater than 400% of the signal strength measured by all other wireless power transmitter managers. For example if wireless power transmitter manager one 1602 receives 23B0% signal strength from customer device, wireless power transmitter manager one 1602 may still have control over power transfer and wireless power receiver's power records
If wireless power receiver 1606 continues moving toward room A, but wireless power transmitter manager one 1602 receives 410% signal strength from customer device, wireless power transmitter manager one 1602 may still have control over power transfer and wireless power receiver's power records.
Wireless power receiver 1606 may move until mid-way between room A and room B. If wireless power transmitter manager one 1602 and wireless power transmitter manager two 1604 receives 400% signal strength from customer device, wireless power transmitter manager one 1602 may still have control over power transfer and wireless power receiver's power records.
Wireless power receiver 1606 continues moving towards room A. If wireless power transmitter manager one 1602 may receive 40% or 45% signal strength from customer device and wireless power transmitter manager two 1604 may receive 405% or 410% signal strength from customer device for a minimum amount of time, wireless power transmitter manager one 1602 may effect a transmitter communications transition, transferring control of power transfer, and may provide wireless power receiver's power record to wireless power transmitter manager two 1604. Wireless power transmitter manager two 1604 may take control over power transfer and wireless receiver power's power record.
If wireless power receiver 1606 moves back from room A to room B, wireless power transmitter manager two 1604 may have control over power transfer for wireless power receiver 1606 until signal strength drops to 45% or less for a minimum amount of time. Wireless power transmitter manager one 1602 may take control over power transfer until customer device's signal strength reaches 405% or more for a minimum amount of time.
ExamplesExample #1 is an application of the system described in
B. Cluster Management of Transmitters
The wireless power management system provides cluster management of a plurality or cluster of transmitters at a location, facilitating the transfer of power from two or more transmitters in the cluster of transmitters to a power receiver. In cluster management of a plurality of transmitters, transmitter communications transition refers to transition of communications with a wireless power receiver between one wireless power transmitter to another wireless power transmitter in the plurality or cluster of transmitters. The communications involved in a transmitter communications transition may include one or more of one way communications, two way communications, and wireless transfer of power. In one embodiment, transmitter communications transition refers specifically to a transition of communications with a wireless power receiver, between one wireless power transmitter manager to another wireless power transmitter manager of the plurality or cluster of transmitters. In an embodiment, transmitter communications transitions occur as a mobile device associated with a power receiver moves to, from, or within the transmitter cluster location.
In an exemplary transmitter and receiver embodiment, a receiver is embedded in or otherwise joined to a device such as a mobile phone. In the embodiment described below, status communications between transmitter and receiver are hosted using the Bluetooth Low Energy (BLE) wireless communications protocol. BLE is exemplary of a broad range of wireless communications protocols that are capable of hosting status communications between the transmitters and receivers (for example, Wi-Fi (IEEE 23A02.11), Near Field Communication (NFC), radio frequency identification (RFID), iBeacon), and the present transmitter cluster management method is not limited to a particular status communication protocol. The transmitter and receiver each has a Bluetooth low energy (BLE) processor. In use, the transmitter's BLE processor scans for Bluetooth devices. When the receiver's Bluetooth processor powers up, it begins advertising that it is a Bluetooth device. The advertisement includes a unique identifier so that when the transmitter scans the advertisement, it will distinguish that receiver's advertisement from all other Bluetooth devices in range. In response to this identification, the transmitter immediately forms a communication connection with the receiver and will command the receiver.
After forming the BLE communication connection between transmitter and receiver, the transmitter commences sending power transfer signals to the receiver (for example, at a rate of 3400 times a second), and the receiver sends voltage sample measurements back to the transmitter. The transmitter analyzes these voltage measurements while varying the configuration of the transmitter antennas in phase and gain, until achieving a maximum voltage level. At this level, there is maximum energy in the pocket around the receiver. The wireless power transfer management system continually receives status and usage data from the transmitter, and through the transmitter, obtains status and usage information from the receiver), as with all other transmitters and receivers in the system. For example, as applied to energy harvest, the receiver communicates the updated energy harvest value to the transmitter, once a second. The transmitter accumulates data such as energy harvest values from the receiver, and from any other receiver with which it communicates. Periodically, the transmitter uploads accumulated energy information to the wireless power management system.
The present transmitter cluster management method addresses situations in which a plurality or cluster of transmitters provides power to a given receiver at a location using pocket-forming. Two or more transmitters each may execute a procedure for pocket-forming at the given receiver, as multiple pockets formed at the receiver by the two or more transmitters generally would improve power transfer efficiency or control for that receiver.
In transferring power to a given receiver with a plurality of transmitters, each transmitter will execute the same general communication procedure that applies to power transfers between a single transmitter and receiver. After forming a BLE communication connection between the respective transmitter and receiver, the transmitter begins sending power transfer signals to the receiver (e.g. 3400 times a second), and the receiver sends voltage sample measurements back to the transmitter. Each of the plurality of transmitters would analyze these voltage measurements while varying the configuration of the transmitter antennas in phase and gain, until achieving a maximum voltage level. At this level, there is maximum energy in the pocket formed by that respective transmitter around the receiver. Each transmitter that is executing power transfers to the receiver will periodically communicate accumulated energy information for the receiver, and other status and usage information, to the wireless power management system.
In one embodiment, the available transmitters TX will include any transmitter within the cluster capable of transferring power to receiver RX, including the transmitter of step 1701 and any other TX within range of the receiver as reported to the management system. One or more wireless power transmitters may automatically transmit power to any single wireless power receiver that is close enough for it to establish a communication connection using a suitable communication technology, including Bluetooth Low Energy or the like. The wireless power receiver may then power or charge an electrically connected client device.
However this may not be the case at some locations with a cluster of transmitters. The system can be configured by the wireless power management system to transmit power only to specific wireless power receivers depending on specific system criteria or conditions, such as the time or hour of the day for automatic time-based scheduled power transmission, wireless power receiver physical location, owner of client device, or other suitable conditions and/or criteria. For example, a transmitter TX of the cluster of transmitters may be dedicated to powering one or more device of a particular user, wherein other devices and receivers are not authorized to receive power from that transmitter. In the following discussion, references to available transmitters or to transmitters available to a given receiver mean transmitters that are within power transfer range of that receiver, and that can be used to transfer power to that receiver based upon all other considerations, such as any limitation on transmitter use in specific system criteria or conditions recorded in the wireless power management system.
At step 1705, it is assumed that two or more transmitters TX are available to transfer power to receiver RX. At this step, the two or more transmitters coordinate communications with receiver RX in an embodiment (such as Bluetooth® communications) in which only one transmitter TX can communicate with receiver RX at a time. In one embodiment as explained below, communications are coordinated by one of the two or more transmitters which is selected as a master transmitter. At step 1707, the available transmitters TX transfer power to receiver RX, subject to the coordination of communications at step 1705. At step 1709, the management system detects a transmitter communications transition within the cluster of transmitters that are in communication with receiver RX. This transmitter communications transition may involve one of the available transmitters ceasing its communications with receiver RX (e.g. due to receiver RX moving out of range of that transmitter); a new transmitter TX establishing communications with receiver RX; or a combination of these occurrences. Typically in this event, unless the transmitter communications transition entails the end of all connections of receiver RX with transmitters in the cluster, the power transfer management system and the transmitter(s) available after the transition will repeat steps 1703 through 1709 of this cluster management method.
When multiple wireless power transmitters are executing power transfers to a single receiver using BLE communications between transmitters and receiver, one or more wireless power transmitter managers embedded in the wireless power transmitters coordinate communications between the respective transmitters and the receiver. Bluetooth protocols only permit one communication connection at a time between the wireless power receiver and the multiple wireless power transmitters. Wireless power manager application software within the wireless power transmitter managers may carry out a routine, as a set of instructions and/or algorithm, for coordinating communication between communication managers of the multiple wireless power transmitters (wireless power transmitter cluster). This routine coordinates contemporaneous communications of the respective wireless power transmitters with the power receiver. As used in this description of cluster management of wireless power transmitters, contemporaneous means that at least two wireless power transmitters communicate with a power receiver during the same general period of time, but it does not mean that more than one wireless power transmitter communicate with the power receiver at exactly the same time. In an embodiment, the routine carried out by the wireless power manager application employs time division multiplexing (TDM) of contemporaneous communications between at least two wireless power transmitters and the power receiver.
In one embodiment involving a centralized control method, the wireless power management system selects one of the transmitters as a master transmitter. The master transmitter controls the order and timing of communications with the receiver among the plurality of transmitters that are executing power transfers to the receiver. Alternative methods for coordinating communications also are possible besides this centralized control method, such as methods involving decentralized control among the plurality of transmitters.
In a system 1902 illustrated in
When transmitters TX1 1904, TX2 1906, TX3 1908 power up, each of the transmitters begins regularly to broadcast across the network a message including its IP address and other information identifying the transmitter. Each transmitter in the network has access to broadcasts of the other transmitters, and each transmitter builds a list of all transmitters of the network, including identification of one of the transmitters as master transmitter. In a first embodiment of centralized control, the system identifies as master transmitter the transmitter with the lowest IP number, here shown as TX3 with IP address 192.168.000.3. Within the general approach of centralized control of transmitter-receiver communications by a master transmitter, other algorithms besides lowest IP number can be used to determine the master transmitter.
The system repeats this procedure regularly, so that if master transmitter TX3 went off line, the remaining transmitters would recalculate and assign one of the remaining transmitters as master. If the other transmitters did not see a UDP broadcast message from the master transmitter within a set period of time (e.g., 15 seconds), these remaining transmitters would recalculate the list of available transmitters and would assign one of the remaining transmitters as master based upon the applicable algorithm (in this embodiment, lowest IP number).
Receiver RX1 1916 periodically broadcasts Bluetooth advertisements as the device with receiver approaches location 2024 (seen in
During a period following time T5, all three transmitters TX1, TX2, and TX3 are available to transfer power to receiver RX1, subject to coordination of communications of the three transmitters with receiver RX1 by the master transmitter TX3 (step 1705 in the method of
At time T6, receiver RX3 has left the range of transmitter TX3, while remaining within the range of transmitters TX1 and TX2. During the period in which a transmitter has been authorized to transmit power to an identified receiver, among other data the transmitter communicates to management system 1920, are data on the signal strength of its communications with the receiver, so that by time T6 management system 1920 detects that transmitter TX3 is out of range for receiver RX1 (step 1709 in the method of
In addition to tracking which transmitters are within range of a given receiver, the management system 1920 can limit the power output to given receivers and devices, e.g. based upon safety concerns. Various mobile phones have maximum DC power levels at or just under 4.0 watts (e.g., 3.96, 3.97, 3.98 or 3.99 watts). In the event of a transmitter cluster management transition, i.e. a change to the set of transmitters in communication with a given receiver, management system 1920 can send a message to the master transmitter to ensure compliance with any applicable maximum power level. This message would instruct available transmitters to limit power transfer from individual transmitters among the cluster of transmitters, thereby to ensure safe power transfers from each transmitter.
The foregoing discussion describes controlling cluster management of transmitters through the interaction of a cluster of transmitters with a wireless power management system, preferably a cloud computing management system with networked remote servers are networked for centralized data storage and online access to data management services. In an alternative embodiment, the cluster of transmitters achieves transmitter cluster management under the control of the transmitters themselves, without oversight by a wireless power management system. This is possible since the transmitters themselves can replicate most of the management information and functionality used by the wireless power management system in transmitter cluster management.
The transmitter cluster management scheme discussed above involves hierarchical management of all transmitters at given locations, sometimes herein called a transmitter cluster, in controlling power transfer by the transmitters to a receiver at that location. Other transmitter cluster management schemes are possible, which may manage transmitter-receiver connections at any level of a hierarchical structure. For example, the management system may define a given transmitter cluster as a subset of all transmitters at a location, and manage receiver interactions only with these transmitters separate from other transmitters at the location. Furthermore, the transmitter cluster management scheme may manage transmitter-receiver power transfers and communications across multiple, neighboring locations. For example, two neighboring households each may have two transmitters, which may be organized into one or two clusters managed by the cloud based power transfer management system. The system could manage neighboring locations as clusters, so all four transmitters would be part of one cluster; or, the system could manage each billing address as a separate cluster, so there would be two clusters each with two transmitters.
While various aspects and embodiments have been disclosed, other aspects and embodiments are contemplated. The various aspects and embodiments disclosed are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
The foregoing method descriptions and the interface configuration are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the steps in the foregoing embodiments may be performed in any order. Words such as “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.
The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed here may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description here.
When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed here may be embodied in a processor-executable software module which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used here, 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. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.
Claims
1. A system for selecting which power transmitter should deliver wireless power to a device in a wireless power delivery network, the system comprising:
- a plurality of power transmitters, each respective power transmitter communicatively coupled to a respective transmitter manager, the plurality of power transmitters including: a first power transmitter communicatively coupled to a first transmitter manager that is configured to detect, based on communication signals received from a wireless power receiver, a first signal strength level associated with the wireless power receiver and; a second power transmitter communicatively coupled to a second transmitter manager that is configured to detect, based on communication signals received from the wireless power receiver, a second signal strength level associated with the wireless power receiver;
- wherein: when the first signal strength level is greater than the second signal strength level, the first transmitter manager instructs the first power transmitter to transmit radio frequency (RF) power waves to the wireless power receiver; and when the second signal strength level is greater than the first signal strength level, the second transmitter manager instructs the second power transmitter to transmit RF power waves to the wireless power receiver; the wireless power receiver is configured to convert energy from the RF powers waves into usable power for charging the wireless power receiver or a device that is coupled with the wireless power receiver.
2. The system of claim 1, wherein the wireless power receiver is less than 30 feet away from the first and second power transmitters.
3. The system of claim 1, further comprising at least one database configured for storing information related to the device, the information selected from the group consisting of charging history, charging schedules, charging status, device ID, and combinations thereof.
4. The system of claim 3, wherein each respective transmitter manager provides the information related to the device to a respective power transmitter that is communicatively coupled thereto.
5. The system of claim 1, wherein each respective transmitter manager communicates with the wireless power receiver via a protocol selected from the group consisting of Bluetooth, Bluetooth Low Energy, Wi-Fi, NFC, ZigBee, and combinations thereof.
6. The system of claim 1, wherein each respective transmitter manager communicably delivers to at least one remote server information related to performance of the plurality of power transmitters, performance of the wireless power receiver, or information related to the device.
7. The system of claim 1, wherein:
- when the first signal strength level is greater than the second signal strength level, the first signal strength level is also greater than a signal strength threshold and the first power transmitter is the only power transmitter of the plurality of power transmitters that is transmitting RF waves to the wireless power receiver, and
- when the second signal strength level is greater than the first signal strength level, the second signal strength level is also greater than the signal strength threshold and the second power transmitter is the only power transmitter of the plurality of power transmitters that is transmitting RF waves to the wireless power receiver.
8. The system of claim 7, wherein the signal strength threshold corresponds to a signal strength level that is 40% or greater of a maximum signal transmission capability of the wireless power receiver.
9. The system of claim 1, wherein the first and second transmitter managers are configured to:
- compare the first and second signal strength levels; and
- determine (i) when the first signal strength level is greater than the second signal strength and (ii) when the second signal strength level is greater than the first signal strength level.
10. The system of claim 1, wherein:
- the first power transmitter is located in a first physical room, and the second power transmitter is located in a second physical room that is distinct from the first physical room.
11. The system of claim 1, wherein:
- when the first signal strength level is greater than the second signal strength level, the wireless power receiver is located in the first physical room, and
- when the second signal strength level is greater than the first signal strength level, the wireless power receiver is located in the second physical room.
12. The system of claim 1, wherein the wireless power receiver is integrated with the device.
13. The system of claim 1, wherein the first transmitter manager and the second transmitter manager are a same transmitter manager.
14. A method for selecting which power transmitter should deliver wireless power to a device in a wireless power delivery network, the method comprising:
- at a system comprising a plurality of power transmitters, each respective power transmitter communicatively coupled to a respective transmitter manager, the plurality of power transmitters including a first power transmitter communicatively coupled to a first transmitter manager and a second power transmitter communicatively coupled to a second transmitter manager:
- detecting by the first transmitter manager, based on communication signals received from a wireless power receiver, a first signal strength level associated with the wireless power receiver;
- detecting by the second transmitter manager, based on communication signals received from the wireless power receiver, a second signal strength level associated with the wireless power receiver;
- instructing, by the first transmitter manager, the first power transmitter to transmit radio frequency (RF) power waves to the wireless power receiver when the first signal strength level is greater than the second signal strength level; and
- instructing, by the second transmitter manager, the second power transmitter to transmit RF power waves to the wireless power receiver when the second signal strength level is greater than the first signal strength level,
- wherein the wireless power receiver is configured to convert energy from the RF powers waves into usable power for charging the wireless power receiver or a device that is coupled with the wireless power receiver.
15. The method of claim 14, wherein the wireless power receiver is less than 30 feet away from the first and second power transmitters.
16. The method of claim 14, further comprising at least one database configured for storing information related to the device, the information selected from the group consisting of charging history, charging schedules, charging status, device ID, and combinations thereof.
17. The method of claim 16, wherein each respective transmitter manager provides information related to the device to a respective power transmitter that is communicatively coupled thereto.
18. The method of claim 14, wherein:
- when the first signal strength level is greater than the second signal strength level, the first signal strength level is also greater than a signal strength threshold and the first power transmitter is the only power transmitter of the plurality of power transmitters that is transmitting RF waves to the wireless power receiver, and
- when the second signal strength level is greater than the first signal strength level, the second signal strength level is also greater than the signal strength threshold and the second power transmitter is the only power transmitter of the plurality of power transmitters that is transmitting RF waves to the wireless power receiver.
19. The method of claim 18, wherein the signal strength threshold corresponds to a signal strength level that is 40% or greater of a maximum signal transmission capability of the wireless power receiver.
20. The method of claim 14, wherein the first and second transmitter managers are configured to:
- compare the first and second signal strength levels; and
- determine (i) when the first signal strength level is greater than the second signal strength and (ii) when the second signal strength level is greater than the first signal strength level.
21. The method of claim 14, wherein:
- the first power transmitter is located in a first physical room, and
- the second power transmitter is located in a second physical room that is distinct from the first physical room.
22. The method of claim 14, wherein:
- when the first signal strength level is greater than the second signal strength level, the wireless power receiver is located in the first physical room, and
- when the second signal strength level is greater than the first signal strength level, the wireless power receiver is located in the second physical room.
23. The method of claim 14, wherein the wireless power receiver is integrated with the device.
24. The method of claim 14, wherein the first transmitter manager and the second transmitter manager are a same transmitter manager.
25. A non-transitory, computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a plurality of transmitter managers that are each communicatively coupled to a respective transmitter of a plurality of transmitters, the plurality of power transmitters including a first power transmitter communicatively coupled to a first transmitter manager and a second power transmitter communicatively coupled to a second transmitter manager, cause the plurality of transmitter managers to:
- detect by the first transmitter manager, based on communication signals received from a wireless power receiver, a first signal strength level associated with the wireless power receiver;
- detect by the second transmitter manager, based on communication signals received from the wireless power receiver, a second signal strength level associated with the wireless power receiver;
- instruct, by the first transmitter manager, the first power transmitter to transmit radio frequency (RF) power waves to the wireless power receiver when the first signal strength level is greater than the second signal strength level; and
- instruct, by the second transmitter manager, the second power transmitter to transmit RF power waves to the wireless power receiver when the second signal strength level is greater than the first signal strength level,
- wherein the wireless power receiver is configured to convert energy from the RF powers waves into usable power for charging the wireless power receiver or a device that is coupled with the wireless power receiver.
| 787412 | April 1905 | Tesla |
| 3434678 | May 1965 | Brown et al. |
| 3696384 | October 1972 | Lester |
| 3754269 | August 1973 | Clavin |
| 4101895 | July 18, 1978 | Jones, Jr. |
| 4360741 | November 23, 1982 | Fitzsimmons et al. |
| 4944036 | July 24, 1990 | Hyatt |
| 4995010 | February 19, 1991 | Knight |
| 5200759 | April 6, 1993 | McGinnis |
| 5211471 | May 18, 1993 | Rohrs |
| 5548292 | August 20, 1996 | Hirshfield et al. |
| 5556749 | September 17, 1996 | Mitsuhashi et al. |
| 5568088 | October 22, 1996 | Dent et al. |
| 5646633 | July 8, 1997 | Dahlberg |
| 5697063 | December 9, 1997 | Kishigami et al. |
| 5712642 | January 27, 1998 | Hulderman |
| 5936527 | August 10, 1999 | Isaacman et al. |
| 5982139 | November 9, 1999 | Parise |
| 6046708 | April 4, 2000 | MacDonald, Jr. et al. |
| 6127799 | October 3, 2000 | Krishnan |
| 6127942 | October 3, 2000 | Welle |
| 6163296 | December 19, 2000 | Lier et al. |
| 6289237 | September 11, 2001 | Mickle et al. |
| 6329908 | December 11, 2001 | Frecska |
| 6421235 | July 16, 2002 | Ditzik |
| 6437685 | August 20, 2002 | Hanaki |
| 6456253 | September 24, 2002 | Rummeli et al. |
| 6476795 | November 5, 2002 | Derocher et al. |
| 6501414 | December 31, 2002 | Amdt et al. |
| 6583723 | June 24, 2003 | Watanabe et al. |
| 6597897 | July 22, 2003 | Tang |
| 6615074 | September 2, 2003 | Mickle et al. |
| 6664920 | December 16, 2003 | Mott et al. |
| 6798716 | September 28, 2004 | Charych |
| 6803744 | October 12, 2004 | Sabo |
| 6856291 | February 15, 2005 | Mickle et al. |
| 6911945 | June 28, 2005 | Korva |
| 6960968 | November 1, 2005 | Odendaal et al. |
| 6967462 | November 22, 2005 | Landis |
| 6988026 | January 17, 2006 | Breed et al. |
| 7003350 | February 21, 2006 | Denker et al. |
| 7027311 | April 11, 2006 | Vanderelli et al. |
| 7068991 | June 27, 2006 | Parise |
| 7183748 | February 27, 2007 | Unno et al. |
| 7191013 | March 13, 2007 | Miranda et al. |
| 7196663 | March 27, 2007 | Bolzer et al. |
| 7205749 | April 17, 2007 | Hagen et al. |
| 7222356 | May 22, 2007 | Yonezawa et al. |
| 7274334 | September 25, 2007 | o'Riordan et al. |
| 7274336 | September 25, 2007 | Carson |
| 7351975 | April 1, 2008 | Brady et al. |
| 7359730 | April 15, 2008 | Dennis et al. |
| 7392068 | June 24, 2008 | Dayan |
| 7403803 | July 22, 2008 | Mickle et al. |
| 7451839 | November 18, 2008 | Perlman |
| 7463201 | December 9, 2008 | Chiang et al. |
| 7614556 | November 10, 2009 | Overhultz et al. |
| 7639994 | December 29, 2009 | Greene et al. |
| 7643312 | January 5, 2010 | Vanderelli et al. |
| 7652577 | January 26, 2010 | Madhow et al. |
| 7702771 | April 20, 2010 | Ewing et al. |
| 7786419 | August 31, 2010 | Hyde et al. |
| 7812771 | October 12, 2010 | Greene et al. |
| 7830312 | November 9, 2010 | Choudhury et al. |
| 7844306 | November 30, 2010 | Shearer et al. |
| 7868482 | January 11, 2011 | Greene et al. |
| 7898105 | March 1, 2011 | Greene et al. |
| 7904117 | March 8, 2011 | Doan et al. |
| 7925308 | April 12, 2011 | Greene et al. |
| 8055003 | November 8, 2011 | Mittleman et al. |
| 8070595 | December 6, 2011 | Alderucci et al. |
| 8072380 | December 6, 2011 | Crouch |
| 8092301 | January 10, 2012 | Alderucci et al. |
| 8099140 | January 17, 2012 | Arai |
| 8115448 | February 14, 2012 | John |
| 8159090 | April 17, 2012 | Greene et al. |
| 8159364 | April 17, 2012 | Zeine |
| 8180286 | May 15, 2012 | Yamasuge |
| 8228194 | July 24, 2012 | Mickle |
| 8264101 | September 11, 2012 | Hyde et al. |
| 8264291 | September 11, 2012 | Morita |
| 8278784 | October 2, 2012 | Cook et al. |
| 8284101 | October 9, 2012 | Fusco |
| 8310201 | November 13, 2012 | Wright |
| 8362745 | January 29, 2013 | Tinaphong |
| 8380255 | February 19, 2013 | Shearer et al. |
| 8410953 | April 2, 2013 | Zeine |
| 8411963 | April 2, 2013 | Luff |
| 8432062 | April 30, 2013 | Greene et al. |
| 8432071 | April 30, 2013 | Huang et al. |
| 8446248 | May 21, 2013 | Zeine |
| 8447234 | May 21, 2013 | Cook |
| 8451189 | May 28, 2013 | Fluhler |
| 8452235 | May 28, 2013 | Kirby et al. |
| 8457656 | June 4, 2013 | Perkins et al. |
| 8461817 | June 11, 2013 | Martin et al. |
| 8467733 | June 18, 2013 | Leabman |
| 8552597 | October 8, 2013 | Song et al. |
| 8558661 | October 15, 2013 | Zeine |
| 8560026 | October 15, 2013 | Chanterac |
| 8604746 | December 10, 2013 | Lee |
| 8614643 | December 24, 2013 | Leabman |
| 8621245 | December 31, 2013 | Shearer et al. |
| 8626249 | January 7, 2014 | Kuusilinna et al. |
| 8629576 | January 14, 2014 | Levine |
| 8653966 | February 18, 2014 | Rao et al. |
| 8674551 | March 18, 2014 | Low et al. |
| 8686685 | April 1, 2014 | Moshfeghi |
| 8712355 | April 29, 2014 | Black et al. |
| 8712485 | April 29, 2014 | Tam |
| 8718773 | May 6, 2014 | Wills et al. |
| 8729737 | May 20, 2014 | Schatz et al. |
| 8736228 | May 27, 2014 | Freed et al. |
| 8770482 | July 8, 2014 | Ackermann et al. |
| 8772960 | July 8, 2014 | Yoshida |
| 8823319 | September 2, 2014 | Von Novak, III et al. |
| 8854176 | October 7, 2014 | Zeine |
| 8860364 | October 14, 2014 | Low et al. |
| 8897770 | November 25, 2014 | Frolov et al. |
| 8923189 | December 30, 2014 | Leabman |
| 8928544 | January 6, 2015 | Massie et al. |
| 8937408 | January 20, 2015 | Ganem et al. |
| 8946940 | February 3, 2015 | Kim et al. |
| 8963486 | February 24, 2015 | Kirby et al. |
| 8970070 | March 3, 2015 | Sada et al. |
| 8989053 | March 24, 2015 | Skaaksrud et al. |
| 9000616 | April 7, 2015 | Greene et al. |
| 9001622 | April 7, 2015 | Perry |
| 9006934 | April 14, 2015 | Kozakai et al. |
| 9021277 | April 28, 2015 | Shearer et al. |
| 9030161 | May 12, 2015 | Lu et al. |
| 9059598 | June 16, 2015 | Kang et al. |
| 9059599 | June 16, 2015 | Won et al. |
| 9077188 | July 7, 2015 | Moshfeghi |
| 9088216 | July 21, 2015 | Garrity et al. |
| 9124125 | September 1, 2015 | Leabman et al. |
| 9130397 | September 8, 2015 | Leabman et al. |
| 9130602 | September 8, 2015 | Cook |
| 9142998 | September 22, 2015 | Yu et al. |
| 9143000 | September 22, 2015 | Leabman et al. |
| 9143010 | September 22, 2015 | Urano |
| 9178389 | November 3, 2015 | Hwang |
| 9225196 | December 29, 2015 | Huang et al. |
| 9242411 | January 26, 2016 | Kritchman et al. |
| 9244500 | January 26, 2016 | Cain et al. |
| 9252628 | February 2, 2016 | Leabman et al. |
| 9270344 | February 23, 2016 | Rosenberg |
| 9282582 | March 8, 2016 | Dunsbergen et al. |
| 9294840 | March 22, 2016 | Anderson et al. |
| 9297896 | March 29, 2016 | Andrews |
| 9318898 | April 19, 2016 | John |
| 9368020 | June 14, 2016 | Bell et al. |
| 9401977 | July 26, 2016 | Gaw |
| 9444283 | September 13, 2016 | Son et al. |
| 9450449 | September 20, 2016 | Leabman et al. |
| 9461502 | October 4, 2016 | Lee et al. |
| 9520725 | December 13, 2016 | Masaoka et al. |
| 9520748 | December 13, 2016 | Hyde et al. |
| 9522270 | December 20, 2016 | Perryman et al. |
| 9537354 | January 3, 2017 | Bell et al. |
| 9537357 | January 3, 2017 | Leabman |
| 9537358 | January 3, 2017 | Leabman |
| 9538382 | January 3, 2017 | Bell et al. |
| 9544640 | January 10, 2017 | Lau |
| 9559553 | January 31, 2017 | Bae |
| 9564773 | February 7, 2017 | Pogorelik et al. |
| 9590444 | March 7, 2017 | Walley |
| 9620996 | April 11, 2017 | Zeine |
| 20020001307 | January 3, 2002 | Nguyen et al. |
| 20020028655 | March 7, 2002 | Rosener et al. |
| 20020034958 | March 21, 2002 | Oberschmidt et al. |
| 20020054330 | May 9, 2002 | Jinbo et al. |
| 20020072784 | June 13, 2002 | Sheppard et al. |
| 20020095980 | July 25, 2002 | Breed et al. |
| 20020103447 | August 1, 2002 | Terry |
| 20020133592 | September 19, 2002 | Matsuda |
| 20020172223 | November 21, 2002 | Stilp |
| 20030058187 | March 27, 2003 | Billiet et al. |
| 20030076274 | April 24, 2003 | Phelan et al. |
| 20030179152 | September 25, 2003 | Watada et al. |
| 20030179573 | September 25, 2003 | Chun |
| 20030192053 | October 9, 2003 | Sheppard et al. |
| 20040019624 | January 29, 2004 | Sukegawa |
| 20040020100 | February 5, 2004 | O'Brian et al. |
| 20040036657 | February 26, 2004 | Forster et al. |
| 20040113543 | June 17, 2004 | Daniels |
| 20040119675 | June 24, 2004 | Washio et al. |
| 20040107641 | June 10, 2004 | Walton et al. |
| 20040130425 | July 8, 2004 | Dayan |
| 20040130442 | July 8, 2004 | Breed |
| 20040142733 | July 22, 2004 | Parise |
| 20040145342 | July 29, 2004 | Lyon |
| 20040196190 | October 7, 2004 | Mendolia et al. |
| 20040207559 | October 21, 2004 | Milosavljevic |
| 20040218759 | November 4, 2004 | Yacobi |
| 20040259604 | December 23, 2004 | Mickle et al. |
| 20040263124 | December 30, 2004 | Wieck et al. |
| 20050007276 | January 13, 2005 | Barrick et al. |
| 20050030118 | February 10, 2005 | Wang |
| 20050046584 | March 3, 2005 | Breed |
| 20050055316 | March 10, 2005 | Williams |
| 20050116683 | June 2, 2005 | Cheng |
| 20050117660 | June 2, 2005 | Vialle et al. |
| 20050171411 | August 4, 2005 | KenKnight |
| 20050198673 | September 8, 2005 | Kit et al. |
| 20050227619 | October 13, 2005 | Lee et al. |
| 20050232469 | October 20, 2005 | Schofield |
| 20050282591 | December 22, 2005 | Shaff |
| 20060013335 | January 19, 2006 | Leabman |
| 20060019712 | January 26, 2006 | Choi |
| 20060030279 | February 9, 2006 | Leabman et al. |
| 20060092079 | May 4, 2006 | de Rochemont |
| 20060094425 | May 4, 2006 | Mickle et al. |
| 20060113955 | June 1, 2006 | Nunally |
| 20060136004 | June 22, 2006 | Cowan et al. |
| 20061195232 | June 2006 | Yun et al. |
| 20060160517 | July 20, 2006 | Yoon |
| 20060183473 | August 17, 2006 | Ukon |
| 20060190063 | August 24, 2006 | Kanzius |
| 20060192913 | August 31, 2006 | Shutou et al. |
| 20060238365 | October 26, 2006 | Vecchione et al. |
| 20060266564 | November 30, 2006 | Perlman et al. |
| 20060266917 | November 30, 2006 | Baldis et al. |
| 20060278706 | December 14, 2006 | Hatakayama et al. |
| 20060284593 | December 21, 2006 | Nagy et al. |
| 20060287094 | December 21, 2006 | Mahaffey et al. |
| 20070007821 | January 11, 2007 | Rossetti |
| 20070019693 | January 25, 2007 | Graham |
| 20070021140 | January 25, 2007 | Keyes |
| 20070060185 | March 15, 2007 | Simon et al. |
| 20070070490 | March 29, 2007 | Tsunoda et al. |
| 20070093269 | April 26, 2007 | Leabman et al. |
| 20070097653 | May 3, 2007 | Gilliland et al. |
| 20070103110 | May 10, 2007 | Sagoo |
| 20070106894 | May 10, 2007 | Zhang |
| 20070109121 | May 17, 2007 | Cohen |
| 20070139000 | June 21, 2007 | Kozuma |
| 20070149162 | June 28, 2007 | Greene et al. |
| 20070173196 | July 26, 2007 | Gallic |
| 20070173214 | July 26, 2007 | Mickle et al. |
| 20070178857 | August 2, 2007 | Greene et al. |
| 20070178945 | August 2, 2007 | Cook et al. |
| 20070182367 | August 9, 2007 | Partovi |
| 20070191074 | August 16, 2007 | Harrist et al. |
| 20070191075 | August 16, 2007 | Greene et al. |
| 20070197281 | August 23, 2007 | Stronach |
| 20070210960 | September 13, 2007 | Rofougaran et al. |
| 20070222681 | September 27, 2007 | Greene et al. |
| 20070273486 | November 29, 2007 | Shiotsu |
| 20070298846 | December 27, 2007 | Greene et al. |
| 20080014897 | January 17, 2008 | Cook et al. |
| 20080062062 | March 13, 2008 | Borau et al. |
| 20080062255 | March 13, 2008 | Gal |
| 20080067874 | March 20, 2008 | Tseng |
| 20080074324 | March 27, 2008 | Puzella et al. |
| 20080089277 | April 17, 2008 | Aledander et al. |
| 20080113816 | May 15, 2008 | Mahaffey et al. |
| 20080122297 | May 29, 2008 | Arai |
| 20080123383 | May 29, 2008 | Shionoiri |
| 20080129536 | June 5, 2008 | Randall et al. |
| 20080169910 | July 17, 2008 | Greene et al. |
| 20080197802 | August 21, 2008 | Onishi |
| 20080204342 | August 28, 2008 | Kharadly |
| 20080204350 | August 28, 2008 | Tam et al. |
| 20080210762 | September 4, 2008 | Osada et al. |
| 20080211458 | September 4, 2008 | Lawther et al. |
| 20080248758 | October 9, 2008 | Schedelbeck et al. |
| 20080248846 | October 9, 2008 | Stronach et al. |
| 20080278378 | November 13, 2008 | Chang et al. |
| 20080309452 | December 18, 2008 | Zeine |
| 20090002493 | January 1, 2009 | Kates |
| 20090019183 | January 15, 2009 | Wu et al. |
| 20090036065 | February 5, 2009 | Siu |
| 20090047998 | February 19, 2009 | Alberth, Jr. |
| 20090058354 | March 5, 2009 | Harrison |
| 20090058361 | March 5, 2009 | John |
| 20090096412 | April 16, 2009 | Huang |
| 20090096413 | April 16, 2009 | Partovi |
| 20090102292 | April 23, 2009 | Cook et al. |
| 20090102296 | April 23, 2009 | Greene et al. |
| 20090108679 | April 30, 2009 | Porwal |
| 20090128262 | May 21, 2009 | Lee et al. |
| 20090157911 | June 18, 2009 | Aihara |
| 20090200985 | August 13, 2009 | Zane et al. |
| 20090206791 | August 20, 2009 | Jung |
| 20090207092 | August 20, 2009 | Nysen et al. |
| 20090218884 | September 3, 2009 | Soar |
| 20090218891 | September 3, 2009 | McCollough |
| 20090219903 | September 3, 2009 | Alamouti et al. |
| 20090243397 | October 1, 2009 | Cook et al. |
| 20090264069 | October 22, 2009 | Yamasuge |
| 20090280866 | November 12, 2009 | Lo et al. |
| 20090281678 | November 12, 2009 | Wakamatsu |
| 20090284082 | November 19, 2009 | Mohammadian |
| 20090284083 | November 19, 2009 | Karalis et al. |
| 20090284220 | November 19, 2009 | Toncich et al. |
| 20090284227 | November 19, 2009 | Mohammadian et al. |
| 20090284325 | November 19, 2009 | Rossiter et al. |
| 20090286475 | November 19, 2009 | Toncich et al. |
| 20090291634 | November 26, 2009 | Saarisalo |
| 20090299175 | December 3, 2009 | Bernstein et al. |
| 20090315412 | December 24, 2009 | Yamamoto et al. |
| 20090322281 | December 31, 2009 | Kamijo et al. |
| 20100001683 | January 7, 2010 | Huang et al. |
| 20100007307 | January 14, 2010 | Baarman et al. |
| 20100007569 | January 14, 2010 | Sim et al. |
| 20100019686 | January 28, 2010 | Gutierrez, Jr. |
| 20100026605 | February 4, 2010 | Yang et al. |
| 20100027379 | February 4, 2010 | Saulnier et al. |
| 20100029383 | February 4, 2010 | Dai |
| 20100033021 | February 11, 2010 | Bennett |
| 20100033390 | February 11, 2010 | Alamouti et al. |
| 20100041453 | February 18, 2010 | Grimm, Jr. |
| 20100044123 | February 25, 2010 | Perlman et al. |
| 20100054200 | March 4, 2010 | Tsai |
| 20100060534 | March 11, 2010 | Oodachi |
| 20100075607 | March 25, 2010 | Hosoya |
| 20100079005 | April 1, 2010 | Hyde et al. |
| 20100082193 | April 1, 2010 | Chiappetta |
| 20100087227 | April 8, 2010 | Francos et al. |
| 20100090656 | April 15, 2010 | Shearer et al. |
| 20100109443 | May 6, 2010 | Cook et al. |
| 20100119234 | May 13, 2010 | Suematsu et al. |
| 20100123618 | May 20, 2010 | Martin et al. |
| 20100123624 | May 20, 2010 | Minear et al. |
| 20100127660 | May 27, 2010 | Cook et al. |
| 20100142418 | June 10, 2010 | Nishioka et al. |
| 20100142509 | June 10, 2010 | Zhu et al. |
| 20100151808 | June 17, 2010 | Toncich et al. |
| 20100156721 | June 24, 2010 | Alamouti et al. |
| 20100164433 | July 1, 2010 | Janefalker et al. |
| 20100171461 | July 8, 2010 | Baarman et al. |
| 20100174629 | July 8, 2010 | Taylor et al. |
| 20100176934 | July 15, 2010 | Chou et al. |
| 20100181961 | July 22, 2010 | Novak et al. |
| 20100181964 | July 22, 2010 | Huggins et al. |
| 20100194206 | August 5, 2010 | Burdo et al. |
| 20100201189 | August 12, 2010 | Kirby et al. |
| 20100201201 | August 12, 2010 | Mobarhan et al. |
| 20100201314 | August 12, 2010 | Toncich et al. |
| 20100207572 | August 19, 2010 | Kirby et al. |
| 20100214177 | August 26, 2010 | Parsche |
| 20100225270 | September 9, 2010 | Jacobs et al. |
| 20100227570 | September 9, 2010 | Hendin |
| 20100237709 | September 23, 2010 | Hall et al. |
| 20100244576 | September 30, 2010 | Hillan et al. |
| 20100259110 | October 14, 2010 | Kurs et al. |
| 20100259447 | October 14, 2010 | Crouch |
| 20100264747 | October 21, 2010 | Hall et al. |
| 20100277121 | November 4, 2010 | Hall et al. |
| 20100289341 | November 18, 2010 | Ozaki et al. |
| 20100295372 | November 25, 2010 | Hyde et al. |
| 20100308767 | December 9, 2010 | Rofougaran et al. |
| 20100309079 | December 9, 2010 | Rofougaran et al. |
| 20100309088 | December 9, 2010 | Hyvonen et al. |
| 20100315045 | December 16, 2010 | Zeine |
| 20100316163 | December 16, 2010 | Forenza et al. |
| 20100327766 | December 30, 2010 | Recker et al. |
| 20100328044 | December 30, 2010 | Waffenschmidt et al. |
| 20100332401 | December 30, 2010 | Prahlad et al. |
| 20110018360 | January 27, 2011 | Baarman et al. |
| 20110028114 | February 3, 2011 | Kerselaers |
| 20110031928 | February 10, 2011 | Soar |
| 20110032149 | February 10, 2011 | Leabman |
| 20110032866 | February 10, 2011 | Leabman |
| 20110034190 | February 10, 2011 | Leabman |
| 20110034191 | February 10, 2011 | Leabman |
| 20110043047 | February 24, 2011 | Karalis et al. |
| 20110043163 | February 24, 2011 | Baarman et al. |
| 20110043327 | February 24, 2011 | Baarman et al. |
| 20110050166 | March 3, 2011 | Cook et al. |
| 20110055037 | March 3, 2011 | Hayashigawa et al. |
| 20110056215 | March 10, 2011 | Ham |
| 20110057607 | March 10, 2011 | Carobolante |
| 20110074342 | March 31, 2011 | MacLaughlin |
| 20110074349 | March 31, 2011 | Ghovanloo |
| 20110074620 | March 31, 2011 | Wintermantel |
| 20110078092 | March 31, 2011 | Kim et al. |
| 20110090126 | April 21, 2011 | Szini et al. |
| 20110114401 | May 19, 2011 | Kanno et al. |
| 20110115303 | May 19, 2011 | Baarman et al. |
| 20110115432 | May 19, 2011 | El-Maleh |
| 20110115605 | May 19, 2011 | Dimig et al. |
| 20110121660 | May 26, 2011 | Azancot et al. |
| 20110122026 | May 26, 2011 | DeLaquil et al. |
| 20110127845 | June 2, 2011 | Walley et al. |
| 20110127952 | June 2, 2011 | Walley et al. |
| 20110133655 | June 9, 2011 | Recker et al. |
| 20110133691 | June 9, 2011 | Hautanen |
| 20110148578 | June 23, 2011 | Aloi et al. |
| 20110151789 | June 23, 2011 | Viglione et al. |
| 20110154429 | June 23, 2011 | Stantchev |
| 20110156494 | June 30, 2011 | Mashinsky |
| 20110156640 | June 30, 2011 | Moshfeghi |
| 20110163128 | July 7, 2011 | Taguchi et al. |
| 20110175455 | July 21, 2011 | Hashiguchi |
| 20110175461 | July 21, 2011 | Tinaphong |
| 20110181120 | July 28, 2011 | Liu et al. |
| 20110182245 | July 28, 2011 | Malkamaki et al. |
| 20110184842 | July 28, 2011 | Melen |
| 20110188207 | August 4, 2011 | Won et al. |
| 20110194543 | August 11, 2011 | Zhao et al. |
| 20110195722 | August 11, 2011 | Walter et al. |
| 20110215086 | September 8, 2011 | Yeh |
| 20110217923 | September 8, 2011 | Ma |
| 20110220634 | September 15, 2011 | Yeh |
| 20110221389 | September 15, 2011 | Won et al. |
| 20110222272 | September 15, 2011 | Yeh |
| 20110243040 | October 6, 2011 | Khan et al. |
| 20110243050 | October 6, 2011 | Yanover |
| 20110244913 | October 6, 2011 | Kim et al. |
| 20110248573 | October 13, 2011 | Kanno et al. |
| 20110248575 | October 13, 2011 | Kim et al. |
| 20110249678 | October 13, 2011 | Bonicatto |
| 20110254377 | October 20, 2011 | Widmer et al. |
| 20110254503 | October 20, 2011 | Widmer et al. |
| 20110259953 | October 27, 2011 | Baarman et al. |
| 20110273977 | November 10, 2011 | Shapira et al. |
| 20110278941 | November 17, 2011 | Krishna et al. |
| 20110279226 | November 17, 2011 | Chen et al. |
| 20110281535 | November 17, 2011 | Low et al. |
| 20110282415 | November 17, 2011 | Eckhoff et al. |
| 20110285213 | November 24, 2011 | Kowalewski |
| 20110286374 | November 24, 2011 | Shin et al. |
| 20110291489 | December 1, 2011 | Tsai et al. |
| 20110302078 | December 8, 2011 | Failing |
| 20110304216 | December 15, 2011 | Baarman |
| 20110304437 | December 15, 2011 | Beeler |
| 20120013196 | January 19, 2012 | Kim et al. |
| 20120013198 | January 19, 2012 | Uramoto et al. |
| 20120013296 | January 19, 2012 | Heydari et al. |
| 20120019419 | January 26, 2012 | Prat et al. |
| 20120043887 | February 23, 2012 | Mesibov |
| 20120051109 | March 1, 2012 | Kim et al. |
| 20120051294 | March 1, 2012 | Guillouard |
| 20120056486 | March 8, 2012 | Endo et al. |
| 20120056741 | March 8, 2012 | Zhu et al. |
| 20120074891 | March 29, 2012 | Anderson et al. |
| 20120231856 | September 13, 2012 | Lee et al. |
| 20120080957 | April 5, 2012 | Cooper et al. |
| 20120086284 | April 12, 2012 | Capanella et al. |
| 20120095617 | April 19, 2012 | Martin et al. |
| 20120098350 | April 26, 2012 | Campanella et al. |
| 20120098485 | April 26, 2012 | Kang et al. |
| 20120099675 | April 26, 2012 | Kitamura et al. |
| 20120103562 | May 3, 2012 | Clayton |
| 20120104849 | May 3, 2012 | Jackson |
| 20120105252 | May 3, 2012 | Wang |
| 20120112532 | May 10, 2012 | Kesler et al. |
| 20120119914 | May 17, 2012 | Uchida |
| 20120126743 | May 24, 2012 | Rivers, Jr. |
| 20120132647 | May 31, 2012 | Beverly et al. |
| 20120133214 | May 31, 2012 | Yun et al. |
| 20120146426 | June 14, 2012 | Sabo |
| 20120146576 | June 14, 2012 | Partovi |
| 20120146577 | June 14, 2012 | Tanabe |
| 20120147802 | June 14, 2012 | Ukita et al. |
| 20120150670 | June 14, 2012 | Taylor et al. |
| 20120153894 | June 21, 2012 | Widmer et al. |
| 20120157019 | June 21, 2012 | Li |
| 20120161531 | June 28, 2012 | Kim et al. |
| 20120161544 | June 28, 2012 | Kashiwagi et al. |
| 20120169276 | July 5, 2012 | Wang |
| 20120169278 | July 5, 2012 | Choi |
| 20120173418 | July 5, 2012 | Beardsmore et al. |
| 20120181973 | July 19, 2012 | Lyden |
| 20120182427 | July 19, 2012 | Marshall |
| 20120187851 | July 26, 2012 | Huggins et al. |
| 20120193999 | August 2, 2012 | Zeine |
| 20120201153 | August 9, 2012 | Bharadia et al. |
| 20120201173 | August 9, 2012 | Jian et al. |
| 20120206299 | August 16, 2012 | Valdes-Garcia |
| 20120212072 | August 23, 2012 | Miyabayashi et al. |
| 20120214536 | August 23, 2012 | Kim et al. |
| 20120200399 | August 9, 2012 | Chae |
| 20120228956 | September 13, 2012 | Kamata |
| 20120235636 | September 20, 2012 | Partovi |
| 20120242283 | September 27, 2012 | Kim et al. |
| 20120248886 | October 4, 2012 | Kesler et al. |
| 20120248891 | October 4, 2012 | Drennen |
| 20120249051 | October 4, 2012 | Son et al. |
| 20120262002 | October 18, 2012 | Widmer et al. |
| 20120267900 | October 25, 2012 | Huffman et al. |
| 20120268238 | October 25, 2012 | Park et al. |
| 20120274154 | November 1, 2012 | DeLuca |
| 20120280650 | November 8, 2012 | Kim et al. |
| 20120292993 | November 22, 2012 | Mettler et al. |
| 20120293119 | November 22, 2012 | Park et al. |
| 20120299389 | November 29, 2012 | Lee et al. |
| 20120299540 | November 29, 2012 | Perry |
| 20120299541 | November 29, 2012 | Perry |
| 20120299542 | November 29, 2012 | Perry |
| 20120300588 | November 29, 2012 | Perry |
| 20120300592 | November 29, 2012 | Perry |
| 20120300593 | November 29, 2012 | Perry |
| 20120306705 | December 6, 2012 | Sakurai et al. |
| 20120309295 | December 6, 2012 | Maguire |
| 20120309308 | December 6, 2012 | Kim et al. |
| 20120309332 | December 6, 2012 | Liao |
| 20120313449 | December 13, 2012 | Kurs |
| 20120326660 | December 27, 2012 | Lu et al. |
| 20130002550 | January 3, 2013 | Zalewski |
| 20130024059 | January 24, 2013 | Miller et al. |
| 20130026981 | January 31, 2013 | Van Der Lee |
| 20130026982 | January 31, 2013 | Rothenbaum |
| 20130032589 | February 7, 2013 | Chung |
| 20130033571 | February 7, 2013 | Steen |
| 20130038124 | February 14, 2013 | Newdoll et al. |
| 20130038402 | February 14, 2013 | Karalis et al. |
| 20130043738 | February 21, 2013 | Park et al. |
| 20130049471 | February 28, 2013 | Oleynik |
| 20130049475 | February 28, 2013 | Kim et al. |
| 20130057078 | March 7, 2013 | Lee |
| 20130057205 | March 7, 2013 | Lee et al. |
| 20130057210 | March 7, 2013 | Negaard et al. |
| 20130057364 | March 7, 2013 | Kesler et al. |
| 20130063082 | March 14, 2013 | Lee et al. |
| 20130063143 | March 14, 2013 | Adalsteinsson et al. |
| 20130069444 | March 21, 2013 | Waffenschmidt et al. |
| 20130077650 | March 28, 2013 | Traxler et al. |
| 20130078918 | March 28, 2013 | Crowley et al. |
| 20130082651 | April 4, 2013 | Park et al. |
| 20130082653 | April 4, 2013 | Lee et al. |
| 20130083774 | April 4, 2013 | Son et al. |
| 20130088082 | April 11, 2013 | Kang et al. |
| 20130088090 | April 11, 2013 | Wu |
| 20130088192 | April 11, 2013 | Eaton |
| 20130088331 | April 11, 2013 | Cho |
| 20130093388 | April 18, 2013 | Partovi |
| 20130099389 | April 25, 2013 | Hong et al. |
| 20130099586 | April 25, 2013 | Kato |
| 20130106197 | May 2, 2013 | Bae et al. |
| 20130107023 | May 2, 2013 | Tanaka et al. |
| 20130119777 | May 16, 2013 | Rees |
| 20130119929 | May 16, 2013 | Partovi |
| 20130120217 | May 16, 2013 | Ueda et al. |
| 20130132010 | May 23, 2013 | Winger et al. |
| 20130134923 | May 30, 2013 | Smith |
| 20130137455 | May 30, 2013 | Xia |
| 20130141037 | June 6, 2013 | Jenwatanavet et al. |
| 20130148341 | June 13, 2013 | Williams |
| 20130149975 | June 13, 2013 | Yu et al. |
| 20130154387 | June 20, 2013 | Lee et al. |
| 20130155748 | June 20, 2013 | Sundstrom |
| 20130157729 | June 20, 2013 | Tabe |
| 20130169061 | July 4, 2013 | Microshnichenko et al. |
| 20130169219 | July 4, 2013 | Gray |
| 20130169348 | July 4, 2013 | Shi |
| 20130171939 | July 4, 2013 | Tian et al. |
| 20130178253 | July 11, 2013 | Karaoguz |
| 20130181881 | July 18, 2013 | Christie et al. |
| 20130193769 | August 1, 2013 | Mehta et al. |
| 20130197320 | August 1, 2013 | Albert et al. |
| 20130200064 | August 8, 2013 | Alexander |
| 20130207477 | August 15, 2013 | Nam et al. |
| 20130207604 | August 15, 2013 | Zeine |
| 20130210357 | August 15, 2013 | Qin et al. |
| 20130221757 | August 29, 2013 | Cho et al. |
| 20130234530 | September 12, 2013 | Miyauchi |
| 20130234536 | September 12, 2013 | Chemishkian et al. |
| 20130234658 | September 12, 2013 | Endo et al. |
| 20130241306 | September 19, 2013 | Aber et al. |
| 20130241468 | September 19, 2013 | Moshfeghi |
| 20130241474 | September 19, 2013 | Moshfeghi |
| 20130249478 | September 26, 2013 | Hirano |
| 20130249479 | September 26, 2013 | Partovi |
| 20130254578 | September 26, 2013 | Huang et al. |
| 20130264997 | October 10, 2013 | Lee et al. |
| 20130268782 | October 10, 2013 | Tam et al. |
| 20130270923 | October 17, 2013 | Cook et al. |
| 20130278209 | October 24, 2013 | Von Novak |
| 20130285477 | October 31, 2013 | Lo et al. |
| 20130285606 | October 31, 2013 | Ben-Shalom et al. |
| 20130288600 | October 31, 2013 | Kuusilinna et al. |
| 20130293423 | November 7, 2013 | Moshfeghi |
| 20130310020 | November 21, 2013 | Kazuhiro |
| 20130311798 | November 21, 2013 | Sultenfuss |
| 20130328417 | December 12, 2013 | Takeuchi |
| 20130339108 | December 19, 2013 | Ryder et al. |
| 20130343251 | December 26, 2013 | Zhang |
| 20140001846 | January 2, 2014 | Mosebrook |
| 20140001875 | January 2, 2014 | Nahidipour |
| 20140001876 | January 2, 2014 | Fujiwara et al. |
| 20140006017 | January 2, 2014 | Sen |
| 20140008992 | January 9, 2014 | Leabman |
| 20140008993 | January 9, 2014 | Leabman |
| 20140009108 | January 9, 2014 | Leabman |
| 20140011531 | January 9, 2014 | Burstrom et al. |
| 20140015336 | January 16, 2014 | Weber et al. |
| 20140015344 | January 16, 2014 | Mohamadi |
| 20140021907 | January 23, 2014 | Yun et al. |
| 20140021908 | January 23, 2014 | McCool |
| 20140035524 | February 6, 2014 | Zeine |
| 20140035526 | February 6, 2014 | Tripathi et al. |
| 20140049422 | February 20, 2014 | Von Novak et al. |
| 20140055098 | February 27, 2014 | Lee et al. |
| 20140057618 | February 27, 2014 | Zirwas et al. |
| 20140062395 | March 6, 2014 | Kwon et al. |
| 20140086125 | March 27, 2014 | Polo et al. |
| 20140091756 | April 3, 2014 | Ofstein et al. |
| 20140091968 | April 3, 2014 | Harel et al. |
| 20140111147 | April 24, 2014 | Soar |
| 20140113689 | April 24, 2014 | Lee |
| 20140117946 | May 1, 2014 | Muller et al. |
| 20140118140 | May 1, 2014 | Amis |
| 20140133279 | May 15, 2014 | Khuri-Yakub |
| 20140139034 | May 22, 2014 | Sankar et al. |
| 20140139039 | May 22, 2014 | Cook et al. |
| 20140139180 | May 22, 2014 | Kim et al. |
| 20140141838 | May 22, 2014 | Cai et al. |
| 20140142876 | May 22, 2014 | John et al. |
| 20140143933 | May 29, 2014 | Low et al. |
| 20140145879 | May 29, 2014 | Pan |
| 20140152117 | June 5, 2014 | Sanker |
| 20140159651 | June 12, 2014 | Von Novak et al. |
| 20140159652 | June 12, 2014 | Hall et al. |
| 20140159662 | June 12, 2014 | Furui |
| 20140159667 | June 12, 2014 | Kim et al. |
| 20140175893 | June 26, 2014 | Sengupta et al. |
| 20140176054 | June 26, 2014 | Porat et al. |
| 20140177399 | June 26, 2014 | Teng et al. |
| 20140184148 | July 3, 2014 | Van Der Lee et al. |
| 20140184155 | July 3, 2014 | Cha |
| 20140184163 | July 3, 2014 | Das et al. |
| 20140184170 | July 3, 2014 | Jeong |
| 20140191568 | July 10, 2014 | Partovi |
| 20140194092 | July 10, 2014 | Wanstedt et al. |
| 20140194095 | July 10, 2014 | Wanstedt et al. |
| 20140206384 | July 24, 2014 | Kim et al. |
| 20140210281 | July 31, 2014 | Ito et al. |
| 20140217967 | August 7, 2014 | Zeine et al. |
| 20140225805 | August 14, 2014 | Pan et al. |
| 20140232320 | August 21, 2014 | Ento July et al. |
| 20140239733 | August 28, 2014 | Mach et al. |
| 20140241231 | August 28, 2014 | Zeine |
| 20140245036 | August 28, 2014 | Oishi |
| 20140246416 | September 4, 2014 | White |
| 20140247152 | September 4, 2014 | Proud |
| 20140252813 | September 11, 2014 | Lee et al. |
| 20140252866 | September 11, 2014 | Walsh et al. |
| 20140265725 | September 18, 2014 | Angle et al. |
| 20140265727 | September 18, 2014 | Berte |
| 20140265943 | September 18, 2014 | Angle et al. |
| 20140266025 | September 18, 2014 | Jakubowski |
| 20140273892 | September 18, 2014 | Nourbakhsh |
| 20140281655 | September 18, 2014 | Angle et al. |
| 20140292090 | October 2, 2014 | Cordeiro et al. |
| 20140312706 | October 23, 2014 | Fiorello et al. |
| 20140325218 | October 30, 2014 | Shimizu et al. |
| 20140327320 | November 6, 2014 | Muhs et al. |
| 20140327390 | November 6, 2014 | Park et al. |
| 20140346860 | November 27, 2014 | Aubry et al. |
| 20140354063 | December 4, 2014 | Leabman et al. |
| 20140354221 | December 4, 2014 | Leabman et al. |
| 20140355718 | December 4, 2014 | Guan et al. |
| 20140357309 | December 4, 2014 | Leabman et al. |
| 20140368048 | December 18, 2014 | Leabman |
| 20140368161 | December 18, 2014 | Leabman et al. |
| 20140375253 | December 25, 2014 | Leabman et al. |
| 20140375255 | December 25, 2014 | Leabman et al. |
| 20140375258 | December 25, 2014 | Arkhipenkov |
| 20140375261 | December 25, 2014 | Manova-Elssibony et al. |
| 20140376646 | December 25, 2014 | Leabman et al. |
| 20150001949 | January 1, 2015 | Leabman et al. |
| 20150002086 | January 1, 2015 | Matos et al. |
| 20150003207 | January 1, 2015 | Lee et al. |
| 20150008980 | January 8, 2015 | Kim et al. |
| 20150011160 | January 8, 2015 | Uurgovan et al. |
| 20150015180 | January 15, 2015 | Miller et al. |
| 20150015192 | January 15, 2015 | Leabman et al. |
| 20150015194 | January 15, 2015 | Leabman et al. |
| 20150015195 | January 15, 2015 | Leabman et al. |
| 20150021990 | January 22, 2015 | Myer et al. |
| 20150022008 | January 22, 2015 | Leabman et al. |
| 20150022009 | January 22, 2015 | Leabman et al. |
| 20150022010 | January 22, 2015 | Leabman et al. |
| 20150028688 | January 29, 2015 | Masaoka |
| 20150028694 | January 29, 2015 | Leabman et al. |
| 20150028697 | January 29, 2015 | Leabman et al. |
| 20150029397 | January 29, 2015 | Leabman et al. |
| 20150035715 | February 5, 2015 | Kim et al. |
| 20150041459 | February 12, 2015 | Leabman et al. |
| 20150042264 | February 12, 2015 | Leabman et al. |
| 20150042265 | February 12, 2015 | Leabman et al. |
| 20150044977 | February 12, 2015 | Ramasamy et al. |
| 20150046526 | February 12, 2015 | Bush et al. |
| 20150061404 | March 5, 2015 | Lamenza et al. |
| 20150076917 | March 19, 2015 | Leabman et al. |
| 20150076927 | March 19, 2015 | Leabman et al. |
| 20150077036 | March 19, 2015 | Leabman et al. |
| 20150077037 | March 19, 2015 | Leabman et al. |
| 20150091520 | April 2, 2015 | Blum et al. |
| 20150097663 | April 9, 2015 | Sloo et al. |
| 20150102681 | April 16, 2015 | Leabman et al. |
| 20150102764 | April 16, 2015 | Leabman et al. |
| 20150102769 | April 16, 2015 | Leabman et al. |
| 20150108848 | April 23, 2015 | Joehren |
| 20150115877 | April 30, 2015 | Aria et al. |
| 20150115878 | April 30, 2015 | Park |
| 20150123483 | May 7, 2015 | Leabman et al. |
| 20150123496 | May 7, 2015 | Leabman et al. |
| 20150128733 | May 14, 2015 | Taylor et al. |
| 20150130285 | May 14, 2015 | Leabman et al. |
| 20150148664 | May 28, 2015 | Stolka et al. |
| 20150155737 | June 4, 2015 | Mayo |
| 20150155738 | June 4, 2015 | Leabman et al. |
| 20150162751 | June 11, 2015 | Leabman et al. |
| 20150162779 | June 11, 2015 | Lee et al. |
| 20150171656 | June 18, 2015 | Leabman et al. |
| 20150171658 | June 18, 2015 | Manova-Elssibony et al. |
| 20150171931 | June 18, 2015 | Won et al. |
| 20150177326 | June 25, 2015 | Chakraborty et al. |
| 20150188352 | July 2, 2015 | Peek et al. |
| 20150199665 | July 16, 2015 | Chu |
| 20150207333 | July 23, 2015 | Baarman et al. |
| 20150222126 | August 6, 2015 | Leabman et al. |
| 20150236520 | August 20, 2015 | Baarman |
| 20150244187 | August 27, 2015 | Horie |
| 20150244201 | August 27, 2015 | Chu |
| 20150244341 | August 27, 2015 | Ritter et al. |
| 20150249484 | September 3, 2015 | Mach et al. |
| 20150255989 | September 10, 2015 | Walley et al. |
| 20150263534 | September 17, 2015 | Lee et al. |
| 20150263548 | September 17, 2015 | Cooper |
| 20150270741 | September 24, 2015 | Leabman et al. |
| 20150280484 | October 1, 2015 | Radziemski et al. |
| 20150288438 | October 8, 2015 | Maltsev et al. |
| 20150318729 | November 5, 2015 | Leabman |
| 20150326024 | November 12, 2015 | Bell et al. |
| 20150326025 | November 12, 2015 | Bell et al. |
| 20150326063 | November 12, 2015 | Leabman et al. |
| 20150326068 | November 12, 2015 | Bell et al. |
| 20150326069 | November 12, 2015 | Petras et al. |
| 20150326070 | November 12, 2015 | Petras et al. |
| 20150326072 | November 12, 2015 | Petras et al. |
| 20150326142 | November 12, 2015 | Petras et al. |
| 20150333528 | November 19, 2015 | Leabman |
| 20150333529 | November 19, 2015 | Leabman |
| 20150333573 | November 19, 2015 | Leabman |
| 20150333800 | November 19, 2015 | Perry et al. |
| 20150340759 | November 26, 2015 | Bridgelall et al. |
| 20150340903 | November 26, 2015 | Bell et al. |
| 20150340909 | November 26, 2015 | Bell et al. |
| 20150340910 | November 26, 2015 | Petras et al. |
| 20150340911 | November 26, 2015 | Bell et al. |
| 20150341087 | November 26, 2015 | Moore et al. |
| 20150349574 | December 3, 2015 | Leabman |
| 20150358222 | December 10, 2015 | Berger et al. |
| 20150365138 | December 17, 2015 | Miller et al. |
| 20160005068 | January 7, 2016 | Im et al. |
| 20160012695 | January 14, 2016 | Bell et al. |
| 20160013656 | January 14, 2016 | Bell et al. |
| 20160013677 | January 14, 2016 | Bell et al. |
| 20160013678 | January 14, 2016 | Bell et al. |
| 20160013855 | January 14, 2016 | Campos |
| 20160020636 | January 21, 2016 | Khlat |
| 20160020649 | January 21, 2016 | Bell et al. |
| 20160020830 | January 21, 2016 | Bell et al. |
| 20160042206 | February 11, 2016 | Pesavento et al. |
| 20160054396 | February 25, 2016 | Bell et al. |
| 20160054440 | February 25, 2016 | Younis |
| 20160056635 | February 25, 2016 | Bell |
| 20160056640 | February 25, 2016 | Mao |
| 20160056669 | February 25, 2016 | Bell |
| 20160056966 | February 25, 2016 | Bell |
| 20160065005 | March 3, 2016 | Won et al. |
| 20160079799 | March 17, 2016 | Khlat |
| 20160099601 | April 7, 2016 | Leabman et al. |
| 20160099602 | April 7, 2016 | Leabman et al. |
| 20160099609 | April 7, 2016 | Leabman et al. |
| 20160099610 | April 7, 2016 | Leabman et al. |
| 20160099611 | April 7, 2016 | Leabman et al. |
| 20160099612 | April 7, 2016 | Leabman et al. |
| 20160099613 | April 7, 2016 | Leabman et al. |
| 20160099614 | April 7, 2016 | Leabman et al. |
| 20160099755 | April 7, 2016 | Leabman et al. |
| 20160099756 | April 7, 2016 | Leabman et al. |
| 20160099757 | April 7, 2016 | Leabman et al. |
| 20160099758 | April 7, 2016 | Leabman et al. |
| 20160100124 | April 7, 2016 | Leabman et al. |
| 20160100312 | April 7, 2016 | Bell et al. |
| 20160126752 | May 5, 2016 | Vuori et al. |
| 20160126776 | May 5, 2016 | Kim et al. |
| 20160141908 | May 19, 2016 | Jakl et al. |
| 20160164563 | June 9, 2016 | Khawand et al. |
| 20160181867 | June 23, 2016 | Daniel et al. |
| 20160181873 | June 23, 2016 | Mitcheson et al. |
| 20160191121 | June 30, 2016 | Bell |
| 20160204622 | July 14, 2016 | Leabman |
| 20160204642 | July 14, 2016 | Oh |
| 20160238365 | August 18, 2016 | Wixey et al. |
| 20160323000 | November 3, 2016 | Liu et al. |
| 20160336804 | November 17, 2016 | Son et al. |
| 20160339258 | November 24, 2016 | Perryman et al. |
| 20160359367 | December 8, 2016 | Rothschild |
| 20170005516 | January 5, 2017 | Leabman et al. |
| 20170025903 | January 26, 2017 | Song et al. |
| 20170026087 | January 26, 2017 | Tanabe |
| 20170043675 | February 16, 2017 | Jones et al. |
| 20170047784 | February 16, 2017 | Jung et al. |
| 20170085120 | March 23, 2017 | Leabman et al. |
| 20170085437 | March 23, 2017 | Condeixa et al. |
| 20170092115 | March 30, 2017 | Sloo et al. |
| 203826555 | September 2014 | CN |
| 104090265 | October 2014 | CN |
| 1028482 | August 2000 | EP |
| 1081506 | March 2001 | EP |
| 2397973 | June 2010 | EP |
| 2346136 | July 2011 | EP |
| 2545635 | January 2013 | EP |
| 2006157586 | June 2006 | JP |
| 2007043432 | February 2007 | JP |
| 2008167017 | July 2008 | JP |
| 20060061776 | June 2006 | KR |
| 20070044302 | April 2007 | KR |
| 100755144 | September 2007 | KR |
| 20110132059 | December 2011 | KR |
| 20110135540 | December 2011 | KR |
| 20120009843 | February 2012 | KR |
| 20120108759 | October 2012 | KR |
| 1020130026977 | March 2013 | KR |
| 9952173 | October 1999 | WO |
| WO 200111716 | February 2001 | WO |
| 2004077550 | September 2004 | WO |
| 2003091943 | November 2006 | WO |
| WO 2006122783 | November 2006 | WO |
| 2008156571 | December 2008 | WO |
| 2010022181 | February 2010 | WO |
| WO 2010039246 | April 2010 | WO |
| WO 2010138994 | December 2010 | WO |
| 2011112022 | September 2011 | WO |
| WO 2012177283 | December 2012 | WO |
| 2013035190 | March 2013 | WO |
| WO 2013031988 | March 2013 | WO |
| WO 2013042399 | March 2013 | WO |
| WO 2013052950 | April 2013 | WO |
| WO 2013105920 | July 2013 | WO |
| WO 2014075103 | May 2014 | WO |
| 2014/132258 | September 2014 | WO |
| WO 2014182788 | November 2014 | WO |
| WO 2014182788 | November 2014 | WO |
| WO 2014197472 | December 2014 | WO |
| WO 2014209587 | December 2014 | WO |
| WO 2015038773 | March 2015 | WO |
| WO 2015097809 | July 2015 | WO |
| WO 2015161323 | October 2015 | WO |
| WO 2016048512 | March 2016 | WO |
| WO 2016187357 | November 2016 | WO |
- International Search Report dated Jan. 27, 2015 corresponding to International Patent Application No. PCT/US2014/037170, 4 pages.
- International Search Report dated Oct. 16, 2014 corresponding to International Patent Application No. PCT/US2014/041546, 4 pages.
- International Search Report dated Oct. 13, 2014 corresponding to International Patent Application No. PCT/US2014/041534, 4 pages.
- International Search Report dated Nov. 12, 2014 corresponding to International Patent Application No. PCT/US2014/046956, 4 pages.
- Written Opinion of the International Searching Authority dated Nov. 12, 2014 corresponding to International Patent Application No. PCT/US2014/046956, 6 pages.
- International Search Report dated Sep. 12, 2014 corresponding to International Patent Application No. PCT/US2014/037072, 3 pages.
- International Search Report and Written Opinion of the International Searching Authority, or the Declaration dated Mar. 11, 2016 in International Application No. PCT/US15/67279, 13 pages.
- Energous Corp., Written Opinion, PCT/US2014/037170 , dated Sep. 15, 2014, 7 pgs.
- Energous Corp., IPRP, PCT/US2014/037170, dated Nov. 10, 2015, 8 pgs.
- Energous Corp., Written Opinion, PCT/US2014/041534, dated Oct. 13, 2014, 6 pgs.
- Energous Corp., IPRP, PCT/US2014/041534, dated Dec. 29, 2015, 7 pgs.
- Energous Corp., IPRP, PCT/US2014/046956, dated Jan. 19, 2016, 7 pgs.
- Energous Corp., Written Opinion, PCT/US2014/037072, dated Sep. 12, 2014, 5 pgs.
- Energous Corp., IPRP, PCT/US2014/037072, dated Nov. 10, 2015, 6 pgs.
- Energous Corp., ISRWO, PCT/US2014/068568, dated Mar. 20, 2015, 10 pgs.
- Energous Corp., IPRP, PCT/US2014/068568, dated Jun. 14, 2016, 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/055195, dated Dec. 22, 2014, 11 pgs.
- Energous Corp., IPRP, PCT/US2014/055195, dated Mar. 22, 2016, 9 pgs.
- Energous Corp., ISRWO, PCT/US2015/067291, dated Mar. 4, 2016, 10 pgs.
- Energous Corp., IPRP, PCT/US2015/067291, dated Jul. 4, 2017, 4 pgs.
- Energous Corp., ISRWO, PCT/US2015/067242, dated Mar. 16, 2016, 9 pgs.
- Energous Corp., IPRP, PCT/US2015/067242, dated Jun. 27, 2017, 7 pgs.
- Energous Corp., ISRWO, PCT/US2015/067243, dated Mar. 10, 2016, 11 pgs.
- Energous Corp., ISRWO, PCT/US2015/067243, dated Jun. 27, 2017, 7 pgs.
- Energous Corp., ISRWO, PCT/US2014/037109, dated Apr. 8, 2016, 12 pgs.
- Energous Corp., IPRP, PCT/US2014/037109, dated Apr. 12, 2016, 9 pgs.
- Energous Corp., ISRWO, PCT/US2015/067275, dated Mar. 3, 2016, 8 pgs.
- Energous Corp., IPRP, PCT/US2015/067275, dated Jul. 4, 2017, 7 pgs.
- Energous Corp., ISRWO, PCT/US2015/067245, dated Mar. 17, 2016, 8 pgs.
- Energous Corp., IPRP, PCT/US2015/067245, dated Jun. 27, 2017, 7 pgs.
- Energous Corp., ISRWO, PCT/US2014/041546, dated Oct. 16, 2014, 12 pgs.
- Energous Corp., IPRP, PCT/US2014/041546, dated Dec. 29, 2015, 9 pgs.
- Energous Corp., ISRWO, PCT/US2015/67250, dated Mar. 30, 2016, 11 pgs.
- Energous Corp., IPRP, PCT/US2015/67250, dated Mar. 30, 2016, 10 pgs.
- Energous Corp., ISRWO, PCT/US2015/067325, dated Mar. 10, 2016, 9 pgs.
- Energous Corp., IPRP, PCT/US2015/067325, dated Jul. 4, 2017, 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/040697, dated Oct. 1, 2014, 12 pgs.
- Energous Corp.,IPRP, PCT/US2014/040697, dated Dec. 8, 2015, 9 pgs.
- Energous Corp., ISRWO, PCT/US2014/040705, dated Sep. 23, 2014, 8 pgs.
- Energous Corp., IPRP, PCT/US2014/040705, dated Dec. 8, 2015, 6 pgs.
- Energous Corp., ISRWO, PCT/US2015/067249, dated Mar. 29, 2016, 8 pgs.
- Energous Corp., IPRP, PCT/US2015/067249, dated Jun. 27, 2017, 7 pgs.
- Energous Corp., ISRWO, PCT/US2015/067246, dated May 11, 2016, 18 pgs.
- Energous Corp., IPRP, PCT/US2015/067246, dated Jun. 27, 2017, 9 pgs.
- Energous Corp., ISRWO, PCT/US2014/059317, dated Feb. 24, 2015, 13 pgs.
- Energous Corp., IPRP, PCT/US2014/059317, dated Apr. 12, 2016, 10 pgs.
- Energous Corp., ISRWO, PCT/US2014/049669, dated Nov. 13, 2014, 10 pgs.
- Energous Corp., IPRP, PCT/US2014/049669, dated Feb. 9, 2016, 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/041323, dated Oct. 1, 2014, 10 pgs.
- Energous Corp., IPRP, PCT/US2014/041323, dated Dec. 22, 2015, 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/048002, dated Nov. 13, 2014, 11 pgs.
- Energous Corp., IPRP, PCT/US2014/048002, dated Feb. 12, 2015 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/062682, dated Feb. 12, 2015, 10 pgs.
- Energous Corp., IPRP, PCT/US2014/062682, dated May 3, 2016, 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/049666, dated Nov. 10, 2014, 7 pgs.
- Energous Corp., IPRP, PCT/US2014/049666, dated Feb. 9, 2016, 5 pgs.
- Energous Corp., ISRWO, PCT/US2014/046961, dated Nov. 24, 2014, 16 pgs.
- Energous Corp., IPRP, PCT/US2014/046961, dated Jan. 19, 2016, 8 pgs.
- Energous Corp., ISRWO, PCT/US2015/067279, dated Mar. 11, 2015, 13 pgs.
- Energous Corp., IPRP, PCT/US2015/067279, dated Jul. 4, 2017, 7 pgs.
- Energous Corp., ISRWO, PCT/US2014/041342, dated Jan. 27, 2015, 10 pgs.
- Energous Corp., IPRP, PCT/US2014/041342, dated Dec. 15, 2015, 8 pgs.
- Energous Corp., ISRWO, PCT/US2014/046941, dated Nov. 6, 2014, 11 pgs.
- Energous Corp., IPRP, PCT/US2014/046941, dated Jan. 19, 2016, 9 pgs.
- Energous Corp., ISR, PCT/US2014/062661, dated Jan. 27, 2015, 3 pgs.
- Energous Corp., Written Opinion, PCT/US2014/062661, dated Jan. 27, 2015, 9 pgs.
- Energous Corp., IPRP, PCT/US2014/062661, dated May 3, 2016, 10 pgs.
- Energous Corp., ISRWO, PCT/US2014/059871, dated Jan. 23, 2015, 12 pgs.
- Energous Corp., IPRP, PCT/US2014/059871, dated Apr. 12, 2016, 9 pgs.
- Energous Corp., ISRWO, PCT/US2014/045102, dated Oct. 28, 2014, 14 pgs.
- Energous Corp., IPRP, PCT/US2014/045102, dated Jan. 12, 2016, 11 pgs.
- Energous Corp., ISRWO, PCT/US2014/059340, dated Jan. 15, 2015, 13 pgs.
- Energous Corp., IPRP, PCT/US2014/059340, dated Apr. 12, 2016, 11 pgs.
- Energous Corp., ISRWO, PCT/US2015/067282, dated Jul. 5, 2016, 7 pgs.
- Energous Corp., IPRP, PCT/US2015/067282, dated Jul. 4, 2017, 6 pgs.
- Energous Corp., ISRWO, PCT/US2014/041558, dated Oct. 10, 2014, 8 pgs.
- Energous Corp., IPRP, PCT/US2014/041558, dated Dec. 29, 2015, 6 pgs.
- Energous Corp., ISRWO, PCT/US2014/045119, dated Oct. 13, 2014, 11 pgs.
- Energous Corp., IPRP, PCT/US2014/045119, dated Jan. 12, 2016, 9 pgs.
- Energous Corp., ISRWO PCT/US2014/045237, dated Oct. 13, 2014, 16 pgs.
- Energous Corp., IPRP , PCT/US2014/045237, dated Jan. 12, 2016, 12 pgs.
- Energous Corp., ISRWO , PCT/US2014/054897, dated Feb. 17, 2015, 10 pgs.
- Energous Corp., IPRP , PCT/US2014/054897, dated Mar. 15, 2016, 8 pgs.
- Energous Corp., ISRWO , PCT/US2015/067334, dated Mar. 3, 2016, 6 pgs.
- Energous Corp., IPRP , PCT/US2015/067334, dated Jul. 4, 2017, 5 pgs.
- Energous Corp., ISRWO , PCT/US2014/047963, dated Nov. 7, 2014, 13 pgs.
- Energous Corp., IPRP , PCT/US2014/047963, dated Jan. 26, 2016, 10 pgs.
- Energous Corp., ISRWO , PCT/US2014/054891, dated Dec. 18, 2014, 12 pgs.
- Energous Corp., IPRP , PCT/US2014/054891, dated Mar. 15, 2016, 10 pgs.
- Energous Corp., ISRWO , PCT/US2014/054953, dated Dec. 4, 2014, 7 pgs.
- Energous Corp., IPRP , PCT/US2014/054953, dated Mar. 22, 2016, 5 pgs.
- Energous Corp.,ISRWO , PCT/US2015/067294, dated Mar. 29, 2016, 7 pgs.
- Energous Corp.,IPRP , PCT/US2015/067294, dated Jul. 4, 6 pgs.
- Energous Corp.,ISRWO , PCT/US2014/062672 dated Jan. 26, 2015, 11 pgs.
- Energous Corp., IPRP , PCT/US2014/062672 dated May 10, 2016, 8 pgs.
- Energous Corp.,ISRWO , PCT/US2014/044810 dated Oct. 21, 2014, 12 pgs.
- Energous Corp., IPRP , PCT/US2014/044810, dated Jan. 5, 2016, 10 pgs.
- Energous Corp., ISRWO , PCT/US2015/067271, dated Mar. 11, 2016, 6 pgs.
- Energous Corp., IPRP , PCT/US2015/067271, dated Jul. 4, 2017, 5 pgs.
- Energous Corp., ISRWO , PCT/US2014/040648, dated Oct. 10, 2014, 11 pgs.
- Energous Corp., IPRP , PCT/US2014/040648, dated Dec. 8, 2015, 8 pgs.
- Energous Corp., ISRWO , PCT/US2014/049673, dated Nov. 18, 2014, 10 pgs.
- Energous Corp., IPRP , PCT/US2014/049673, dated Feb. 9, 2016, 6 pgs.
- Energous Corp., ISRWO , PCT/US2014/068282, dated Mar. 19, 2015, 13 pgs.
- Energous Corp., IPRP, PCT/US2014/068282, dated Jun. 7, 2016, 10 pgs.
- Energous Corp., ISRWO, PCT/US2014/068586, dated Mar. 20, 2015, 11 pgs.
- Energous Corp., IPRP, PCT/US2014/068586, dated Jun. 14, 2016, 8 pgs.
- Energous Corp., ISRWO, PCT/US2016/068504, dated Mar. 30, 2017, 8 pgs.
- Energous Corp., ISRWO, PCT/US2016/068495, dated Mar. 30, 2017, 9 pgs.
- Energous Corp., ISRWO, PCT/US2015/067287, dated Feb. 2, 2016, 8 pgs.
- Energous Corp., IPRP, PCT/US2015/067287, dated Jul. 4, 2017, 6 pgs.
- Energous Corp., ISRWO, PCT/US2016/068551, dated Mar. 17, 2017, 8 pgs.
- Energous Corp., ISRWO, PCT/US2016/068498, dated May 17, 2017, 8 pgs.
- Energous Corp., ISRWO, PCT/US2016/068993, dated Mar. 13, 2017, 12 pgs.
- Energous Corp., ISRWO, PCT/US2016/068565, dated Mar. 8, 2017, 11 pgs.
- Energous Corp., ISRWO, PCT/US2016/068987, dated May 8, 2017, 10 pgs.
- Energous Corp., ISRWO, PCT/US2016/069316 , dated Mar. 16, 2017, 15 pgs.
- Supplementary European Search Report, EP Patent Application No. EP14818136-5, dated Jul. 21, 2016, 9 pgs.
- European Search Report, EP Patent Application No. EP16189052.0, dated Jan. 31, 2017, 11 pgs.
- European Search Report, EP Patent Application No. EP16189319-3, dated Feb. 1, 2017, 9 pgs.
- European Search Report, EP Patent Application No. EP14822971, dated Feb. 1, 2017, 9 pgs.
- European Search Report, EP Patent Application No. EP16189987, dated Feb. 1, 2017, 8 pgs.
- European Search Report, EP Patent Application No. 16196205.5, dated Mar. 28, 2017.
- European Search Report, EP Patent Application No. 16189300, dated Feb. 28, 2017, 4 pgs.
- European Search Report, EP Patent Application No. 16189988.5, dated Mar. 1, 2017, 4 pgs.
- European Search Report, EP Patent Application No. 16189982.5, dated Jan. 27, 2017, 9 pgs.
- European Search Report, EP Patent Application No. 16189974, dated Mar. 2, 2017, 5 pgs.
- European Search Report, EP Patent Application No. 16193743, dated Feb. 2, 2017, 5 pgs.
- European Search Report, EP Patent Application No. 14868901.1, dated Jul. 7, 2017, 5 pgs.
- L.H. Hsieh et al. Development of a Retrodirective Wireless Microwave Power Transmission System, IEEE, 2003 pp. 393-396.
- B.D. Van Veen et al., Beamforming: A Versatile Approach to Spatial Filtering, IEEE, ASSP Magazine, Apr. 1988, pp. 4-24.
- Leabman, Adaptive Band-partitioning for Interference Cancellation in Communication System, Thesis Massachusetts Institute of Technology, Feb. 1997, pp. 1-70.
- Panda, SIW based Slot Array Antenna and Power Management Circuit for Wireless Energy Harvesting Applications, IEEE APSURSI, Jul. 2012, 2 pgs.
- Singh, Wireless Power Transfer Using Metamaterial Bonded Microstrip Antenna for Smart Grid WSN: In Fourth International Conference on Advances in Computing and Communications (ICACC), Aug. 27-29, 2014, Abstract 299.
- T. Gill et al. “A System for Change Detection and Human Recognition in Voxel Space using the Microsoft Kinect Sensor,” 2011 IEEE Applied Imagery Pattern Recognition Workshop. 8 pgs.
- J. Han et al. Enhanced Computer Vision with Microsoft Kinect Sensor: A Review, IEEE Transactions on Cybermetics vol. 43, No. 5. pp. 1318-1334.
- Zhai, “A Practical wireless charging system based on ultra-wideband retro-reflectie beamforming” 2010 IEEE Antennas and Propagation Society International Symposium, Toronto, ON 2010, pp. 1-4.
- Mao: BeamStar: An Edge-Based Approach to Routing in Wireless Sensors Networks, IEEE Transactions on Mobile Computing, IEEE Service Center, Los Alamitos, CA US, vol. 6, No. 11, Nov. 1, 2007, 13 pgs.
- Smolders—Institute of Electrical 1-15 and Electronics Engineers: “Broadband microstrip array antennas” Digest of the Antennas and Propagation Society International Symposium. Seattle, WA Jun. 19-24, 1994. Abstract.
- Paolo Nenzi et al; “U-Helix: On-chip short conical antenna”, 2013 7th European Conference on Antennas and Propagation (EUCAP), ISBN:978-1-4673-2187-7, IEEE, Apr. 8, 2013, 5 pgs.
- Adamiuk G et al; “Compact, Dual-Polarized UWB-Antanna, Embedded in a Dielectric” IEEE Transactions on Antenna and Propagation, IEEE Service Center, Piscataway, NJ, US vol. 56, No. 2, ISSN: 0018-926X, abstract; Figure 1, Feb. 1, 2010, 8 pgs.
Type: Grant
Filed: Dec 30, 2014
Date of Patent: Jan 9, 2018
Patent Publication Number: 20160099758
Assignee: Energous Corporation (San Jose, CA)
Inventors: Douglas Bell (Pleasanton, CA), Michael Leabman (San Ramon, CA)
Primary Examiner: An Luu
Application Number: 14/586,261
International Classification: H02J 17/00 (20060101); H04B 5/00 (20060101); H02J 7/02 (20160101); H04L 12/10 (20060101); H04W 4/00 (20090101); H02J 7/00 (20060101); H02J 50/27 (20160101); H04W 12/08 (20090101);
