Patent Grant
10554052
The present disclosure relates generally to wireless power transmission.
Portable 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.
Although the use of wireless power transmission may significantly solve the problem of using wires or pads for charging devices, when a device fails in the system, the power transfer to an electronic device may be interrupted. Different causes may exist for a failure, including a loss of power, a failure in the hardware or software of a wireless power transmitter manager, overload of the wireless power transmitter manager, and malfunction in a wireless power receiver, among others. Constant monitoring may be needed in the wireless power transmission system to avoid a breakdown in the network. For the foregoing reasons, there is a need for a system and method for a self-system analysis that may search problems in the network and when it detects a problem, makes an analysis and at the same time makes a recommendation for enhancement or correction in the system.
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. 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, an apparatus for wirelessly providing power, comprises: a wireless power transmitter comprising a power transmitter manager, operatively coupled to the wireless power transmitter, wherein the power transmitter manager is configured to control power transmission signals to form three-dimensional pockets of energy for providing power from the wireless power transmitter to a receiver; a communication apparatus configured for communicating with a network; and a storage device operatively coupled to the wireless power transmission manager, the storage device being configured to store information for a device associated with the receiver that is registered with the network, and to communicate the information to a cloud.
In another embodiment, a method for wirelessly providing power in an apparatus, comprises: controlling, by a power transmitter manager of a wireless power transmitter, to form three-dimensional pockets of energy for providing power from the wireless power transmitter to a receiver; detecting, by the wireless power transmitter, a fault in at least one of the wireless power transmitter and the receiver; and transmitting, by a communication apparatus of the wireless power transmitter, the detected fault to a network.
In another embodiment, a system for wirelessly providing power, comprises: a server, communicatively coupled to each of a plurality of power sources via a network, wherein each of the power sources is configured to detect a fault in at least one of an associated wireless power transmitter and an associated receiver, the server being configured to receive at least one detected fault transmitted from the plurality of power sources, process the received detected fault, and provide a recommendation for correcting the received detected fault; wherein a respective one of the power sources comprises: the at least one associated wireless power transmitter; a power transmitter manager operatively coupled to the at least one associated wireless power transmitter, wherein the power transmitter manager is configured to control power transmission signals to form three-dimensional pockets of energy for providing power from the at least one associated wireless power transmitter to the associated receiver, and a communication apparatus configured for communicating with the network.
In a further embodiment, a processor-based system for managing a wireless power transmission system comprising at least one power transmitter, configured to generate pocket-forming energy in three dimensional space to at least one power receiver for charging, the processor-based system comprises: a processor; a database operatively coupled to the processor; and communications, operatively coupled to the processor, wherein the communications is operable to communicate with a network, wherein the processor is configured to receive system operation data from the at least one power transmitter via the network, wherein the system operation data comprises at least one of power transmitter status and power transmitter usage.
In another embodiment, A processor-based method for managing a wireless power transmission system comprising at least one power transmitter, configured to generate pocket-forming energy in three dimensional space to at least one power receiver for charging, the method comprises: configuring communications, operatively coupled to a processor and database, to communicate with a network; and receiving system operation data from the at least one power transmitter via the communications, wherein the system operation data comprises at least one of power transmitter status and power transmitter usage.
In a further embodiment, a processor-based system for managing a power system comprising at least one power transmitter, configured to generate pocket-forming energy in three dimensional space to at least one power receiver for charging, the processor-based system comprising: a processor; a database operatively coupled to the processor; and communications, operatively coupled to the processor, wherein the communications is operable to communicate with a network, that is further communicatively coupled to the at least one power transmitter configured with a wireless power transmitter manager, wherein the processor is configured to receive system operation data from the at least one power transmitter via the network, wherein the system operation data comprises at least one of power transmitter status and power transmitter usage.
In yet another embodiment, a wireless power transmission management system, comprises: at least one transmitter comprising an antenna array, the transmitter being configured to provide pocket-forming energy in three-dimensional space via the antenna array to at least one of a plurality of devices, the transmitter being further configured to communicate data to a network, wherein the data comprises at least one of transmitter data and device data; and a remote system manager operatively coupled to the network, wherein the remote system manager is configured to process the data communicated to the network to determine a status of the system.
In a further embodiment, a method for monitoring a wireless power system, comprises: providing, by a transmitter, pocket-forming energy in three-dimensional space to at least one of a plurality of devices, wherein the transmitter is coupled to a respective antenna array; and communicating, by the transmitter, data from the transmitter to a network, the data comprising at least one of transmitter data and device data; wherein the data communicated to the network is processed in a remote system manager, operatively coupled to the network, to determine a status of the wireless power system.
In another embodiment, a wireless power transmission system for monitoring the distribution of pocket-forming energy in three-dimensional space, comprises: at least one transmitter, comprising: an antenna array, wherein the transmitter is configured to provide the pocket-forming energy in three-dimensional space via the antenna array to at least one of a plurality of devices, an antenna manager configured to control power and direction angle of the antenna array, a storage configured to receive and store data comprising at least one of transmitter data and device data, and communications configured to communicate the stored data to a network; wherein a remote system manager is operatively coupled to the network, the remote system manager being configured to receive and process communicated data to determine a status of the wireless power transmission system and perform an action in response to the determined status.
In a further embodiment, a processor-based system for managing a wireless power transmission system comprising at least one power transmitter, configured to generate pocket-forming energy in three dimensional space to at least one power receiver, the processor-based system comprises: a processor; a database operatively coupled to the processor; and communications, operatively coupled to the processor, wherein the communications is operable to communicate with a network, wherein the processor is configured to receive system operation data from the at least one power transmitter via the network and to communicate the system operation data to a cloud, wherein the system operation data comprises at least one of power transmitter status, power transmitter usage, power receiver status, and power receiver usage.
In another embodiment, a processor-based method for managing a wireless power transmission system comprising at least one power transmitter, configured to generate pocket-forming energy in three dimensional space to at least one power receiver for charging, the method comprises: configuring, by a processor, communications operatively coupled to the processor and a database, to communicate with a network; receiving, by the processor, system operation data from the at least one power transmitter via the communications, wherein the system operation data comprises at least one of power transmitter status, power transmitter usage, power receiver status, and power receiver usage; and communicating, by the processor, the received system operation data to a client device for display using a graphical user interface (GUI).
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 locationmay 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. Systems and Methods for Managing and Controlling a Wireless Power Network (Basic)
In one embodiment, wireless power transmitter 1102 may include a microprocessor that integrates a power transmitter manager app 1108 (PWR TX MGR APP) as embedded software, and a third party application programming interface 1110 (Third Party API) for a Bluetooth Low Energy chip 1112 (BLE CHIP HW). Bluetooth Low Energy chip 1112 may enable communication between wireless power transmitter 1102 and other devices such as, client device 1104. In some embodiment, Bluetooth Low Energy chip 1112 may be utilize another type of wireless protocol such as Bluetooth®, Wi-Fi, NFC, and ZigBee. Wireless power transmitter 1102 may also include an antenna manager software 1114 (Antenna MGR Software) to control an RF antenna array 1116 that may be used to form controlled RF waves that act as power transmission signals that may converge in 3-d space and create pockets of energy on wireless power receivers. 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 receiver converting the transmitted energy to electrical power.
Power transmitter manager app 1108 may call third party application programming interface 1110 for running a plurality of functions such as starting a connection, ending a connection, and sending data among others. Third party application programming interface 1110 may command Bluetooth Low Energy chip 1112 according to the functions called by power transmitter manager app 1108.
Power transmitter manager app 1108 may also include a database 1118, which may store database comprising identification and attribute information of the wireless power transmitter 1102, of the receiver 1106, and of client devices 1104. Exemplary identification and attribute information includes identifiers for a client device 1104, voltage ranges for a client device 1104, location, signal strength and/or any relevant information from a client device 1104. Database 1118 may also store information relevant to the wireless power network such as, receiver ID's, transmitter ID's, end-user handheld devices, system management servers, charging schedules (information indicative of the scheduling of a charge time for the client device 1104), charging priorities and/or any data relevant to a wireless power network. Other examples of identification and attribute information include information indicative of level of power usage of one of the client device 1104; information indicative of power received at the receiver 1106 that is available to the client device 1104; and information of the duration of power usage of the client device.
Third party application programming interface 1110 at the same time may call power transmitter manager app 1108 through a callback function which may be registered in the power transmitter manager app 1108 at boot time. Third party application programming interface 1110 may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or a message is received.
Client device 1104 may include a power receiver app 1120 (PWR RX APP), a third party application programming interface 1122 (Third party API) for a Bluetooth Low Energy chip 1124 (BLE CHIP HW), and a RF antenna array 1126 which may be used to receive and utilize the pockets of energy sent from wireless power transmitter 1102.
Power receiver app 1120 may call third party application programming interface 1122 for running a plurality of functions such as start a connection, end the connection, and send data among others. Third party application programming interface 1122 may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or message is received.
Client device 1104 may be paired to an adaptable paired receiver 1106 via a BLE connection 1128. A graphical user interface (GUI 1130) may be used to manage the wireless power network from a client device 1104. GUI 1130 may be a software module that may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others. Client device 1104 may also communicate with wireless power transmitter 1102 via a BLE connection 1128 to send important data such as an identifier for the device as well as battery level information, antenna voltage, geographic location data, or other information that may be of use for the wireless power transmitter 1102.
A wireless power manager 1132 software may be used in order to manage wireless power network 1100. Wireless power manager 1132 may be a software module hosted in memory and executed by a processor inside a computing device 1134. The wireless power manager 1132 may include instructions to generate outputs and to receive inputs via a Graphical User Interface (GUI), so that a user 1136 may see options and statuses, and may enter commands to manage the wireless power network 1100. The computing device 1134 may be connected to the wireless power transmitter 1102 through standard communication protocols which may include Bluetooth®, Bluetooth Low Energy (BLE), Wi-Fi, NFC, and ZigBee®. Power transmitter manager app 1108 may exchange information with wireless power manager 1132 in order to control access and power transmission from client devices 1104. Functions controlled by the wireless power manager 1132 may include, scheduling power transmission for individual devices, priorities between different client devices, access credentials for each client, physical location, broadcasting messages, and/or any functions required to manage the wireless power network 1100.
Sequence diagram 1200 illustrates the interactions between objects or roles in a wireless powered network. The objects or roles described here may include, but is not limited to, a user 1202 which manages the wireless power network, a wireless power manager 1204 which serves as a front end application for managing the wireless power network, power receiver devices with corresponding power receiver apps 1206 and transmitters with corresponding power transmitter manager apps 1208.
The process may begin when wireless power manager 1204 requests 1210 information from a power transmitter manager app 1208 hosted in a wireless transmitter. Request 1210 may include authentication security such as user name and password. Power transmitter manager apps 1208 may then verify the request 1210 and grant access to the wireless power manager 1204.
Wireless power manager 1204 may continuously request 1210 information for different time periods in order to continue updating itself. Power transmitter manager app 1208 may then send database records 1212 to the wireless power manager 1204. Wireless power manager 1204 may then display 1214 these records with options in a suitable GUI to a user 1202. User 1202 may then perform different actions in order to manage the wireless power network. For example and without limitation, a user 1202 may configure powering schedules 1216 for different devices, the user 1202 may also establish priorities depending on time 1218, type of client 1220, physical location 1222 or may even choose to broadcast a message 1224 to client devices. The wireless power manager 1204 may then send 1226 the updated database records back to the power transmitter manager apps 1208.
In a wireless network power grid more than one transmitter may be used. Power transmitter manager apps 1208 hosted on each transmitter may share updates 1228 to the device database. Power transmitter manager apps 1208 may then perform an action 1230 depending on the command and updates made by the user 1202 such as, charge a wireless device, send a message to the wireless devices, set a schedule to charge different devices, set power priority to specific devices, etc.
B. System and Method for a Self-system Analysis in a Wireless Power Transmission Network
Under the control of wireless power transmitter manager 1302, the wireless power transmission system 1300 may transmit controlled RF waves that act as power transmission signals that may converge in 3-d space and create pockets of energy on wireless power receivers. 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 receiver converting the transmitted energy to electrical power.
Wireless power receiver 1304 may be paired with customer device 1306 or may be built into customer device 1306. Examples of customer devices 1306 may include laptop computer, smartphones, tablets, music players, and toys, among other. Customer device 1306 may include a graphical user interface 1312 (GUI). Wireless power transmitter manager 1302 may receive customer device's signal strength from advertisement emitted by wireless power receiver 1304 for detecting if wireless power receiver 1304 is paired with customer device and also for the purpose of detecting if wireless power receiver 1304 is nearer to wireless power transmitter manager 1302 than to any other wireless power transmitter manager 2902 in the wireless power transmission system 1300. Wireless power receiver 1304 may be defined as assigned to wireless power transmitter manager 1302, which may have exclusive control and authority to change the wireless power receiver's record in device database 1316 until wireless power receiver 1304 moves to a new location closer to another wireless power transmitter manager 1302. An individual copy of wireless power receiver's record may be stored in device database 1316 of each wireless power transmitter manager 1302 and also in each server of wireless power transmission system 1300, through a cloud (not shown in
According to some aspects of this embodiment, one or more servers (not shown in
Under the control of wireless power transmitter manager 1302, the wireless power transmission system 1300 may transfer power in a range up to 30 feet.
Wireless power transmitter manager 1302 may use, but is not limited to, Bluetooth low energy (BLE) to establish a communication link 1308 with wireless power receiver 1304 and a control link 1310 with customer device's graphical user interface (GUI). Wireless power transmitter manager 1302 may use control link 1310 to receive commands from and receive pairing information from customer device's graphical user interface (GUI).
Wireless power transmitter manager 1302 may include antenna manager software 1314 to track customer device 1306. Antenna manager software 1314 may use real time telemetry to read the state of the power received by customer device 1306.
According to some aspects of this embodiment, wireless power transmitter manager 1302 may include a device database 1316, where device database 1316 may store three sub-dimensions of data: past, present, and future. The future data may include customer devices 1306 power schedules. The present data may include the locations and/or movements in the system, configuration, pairing, errors, faults, alarms, problems, messages sent between the wireless power devices, and tracking information, among others. With reference to
In other situations, there can be multiple wireless power transmitter managers 1302 and/or multiple wireless power receivers 1304 for powering various customer devices 1306.
Each wireless power transmitter manager 1406 in wireless power transmission network 1400 may receive customer device's signal strength from advertisement emitted by wireless power receiver 1404 and graphical user interface 1408 (GUI) for the purpose of detecting if wireless power receiver 1404 is paired with graphical user interface 1408 (GUI) and also for detecting if wireless power receiver 1404 is nearer to wireless power transmitter manager 1406 than to any other wireless power transmitter manager 1406 in the wireless power transmission network 1400. Wireless power receiver 1404 may be defined as assigned to wireless power transmitter manager 1406, which may have exclusive control and authority to change the wireless power receiver's record in device database 1410 until wireless power receiver 1404 moves to a new location closer to another wireless power transmitter manager 1406. An individual copy of wireless power receiver's record may be stored in device database 1410 of each wireless power transmitter manager 1406 and also in each server 1414 of wireless power transmission network 1400, through a cloud 1416.
According to some aspects of this embodiment, one or more servers 1414 may function as a backup of device database 1410 in the wireless power transmission network 1400. Server 1414 may search devices in wireless power transmission network 1400. Server 1414 may locate device database 1410 through UDP packets that are broadcast when a given wireless power transmitter manager 1406 boots up. The UDP packet may include the UUID of wireless power transmitter manager 1406 and also its location. To back up a specific device database 1410, server 1414 may request access to a given wireless power transmitter manager 1406 in the network 1400. Server 1414 may establish a connection with wireless power transmitter managers 1406 and wireless power transmitter manager 1406 may accept the connection and wait for the first amount of data from server 1414. The first amount of data may be 128 bits UUID, once wireless power transmitter manager 1406 verifies the data, it may allow server 1414 to read a device database 1410. Server 1414 may backup device database 1410. Also wireless power transmitter manager 1406 may be able to reestablish its own device database 1410 from the information stored in server 1414. For example if a given wireless power transmitter manager 1406 experience a power interruption, resulting in a software restart or system boot up, it may broadcast a UDP packet to search any server 1414 in the network 1400. Once wireless power transmitter manager 1406 finds server 1414, it may establish a TCP connection to restore its own device database 1410.
Each wireless power transmitter manager in wireless power transmission network 1400 may include device database 1410. When a record change in a given device database 1410, this change may be distributed to all device databases 1410 in wireless power transmission network 1400.
Device database 1410 may store three sub-dimensions of data: past, present, and future. The future data may include customer devices 1402 power schedules. The present data may include the locations and/or movements in the system, configuration, pairing, errors, faults, alarms, problems, messages sent between the wireless power devices, and tracking information, among others. The past data may include details such as the amount of power customer device 1402 used, the amount of energy that was transferred to customer device's battery, and thus sold to the customer who has or owns the device, the amount of time customer device 1402 has been assigned to a given wireless power transmitter manager 1406, when did customer device 1402 start pairing with graphical user interface 1408 (GUI), activities in the system, any action or event of any wireless power device in the system, errors, faults, and design problems, among others, for each customer device 1402 in wireless power transmission network. Device database 1410 may also store customer device's power schedule, customer device's status, names, customer sign-in names, authorization and authentication credentials, encrypted information, areas, details running the system, and information about all wireless power devices such as wireless power transmitter managers, wireless power receivers, end user hand-held devices, and servers, among others.
Each wireless power device in wireless power transmission network 1400 may include a universally unique identifier (UUID). When a given wireless power transmitter manager 1406 boots up, and periodically thereafter, it may broadcast a user datagram protocol (UDP) packet that contains its unique UUID, and status to all devices in wireless power transmission network 1400. The UDP packet is only distributed through the local network. Each wireless power transmitter manager 1406 and server 1414 in wireless power transmission network may establish, but is not limited to, a Wi-Fi connection 1412 to share updated device database's records between other wireless power devices in the system, including such device database information as: quality control information, wireless power device's status, wireless power device's configuration, control, logs, schedules, statistics, and problem reports, among others.
In another aspect of this embodiment, any wireless power transmitter manager, besides using UDP packets to send information through wireless power transmission network 3200, may also use transmission control protocol (TCP) to exchange information outside the local network.
In another aspect of this embodiment, server 1414 and wireless power transmitter managers 1406 may be connected to a cloud 1416. Cloud 1416 may be used to share between wireless power devices any device database information, among others.
According to some aspects of this embodiment, each wireless power transmitter manager 1406 and server 1414 in the network may be connected to a business cloud 1420 through an internet cloud 1418. Business cloud 1420 may belong to a given business using a service provider to offer wireless power transfer to their users. Business cloud 1420 may be connected to a Business service provider server 1422. Business service provider server 1422 may store marketing information, customer billing, customer configuration, customer authentication, and customer support information, among others.
Internet cloud 1418 may be also connected to a service provider cloud 1424. Service provider cloud 1424 may store marketing and engineering information, such as less popular features, errors in the system, problems report, statistics, and quality control, among others.
Each wireless power transmitter manager 1406 may periodically establish a TCP connection with business cloud 1420 and service provider cloud 1424 to send its respective device database 1410.
In a different aspect of this embodiment, each wireless power transmitter manager 1406 in wireless power transmission network 1400 may be able to detect failures in the network. Example of failure in the network may include overheating in any wireless power transmitter manager 1406, malfunction, and overload, among others. If a failure is detected by any of wireless power transmitter manager 1406 in the system, then the failure may be analyzed by any wireless power transmitter manager 1406 in the system. After the analysis is completed, a recommendation may be generated to enhance or correct the system. The recommendation may be sent through cloud 1416 to business service provider server 1422 and also to service provider cloud 1424. Service provider cloud 1424 may use the recommendation as quality control, engineering control, and to generated statistics, among others. Also the recommendation may be communicated to the person in charge of managing wireless power transmission network 1400 by text messages or E-mail. Also any device in the network with a copy of device database 1410 may be able to perform an analysis and generate a recommendation to enhance or correct the system.
In another aspect of this embodiment, each wireless power transmitter manager 1406 may send an alert message for different conditions, where wireless power transmitter manager 1406 may include a LED, which blinks for indicating under which conditions wireless power transmitter manager 1406 may be working.
In another aspect of this embodiment, wireless power transmitter manager 1406 may be able to detect failures on its own performance. If wireless power transmitter manager 1406 detects a failure, the analysis may be performed locally by wireless power transmitter manager 1406. After the analysis is completed, a recommendation may be generated to enhance or correct the system. Then wireless power transmitter manager 1406 may send the information through cloud 1416 to business service provider server 1422 and service provider cloud 1424. Also the recommendation may be communicated to the person in charge of managing wireless power transmission network 1400 by text messages or E-mail.
In a wireless power transmission network, multiple wireless power transmitter managers and/or multiple wireless power receivers may be used for powering various customer devices.
Each wireless power transmitter manager in the system may scan the wireless power transmission network, at step 1502. Each wireless power transmitter manager in wireless power transmission network may receive customer device's signal strength from advertisement emitted by a wireless power receiver and a graphical user interface (GUI) for the purpose of detecting if wireless power receiver is paired with graphical user interface (GUI) and also for detecting if wireless power receiver is nearer to wireless power transmitter manager than to any other wireless power transmitter manager in the wireless power transmission network. Wireless power receiver may be defined as assigned to wireless power transmitter manager, which may have exclusive control and authority to change the wireless power receiver's record in device database until wireless power receiver moves to a new location closer to another wireless power transmitter manager. An individual copy of wireless power receiver's record may be stored in device database of each wireless power transmitter manager and also in each server of wireless power transmission network, through a cloud.
According to some aspects of this embodiment, one or more servers may function as a backup of the device database in the wireless power transmission network. The servers and wireless power transmitter managers in the wireless power transmission network may be connected to the cloud. The cloud may be used to share between system devices: quality control information, statistics, and problem reports, among others.
Wireless power transmitter manager may search for wireless power receivers to communicate with and send power. A wireless power receiver may be paired with customer device or may be built in customer device. 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).
Wireless power transmitter manager may be able to detect failures in the wireless power transmission network, at step 1504. Examples of failure may include loss of power, failure in the hardware or software of the wireless power transmitter manager, malfunction in a wireless power transmitter manager, and overload of the wireless power transmitter manager, and malfunction in a wireless power receiver, overheating or other environmental problems, and intrusion, among others.
If wireless power transmitter manager detects a failure in the wireless power transmission network, it may update its device database to register the failure, at step 1506. Each wireless power transmitter manager in wireless power transmission network may include a device database, where device database may store three sub-dimensions of data: past, present, and future. The future data may include customer devices power schedules. The present data may include the locations and/or movements in the system, configuration, pairing, errors, faults, alarms, problems, messages sent between the wireless power devices, and tracking information, among others. The past data may include details such as the amount of power customer device used, the amount of energy that was transferred to customer device's battery, and thus sold to the customer who has or owns the device, the amount of time customer device has been assigned to a given wireless power transmitter manager, when did customer device start pairing with the graphical user interface (GUI), activities in the system, any action or event of any wireless power device in the system, errors, faults, and design problems, among others, for each customer device in wireless power transmission network. Device database may also store customer device's power schedule, customer device's status, names, customer sign-in names, authorization and authentication credentials, encrypted information, areas, details running the system, and information about all wireless power devices such as wireless power transmitter managers, wireless power receivers, end user hand-held devices, and servers, among others.
When a record changes in a given device database, this change may be distributed to all device databases in wireless power transmission network.
Subsequently, wireless power transmitter manager may analyze the failure in the wireless power transmission network, at step 1508. In another aspect of this embodiment the failure may be analyzed by any device in the wireless power transmission network with a copy of device database.
After the analysis is completed, a recommendation may be generated to enhance or correct the system, at step 1510.
Wireless power transmitter manager may send the recommendation to a business service provider server and also to service provider cloud, at step 1512. Service provider cloud may use the recommendation as quality control, engineering control, and to generated statistics, among others. Also the recommendation may be communicated to the person in charge of managing wireless power transmission network by text messages or E-mail.
Else wireless power transmitter manager may continue scanning the wireless power transmission network, at step 1514.
Examples
Example #1 is a wireless power transmission network with components similar to those described in
III. Status and Usage
A. Systems and Methods for Tracking the Status and Usage Information of a Wireless Power Transmission System
According to some embodiments, wireless power transmission system architecture 1600 may include a multiple wireless power transmission systems 1602 which may be able to transmit information to a remote information service 1604 through an internet cloud 1606. In some embodiments, a multiple wireless power transmission system 1602 may include one or more wireless power transmitters 1608, zero or more computing device 1620 coupled with wireless power receivers 1610, zero or more non-computing devices 1632 coupled with wireless power receivers 1610, a system management service 1612, and a local network 1614. Network 1614 connections may refer to any suitable connection between computers such as intranets, local area networks (LAN), virtual private networks (VPN), wireless area networks (WAN), and the internet, among others.
According to some embodiments, each wireless power transmitter 1608 may include a wireless power transmitter manager 1616 and a distributed system database 1618. Each wireless power transmitter 1608 may be able to manage and transmit power to one or more wireless power receivers 1610, and each wireless power receiver 1610 may be able to charge and provide power to computing devices 1620 and/or non-computing devices 1632. Examples of suitable computing devices 1620 may include smartphones, tablets, notebooks, and laptops, amongst others. Examples of suitable non-computing devices 1632 may include toys, toothbrushes, LED lights, game remote controls, and music players, amongst others.
Wireless power transmitter manager 1616 may be able to control the behavior of wireless power transmitters 1608, monitoring different aspects, such as the started time of power transmission, the unique system identification of both wireless power transmitter 1608 and wireless power receiver 1610, the amount of devices connected, the direction angle of the antennas used, as well as, the voltage at wireless power receiver 1610's antenna may be reported; and the real-time communication connection between wireless power transmitter 1608 and wireless power receiver 1610, which may be used for tracking information from wireless power receiver 1610 no matter where it is located or moved; among others.
According to some embodiments, distributed system database 1618 may record relevant information from wireless power receivers 1610 within computing devices 1620/non-computing devices 1632, wireless power transmitter 1608, and system management service 1612. Information may include but is not limited to identifiers for computing devices 1620/non-computing devices 1632, voltage ranges for computing devices 1620/non-computing devices 1632, location, signal strength, wireless power receiver 1610 ID's, wireless power transmitter 1608 ID's, end-user handheld device names ID's, system management server ID's, charging schedules, charging priorities, and/or any data relevant to multiple wireless power transmission system 1602. Additionally, wireless power transmitters 1608, wireless power receiver 1610 within computing devices 1620/non-computing devices 1632 and system management service 1612 may operate as system information generator.
System management service 1612 may automatically monitor the database integrity of each computing devices 1620, and may automatically communicate with a computing devices 1620 to correct a detected error in its database. System management service 1612 may include components, such as a system management server 1634, a system management manager 1636, and a system management database 1638.
Distributed system database 1618 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.
In some embodiments, wireless power transmitters 1608 may use network 1614 to send and receive information. Network 1614 may be a local area network, or any suitable communication system between the components of the multiple wireless power transmission system 1602. Network 1614 may enable communication between two or more wireless power transmitters 1608, the communication of wireless power transmitters 1608 with system management service 1612, and may facilitate the communication between multiple wireless power transmission system 1602 and remote information service 1604 through internet cloud 1606, amongst others.
Remote information service 1604 may be operated by the owner of the system, the manufacturer or supplier of the system, or a service provider. Remote information service 1604 may include different components, such as a back-end server 1622, a remote information service manager 1624, and a general remote information service database 1626. Back-end server 1622 and remote information service manager 1624 may be included into a single physical or virtual server. Remote information service database 1626 may include information data in a format or form discernible by remote information service 1604, possibly in encrypted form. Additionally, wireless power transmitter 1608, computing device 1620 and system management service 1612, may generate usage and status information in a format or form discernible by remote information service 1604, possibly in encrypted form. Remote information service database 1626 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.
Wireless power transmission system architecture 1600 may also include different authorized computing devices 1628, which may access remote information service 1604 through internet cloud 1606 in order to collect and store information about the status and usage of multiple wireless power transmission system 1602. The computing devices 1628 may be owned by system owner, manufacturer of system, or client for fee based distribution of status and usage information. The authorized computing devices 1628 may be operated by suitable users (e.g. clients, manufacturers or suppliers of the system) in order to determine if the multiple wireless power transmission system 1602 is operating correctly (or as expected) or has problems, as well as, to observe how the system is being used by users for marketing or customer service purposes. The collected information may be reported or edited by the authorized computing devices 1628 through a user interface 1630, which may display different functions, and which may be a web site or other. The collected information may be provided in return for a fee.
The computing devices and the software modules within the multiple wireless power transmission system, may interact with each other through a suitable network connection. Network connections may refer to any suitable connection between computers such as intranets, local area networks (LAN), virtual private networks (VPN), wireless area networks (WAN), and the internet, among others.
According to one or more embodiments, process 1700 may start whenever a client computing device operated by a user, is connected to the multiple wireless power transmission system software (e.g. application software), at step 1702. Specifically, the client computing device may initially download and install the multiple wireless power transmission system software from a public or private application store, where the application software may run on any computing device with operating system, such as iOS, Android, and Microsoft Windows, among others. Examples of computing devices may include smartphones, tablets, laptops, music players, and any other computing device.
Once the client computing device is connected to the multiple wireless power transmission system, users may interact with the multiple wireless power transmission system through a user interface displayed on the suitable client computing devices, at step 1704. Users interface may allow users to interact with the multiple wireless power transmission system through different options, such as the selection of a computing device to be charged, monitor the status of charge of one or more wireless power receiver, and create a schedule charge for one or more wireless power receiver, report the time when transmission ended, and the 7 total energy or power that was transmitted and received, among others.
The process may continue with step 1706, where the system information generator may establish communication with the remote information server. Specifically, the remote information server may be located within the internet cloud or at a physical premises, and may be one or more discreet or virtual computer systems. Additionally, the system information generator may generate and store the information regarding the status and usage of the multiple wireless power transmission system within the distributed system database. Information may include but is not limited to, how all components of the system are used; the present status of the system; other categories of information including but is not limited to, errors, faults, problems, trouble reports, logs of operational events, each command issued by each user, user configurations, amount of power transmitted per power transmitter and per power receiver, metrics of all software and hardware activity, values measured or read from hardware of the system, metrics and details of every automatic operation performed by the system software, description and details of present and past location of all client computing devices and power receivers of the system, details of transmitter communications transitions (i.e. transfer of communications and/or control of power receiver from one power transmitter unit to another), all user scheduled configuration, all identifications of all system components, all software defined version labels for system components; and the present and past information for all of the above, times of occurrence, and identification of each associated system component for each of the above, among others.
The distributed system database 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 software within the system information generator component that manages the distributed system database may automatically establish a secured or encrypted communication connection to verify the credentials of the remote information service, at step 1708 via ID code. If the remote information service' credentials are verified, the system information generator may transmit the information data to the remote information service, at step 1710. However, if connection cannot be established with the remote information service, the disclosed system information generator may try again at a later time until the information data has been successfully sent to the remote information service.
Whenever the system information generator generates any information data to be stored in the distributed system database, the system information generator may create a system information record, at step 1712, which may include information data in a format or discernible form by the remote information service, possibly in encrypted form. Subsequently, when the information on demand is stored in the distributed system database, the remote information service may receive the information that may come from the system information generator, at step 1714. Once the information on demand has been successfully received, remote information service replies with an acknowledgment message to system information generator, at step 1716. The information may be stored within a remote information service database. Additionally, the remote information manager within the remote information service may be responsible to execute some actions, such as update information, receive information, store information, and send information to computing devices.
The process may continue at step 1718, where once the information on demand has been successfully transmitted, the system information generator may delete the old disposable record of what it just sent to the remote information service from its local copy of the distributed system database in order to not overrun beyond its data storage capacity.
Finally, the authorized client computing device with the validated credentials may download the information from the remote information service, at step 1720, and then the authorized client computing device may report and/or edit the information on demand, at step 1722 from the multiple wireless power transmission system.
The information may be used for different purposes such as for the observation or verification of past or present expected system status or operation, and system configuration; for the purpose of rapidly detecting and responding to problems, trouble, issues, errors, or faults within the system; for information including but not limited to statistics or metrics describing how the system features are in use for the purpose of increased accuracy of strategic marketing and sales focus; and for information required for billing end users, of the multiple wireless power transmission system, for power received.
Examples
Example #1 is an embodiment of a wireless power transmission system where a wireless power transmitter transmits power to a wireless power receiver to charge a client device attached to the receiver. After the transmission of power, the transmitter, also being a system information generator, establishes a communication connection with a remote information service, which may be Internet cloud based. The transmitter then communicates the detailed usage of the system in transmission of power from the transmitter through the receiver to the client device. The information service communicates an acknowledgement back to transmitter, and transmitter then deletes the usage information that was sent, to prevent transmitter's memory or database from overflowing. The information service may then distribute or provide for a fee the information to a user or computing device of another party.
The disclosed information may include, but is not limited to, the time when power transmission started, the unique system identification of both power transmitter and power receiver, the amount and direction angle of antennas used; as well as, the voltage at the power receiver's antenna reported by the power receiver to the power transmitter through the real-time communication connection between the transmitter and the receiver that is used for tracking the receiver no matter the receiver's location or movement.
B. Systems and Methods for Communication with Remote Management Systems
Power transmitters 1802 may transmit controlled Radio Frequency (RF) waves which may converge in 3-D space. 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 that may be 3-dimensional in shape whereas null-spaces may be present outside the constructive interference patterns.
According to exemplary embodiments, power transmitters 1802 may include a power transmitter manager application 1810, a third party Bluetooth Low Energy (BLE) API 1812, a BLE chip 1814, an antenna manager software 1816 and an antenna array 1818 among other components. Power transmitter manager application 1810 may be an executable program loaded into a non-volatile memory within a power transmitter 1802. Power transmitter manager application 1810 may control the behavior of power transmitter 1802, monitor the state of charge of electronic devices 1806, electronic devices 1808 and power receivers 1804, may keep track of the location of power receivers 1804 and may execute power schedules, amongst others. In some embodiments, power transmitters 1802 may include a distributed wireless power transmission system database (not shown in figure) for storing information related to power receivers 1804, electronic devices 1806, power status, power schedules, IDs, pairing and any suitable information necessary for running the system.
Third party BLE API 1812 may enable the effective interaction between power transmitter manager application 1810 and BLE chip 1814. Antenna manager software 1816 may process orders from power transmitter manager application 1810 and may control power and direction angle of antenna array 1818.
Antenna arrays 1818 that may be included in power transmitters 1802 may include a number of antenna elements capable of transmitting power. In some embodiments, antenna array 1818 may include from up to 2612 antenna elements which may be distributed in an equally spaced grid. In one embodiment, antenna array 1818 may have an 8×8 grid to have a total of 64 antenna elements. In another embodiment, antenna array 1818 may have a 16×16 grid to have a total of 256 antenna elements. In another embodiment, antenna array 1818 may have a total of 512 antenna elements. However, the number of antenna elements may vary in relation with the desired range and power transmission capacity of power transmitter 1802. Generally, with more antenna elements, a wider range and higher power transmission capacity may be achieved. Alternate configurations may also be possible including circular patterns or polygon arrangements, amongst others.
The antenna elements of antenna array 1818 may include suitable antenna types for operating in frequency bands such as 900 MHz, 2.5 GHz, 38.250 GHz, or 38.8 GHz, antenna elements may operate in independent frequencies, allowing a multichannel operation of pocket-forming.
Power transmitter 1802 may additionally include other suitable communications methods such as Wi-Fi, ZigBee and LAN amongst others.
Power receivers 1804 may include a power receiver application 1820, a third party BLE API 1812, a BLE chip 1814, and a power reception antenna array 1822. Power receivers 1804 may be capable of utilizing pockets of energy produced by power transmitter 1802 for charging or powering electronic devices 1806 and electronic devices 1808. Power receiver application 1820 may be an executable program loaded into a non-volatile memory within a power receiver 1804.
Third party BLE API 1812 may enable the effective interaction between power receiver application 1820 and BLE chip 1814. Antenna array 1822 may be capable of harvesting power from pockets of energy.
Electronic devices 1806 and electronic devices 1808 may include a GUI for managing the wireless power system architecture 1800. The GUI may be associated with an executable program loaded into a non-volatile memory. In some embodiments, electronic devices 1806 and electronic devices 1808 may include a distributed wireless power transmission system database (not shown in figure) for storing information related to power receivers 1804, power status, power schedules, IDs, pairing and any suitable information necessary for running the system.
In some embodiments, wireless power system architecture 1800 may include multiple power transmitters 1802 and/or multiple power receivers 1804 for charging a plurality of electronic devices 1806. In systems including multiple power transmitters 1802, the two or more power transmitters may be in constant communication using any suitable communication channel available, including Bluetooth®, BLE, Wi-Fi, ZigBee, LAN, LTE and LTE direct amongst others.
According to some embodiments, wireless power transmission system network 1900 may include multiple wireless power transmission systems 1902 capable of communicating with a remote management system 1904 through internet cloud 1906.
In some embodiments, wireless power transmission system 1902 may include one or more wireless power transmitters 1908, one or more power receivers 1910, one or more backup servers 1912 and a local network 1914.
According to some embodiments, each power transmitter 1908 may include a wireless power transmitter manager 1916 and a distributed wireless power transmission system database 1918. Each power transmitter 1908 may be capable of managing and transmitting power to one or more power receivers 1910, where each power receiver 1910 may be capable of charging or providing power to one or more electronic devices 1920.
Power transmitter managers 1916 may control the behavior of power transmitters 1908, monitor the state of charge of electronic devices 1920, and power receivers 1910, may keep track of the location of power receivers 1910 and may execute power schedules, run system check-ups and keep track of the energy provided to each of the different electronic devices 1920, amongst others.
According to some embodiments, database 1918 may store relevant information from electronic devices 1920 such as, identifiers for electronic devices 1920, voltage ranges for electronic devices 1920, location, signal strength and/or any relevant information from electronic devices 1920. Database 1918 may also store information relevant to the wireless power transmission system 1902 such as, receiver ID's, transmitter ID's, end-user handheld device names ID's, system management server ID's, charging schedules, charging priorities and/or any data relevant to a power transmission system network 1900.
Additionally, in some embodiments, database 1918 may store data of past and present system status.
The past system status data may include details such as the amount of power delivered to an electronic device 1920, the amount of energy that was transferred to a group of electronic devices 1920 associated with a user, the amount of time an electronic device 1920 has been associated to a wireless power transmitter 1908, pairing records, activities within the system, any action or event of any wireless power device in the system, errors, faults, and configuration problems, among others. Past system status data may also include power schedules, names, customer sign-in names, authorization and authentication credentials, encrypted information, physical areas of system operation, details for running the system, and any other suitable system or user-related information.
Present system status data stored in database 1918 may include the locations and/or movements in the system, configuration, pairing, errors, faults, alarms, problems, messages sent between the wireless power devices, and tracking information, among others.
According to some exemplary embodiments, databases 1918 within power transmitters 1908 may further store future system status information, where the future status of the system may be forecasted or evaluated according to historical data from past system status data and present system status data.
In some embodiments, records from all device databases 1918 in a wireless power transmission system 1902 may also be stored and periodically updated in server 1912. In some embodiments, wireless power transmission system network 1900 may include two or more servers 1912.
In another exemplary embodiment, wireless power transmitters 1908 may further be capable of detecting failures in the wireless power transmission system 1902. Examples of failures in power transmission system 1902 may include overheating of any component, malfunction, and overload, among others. If a failure is detected by any of wireless power transmitters 1908 within the system, then the failure may be analyzed by any wireless power transmitter manager 1916 in the system. After the analysis is completed, a recommendation or an alert may be generated and reported to owner of the power transmission system or to a remote cloud-based information service, for distribution to system owner or manufacturer or supplier.
In some embodiments, power transmitters 1908 may use network 1914 to send and receive information. Network 1914 may be a local area network, or any suitable communication system between the components of the wireless power transmission system 1902. Network 1914 may enable communication between power transmitters, the communication of power transmitters with server 1912, and may facilitate the communication between power transmission system 1902 and remote management system 1904, amongst others.
According to some embodiments, network 1914 may facilitate data communication between power transmission system 1902 and remote management system 1904 through internet cloud 1906.
Remote management system 1904 may be operated by the owner of the system, the manufacturer or supplier of the system or a service provider. Remote management system may include business cloud 1922, remote manager 1924 and backend server 1926, where the remote manager 1924 may further include a general database 1928. Functionality of backend server 1926 and remote manager 1924 can be combined into a single physical or virtual server.
General database 1928 may store additional backups of the information stored in the device databases 1918. Additionally, general database 1928 may store marketing information, customer billing, customer configuration, customer authentication, and customer support information, among others. In some embodiments, general database 1928 may also store information, such as less popular features, errors in the system, problems report, statistics, and quality control, among others.
Each wireless power transmitter 1908 may periodically establish a TCP communication connection with remote manager 1924 for authentication, problem report purposes or reporting of status or usage details, among others.
Then, the server within the wireless power transmission system may run a system check-up 2004. In this step, the server within the wireless power transmission system may check for any present failure, error or abnormal function of any system or subsystem components. Additionally, the server within the wireless power transmission system may check and perform an evaluation of the current system configuration.
Afterwards, the system may generate present status report 2006 and future status report 2008. Present status report may include any present failure, error or abnormal function of any system or subsystem components; a list of presently online end-users and devices, current system configuration and power schedules, amongst others.
Future status report 2008 may include forecasts based on the extrapolation or evaluation of past and present system status reports. For example, the system may be able to extrapolate possible impending sub-system component failure based on logged past behavior of sub-system components. The system may also be able to evaluate the power schedules and determine if any device will be out of energy according to historical power consumption and current power schedule.
In some embodiments, the system may further evaluate the system configuration to check if any configuration set by an operator or end-user may cause an unwanted system behavior. Such will be reported using the same techniques described above.
Then, the wireless power transmitters may evaluate 2010 if an alert is needed. If an alert is needed, the alert may be immediately generated and sent 2012. Depending of the type of problem detected, the alerts may be sent to the end-users, the system's owner, the service provider or any suitable combination, or to a remote system manager which can distribute a description of this urgent situation to customer service or other personnel via email, text message, or synthesized voice telephone call, according to alert configuration records stored within general database.
After the alert has been sent or if there is no alert needed, the server within the wireless power transmission system executing the report generation algorithm described in
Then, using a suitable TCP/IP connection the reports may be sent 2016 to a remote system manager for further evaluation. In some embodiments, the system may receive 2018 feedback from the remote system manager to indicate verification and storage of any received information.
Then, the system may generate 2104 a logged usage report which may include logged usage details and wireless energy consumption details. The wireless energy consumption details may include the amount of power delivered to each device and total amount of power delivered to the devices associated with each end user.
In some embodiments, the logged usage report may be used to compute power bills to charge end-users for the amount of wireless power received during a given time period.
Then, the system may generate 2106 an automatic actions report which may include automatic actions performed by or over any of the system components, including all power transmitters, power receivers, and any system management GUI.
Subsequently, the system may generate 2108 a location and movement report, which may include the location and movement tracking details of power receivers relative to power transmitters in the system.
After the reports have been generated the system may assemble past status report 2100 and update 2110 the database.
Then, using a suitable TCP/IP connection the reports may be sent 2112 to a remote system manager for further evaluation. In some embodiments, the system may receive 2114 feedback from the remote system manager to indicate verification and storage of any received information.
Additionally, the system may check 2208 the state of charge all the electronic devices within the system. If any electronic device within the system is in urgent need 2210 of charge the system may generate and send 2212 an alert. The alert may be sent to the users in form of text messages, emails, voice synthesis telephone communication or any other suitable means.
In some embodiments, whenever an electronic device has a minimum amount of energy left the system may be capable of contacting the end-user to make the end user aware of the current state of charge of the electronic device.
After the reports have been generated the system may assemble present status report 2200 and update 2214 the database.
Then, using a suitable TCP/IP connection the reports may be sent 2216 to a remote system manager for further evaluation. In some embodiments, the system may receive 2218 feedback from the remote system manager to indicate verification and storage of any received information.
Afterwards, the system may perform 2306 a system configuration analysis, in which the system may evaluate any configuration set by the system operator or end-user to determine if it may cause any unwanted system behavior.
Then, if a problem was found 2308 in any of the first 3 steps, the system may generate a suitable alert 2310. If an alert is sent to an end-user or system operator it may be in the form of text messages, emails, voice synthesis telephone communication or any other suitable means. In some embodiments, the system provider may be contacted by similar means.
Afterwards, the system may assemble future status report 2300 and update 2312 the database.
Subsequently, using a suitable TCP/IP connection the reports may be sent 2314 to a remote system manager for further evaluation. In some embodiments, the system may receive 2318 feedback from the remote system manager to indicate verification and storage of any received information.
Examples
In example #1 a wireless power transmission system generates a general status report as described in
In example #2 a wireless power transmission system generates a general status report as described in
In example #3 a wireless power service provider utilizes the past status reports generated by wireless power delivery system over the past 30 days to compute bills and charge end-users for their wireless power consumption.
In example #4 an end-user's electronic device requests wireless power. The wireless power transmitter utilizes a suitable TCP/IP connection to communicate with a remote system manager and authenticate the end-user's credentials. The credentials of the end-user are authenticated and the electronic device is charged.
C. Status and Usage Embodiment (Graphical User Interface Demo)
Referring further to
Remote information service manager 1624 can generate records of the received system operation data, and can generate analyses of the system operation data. For example, the remote information service manager can generate statistics, data tables, charts, maps (e.g. local, regional, national, and international maps), financial analyses, data correlation analyses, and trend analyses. Remote information services manager 1624 can communicate records and analyses of the system operation data to client devices 1628 for display using a graphical user interface (GUI) 1630. Client devices 1628 may include computing devices 1620 that are paired with power receivers 1610 for charging using pocket-forming energy in the wireless power transmission system, and may include workstations that are not paired with receivers.
Examples of system operation data, or status and usage data, received by the remote information service 1604 include errors, faults, trouble reports, logs of operational events, a command issued by the at least one power receiver, power receiver and power transmitter hardware configurations, amount of power transmitted per power transmitter and per power receiver, metrics of software and hardware activity, metrics of automatic operation performed by system software, location of the at least one power receiver, a transmitter communications transition, and power receiver charge scheduling configuration.
Other examples of status and usage data received by the remote information service 1604 include data pertaining to client devices (such as computing devices 1620 and non-computing device 1632) that are registered with remote information service 1604 and that are paired with receivers 1610. Examples of such status and usage information include battery level information, receiver antenna voltage, client device geographic location data, client device hardware configurations, metrics of client device charging activity, and client device charge scheduling.
Two functions of the wireless power management system are to track and report the status of transmitters, receivers, and devices within the network, and to track usage of the charging service by various devices and receivers. The wireless power management system collects and analyzes the status and usage data, and provides a variety of analytics to system operators and authorized users.
An exemplary category of status and usage data involves measurement and reporting of energy harvested by a device from a wireless power receiver. In an embodiment, energy is harvested from a wireless power receiver by conversion of energy conveyed by power transmission signals such as RF waves, into electrical energy that is transmitted as direct current to a client device. This measurement in the wireless power system is analogous to an energy meter. In one embodiment, each receiver has non-volatile memory, which accumulates data on total energy harvest over time. Using BLE, receivers send response messages to the transmitter at 2200 times per second. Each time the receiver receives a BLE communication or energy wave from the transmitter, it records the spot power it harvests from the energy pocket and delivers to the device. The receiver counts number of power readings per second, and once a second sums the power transfer readings, providing a measurement of energy. The receiver IC then updates non-volatile memory with the latest energy measurement.
The wireless power management system continually uploads status and usage data from receivers, from transmitters, and from devices to the cloud-based management 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 this data for all receivers that it communicates with. Periodically, the transmitter uploads accumulated energy information to the cloud-based management system. By this means, the wireless power management system collects information on energy received by all receivers worldwide.
If given receivers move out of communication range from a transmitter, the information accumulated in non-volatile memory is available for later communication to a transmitter once in range. In addition, the information accumulated by the non-volatile memory can be made available to a user of the given device, e.g. to provide a report of his wireless energy harvest over time. Furthermore, enterprises with an information on energy harvest of all users would have access to this information collected from the respective devices.
This measurement of total energy harvest is used in the first instance to measure how much wireless power is being transferred. This data can be used to improve transmitter operation, for billing, and for other system management functions. For example, information on the energy received by assigned receivers from a given transmitter is used as feedback to the transmitter on the efficiency of power transfer. The transmitter may act on this information to adjust the phase and gain of its antennas in order to maximize the amount of harvested energy.
In the system 2400 of
Remote information service 2402 may comprise a business cloud that is accessible via through an internet cloud 2408 using web server 2416. The operator/user may browse the specific URL or IP address associated to configuration GUI web pages provided by web service software 2412 operating within remote information service 2402. GUI web pages may provide status and usage information stored in database 2410 of the remote information service 2402. Web service software 2412 may use JavaScript or other suitable method for serving web pages, through embedded web, Apache, Internet Information Services (IIS), or any other suitable web server application.
The operator/user may obtain a specific URL or IP address associated to remote information service 2402 from some suitable source. The operator/user may use computer device 2406 with a suitable operating system such as Microsoft Windows, Apple iOS, Android or Linux, among others, to browse configuration GUI web pages 2414 using a standard web browser such as Chrome, Firefox, Internet Explorer, or Safari, among others, via an input device such as a touch screen, a mouse, a keyboard, a keypad, and others.
Another format of status and usage reporting uses the form factor for PDAs and other mobile devices.
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 rearranged. 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.
This application is a continuation of U.S. patent application Ser. No. 14/748,101, filed on Jun. 23, 2015, which is a continuation of U.S. patent application Ser. No. 14/585,271, filed on Dec. 30, 2014 (U.S. Pat. No. 9,867,062), which is a continuation-in-part of U.S. Non-Provisional patent application Ser. No. 14/337,002, filed Jul. 21, 2014 (U.S. Pat. No. 9,838,083), each of which is herein fully incorporated by reference in its respective entirety. This application is also a continuation of U.S. patent application Ser. No. 14/587,025, filed on Dec. 31, 2014, which is a continuation-in-part of U.S. patent application Ser. No. 14/330,931, filed on Jul. 14, 2014; and is also a continuation-in-part of U.S. patent application Ser. No. 14/330,936, filed on Jul. 14, 2014, each of which is herein fully incorporated by reference in its respective entirety. This application relates to U.S. Non-Provisional patent application Ser. No. 13/891,430, filed May 10, 2013; U.S. Non-Provisional patent application Ser. No. 13/925,469, filed Jun. 24, 2013; U.S. Non-Provisional patent application Ser. No. 13/946,082, filed Jul. 19, 2013; U.S. Non-Provisional patent application Ser. No. 13/891,399, filed May 10, 2013; U.S. Non-Provisional patent application Ser. No. 13/891,445, filed May 10, 2013; U.S. Non-Provisional patent application Ser. No. 14/465,532, filed Aug. 21, 2014; U.S. Non-Provisional patent application Ser. No. 14/286,129, filed May 23, 2014; U.S. Non-Provisional patent application Ser. No. 14/272,039, filed May 7, 2014; U.S. Non-Provisional patent application Ser. No. 14/272,066, filed May 7, 2014; U.S. Non-Provisional patent application Ser. No. 14/272,124, filed May 7, 2014; U.S. Non-Provisional patent application Ser. No. 14/583,625, filed Dec. 27, 2014; U.S. Non-Provisional patent application Ser. No. 14/583,630, filed Dec. 27, 2014; U.S. Non-Provisional patent application Ser. No. 14/583,634, filed Dec. 27, 2014; U.S. Non-Provisional patent application Ser. No. 14/583,640, filed Dec. 27, 2014; U.S. Non-Provisional patent application Ser. No. 14/583,641, filed Dec. 27, 2014; U.S. Non-Provisional patent application Ser. No. 14/583,643, filed Dec. 27, 2014, each of which is incorporated herein by reference in its respective entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 787412 | Tesla | Apr 1905 | A |
| 2811624 | Haagensen | Oct 1957 | A |
| 2863148 | Gammon et al. | Dec 1958 | A |
| 3167775 | Guertler | Jan 1965 | A |
| 3434678 | Brown et al. | Mar 1969 | A |
| 3696384 | Lester | Oct 1972 | A |
| 3754269 | Clavin | Aug 1973 | A |
| 4101895 | Jones, Jr. | Jul 1978 | A |
| 4360741 | Fitzsimmons et al. | Nov 1982 | A |
| 4944036 | Hyatt | Jul 1990 | A |
| 4995010 | Knight | Feb 1991 | A |
| 5200759 | McGinnis | Apr 1993 | A |
| 5211471 | Rohrs | May 1993 | A |
| 5548292 | Hirshfield et al. | Aug 1996 | A |
| 5556749 | Mitsuhashi et al. | Sep 1996 | A |
| 5568088 | Dent et al. | Oct 1996 | A |
| 5646633 | Dahlberg | Jul 1997 | A |
| 5697063 | Kishigami et al. | Dec 1997 | A |
| 5712642 | Hulderman | Jan 1998 | A |
| 5936527 | Isaacman et al. | Aug 1999 | A |
| 5982139 | Parise | Nov 1999 | A |
| 6046708 | MacDonald, Jr. et al. | Apr 2000 | A |
| 6127799 | Krishnan | Oct 2000 | A |
| 6127942 | Welle | Oct 2000 | A |
| 6163296 | Lier et al. | Dec 2000 | A |
| 6271799 | Rief | Aug 2001 | B1 |
| 6289237 | Mickle et al. | Sep 2001 | B1 |
| 6329908 | Frecska | Dec 2001 | B1 |
| 6400586 | Raddi et al. | Jun 2002 | B2 |
| 6421235 | Ditzik | Jul 2002 | B2 |
| 6437685 | Hanaki | Aug 2002 | B2 |
| 6456253 | Rummeli et al. | Sep 2002 | B1 |
| 6476795 | Derocher et al. | Nov 2002 | B1 |
| 6501414 | Amdt et al. | Dec 2002 | B2 |
| 6583723 | Watanabe et al. | Jun 2003 | B2 |
| 6597897 | Tang | Jul 2003 | B2 |
| 6615074 | Mickle et al. | Sep 2003 | B2 |
| 6650376 | Obitsu | Nov 2003 | B1 |
| 6664920 | Mott et al. | Dec 2003 | B1 |
| 6680700 | Hilgers | Jan 2004 | B2 |
| 6798716 | Charych | Sep 2004 | B1 |
| 6803744 | Sabo | Oct 2004 | B1 |
| 6853197 | McFarland | Feb 2005 | B1 |
| 6856291 | Mickle et al. | Feb 2005 | B2 |
| 6911945 | Korva | Jun 2005 | B2 |
| 6960968 | Odendaal et al. | Nov 2005 | B2 |
| 6967462 | Landis | Nov 2005 | B1 |
| 6988026 | Breed et al. | Jan 2006 | B2 |
| 7003350 | Denker et al. | Feb 2006 | B2 |
| 7027311 | Vanderelli et al. | Apr 2006 | B2 |
| 7068234 | Sievenpiper | Jun 2006 | B2 |
| 7068991 | Parise | Jun 2006 | B2 |
| 7079079 | Jo et al. | Jul 2006 | B2 |
| 7183748 | Unno et al. | Feb 2007 | B1 |
| 7191013 | Miranda et al. | Mar 2007 | B1 |
| 7193644 | Carter | Mar 2007 | B2 |
| 7196663 | Bolzer et al. | Mar 2007 | B2 |
| 7205749 | Hagen et al. | Apr 2007 | B2 |
| 7215296 | Abramov et al. | May 2007 | B2 |
| 7222356 | Yonezawa et al. | May 2007 | B1 |
| 7274334 | o'Riordan et al. | Sep 2007 | B2 |
| 7274336 | Carson | Sep 2007 | B2 |
| 7351975 | Brady et al. | Apr 2008 | B2 |
| 7359730 | Dennis et al. | Apr 2008 | B2 |
| 7372408 | Gaucher | May 2008 | B2 |
| 7392068 | Dayan | Jun 2008 | B2 |
| 7403803 | Mickle et al. | Jul 2008 | B2 |
| 7443057 | Nunally | Oct 2008 | B2 |
| 7451839 | Perlman | Nov 2008 | B2 |
| 7463201 | Chiang et al. | Dec 2008 | B2 |
| 7471247 | Saily | Dec 2008 | B2 |
| 7535195 | Horovitz et al. | May 2009 | B1 |
| 7614556 | Overhultz et al. | Nov 2009 | B2 |
| 7639994 | Greene et al. | Dec 2009 | B2 |
| 7643312 | Vanderelli et al. | Jan 2010 | B2 |
| 7652577 | Madhow et al. | Jan 2010 | B1 |
| 7679576 | Riedel et al. | Mar 2010 | B2 |
| 7702771 | Ewing et al. | Apr 2010 | B2 |
| 7786419 | Hyde et al. | Aug 2010 | B2 |
| 7812771 | Greene et al. | Oct 2010 | B2 |
| 7830312 | Choudhury et al. | Nov 2010 | B2 |
| 7844306 | Shearer et al. | Nov 2010 | B2 |
| 7868482 | Greene et al. | Jan 2011 | B2 |
| 7898105 | Greene et al. | Mar 2011 | B2 |
| 7904117 | Doan et al. | Mar 2011 | B2 |
| 7911386 | Ito et al. | Mar 2011 | B1 |
| 7925308 | Greene et al. | Apr 2011 | B2 |
| 7948208 | Partovi et al. | May 2011 | B2 |
| 8055003 | Mittleman et al. | Nov 2011 | B2 |
| 8070595 | Alderucci et al. | Dec 2011 | B2 |
| 8072380 | Crouch | Dec 2011 | B2 |
| 8092301 | Alderucci et al. | Jan 2012 | B2 |
| 8099140 | Arai | Jan 2012 | B2 |
| 8115448 | John | Feb 2012 | B2 |
| 8159090 | Greene et al. | Apr 2012 | B2 |
| 8159364 | Zeine | Apr 2012 | B2 |
| 8180286 | Yamasuge | May 2012 | B2 |
| 8228194 | Mickle | Jul 2012 | B2 |
| 8234509 | Gioscia et al. | Jul 2012 | B2 |
| 8264101 | Hyde et al. | Sep 2012 | B2 |
| 8264291 | Morita | Sep 2012 | B2 |
| 8276325 | Clifton et al. | Oct 2012 | B2 |
| 8278784 | Cook et al. | Oct 2012 | B2 |
| 8284101 | Fusco | Oct 2012 | B2 |
| 8310201 | Wright | Nov 2012 | B1 |
| 8338991 | Von Novak et al. | Dec 2012 | B2 |
| 8362745 | Tinaphong | Jan 2013 | B2 |
| 8380255 | Shearer et al. | Feb 2013 | B2 |
| 8384600 | Huang et al. | Feb 2013 | B2 |
| 8410953 | Zeine | Apr 2013 | B2 |
| 8411963 | Luff | Apr 2013 | B2 |
| 8432062 | Greene et al. | Apr 2013 | B2 |
| 8432071 | Huang et al. | Apr 2013 | B2 |
| 8446248 | Zeine | May 2013 | B2 |
| 8447234 | Cook et al. | May 2013 | B2 |
| 8451189 | Fluhler | May 2013 | B1 |
| 8452235 | Kirby et al. | May 2013 | B2 |
| 8457656 | Perkins et al. | Jun 2013 | B2 |
| 8461817 | Martin et al. | Jun 2013 | B2 |
| 8467733 | Leabman | Jun 2013 | B2 |
| 8497601 | Hall et al. | Jul 2013 | B2 |
| 8497658 | Von Novak et al. | Jul 2013 | B2 |
| 8552597 | Song et al. | Aug 2013 | B2 |
| 8558661 | Zeine | Oct 2013 | B2 |
| 8560026 | Chanterac | Oct 2013 | B2 |
| 8604746 | Lee | Dec 2013 | B2 |
| 8614643 | Leabman | Dec 2013 | B2 |
| 8621245 | Shearer et al. | Dec 2013 | B2 |
| 8626249 | Kuusilinna et al. | Jan 2014 | B2 |
| 8629576 | Levine | Jan 2014 | B2 |
| 8653966 | Rao et al. | Feb 2014 | B2 |
| 8674551 | Low et al. | Mar 2014 | B2 |
| 8686685 | Moshfeghi | Apr 2014 | B2 |
| 8686905 | Shtrom | Apr 2014 | B2 |
| 8712355 | Black et al. | Apr 2014 | B2 |
| 8712485 | Tam | Apr 2014 | B2 |
| 8718773 | Wills et al. | May 2014 | B2 |
| 8729737 | Schatz et al. | May 2014 | B2 |
| 8736228 | Freed et al. | May 2014 | B1 |
| 8760113 | Keating | Jun 2014 | B2 |
| 8770482 | Ackermann et al. | Jul 2014 | B2 |
| 8772960 | Yoshida | Jul 2014 | B2 |
| 8823319 | Von Novak, III et al. | Sep 2014 | B2 |
| 8832646 | Wendling | Sep 2014 | B1 |
| 8854176 | Zeine | Oct 2014 | B2 |
| 8860364 | Low et al. | Oct 2014 | B2 |
| 8897770 | Frolov et al. | Nov 2014 | B1 |
| 8903456 | Chu et al. | Dec 2014 | B2 |
| 8917057 | Hui | Dec 2014 | B2 |
| 8923189 | Leabman | Dec 2014 | B2 |
| 8928544 | Massie et al. | Jan 2015 | B2 |
| 8937408 | Ganem et al. | Jan 2015 | B2 |
| 8946940 | Kim et al. | Feb 2015 | B2 |
| 8963486 | Kirby et al. | Feb 2015 | B2 |
| 8970070 | Sada et al. | Mar 2015 | B2 |
| 8989053 | Skaaksrud et al. | Mar 2015 | B1 |
| 9000616 | Greene et al. | Apr 2015 | B2 |
| 9001622 | Perry | Apr 2015 | B2 |
| 9006934 | Kozakai et al. | Apr 2015 | B2 |
| 9021277 | Shearer et al. | Apr 2015 | B2 |
| 9030161 | Lu et al. | May 2015 | B2 |
| 9059598 | Kang et al. | Jun 2015 | B2 |
| 9059599 | Won et al. | Jun 2015 | B2 |
| 9077188 | Moshfeghi | Jul 2015 | B2 |
| 9083595 | Rakib et al. | Jul 2015 | B2 |
| 9088216 | Garrity et al. | Jul 2015 | B2 |
| 9124125 | Leabman et al. | Sep 2015 | B2 |
| 9130397 | Leabman et al. | Sep 2015 | B2 |
| 9130602 | Cook | Sep 2015 | B2 |
| 9142998 | Yu et al. | Sep 2015 | B2 |
| 9143000 | Leabman et al. | Sep 2015 | B2 |
| 9143010 | Urano | Sep 2015 | B2 |
| 9153074 | Zhou et al. | Oct 2015 | B2 |
| 9178389 | Hwang | Nov 2015 | B2 |
| 9225196 | Huang et al. | Dec 2015 | B2 |
| 9240469 | Sun et al. | Jan 2016 | B2 |
| 9242411 | Kritchman et al. | Jan 2016 | B2 |
| 9244500 | Cain et al. | Jan 2016 | B2 |
| 9252628 | Leabman et al. | Feb 2016 | B2 |
| 9270344 | Rosenberg | Feb 2016 | B2 |
| 9276329 | Jones et al. | Mar 2016 | B2 |
| 9282582 | Dunsbergen et al. | Mar 2016 | B1 |
| 9294840 | Anderson et al. | Mar 2016 | B1 |
| 9297896 | Andrews | Mar 2016 | B1 |
| 9318898 | John | Apr 2016 | B2 |
| 9368020 | Bell et al. | Jun 2016 | B1 |
| 9401977 | Gaw | Jul 2016 | B1 |
| 9409490 | Kawashima | Aug 2016 | B2 |
| 9419335 | Pintos | Aug 2016 | B2 |
| 9438045 | Leabman | Sep 2016 | B1 |
| 9438046 | Leabman | Sep 2016 | B1 |
| 9444283 | Son et al. | Sep 2016 | B2 |
| 9450449 | Leabman et al. | Sep 2016 | B1 |
| 9461502 | Lee et al. | Oct 2016 | B2 |
| 9520725 | Masaoka et al. | Dec 2016 | B2 |
| 9520748 | Hyde et al. | Dec 2016 | B2 |
| 9522270 | Perryman et al. | Dec 2016 | B2 |
| 9537354 | Bell et al. | Jan 2017 | B2 |
| 9537357 | Leabman | Jan 2017 | B2 |
| 9537358 | Leabman | Jan 2017 | B2 |
| 9538382 | Bell et al. | Jan 2017 | B2 |
| 9544640 | Lau | Jan 2017 | B2 |
| 9559553 | Bae | Jan 2017 | B2 |
| 9564773 | Pogorelik et al. | Feb 2017 | B2 |
| 9571974 | Choi et al. | Feb 2017 | B2 |
| 9590317 | Zimmerman et al. | Mar 2017 | B2 |
| 9590444 | Walley | Mar 2017 | B2 |
| 9620996 | Zeine | Apr 2017 | B2 |
| 9647328 | Dobric | May 2017 | B2 |
| 9706137 | Scanlon et al. | Jul 2017 | B2 |
| 9711999 | Hietala et al. | Jul 2017 | B2 |
| 9723635 | Nambord et al. | Aug 2017 | B2 |
| 9793758 | Leabman | Oct 2017 | B2 |
| 9793764 | Perry | Oct 2017 | B2 |
| 9800172 | Leabman | Oct 2017 | B1 |
| 9806564 | Leabman | Oct 2017 | B2 |
| 9819230 | Petras et al. | Nov 2017 | B2 |
| 9825674 | Leabman | Nov 2017 | B1 |
| 9843229 | Leabman | Dec 2017 | B2 |
| 9847669 | Leabman | Dec 2017 | B2 |
| 9847677 | Leabman | Dec 2017 | B1 |
| 9853361 | Chen et al. | Dec 2017 | B2 |
| 9853692 | Bell et al. | Dec 2017 | B1 |
| 9859758 | Leabman | Jan 2018 | B1 |
| 9866279 | Bell et al. | Jan 2018 | B2 |
| 9867032 | Verma et al. | Jan 2018 | B2 |
| 9871301 | Contopanagos | Jan 2018 | B2 |
| 9876380 | Leabman et al. | Jan 2018 | B1 |
| 9876394 | Leabman | Jan 2018 | B1 |
| 9876536 | Bell et al. | Jan 2018 | B1 |
| 9882394 | Bell | Jan 2018 | B1 |
| 9887584 | Bell et al. | Feb 2018 | B1 |
| 9893555 | Leabman et al. | Feb 2018 | B1 |
| 9893564 | de Rochemont | Feb 2018 | B2 |
| 9899844 | Bell et al. | Feb 2018 | B1 |
| 9899861 | Leabman et al. | Feb 2018 | B1 |
| 9917477 | Bell et al. | Mar 2018 | B1 |
| 9923386 | Leabman et al. | Mar 2018 | B1 |
| 9939864 | Bell et al. | Apr 2018 | B1 |
| 9965009 | Bell et al. | May 2018 | B1 |
| 9966765 | Leabman | May 2018 | B1 |
| 9966784 | Leabman | May 2018 | B2 |
| 9967743 | Bell et al. | May 2018 | B1 |
| 9973008 | Leabman | May 2018 | B1 |
| 10003211 | Leabman et al. | Jun 2018 | B1 |
| 10014728 | Leabman | Jul 2018 | B1 |
| 10027159 | Hosseini | Jul 2018 | B2 |
| 10038337 | Leabman et al. | Jul 2018 | B1 |
| 10050462 | Leabman et al. | Aug 2018 | B1 |
| 10056782 | Leabman | Aug 2018 | B1 |
| 10063064 | Bell et al. | Aug 2018 | B1 |
| 10068703 | Contopanagos | Sep 2018 | B1 |
| 10075008 | Bell et al. | Sep 2018 | B1 |
| 10090699 | Leabman | Oct 2018 | B1 |
| 10090886 | Bell et al. | Oct 2018 | B1 |
| 10103552 | Leabman et al. | Oct 2018 | B1 |
| 10122219 | Hosseini et al. | Nov 2018 | B1 |
| 10124754 | Leabman | Nov 2018 | B1 |
| 10128686 | Leabman et al. | Nov 2018 | B1 |
| 10134260 | Bell et al. | Nov 2018 | B1 |
| 10135112 | Hosseini | Nov 2018 | B1 |
| 10135294 | Leabman | Nov 2018 | B1 |
| 10141771 | Hosseini et al. | Nov 2018 | B1 |
| 10148097 | Leabman et al. | Dec 2018 | B1 |
| 10153645 | Bell et al. | Dec 2018 | B1 |
| 10153653 | Bell et al. | Dec 2018 | B1 |
| 10153660 | Leabman et al. | Dec 2018 | B1 |
| 10158257 | Leabman | Dec 2018 | B2 |
| 10158259 | Leabman | Dec 2018 | B1 |
| 10164478 | Leabman | Dec 2018 | B2 |
| 10170917 | Bell et al. | Jan 2019 | B1 |
| 10181756 | Bae et al. | Jan 2019 | B2 |
| 10186892 | Hosseini et al. | Jan 2019 | B2 |
| 10193396 | Bell et al. | Jan 2019 | B1 |
| 10199835 | Bell | Feb 2019 | B2 |
| 10199849 | Bell | Feb 2019 | B1 |
| 10205239 | Contopanagos et al. | Feb 2019 | B1 |
| 10211674 | Leabman et al. | Feb 2019 | B1 |
| 10223717 | Bell | Mar 2019 | B1 |
| 10224758 | Leabman et al. | Mar 2019 | B2 |
| 10224982 | Leabman | Mar 2019 | B1 |
| 10230266 | Leabman et al. | Mar 2019 | B1 |
| 10243414 | Leabman et al. | Mar 2019 | B1 |
| 10256657 | Hosseini et al. | Apr 2019 | B2 |
| 10256677 | Hosseini et al. | Apr 2019 | B2 |
| 10263432 | Leabman et al. | Apr 2019 | B1 |
| 10263476 | Leabman | Apr 2019 | B2 |
| 10277054 | Hosseini | Apr 2019 | B2 |
| 10291055 | Bell et al. | May 2019 | B1 |
| 10291066 | Leabman | May 2019 | B1 |
| 10291294 | Leabman | May 2019 | B2 |
| 10298024 | Leabman | May 2019 | B2 |
| 10298133 | Leabman | May 2019 | B2 |
| 10305315 | Leabman et al. | May 2019 | B2 |
| 10312715 | Leabman | Jun 2019 | B2 |
| 10320446 | Hosseini | Jun 2019 | B2 |
| 10333332 | Hosseini | Jun 2019 | B1 |
| 10355534 | Johnston et al. | Jul 2019 | B2 |
| 10389161 | Hosseini et al. | Aug 2019 | B2 |
| 10396588 | Leabman | Aug 2019 | B2 |
| 20010027876 | Tsukamoto et al. | Oct 2001 | A1 |
| 20020001307 | Nguyen et al. | Jan 2002 | A1 |
| 20020024471 | Ishitobi | Feb 2002 | A1 |
| 20020028655 | Rosener et al. | Mar 2002 | A1 |
| 20020034958 | Oberschmidt et al. | Mar 2002 | A1 |
| 20020054330 | Jinbo et al. | May 2002 | A1 |
| 20020065052 | Pande et al. | May 2002 | A1 |
| 20020072784 | Sheppard et al. | Jun 2002 | A1 |
| 20020095980 | Breed et al. | Jul 2002 | A1 |
| 20020103447 | Terry | Aug 2002 | A1 |
| 20020123776 | Von Arx | Sep 2002 | A1 |
| 20020133592 | Matsuda | Sep 2002 | A1 |
| 20020171594 | Fang | Nov 2002 | A1 |
| 20020172223 | Stilp | Nov 2002 | A1 |
| 20030005759 | Breed et al. | Jan 2003 | A1 |
| 20030038750 | Chen | Feb 2003 | A1 |
| 20030058187 | Billiet et al. | Mar 2003 | A1 |
| 20030076274 | Phelan et al. | Apr 2003 | A1 |
| 20030179152 | Watada et al. | Sep 2003 | A1 |
| 20030179573 | Chun | Sep 2003 | A1 |
| 20030192053 | Sheppard et al. | Oct 2003 | A1 |
| 20040019624 | Sukegawa | Jan 2004 | A1 |
| 20040020100 | O'Brian et al. | Feb 2004 | A1 |
| 20040036657 | Forster et al. | Feb 2004 | A1 |
| 20040066251 | Eleftheriades et al. | Apr 2004 | A1 |
| 20040107641 | Walton et al. | Jun 2004 | A1 |
| 20040113543 | Daniels | Jun 2004 | A1 |
| 20040119675 | Washio et al. | Jun 2004 | A1 |
| 20040130425 | Dayan et al. | Jul 2004 | A1 |
| 20040130442 | Breed | Jul 2004 | A1 |
| 20040142733 | Parise | Jul 2004 | A1 |
| 20040145342 | Lyon | Jul 2004 | A1 |
| 20040155832 | Yuanzhu | Aug 2004 | A1 |
| 20040196190 | Mendolia et al. | Oct 2004 | A1 |
| 20040203979 | Attar et al. | Oct 2004 | A1 |
| 20040207559 | Milosavljevic | Oct 2004 | A1 |
| 20040218759 | Yacobi | Nov 2004 | A1 |
| 20040259604 | Mickle et al. | Dec 2004 | A1 |
| 20040263124 | Wieck et al. | Dec 2004 | A1 |
| 20050007276 | Barrick et al. | Jan 2005 | A1 |
| 20050030118 | Wang | Feb 2005 | A1 |
| 20050046584 | Breed | Mar 2005 | A1 |
| 20050055316 | Williams | Mar 2005 | A1 |
| 20050077872 | Single | Apr 2005 | A1 |
| 20050093766 | Turner | May 2005 | A1 |
| 20050116683 | Cheng | Jun 2005 | A1 |
| 20050117660 | Vialle et al. | Jun 2005 | A1 |
| 20050134517 | Gottl | Jun 2005 | A1 |
| 20050171411 | KenKnight | Aug 2005 | A1 |
| 20050198673 | Kit et al. | Sep 2005 | A1 |
| 20050227619 | Lee et al. | Oct 2005 | A1 |
| 20050232469 | Schofield | Oct 2005 | A1 |
| 20050237249 | Nagel | Oct 2005 | A1 |
| 20050237258 | Abramov et al. | Oct 2005 | A1 |
| 20050282591 | Shaff | Dec 2005 | A1 |
| 20060013335 | Leabman | Jan 2006 | A1 |
| 20060019712 | Choi | Jan 2006 | A1 |
| 20060030279 | Leabman et al. | Feb 2006 | A1 |
| 20060033674 | Essig, Jr. et al. | Feb 2006 | A1 |
| 20060071308 | Tang et al. | Apr 2006 | A1 |
| 20060092079 | de Rochemont | May 2006 | A1 |
| 20060094425 | Mickle et al. | May 2006 | A1 |
| 20060113955 | Nunally | Jun 2006 | A1 |
| 20060119532 | Yun et al. | Jun 2006 | A1 |
| 20060136004 | Cowan et al. | Jun 2006 | A1 |
| 20060160517 | Yoon | Jul 2006 | A1 |
| 20060183473 | Ukon | Aug 2006 | A1 |
| 20060190063 | Kanzius | Aug 2006 | A1 |
| 20060192913 | Shutou et al. | Aug 2006 | A1 |
| 20060199620 | Greene et al. | Sep 2006 | A1 |
| 20060238365 | Vecchione et al. | Oct 2006 | A1 |
| 20060266564 | Perlman et al. | Nov 2006 | A1 |
| 20060266917 | Baldis et al. | Nov 2006 | A1 |
| 20060278706 | Hatakayama et al. | Dec 2006 | A1 |
| 20060284593 | Nagy et al. | Dec 2006 | A1 |
| 20060287094 | Mahaffey et al. | Dec 2006 | A1 |
| 20070007821 | Rossetti | Jan 2007 | A1 |
| 20070019693 | Graham | Jan 2007 | A1 |
| 20070021140 | Keyes | Jan 2007 | A1 |
| 20070060185 | Simon et al. | Mar 2007 | A1 |
| 20070070490 | Tsunoda et al. | Mar 2007 | A1 |
| 20070090997 | Brown et al. | Apr 2007 | A1 |
| 20070093269 | Leabman et al. | Apr 2007 | A1 |
| 20070097653 | Gilliland et al. | May 2007 | A1 |
| 20070103110 | Sagoo | May 2007 | A1 |
| 20070106894 | Zhang | May 2007 | A1 |
| 20070109121 | Cohen | May 2007 | A1 |
| 20070139000 | Kozuma | Jun 2007 | A1 |
| 20070149162 | Greene et al. | Jun 2007 | A1 |
| 20070164868 | Deavours et al. | Jul 2007 | A1 |
| 20070173196 | Gallic | Jul 2007 | A1 |
| 20070173214 | Mickle et al. | Jul 2007 | A1 |
| 20070178857 | Greene et al. | Aug 2007 | A1 |
| 20070178945 | Cook et al. | Aug 2007 | A1 |
| 20070182367 | Partovi | Aug 2007 | A1 |
| 20070191074 | Harrist et al. | Aug 2007 | A1 |
| 20070191075 | Greene et al. | Aug 2007 | A1 |
| 20070197281 | Stronach | Aug 2007 | A1 |
| 20070210960 | Rofougaran et al. | Sep 2007 | A1 |
| 20070222681 | Greene et al. | Sep 2007 | A1 |
| 20070228833 | Stevens et al. | Oct 2007 | A1 |
| 20070240297 | Yang et al. | Oct 2007 | A1 |
| 20070257634 | Leschin et al. | Nov 2007 | A1 |
| 20070273486 | Shiotsu | Nov 2007 | A1 |
| 20070291165 | Wang | Dec 2007 | A1 |
| 20070296639 | Hook et al. | Dec 2007 | A1 |
| 20070298846 | Greene et al. | Dec 2007 | A1 |
| 20080014897 | Cook | Jan 2008 | A1 |
| 20080024376 | Norris et al. | Jan 2008 | A1 |
| 20080048917 | Achour et al. | Feb 2008 | A1 |
| 20080062062 | Borau et al. | Mar 2008 | A1 |
| 20080062255 | Gal | Mar 2008 | A1 |
| 20080067874 | Tseng | Mar 2008 | A1 |
| 20080074324 | Puzella et al. | Mar 2008 | A1 |
| 20080089277 | Aledander et al. | Apr 2008 | A1 |
| 20080110263 | Klessel et al. | May 2008 | A1 |
| 20080113816 | Mahaffey et al. | May 2008 | A1 |
| 20080122297 | Arai | May 2008 | A1 |
| 20080123383 | Shionoiri | May 2008 | A1 |
| 20080129536 | Randall et al. | Jun 2008 | A1 |
| 20080140278 | Breed | Jun 2008 | A1 |
| 20080169910 | Greene et al. | Jul 2008 | A1 |
| 20080197802 | Onishi | Aug 2008 | A1 |
| 20080204342 | Kharadly | Aug 2008 | A1 |
| 20080204350 | Tam et al. | Aug 2008 | A1 |
| 20080210762 | Osada et al. | Sep 2008 | A1 |
| 20080211458 | Lawther et al. | Sep 2008 | A1 |
| 20080233890 | Baker | Sep 2008 | A1 |
| 20080248758 | Schedelbeck et al. | Oct 2008 | A1 |
| 20080248846 | Stronach et al. | Oct 2008 | A1 |
| 20080258993 | Gummalla et al. | Oct 2008 | A1 |
| 20080266191 | Hilgers | Oct 2008 | A1 |
| 20080278378 | Chang et al. | Nov 2008 | A1 |
| 20080309452 | Zeine | Dec 2008 | A1 |
| 20090002493 | Kates | Jan 2009 | A1 |
| 20090010316 | Rofougaran et al. | Jan 2009 | A1 |
| 20090019183 | Wu et al. | Jan 2009 | A1 |
| 20090036065 | Siu | Feb 2009 | A1 |
| 20090039828 | Jakubowski | Feb 2009 | A1 |
| 20090047998 | Alberth, Jr. | Feb 2009 | A1 |
| 20090058354 | Harrison | Mar 2009 | A1 |
| 20090058361 | John | Mar 2009 | A1 |
| 20090058731 | Geary et al. | Mar 2009 | A1 |
| 20090060012 | Gresset et al. | Mar 2009 | A1 |
| 20090067198 | Graham et al. | Mar 2009 | A1 |
| 20090067208 | Martin et al. | Mar 2009 | A1 |
| 20090073066 | Jordon et al. | Mar 2009 | A1 |
| 20090096412 | Huang | Apr 2009 | A1 |
| 20090096413 | Partovi | Apr 2009 | A1 |
| 20090102292 | Cook et al. | Apr 2009 | A1 |
| 20090102296 | Greene et al. | Apr 2009 | A1 |
| 20090108679 | Porwal | Apr 2009 | A1 |
| 20090122847 | Nysen et al. | May 2009 | A1 |
| 20090128262 | Lee et al. | May 2009 | A1 |
| 20090157911 | Aihara | Jun 2009 | A1 |
| 20090174604 | Keskitalo | Jul 2009 | A1 |
| 20090180653 | Sjursen et al. | Jul 2009 | A1 |
| 20090200985 | Zane et al. | Aug 2009 | A1 |
| 20090206791 | Jung | Aug 2009 | A1 |
| 20090207090 | Pettus et al. | Aug 2009 | A1 |
| 20090207092 | Nysen et al. | Aug 2009 | A1 |
| 20090218884 | Soar | Sep 2009 | A1 |
| 20090218891 | McCollough | Sep 2009 | A1 |
| 20090219903 | Alamouti et al. | Sep 2009 | A1 |
| 20090243397 | Cook et al. | Oct 2009 | A1 |
| 20090256752 | Akkermans et al. | Oct 2009 | A1 |
| 20090264069 | Yamasuge | Oct 2009 | A1 |
| 20090271048 | Wakamatsu | Oct 2009 | A1 |
| 20090280866 | Lo et al. | Nov 2009 | A1 |
| 20090281678 | Wakamatsu | Nov 2009 | A1 |
| 20090284082 | Mohammadian | Nov 2009 | A1 |
| 20090284083 | Karalis et al. | Nov 2009 | A1 |
| 20090284220 | Toncich et al. | Nov 2009 | A1 |
| 20090284227 | Mohammadian et al. | Nov 2009 | A1 |
| 20090284325 | Rossiter et al. | Nov 2009 | A1 |
| 20090286475 | Toncich et al. | Nov 2009 | A1 |
| 20090286476 | Toncich et al. | Nov 2009 | A1 |
| 20090291634 | Saarisalo | Nov 2009 | A1 |
| 20090299175 | Bernstein et al. | Dec 2009 | A1 |
| 20090308936 | Nitzan et al. | Dec 2009 | A1 |
| 20090312046 | Clevenger et al. | Dec 2009 | A1 |
| 20090315412 | Yamamoto et al. | Dec 2009 | A1 |
| 20090322281 | Kamijo et al. | Dec 2009 | A1 |
| 20100001683 | Huang et al. | Jan 2010 | A1 |
| 20100007307 | Baarman et al. | Jan 2010 | A1 |
| 20100007569 | Sim et al. | Jan 2010 | A1 |
| 20100019686 | Gutierrez, Jr. | Jan 2010 | A1 |
| 20100019908 | Cho et al. | Jan 2010 | A1 |
| 20100026605 | Yang et al. | Feb 2010 | A1 |
| 20100027379 | Saulnier et al. | Feb 2010 | A1 |
| 20100029383 | Dai | Feb 2010 | A1 |
| 20100033021 | Bennett | Feb 2010 | A1 |
| 20100033390 | Alamouti et al. | Feb 2010 | A1 |
| 20100034238 | Bennett | Feb 2010 | A1 |
| 20100041453 | Grimm, Jr. | Feb 2010 | A1 |
| 20100044123 | Perlman et al. | Feb 2010 | A1 |
| 20100054200 | Tsai | Mar 2010 | A1 |
| 20100060534 | Oodachi | Mar 2010 | A1 |
| 20100066631 | Puzella et al. | Mar 2010 | A1 |
| 20100075607 | Hosoya | Mar 2010 | A1 |
| 20100079005 | Hyde et al. | Apr 2010 | A1 |
| 20100079011 | Hyde et al. | Apr 2010 | A1 |
| 20100082193 | Chiappetta | Apr 2010 | A1 |
| 20100087227 | Francos et al. | Apr 2010 | A1 |
| 20100090524 | Obayashi | Apr 2010 | A1 |
| 20100090656 | Shearer et al. | Apr 2010 | A1 |
| 20100109443 | Cook et al. | May 2010 | A1 |
| 20100117596 | Cook et al. | May 2010 | A1 |
| 20100117926 | DeJean, II | May 2010 | A1 |
| 20100119234 | Suematsu et al. | May 2010 | A1 |
| 20100123618 | Martin et al. | May 2010 | A1 |
| 20100123624 | Minear et al. | May 2010 | A1 |
| 20100124040 | Diebel et al. | May 2010 | A1 |
| 20100127660 | Cook et al. | May 2010 | A1 |
| 20100142418 | Nishioka et al. | Jun 2010 | A1 |
| 20100142509 | Zhu et al. | Jun 2010 | A1 |
| 20100148723 | Cook et al. | Jun 2010 | A1 |
| 20100151808 | Toncich et al. | Jun 2010 | A1 |
| 20100156721 | Alamouti et al. | Jun 2010 | A1 |
| 20100156741 | Vazquez et al. | Jun 2010 | A1 |
| 20100164296 | Kurs et al. | Jul 2010 | A1 |
| 20100164433 | Janefalker et al. | Jul 2010 | A1 |
| 20100167664 | Szini | Jul 2010 | A1 |
| 20100171461 | Baarman et al. | Jul 2010 | A1 |
| 20100174629 | Taylor et al. | Jul 2010 | A1 |
| 20100176934 | Chou et al. | Jul 2010 | A1 |
| 20100181961 | Novak et al. | Jul 2010 | A1 |
| 20100181964 | Huggins et al. | Jul 2010 | A1 |
| 20100194206 | Burdo et al. | Aug 2010 | A1 |
| 20100201189 | Kirby et al. | Aug 2010 | A1 |
| 20100201201 | Mobarhan et al. | Aug 2010 | A1 |
| 20100201314 | Toncich et al. | Aug 2010 | A1 |
| 20100207572 | Kirby et al. | Aug 2010 | A1 |
| 20100210233 | Cook et al. | Aug 2010 | A1 |
| 20100213895 | Keating et al. | Aug 2010 | A1 |
| 20100214177 | Parsche | Aug 2010 | A1 |
| 20100222010 | Ozaki et al. | Sep 2010 | A1 |
| 20100225270 | Jacobs et al. | Sep 2010 | A1 |
| 20100227570 | Hendin | Sep 2010 | A1 |
| 20100231470 | Lee et al. | Sep 2010 | A1 |
| 20100237709 | Hall et al. | Sep 2010 | A1 |
| 20100244576 | Hillan et al. | Sep 2010 | A1 |
| 20100256831 | Abramo et al. | Oct 2010 | A1 |
| 20100259110 | Kurs et al. | Oct 2010 | A1 |
| 20100259447 | Crouch | Oct 2010 | A1 |
| 20100264747 | Hall et al. | Oct 2010 | A1 |
| 20100277003 | Von Novak et al. | Nov 2010 | A1 |
| 20100277121 | Hall et al. | Nov 2010 | A1 |
| 20100279606 | Hillan et al. | Nov 2010 | A1 |
| 20100289341 | Ozaki et al. | Nov 2010 | A1 |
| 20100295372 | Hyde et al. | Nov 2010 | A1 |
| 20100308767 | Rofougaran et al. | Dec 2010 | A1 |
| 20100309079 | Rofougaran et al. | Dec 2010 | A1 |
| 20100309088 | Hyvonen et al. | Dec 2010 | A1 |
| 20100315045 | Zeine | Dec 2010 | A1 |
| 20100316163 | Forenza et al. | Dec 2010 | A1 |
| 20100327766 | Recker et al. | Dec 2010 | A1 |
| 20100328044 | Waffenschmidt et al. | Dec 2010 | A1 |
| 20100332401 | Prahlad et al. | Dec 2010 | A1 |
| 20110013198 | Shirley | Jan 2011 | A1 |
| 20110018360 | Baarman et al. | Jan 2011 | A1 |
| 20110028114 | Kerselaers | Feb 2011 | A1 |
| 20110031928 | Soar | Feb 2011 | A1 |
| 20110032149 | Leabman | Feb 2011 | A1 |
| 20110032866 | Leabman | Feb 2011 | A1 |
| 20110034190 | Leabman | Feb 2011 | A1 |
| 20110034191 | Leabman | Feb 2011 | A1 |
| 20110043047 | Karalis et al. | Feb 2011 | A1 |
| 20110043163 | Baarman et al. | Feb 2011 | A1 |
| 20110043327 | Baarman et al. | Feb 2011 | A1 |
| 20110050166 | Cook et al. | Mar 2011 | A1 |
| 20110055037 | Hayashigawa et al. | Mar 2011 | A1 |
| 20110056215 | Ham | Mar 2011 | A1 |
| 20110057607 | Carobolante | Mar 2011 | A1 |
| 20110057853 | Kim et al. | Mar 2011 | A1 |
| 20110062788 | Chen et al. | Mar 2011 | A1 |
| 20110074342 | MacLaughlin | Mar 2011 | A1 |
| 20110074349 | Ghovanloo | Mar 2011 | A1 |
| 20110074620 | Wintermantel | Mar 2011 | A1 |
| 20110078092 | Kim et al. | Mar 2011 | A1 |
| 20110090126 | Szini et al. | Apr 2011 | A1 |
| 20110109167 | Park et al. | May 2011 | A1 |
| 20110114401 | Kanno et al. | May 2011 | A1 |
| 20110115303 | Baarman et al. | May 2011 | A1 |
| 20110115432 | El-Maleh | May 2011 | A1 |
| 20110115605 | Dimig et al. | May 2011 | A1 |
| 20110121660 | Azancot et al. | May 2011 | A1 |
| 20110122018 | Tarng et al. | May 2011 | A1 |
| 20110122026 | DeLaquil et al. | May 2011 | A1 |
| 20110127845 | Walley et al. | Jun 2011 | A1 |
| 20110127952 | Walley et al. | Jun 2011 | A1 |
| 20110133655 | Recker et al. | Jun 2011 | A1 |
| 20110133691 | Hautanen | Jun 2011 | A1 |
| 20110148578 | Aloi et al. | Jun 2011 | A1 |
| 20110148595 | Miller et al. | Jun 2011 | A1 |
| 20110151789 | Viglione et al. | Jun 2011 | A1 |
| 20110154429 | Stantchev | Jun 2011 | A1 |
| 20110156494 | Mashinsky | Jun 2011 | A1 |
| 20110156640 | Moshfeghi | Jun 2011 | A1 |
| 20110163128 | Taguchi et al. | Jul 2011 | A1 |
| 20110175455 | Hashiguchi | Jul 2011 | A1 |
| 20110175461 | Tinaphong | Jul 2011 | A1 |
| 20110181120 | Liu et al. | Jul 2011 | A1 |
| 20110182245 | Malkamaki et al. | Jul 2011 | A1 |
| 20110184842 | Melen | Jul 2011 | A1 |
| 20110188207 | Won et al. | Aug 2011 | A1 |
| 20110193688 | Forsell | Aug 2011 | A1 |
| 20110194543 | Zhao et al. | Aug 2011 | A1 |
| 20110195722 | Walter et al. | Aug 2011 | A1 |
| 20110199046 | Tsai et al. | Aug 2011 | A1 |
| 20110215086 | Yeh | Sep 2011 | A1 |
| 20110217923 | Ma | Sep 2011 | A1 |
| 20110220634 | Yeh | Sep 2011 | A1 |
| 20110221389 | Won et al. | Sep 2011 | A1 |
| 20110222272 | Yeh | Sep 2011 | A1 |
| 20110243040 | Khan et al. | Oct 2011 | A1 |
| 20110243050 | Yanover | Oct 2011 | A1 |
| 20110244913 | Kim et al. | Oct 2011 | A1 |
| 20110248573 | Kanno et al. | Oct 2011 | A1 |
| 20110248575 | Kim et al. | Oct 2011 | A1 |
| 20110249678 | Bonicatto | Oct 2011 | A1 |
| 20110254377 | Widmer et al. | Oct 2011 | A1 |
| 20110254503 | Widmer et al. | Oct 2011 | A1 |
| 20110259953 | Baarman et al. | Oct 2011 | A1 |
| 20110273977 | Shapira et al. | Nov 2011 | A1 |
| 20110278941 | Krishna et al. | Nov 2011 | A1 |
| 20110279226 | Chen et al. | Nov 2011 | A1 |
| 20110281535 | Low et al. | Nov 2011 | A1 |
| 20110282415 | Eckhoff et al. | Nov 2011 | A1 |
| 20110285213 | Kowalewski | Nov 2011 | A1 |
| 20110286374 | Shin et al. | Nov 2011 | A1 |
| 20110291489 | Tsai et al. | Dec 2011 | A1 |
| 20110302078 | Failing | Dec 2011 | A1 |
| 20110304216 | Baarman | Dec 2011 | A1 |
| 20110304437 | Beeler | Dec 2011 | A1 |
| 20110304521 | Ando et al. | Dec 2011 | A1 |
| 20120007441 | John | Jan 2012 | A1 |
| 20120013196 | Kim et al. | Jan 2012 | A1 |
| 20120013198 | Uramoto et al. | Jan 2012 | A1 |
| 20120013296 | Heydari et al. | Jan 2012 | A1 |
| 20120019419 | Prat et al. | Jan 2012 | A1 |
| 20120043887 | Mesibov | Feb 2012 | A1 |
| 20120051109 | Kim et al. | Mar 2012 | A1 |
| 20120051294 | Guillouard | Mar 2012 | A1 |
| 20120056486 | Endo et al. | Mar 2012 | A1 |
| 20120056741 | Zhu et al. | Mar 2012 | A1 |
| 20120068906 | Asher et al. | Mar 2012 | A1 |
| 20120074891 | Anderson et al. | Mar 2012 | A1 |
| 20120080944 | Recker et al. | Apr 2012 | A1 |
| 20120080957 | Cooper et al. | Apr 2012 | A1 |
| 20120086284 | Capanella et al. | Apr 2012 | A1 |
| 20120086615 | Norair | Apr 2012 | A1 |
| 20120095617 | Martin et al. | Apr 2012 | A1 |
| 20120098350 | Campanella et al. | Apr 2012 | A1 |
| 20120098485 | Kang et al. | Apr 2012 | A1 |
| 20120099675 | Kitamura et al. | Apr 2012 | A1 |
| 20120103562 | Clayton | May 2012 | A1 |
| 20120104849 | Jackson | May 2012 | A1 |
| 20120105252 | Wang | May 2012 | A1 |
| 20120112532 | Kesler et al. | May 2012 | A1 |
| 20120119914 | Uchida | May 2012 | A1 |
| 20120126743 | Rivers, Jr. | May 2012 | A1 |
| 20120132647 | Beverly et al. | May 2012 | A1 |
| 20120133214 | Yun et al. | May 2012 | A1 |
| 20120142291 | Rath et al. | Jun 2012 | A1 |
| 20120146426 | Sabo | Jun 2012 | A1 |
| 20120146576 | Partovi | Jun 2012 | A1 |
| 20120146577 | Tanabe | Jun 2012 | A1 |
| 20120147802 | Ukita et al. | Jun 2012 | A1 |
| 20120149307 | Terada et al. | Jun 2012 | A1 |
| 20120150670 | Taylor et al. | Jun 2012 | A1 |
| 20120153894 | Widmer et al. | Jun 2012 | A1 |
| 20120157019 | Li | Jun 2012 | A1 |
| 20120161531 | Kim et al. | Jun 2012 | A1 |
| 20120161544 | Kashiwagi et al. | Jun 2012 | A1 |
| 20120188142 | Shashi et al. | Jun 2012 | A1 |
| 20120169276 | Wang | Jul 2012 | A1 |
| 20120169278 | Choi | Jul 2012 | A1 |
| 20120173418 | Beardsmore et al. | Jul 2012 | A1 |
| 20120179004 | Roesicke et al. | Jul 2012 | A1 |
| 20120181973 | Lyden | Jul 2012 | A1 |
| 20120182427 | Marshall | Jul 2012 | A1 |
| 20120187851 | Huggins et al. | Aug 2012 | A1 |
| 20120193999 | Zeine | Aug 2012 | A1 |
| 20120200399 | Chae | Aug 2012 | A1 |
| 20120201153 | Bharadia et al. | Aug 2012 | A1 |
| 20120201173 | Jian et al. | Aug 2012 | A1 |
| 20120206299 | Valdes-Garcia | Aug 2012 | A1 |
| 20120211214 | Phan | Aug 2012 | A1 |
| 20120212071 | Miyabayashi et al. | Aug 2012 | A1 |
| 20120212072 | Miyabayashi et al. | Aug 2012 | A1 |
| 20120214462 | Chu et al. | Aug 2012 | A1 |
| 20120214536 | Kim et al. | Aug 2012 | A1 |
| 20120228392 | Cameron et al. | Sep 2012 | A1 |
| 20120228956 | Kamata | Sep 2012 | A1 |
| 20120231856 | Lee et al. | Sep 2012 | A1 |
| 20120235636 | Partovi | Sep 2012 | A1 |
| 20120242283 | Kim et al. | Sep 2012 | A1 |
| 20120248886 | Kesler et al. | Oct 2012 | A1 |
| 20120248888 | Kesler et al. | Oct 2012 | A1 |
| 20120248891 | Drennen | Oct 2012 | A1 |
| 20120249051 | Son et al. | Oct 2012 | A1 |
| 20120262002 | Widmer et al. | Oct 2012 | A1 |
| 20120265272 | Judkins | Oct 2012 | A1 |
| 20120267900 | Huffman et al. | Oct 2012 | A1 |
| 20120268238 | Park et al. | Oct 2012 | A1 |
| 20120274154 | DeLuca | Nov 2012 | A1 |
| 20120280650 | Kim et al. | Nov 2012 | A1 |
| 20120286582 | Kim et al. | Nov 2012 | A1 |
| 20120292993 | Mettler et al. | Nov 2012 | A1 |
| 20120293021 | Teggatz et al. | Nov 2012 | A1 |
| 20120293119 | Park et al. | Nov 2012 | A1 |
| 20120299389 | Lee et al. | Nov 2012 | A1 |
| 20120299540 | Perry | Nov 2012 | A1 |
| 20120299541 | Perry | Nov 2012 | A1 |
| 20120299542 | Perry | Nov 2012 | A1 |
| 20120300588 | Perry | Nov 2012 | A1 |
| 20120300592 | Perry | Nov 2012 | A1 |
| 20120300593 | Perry | Nov 2012 | A1 |
| 20120306433 | Kim et al. | Dec 2012 | A1 |
| 20120306705 | Sakurai et al. | Dec 2012 | A1 |
| 20120306707 | Yang et al. | Dec 2012 | A1 |
| 20120306720 | Tanmi et al. | Dec 2012 | A1 |
| 20120307873 | Kim et al. | Dec 2012 | A1 |
| 20120309295 | Maguire | Dec 2012 | A1 |
| 20120309308 | Kim et al. | Dec 2012 | A1 |
| 20120309332 | Liao | Dec 2012 | A1 |
| 20120313449 | Kurs | Dec 2012 | A1 |
| 20120313835 | Gebretnsae | Dec 2012 | A1 |
| 20120326660 | Lu et al. | Dec 2012 | A1 |
| 20130002550 | Zalewski | Jan 2013 | A1 |
| 20130018439 | Chow et al. | Jan 2013 | A1 |
| 20130024059 | Miller et al. | Jan 2013 | A1 |
| 20130026981 | Van Der Lee | Jan 2013 | A1 |
| 20130026982 | Rothenbaum | Jan 2013 | A1 |
| 20130032589 | Chung | Feb 2013 | A1 |
| 20130033571 | Steen | Feb 2013 | A1 |
| 20130038124 | Newdoll et al. | Feb 2013 | A1 |
| 20130038402 | Karalis et al. | Feb 2013 | A1 |
| 20130043738 | Park et al. | Feb 2013 | A1 |
| 20130044035 | Zhuang | Feb 2013 | A1 |
| 20130049471 | Oleynik | Feb 2013 | A1 |
| 20130049475 | Kim et al. | Feb 2013 | A1 |
| 20130049484 | Weissentern et al. | Feb 2013 | A1 |
| 20130057078 | Lee | Mar 2013 | A1 |
| 20130057205 | Lee et al. | Mar 2013 | A1 |
| 20130057210 | Negaard et al. | Mar 2013 | A1 |
| 20130057364 | Kesler et al. | Mar 2013 | A1 |
| 20130058379 | Kim et al. | Mar 2013 | A1 |
| 20130063082 | Lee et al. | Mar 2013 | A1 |
| 20130063143 | Adalsteinsson et al. | Mar 2013 | A1 |
| 20130069444 | Waffenschmidt et al. | Mar 2013 | A1 |
| 20130076308 | Niskala et al. | Mar 2013 | A1 |
| 20130077650 | Traxler et al. | Mar 2013 | A1 |
| 20130078918 | Crowley et al. | Mar 2013 | A1 |
| 20130082651 | Park et al. | Apr 2013 | A1 |
| 20130082653 | Lee et al. | Apr 2013 | A1 |
| 20130083774 | Son et al. | Apr 2013 | A1 |
| 20130088082 | Kang et al. | Apr 2013 | A1 |
| 20130088090 | Wu | Apr 2013 | A1 |
| 20130088192 | Eaton | Apr 2013 | A1 |
| 20130088331 | Cho | Apr 2013 | A1 |
| 20130093388 | Partovi | Apr 2013 | A1 |
| 20130099389 | Hong et al. | Apr 2013 | A1 |
| 20130099586 | Kato | Apr 2013 | A1 |
| 20130106197 | Bae et al. | May 2013 | A1 |
| 20130107023 | Tanaka et al. | May 2013 | A1 |
| 20130119777 | Rees | May 2013 | A1 |
| 20130119778 | Jung | May 2013 | A1 |
| 20130119929 | Partovi | May 2013 | A1 |
| 20130120052 | Siska | May 2013 | A1 |
| 20130120217 | Ueda et al. | May 2013 | A1 |
| 20130130621 | Kim et al. | May 2013 | A1 |
| 20130132010 | Winger et al. | May 2013 | A1 |
| 20130134923 | Smith | May 2013 | A1 |
| 20130137455 | Xia | May 2013 | A1 |
| 20130141037 | Jenwatanavet et al. | Jun 2013 | A1 |
| 20130148341 | Williams | Jun 2013 | A1 |
| 20130149975 | Yu et al. | Jun 2013 | A1 |
| 20130154387 | Lee et al. | Jun 2013 | A1 |
| 20130155748 | Sundstrom | Jun 2013 | A1 |
| 20130157729 | Tabe | Jun 2013 | A1 |
| 20130162335 | Kim et al. | Jun 2013 | A1 |
| 20130169061 | Microshnichenko et al. | Jul 2013 | A1 |
| 20130169219 | Gray | Jul 2013 | A1 |
| 20130169348 | Shi | Jul 2013 | A1 |
| 20130171939 | Tian et al. | Jul 2013 | A1 |
| 20130175877 | Abe et al. | Jul 2013 | A1 |
| 20130178253 | Karaoguz | Jul 2013 | A1 |
| 20130181881 | Christie et al. | Jul 2013 | A1 |
| 20130187475 | Vendik | Jul 2013 | A1 |
| 20130190031 | Persson et al. | Jul 2013 | A1 |
| 20130193769 | Mehta et al. | Aug 2013 | A1 |
| 20130197320 | Albert et al. | Aug 2013 | A1 |
| 20130200064 | Alexander | Aug 2013 | A1 |
| 20130207477 | Nam et al. | Aug 2013 | A1 |
| 20130207604 | Zeine | Aug 2013 | A1 |
| 20130207879 | Rada et al. | Aug 2013 | A1 |
| 20130210357 | Qin et al. | Aug 2013 | A1 |
| 20130221757 | Cho et al. | Aug 2013 | A1 |
| 20130222201 | Ma et al. | Aug 2013 | A1 |
| 20130234530 | Miyauchi | Sep 2013 | A1 |
| 20130234536 | Chemishkian et al. | Sep 2013 | A1 |
| 20130234658 | Endo et al. | Sep 2013 | A1 |
| 20130241306 | Aber et al. | Sep 2013 | A1 |
| 20130241468 | Moshfeghi | Sep 2013 | A1 |
| 20130241474 | Moshfeghi | Sep 2013 | A1 |
| 20130249478 | Hirano | Sep 2013 | A1 |
| 20130249479 | Partovi | Sep 2013 | A1 |
| 20130250102 | Scanlon et al. | Sep 2013 | A1 |
| 20130254578 | Huang et al. | Sep 2013 | A1 |
| 20130264997 | Lee et al. | Oct 2013 | A1 |
| 20130268782 | Tam et al. | Oct 2013 | A1 |
| 20130270923 | Cook et al. | Oct 2013 | A1 |
| 20130278076 | Proud | Oct 2013 | A1 |
| 20130278209 | Von Novak | Oct 2013 | A1 |
| 20130285464 | Miwa | Oct 2013 | A1 |
| 20130285477 | Lo et al. | Oct 2013 | A1 |
| 20130285606 | Ben-Shalom et al. | Oct 2013 | A1 |
| 20130288600 | Kuusilinna et al. | Oct 2013 | A1 |
| 20130288617 | Kim et al. | Oct 2013 | A1 |
| 20130293423 | Moshfeghi | Nov 2013 | A1 |
| 20130307751 | Yu-Juin et al. | Nov 2013 | A1 |
| 20130310020 | Kazuhiro | Nov 2013 | A1 |
| 20130311798 | Sultenfuss | Nov 2013 | A1 |
| 20130328417 | Takeuchi | Dec 2013 | A1 |
| 20130334883 | Kim et al. | Dec 2013 | A1 |
| 20130339108 | Ryder et al. | Dec 2013 | A1 |
| 20130343208 | Sexton et al. | Dec 2013 | A1 |
| 20130343251 | Zhang | Dec 2013 | A1 |
| 20140001846 | Mosebrook | Jan 2014 | A1 |
| 20140001875 | Nahidipour | Jan 2014 | A1 |
| 20140001876 | Fujiwara et al. | Jan 2014 | A1 |
| 20140006017 | Sen | Jan 2014 | A1 |
| 20140008992 | Leabman | Jan 2014 | A1 |
| 20140008993 | Leabman | Jan 2014 | A1 |
| 20140009108 | Leabman | Jan 2014 | A1 |
| 20140009110 | Lee | Jan 2014 | A1 |
| 20140011531 | Burstrom et al. | Jan 2014 | A1 |
| 20140015336 | Weber et al. | Jan 2014 | A1 |
| 20140015344 | Mohamadi | Jan 2014 | A1 |
| 20140021907 | Yun et al. | Jan 2014 | A1 |
| 20140021908 | McCool | Jan 2014 | A1 |
| 20140035524 | Zeine | Feb 2014 | A1 |
| 20140035526 | Tripathi et al. | Feb 2014 | A1 |
| 20140035786 | Ley | Feb 2014 | A1 |
| 20140043248 | Yeh | Feb 2014 | A1 |
| 20140049422 | Von Novak et al. | Feb 2014 | A1 |
| 20140054971 | Kissin | Feb 2014 | A1 |
| 20140055098 | Lee et al. | Feb 2014 | A1 |
| 20140057618 | Zirwas et al. | Feb 2014 | A1 |
| 20140062395 | Kwon et al. | Mar 2014 | A1 |
| 20140082435 | Kitgawa | Mar 2014 | A1 |
| 20140086125 | Polo et al. | Mar 2014 | A1 |
| 20140086592 | Nakahara et al. | Mar 2014 | A1 |
| 20140091756 | Ofstein et al. | Apr 2014 | A1 |
| 20140091968 | Harel et al. | Apr 2014 | A1 |
| 20140091974 | Desclos et al. | Apr 2014 | A1 |
| 20140103869 | Radovic | Apr 2014 | A1 |
| 20140104157 | Burns | Apr 2014 | A1 |
| 20140111147 | Soar | Apr 2014 | A1 |
| 20140113689 | Lee | Apr 2014 | A1 |
| 20140117946 | Muller et al. | May 2014 | A1 |
| 20140118140 | Amis | May 2014 | A1 |
| 20140128107 | An | May 2014 | A1 |
| 20140132210 | Partovi | May 2014 | A1 |
| 20140133279 | Khuri-Yakub | May 2014 | A1 |
| 20140139034 | Sankar et al. | May 2014 | A1 |
| 20140139039 | Cook et al. | May 2014 | A1 |
| 20140139180 | Kim et al. | May 2014 | A1 |
| 20140141838 | Cai et al. | May 2014 | A1 |
| 20140142876 | John et al. | May 2014 | A1 |
| 20140143933 | Low et al. | May 2014 | A1 |
| 20140145879 | Pan | May 2014 | A1 |
| 20140145884 | Dang et al. | May 2014 | A1 |
| 20140152117 | Sanker | Jun 2014 | A1 |
| 20140159651 | Von Novak et al. | Jun 2014 | A1 |
| 20140159652 | Hall et al. | Jun 2014 | A1 |
| 20140159662 | Furui | Jun 2014 | A1 |
| 20140159667 | Kim et al. | Jun 2014 | A1 |
| 20140169385 | Hadani et al. | Jun 2014 | A1 |
| 20140175893 | Sengupta et al. | Jun 2014 | A1 |
| 20140176054 | Porat et al. | Jun 2014 | A1 |
| 20140176061 | Cheatham, III et al. | Jun 2014 | A1 |
| 20140176082 | Visser | Jun 2014 | A1 |
| 20140177399 | Teng et al. | Jun 2014 | A1 |
| 20140184148 | Van Der Lee et al. | Jul 2014 | A1 |
| 20140184155 | Cha | Jul 2014 | A1 |
| 20140184163 | Das et al. | Jul 2014 | A1 |
| 20140184170 | Jeong | Jul 2014 | A1 |
| 20140191568 | Partovi | Jul 2014 | A1 |
| 20140191818 | Waffenschmidt et al. | Jul 2014 | A1 |
| 20140194092 | Wanstedt et al. | Jul 2014 | A1 |
| 20140194095 | Wanstedt et al. | Jul 2014 | A1 |
| 20140197691 | Wang | Jul 2014 | A1 |
| 20140203629 | Hoffman et al. | Jul 2014 | A1 |
| 20140206384 | Kim et al. | Jul 2014 | A1 |
| 20140210281 | Ito et al. | Jul 2014 | A1 |
| 20140217955 | Lin | Aug 2014 | A1 |
| 20140217967 | Zeine et al. | Aug 2014 | A1 |
| 20140225805 | Pan et al. | Aug 2014 | A1 |
| 20140232320 | Ento July et al. | Aug 2014 | A1 |
| 20140232610 | Shigemoto et al. | Aug 2014 | A1 |
| 20140239733 | Mach et al. | Aug 2014 | A1 |
| 20140241231 | Zeine | Aug 2014 | A1 |
| 20140245036 | Oishi | Aug 2014 | A1 |
| 20140246416 | White | Sep 2014 | A1 |
| 20140247152 | Proud | Sep 2014 | A1 |
| 20140252813 | Lee et al. | Sep 2014 | A1 |
| 20140252866 | Walsh et al. | Sep 2014 | A1 |
| 20140265725 | Angle et al. | Sep 2014 | A1 |
| 20140265727 | Berte | Sep 2014 | A1 |
| 20140265943 | Angle et al. | Sep 2014 | A1 |
| 20140266025 | Jakubowski | Sep 2014 | A1 |
| 20140266946 | Bily et al. | Sep 2014 | A1 |
| 20140273892 | Nourbakhsh | Sep 2014 | A1 |
| 20140281655 | Angle et al. | Sep 2014 | A1 |
| 20140292090 | Cordeiro et al. | Oct 2014 | A1 |
| 20140292451 | Zimmerman | Oct 2014 | A1 |
| 20140300452 | Rofe et al. | Oct 2014 | A1 |
| 20140312706 | Fiorello et al. | Oct 2014 | A1 |
| 20140325218 | Shimizu et al. | Oct 2014 | A1 |
| 20140327320 | Muhs et al. | Nov 2014 | A1 |
| 20140327390 | Park et al. | Nov 2014 | A1 |
| 20140333142 | Desrosiers | Nov 2014 | A1 |
| 20140346860 | Aubry et al. | Nov 2014 | A1 |
| 20140354063 | Leabman et al. | Dec 2014 | A1 |
| 20140354221 | Leabman et al. | Dec 2014 | A1 |
| 20140355718 | Guan et al. | Dec 2014 | A1 |
| 20140357309 | Leabman et al. | Dec 2014 | A1 |
| 20140368048 | Leabman | Dec 2014 | A1 |
| 20140368161 | Leabman et al. | Dec 2014 | A1 |
| 20140368405 | Ek et al. | Dec 2014 | A1 |
| 20140375139 | Tsukamoto | Dec 2014 | A1 |
| 20140375253 | Leabman et al. | Dec 2014 | A1 |
| 20140375255 | Leabman et al. | Dec 2014 | A1 |
| 20140375258 | Arkhipenkov | Dec 2014 | A1 |
| 20140375261 | Manova-Elssibony et al. | Dec 2014 | A1 |
| 20140376646 | Leabman et al. | Dec 2014 | A1 |
| 20150001949 | Leabman et al. | Jan 2015 | A1 |
| 20150002086 | Matos et al. | Jan 2015 | A1 |
| 20150003207 | Lee et al. | Jan 2015 | A1 |
| 20150008980 | Kim et al. | Jan 2015 | A1 |
| 20150011160 | Uurgovan et al. | Jan 2015 | A1 |
| 20150015180 | Miller et al. | Jan 2015 | A1 |
| 20150015182 | Brandtman et al. | Jan 2015 | A1 |
| 20150015192 | Leabamn | Jan 2015 | A1 |
| 20150015194 | Leabman et al. | Jan 2015 | A1 |
| 20150015195 | Leabman et al. | Jan 2015 | A1 |
| 20150021990 | Myer et al. | Jan 2015 | A1 |
| 20150022008 | Leabman et al. | Jan 2015 | A1 |
| 20150022009 | Leabman et al. | Jan 2015 | A1 |
| 20150022010 | Leabman et al. | Jan 2015 | A1 |
| 20150022194 | Almalki et al. | Jan 2015 | A1 |
| 20150023204 | Wil et al. | Jan 2015 | A1 |
| 20150028688 | Masaoka | Jan 2015 | A1 |
| 20150028694 | Leabman et al. | Jan 2015 | A1 |
| 20150028697 | Leabman et al. | Jan 2015 | A1 |
| 20150028875 | Irie et al. | Jan 2015 | A1 |
| 20150029397 | Leabman et al. | Jan 2015 | A1 |
| 20150035378 | Calhoun et al. | Feb 2015 | A1 |
| 20150035715 | Kim et al. | Feb 2015 | A1 |
| 20150039482 | Fuinaga | Feb 2015 | A1 |
| 20150041459 | Leabman et al. | Feb 2015 | A1 |
| 20150042264 | Leabman et al. | Feb 2015 | A1 |
| 20150042265 | Leabman et al. | Feb 2015 | A1 |
| 20150044977 | Ramasamy et al. | Feb 2015 | A1 |
| 20150046526 | Bush et al. | Feb 2015 | A1 |
| 20150061404 | Lamenza et al. | Mar 2015 | A1 |
| 20150076917 | Leabman et al. | Mar 2015 | A1 |
| 20150076927 | Leabman et al. | Mar 2015 | A1 |
| 20150077036 | Leabman et al. | Mar 2015 | A1 |
| 20150077037 | Leabman et al. | Mar 2015 | A1 |
| 20150091520 | Blum et al. | Apr 2015 | A1 |
| 20150091706 | Chemishkian et al. | Apr 2015 | A1 |
| 20150097442 | Muurinen | Apr 2015 | A1 |
| 20150097663 | Sloo et al. | Apr 2015 | A1 |
| 20150102681 | Leabman et al. | Apr 2015 | A1 |
| 20150102764 | Leabman et al. | Apr 2015 | A1 |
| 20150102769 | Leabman et al. | Apr 2015 | A1 |
| 20150102973 | Hand et al. | Apr 2015 | A1 |
| 20150108848 | Joehren | Apr 2015 | A1 |
| 20150109181 | Hyde et al. | Apr 2015 | A1 |
| 20150115877 | Aria et al. | Apr 2015 | A1 |
| 20150115878 | Park | Apr 2015 | A1 |
| 20150116153 | Chen et al. | Apr 2015 | A1 |
| 20150123483 | Leabman et al. | May 2015 | A1 |
| 20150123496 | Leabman et al. | May 2015 | A1 |
| 20150128733 | Taylor et al. | May 2015 | A1 |
| 20150130285 | Leabman et al. | May 2015 | A1 |
| 20150130293 | Hajimiri et al. | May 2015 | A1 |
| 20150137612 | Yamakawa et al. | May 2015 | A1 |
| 20150148664 | Stolka et al. | May 2015 | A1 |
| 20150155737 | Mayo | Jun 2015 | A1 |
| 20150155738 | Leabman et al. | Jun 2015 | A1 |
| 20150162751 | Leabman et al. | Jun 2015 | A1 |
| 20150162779 | Lee et al. | Jun 2015 | A1 |
| 20150171512 | Chen et al. | Jun 2015 | A1 |
| 20150171513 | Chen et al. | Jun 2015 | A1 |
| 20150171656 | Leabman et al. | Jun 2015 | A1 |
| 20150171658 | Manova-Elssibony et al. | Jun 2015 | A1 |
| 20150171931 | Won et al. | Jun 2015 | A1 |
| 20150177326 | Chakraborty et al. | Jun 2015 | A1 |
| 20150180133 | Hunt | Jun 2015 | A1 |
| 20150180249 | Jeon et al. | Jun 2015 | A1 |
| 20150181117 | Park et al. | Jun 2015 | A1 |
| 20150187491 | Yanagawa | Jul 2015 | A1 |
| 20150188352 | Peek et al. | Jul 2015 | A1 |
| 20150199665 | Chu | Jul 2015 | A1 |
| 20150201385 | Mercer et al. | Jul 2015 | A1 |
| 20150207333 | Baarman et al. | Jul 2015 | A1 |
| 20150207542 | Zeine | Jul 2015 | A1 |
| 20150222126 | Leabman et al. | Aug 2015 | A1 |
| 20150233987 | Von Novak, III et al. | Aug 2015 | A1 |
| 20150234144 | Cameron et al. | Aug 2015 | A1 |
| 20150236520 | Baarman | Aug 2015 | A1 |
| 20150244070 | Cheng et al. | Aug 2015 | A1 |
| 20150244080 | Gregoire | Aug 2015 | A1 |
| 20150244187 | Horie | Aug 2015 | A1 |
| 20150244201 | Chu | Aug 2015 | A1 |
| 20150244341 | Ritter et al. | Aug 2015 | A1 |
| 20150249484 | Mach et al. | Sep 2015 | A1 |
| 20150255989 | Walley et al. | Sep 2015 | A1 |
| 20150256097 | Gudan et al. | Sep 2015 | A1 |
| 20150260835 | Widmer et al. | Sep 2015 | A1 |
| 20150263534 | Lee et al. | Sep 2015 | A1 |
| 20150263548 | Cooper | Sep 2015 | A1 |
| 20150270618 | Zhu et al. | Sep 2015 | A1 |
| 20150270622 | Takasaki et al. | Sep 2015 | A1 |
| 20150270741 | Leabman et al. | Sep 2015 | A1 |
| 20150280484 | Radziemski et al. | Oct 2015 | A1 |
| 20150288074 | Harper et al. | Oct 2015 | A1 |
| 20150288438 | Maltsev et al. | Oct 2015 | A1 |
| 20150311585 | Church et al. | Oct 2015 | A1 |
| 20150312721 | Singh | Oct 2015 | A1 |
| 20150318729 | Leabman | Nov 2015 | A1 |
| 20150326024 | Bell et al. | Nov 2015 | A1 |
| 20150326025 | Bell et al. | Nov 2015 | A1 |
| 20150326051 | Bell et al. | Nov 2015 | A1 |
| 20150326063 | Leabman et al. | Nov 2015 | A1 |
| 20150326068 | Bell et al. | Nov 2015 | A1 |
| 20150326069 | Petras et al. | Nov 2015 | A1 |
| 20150326070 | Petras et al. | Nov 2015 | A1 |
| 20150326071 | Contopanagos | Nov 2015 | A1 |
| 20150326072 | Petras et al. | Nov 2015 | A1 |
| 20150326142 | Petras et al. | Nov 2015 | A1 |
| 20150326143 | Petras et al. | Nov 2015 | A1 |
| 20150327085 | Hadani | Nov 2015 | A1 |
| 20150333528 | Leabman | Nov 2015 | A1 |
| 20150333529 | Leabman | Nov 2015 | A1 |
| 20150333573 | Leabman | Nov 2015 | A1 |
| 20150333800 | Perry et al. | Nov 2015 | A1 |
| 20150340759 | Bridgelall et al. | Nov 2015 | A1 |
| 20150340903 | Bell et al. | Nov 2015 | A1 |
| 20150340909 | Bell et al. | Nov 2015 | A1 |
| 20150340910 | Petras et al. | Nov 2015 | A1 |
| 20150340911 | Bell et al. | Nov 2015 | A1 |
| 20150341087 | Moore et al. | Nov 2015 | A1 |
| 20150349574 | Leabman | Dec 2015 | A1 |
| 20150358222 | Berger et al. | Dec 2015 | A1 |
| 20150365137 | Miller et al. | Dec 2015 | A1 |
| 20150365138 | Miller et al. | Dec 2015 | A1 |
| 20160005068 | Im et al. | Jan 2016 | A1 |
| 20160012695 | Bell et al. | Jan 2016 | A1 |
| 20160013560 | Daniels | Jan 2016 | A1 |
| 20160013656 | Bell et al. | Jan 2016 | A1 |
| 20160013677 | Bell et al. | Jan 2016 | A1 |
| 20160013678 | Bell et al. | Jan 2016 | A1 |
| 20160013855 | Campos | Jan 2016 | A1 |
| 20160020636 | Khlat | Jan 2016 | A1 |
| 20160020647 | Leabman et al. | Jan 2016 | A1 |
| 20160020649 | Bell et al. | Jan 2016 | A1 |
| 20160020830 | Bell et al. | Jan 2016 | A1 |
| 20160028403 | McCaughan et al. | Jan 2016 | A1 |
| 20160042206 | Pesavento et al. | Feb 2016 | A1 |
| 20160054395 | Bell et al. | Feb 2016 | A1 |
| 20160054396 | Bell et al. | Feb 2016 | A1 |
| 20160054440 | Younis | Feb 2016 | A1 |
| 20160056635 | Bell | Feb 2016 | A1 |
| 20160056640 | Mao | Feb 2016 | A1 |
| 20160056669 | Bell | Feb 2016 | A1 |
| 20160056966 | Bell | Feb 2016 | A1 |
| 20160065005 | Won et al. | Mar 2016 | A1 |
| 20160079799 | Khlat | Mar 2016 | A1 |
| 20160087483 | Hietala et al. | Mar 2016 | A1 |
| 20160087486 | Pogorelik et al. | Mar 2016 | A1 |
| 20160094091 | Shin et al. | Mar 2016 | A1 |
| 20160094092 | Davlantes et al. | Mar 2016 | A1 |
| 20160099601 | Leabman et al. | Apr 2016 | A1 |
| 20160099602 | Leabman et al. | Apr 2016 | A1 |
| 20160099609 | Leabman et al. | Apr 2016 | A1 |
| 20160099610 | Leabman et al. | Apr 2016 | A1 |
| 20160099611 | Leabman et al. | Apr 2016 | A1 |
| 20160099612 | Leabman et al. | Apr 2016 | A1 |
| 20160099613 | Leabman et al. | Apr 2016 | A1 |
| 20160099614 | Leabman et al. | Apr 2016 | A1 |
| 20160099755 | Leabman et al. | Apr 2016 | A1 |
| 20160099756 | Leabman et al. | Apr 2016 | A1 |
| 20160099757 | Leabman et al. | Apr 2016 | A1 |
| 20160099758 | Leabman et al. | Apr 2016 | A1 |
| 20160100124 | Leabman et al. | Apr 2016 | A1 |
| 20160100312 | Bell et al. | Apr 2016 | A1 |
| 20160112787 | Rich | Apr 2016 | A1 |
| 20160126749 | Shichino et al. | May 2016 | A1 |
| 20160126752 | Vuori et al. | May 2016 | A1 |
| 20160126776 | Kim et al. | May 2016 | A1 |
| 20160141908 | Jakl et al. | May 2016 | A1 |
| 20160164563 | Khawand et al. | Jun 2016 | A1 |
| 20160181849 | Govindaraj | Jun 2016 | A1 |
| 20160181854 | Leabman | Jun 2016 | A1 |
| 20160181867 | Daniel et al. | Jun 2016 | A1 |
| 20160181873 | Mitcheson et al. | Jun 2016 | A1 |
| 20160191121 | Bell | Jun 2016 | A1 |
| 20160202343 | Okutsu | Jul 2016 | A1 |
| 20160204622 | Leabman | Jul 2016 | A1 |
| 20160204642 | Oh | Jul 2016 | A1 |
| 20160233582 | Piskun | Aug 2016 | A1 |
| 20160238365 | Wixey et al. | Aug 2016 | A1 |
| 20160240908 | Strong | Aug 2016 | A1 |
| 20160248276 | Hong et al. | Aug 2016 | A1 |
| 20160294225 | Blum et al. | Oct 2016 | A1 |
| 20160299210 | Zeine | Oct 2016 | A1 |
| 20160301240 | Zeine | Oct 2016 | A1 |
| 20160322868 | Akuzawa et al. | Nov 2016 | A1 |
| 20160323000 | Liu et al. | Nov 2016 | A1 |
| 20160336804 | Son et al. | Nov 2016 | A1 |
| 20160339258 | Perryman et al. | Nov 2016 | A1 |
| 20160359367 | Rothschild | Dec 2016 | A1 |
| 20160380464 | Chin et al. | Dec 2016 | A1 |
| 20160380466 | Yang et al. | Dec 2016 | A1 |
| 20170005481 | Von Novak, III | Jan 2017 | A1 |
| 20170005516 | Leabman et al. | Jan 2017 | A9 |
| 20170005524 | Akuzawa et al. | Jan 2017 | A1 |
| 20170005530 | Zeine et al. | Jan 2017 | A1 |
| 20170012448 | Miller et al. | Jan 2017 | A1 |
| 20170025903 | Song et al. | Jan 2017 | A1 |
| 20170026087 | Tanabe | Jan 2017 | A1 |
| 20170040700 | Leung | Feb 2017 | A1 |
| 20170043675 | Jones et al. | Feb 2017 | A1 |
| 20170047784 | Jung et al. | Feb 2017 | A1 |
| 20170187225 | Hosseini | Feb 2017 | A1 |
| 20170063168 | Uchida | Mar 2017 | A1 |
| 20170077733 | Jeong et al. | Mar 2017 | A1 |
| 20170077735 | Leabman | Mar 2017 | A1 |
| 20170077736 | Leabman | Mar 2017 | A1 |
| 20170077764 | Bell et al. | Mar 2017 | A1 |
| 20170077765 | Bell et al. | Mar 2017 | A1 |
| 20170077995 | Leabman | Mar 2017 | A1 |
| 20170085112 | Leabman et al. | Mar 2017 | A1 |
| 20170085120 | Leabman et al. | Mar 2017 | A1 |
| 20170085127 | Leabman | Mar 2017 | A1 |
| 20170085437 | Condeixa et al. | Mar 2017 | A1 |
| 20170092115 | Sloo et al. | Mar 2017 | A1 |
| 20170104263 | Hosseini | Apr 2017 | A1 |
| 20170110887 | Bell et al. | Apr 2017 | A1 |
| 20170110888 | Leabman | Apr 2017 | A1 |
| 20170110889 | Bell | Apr 2017 | A1 |
| 20170110914 | Bell | Apr 2017 | A1 |
| 20170127196 | Blum et al. | May 2017 | A1 |
| 20170134686 | Leabman | May 2017 | A9 |
| 20170141582 | Adolf et al. | May 2017 | A1 |
| 20170141583 | Adolf et al. | May 2017 | A1 |
| 20170163076 | Park et al. | Jun 2017 | A1 |
| 20170168595 | Sakaguchi et al. | Jun 2017 | A1 |
| 20170179763 | Leabman | Jun 2017 | A9 |
| 20170179771 | Leabman | Jun 2017 | A1 |
| 20170187198 | Leabman | Jun 2017 | A1 |
| 20170187222 | Hosseini | Jun 2017 | A1 |
| 20170187223 | Hosseini | Jun 2017 | A1 |
| 20170187228 | Hosseini | Jun 2017 | A1 |
| 20170187248 | Leabman | Jun 2017 | A1 |
| 20170187422 | Hosseini | Jun 2017 | A1 |
| 20170214422 | Na et al. | Jul 2017 | A1 |
| 20170338695 | Port | Nov 2017 | A1 |
| 20180040929 | Chappelle | Feb 2018 | A1 |
| 20180048178 | Leabman | Feb 2018 | A1 |
| 20180123400 | Leabman | May 2018 | A1 |
| 20180131238 | Leabman | May 2018 | A1 |
| 20180159338 | Leabman et al. | Jun 2018 | A1 |
| 20180159355 | Leabman | Jun 2018 | A1 |
| 20180166924 | Hosseini | Jun 2018 | A1 |
| 20180166925 | Hosseini | Jun 2018 | A1 |
| 20180198199 | Hosseini | Jul 2018 | A1 |
| 20180212474 | Hosseini | Jul 2018 | A1 |
| 20180226840 | Leabman | Aug 2018 | A1 |
| 20180241255 | Leabman | Aug 2018 | A1 |
| 20180262014 | Bell | Sep 2018 | A1 |
| 20180262040 | Contopanagos | Sep 2018 | A1 |
| 20180262060 | Johnston | Sep 2018 | A1 |
| 20180287431 | Liu et al. | Oct 2018 | A1 |
| 20180331429 | Kornaros | Nov 2018 | A1 |
| 20180331581 | Hosseini | Nov 2018 | A1 |
| 20180337534 | Bell et al. | Nov 2018 | A1 |
| 20180375340 | Bell et al. | Dec 2018 | A1 |
| 20180375368 | Leabman | Dec 2018 | A1 |
| 20180376235 | Leabman | Dec 2018 | A1 |
| 20190052115 | Hosseini | Feb 2019 | A1 |
| 20190074133 | Contopanagos | Mar 2019 | A1 |
| 20190074728 | Leabman | Mar 2019 | A1 |
| 20190089203 | Leabman | Mar 2019 | A1 |
| 20190131827 | Johnston | May 2019 | A1 |
| 20190173323 | Hosseini | Jun 2019 | A1 |
| 20190222070 | Leabman | Jul 2019 | A1 |
| 20190245389 | Johnston et al. | Aug 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 102292896 | Dec 2011 | CN |
| 102860037 | Jan 2013 | CN |
| 203826555 | Sep 2014 | CN |
| 104090265 | Oct 2014 | CN |
| 103380561 | Sep 2017 | CN |
| 200021665 | Feb 2002 | DE |
| 10-2003216953 | Feb 2015 | DE |
| 1028482 | Aug 2000 | EP |
| 1081506 | Mar 2001 | EP |
| 2397973 | Jun 2010 | EP |
| 2346136 | Jul 2011 | EP |
| 2545635 | Jan 2013 | EP |
| 2747195 | Jun 2014 | EP |
| 3067983 | Sep 2016 | EP |
| 3118970 | Jan 2017 | EP |
| 3145052 | Mar 2017 | EP |
| 2404497 | Feb 2005 | GB |
| 2002319816 | Oct 2002 | JP |
| 2006157586 | Jun 2006 | JP |
| 2007043432 | Feb 2007 | JP |
| 2008167017 | Jul 2008 | JP |
| 2013162624 | Aug 2013 | JP |
| 2015128349 | Jul 2015 | JP |
| WO2015177859 | Apr 2017 | JP |
| 20060061776 | Jun 2006 | KR |
| 20070044302 | Apr 2007 | KR |
| 100755144 | Sep 2007 | KR |
| 20110132059 | Dec 2011 | KR |
| 20110135540 | Dec 2011 | KR |
| 20120009843 | Feb 2012 | KR |
| 20120108759 | Oct 2012 | KR |
| 20130026977 | Mar 2013 | KR |
| 20140023409 | Feb 2014 | KR |
| 20140085200 | Jul 2014 | KR |
| 20150077678 | Jul 2015 | KR |
| WO 199508125 | Mar 1995 | WO |
| WO 199831070 | Jul 1998 | WO |
| WO 9952173 | Oct 1999 | WO |
| WO 200111716 | Feb 2001 | WO |
| WO 2003091943 | Nov 2003 | WO |
| WO 2004077550 | Sep 2004 | WO |
| WO 2006122783 | Nov 2006 | WO |
| WO 2007070571 | Jun 2007 | WO |
| WO 2008024993 | Feb 2008 | WO |
| WO 2008156571 | Dec 2008 | WO |
| WO 2010022181 | Feb 2010 | WO |
| WO 2010039246 | Apr 2010 | WO |
| WO 2010138994 | Dec 2010 | WO |
| WO 2011112022 | Sep 2011 | WO |
| WO 2012177283 | Dec 2012 | WO |
| WO 2013031988 | Mar 2013 | WO |
| WO 2013035190 | Mar 2013 | WO |
| WO 2013038074 | Mar 2013 | WO |
| WO 2013042399 | Mar 2013 | WO |
| WO 2013052950 | Apr 2013 | WO |
| WO 2013105920 | Jul 2013 | WO |
| WO 2014075103 | May 2014 | WO |
| WO 2014132258 | Sep 2014 | WO |
| WO 2014134996 | Sep 2014 | WO |
| WO 2014182788 | Nov 2014 | WO |
| WO 2014182788 | Nov 2014 | WO |
| WO 2014197472 | Dec 2014 | WO |
| WO 2014209587 | Dec 2014 | WO |
| WO 2015038773 | Mar 2015 | WO |
| WO 2015097809 | Jul 2015 | WO |
| WO 2015161323 | Oct 2015 | WO |
| WO 2016024869 | Feb 2016 | WO |
| WO 2016048512 | Mar 2016 | WO |
| WO 2016187357 | Nov 2016 | WO |
| Entry |
|---|
| Energous Corp., ISRWO, PCT/US2014/037170, dated Sep. 15, 2014, 11 pgs. |
| Energous Corp., IPRP, PCT/US2014/037170, dated Nov. 10, 2015, 8 pgs. |
| Energous Corp., ISRWO, PCT/US2014/041534, dated Oct. 13, 2014, 10 pgs. |
| Energous Corp., IPRP, PCT/US2014/041534, dated Dec. 29, 2015, 7 pgs. |
| Energous Corp., ISRWO, PCT/US2014/046956, dated Nov. 12, 2014, 10 pgs. |
| Energous Corp., IPRP, PCT/US2014/046956, dated Jan. 19, 2016, 7 pgs. |
| Energous Corp., ISRWO, PCT/US2014/037072, dated Sep. 12, 2014, 8 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., IPRP, 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., ISRWO, PCT/US2014/062661, dated Jan. 27, 2015, 12 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, 2017, 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. |
| Energous Corp., ISRWO, PCT/US2018/012806 , dated Mar. 23, 2018, 9 pgs. |
| Energous Corp., ISRWO, PCT/US2017/046800 , dated Sep. 11, 2017, 13 pgs. |
| Energous Corp., ISRWO, PCT/US2017/065886, dated Apr. 6, 2018, 13 pgs. |
| Order Granting Reexamination Request Control No. 90013793 Aug. 31, 2016, 23 pgs. |
| Ossia Inc. vs Energous Corp., PGR2016-00023—Institution Decision, Nov. 29, 2016, 29 pgs. |
| Ossia Inc. vs Energous Corp., PGR2016-00024—Institution Decision, Nov. 29, 2016, 50 pgs. |
| Ossia Inc. vs Energous Corp., PGR2016-00024—Judgement-Adverse, Jan. 20, 2017, 3 pgs. |
| ReExam Ordered Control No. 90013793 Feb. 2, 2017, 8 pgs. |
| Ossia Inc. vs Energous Corp., Declaration of Stephen B. Heppe in Support of Petition for Post-Grant Review of U.S. Pat. No. 9,124,125, PGR2016-00024, May 31, 2016, 122 pgs. |
| Ossia Inc. vs Energous Corp., Petition for Post-Grant Review of U.S. Pat. No. 9,124,125, May 31, 2016, 92 pgs. |
| Ossia Inc. vs Energous Corp., Patent Owner Preliminary Response, Sep. 8, 2016, 95 pgs. |
| Ossia Inc. vs Energous Corp., Petition for Post Grant Review of U.S. Pat. No. 9,124,125, May 31, 2016, 86 pgs. |
| Ossia Inc. vs Energous Corp., Declaration of Stephen B. Heppe in Support of Petition for Post-Grant Review of U.S. Pat. No. 9,124,125, PGR2016-00023, May 31, 2016, 144 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, 7 pgs. |
| 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.8, 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. |
| European Search Report. EP15876036, dated May 3, 2018, 8 pgs. |
| European Search Report. EP15874273, dated Apr. 27, 2018, 7 pgs. |
| Supplemental European Search Report. EP3241277, dated Jun. 13, 2018, 10 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 Cybernetics vol. 43, No. 5. pp. 1318-1334, Oct. 3, 2013. |
| Zhai, “A Practical wireless charging system based on ultra-wideband retro-reflective 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 3 pgs. |
| 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. |
| Mascarenas et al.; “Experimental Studies of Using Wireless Energy Transmission for Powering Embedded Sensor Nodes.” Nov. 28, 2009, Journal of Sound and Vibration, pp. 2421-2433. |
| Li et al. High-Efficiency Switching-Mode Charger System Design Considerations with Dynamic Power Path Management, Mar./Apr. 2012 Issue, 8 pgs. |
| Energous Corp., ISRWO, PCT/US2016/069313 dated Nov. 13, 2017, 10 pgs. |
| Energous Corp., IPRP , PCT/US2016/069313 dated Jul. 3, 2018, 7 pgs. |
| Energous Corp., IPRP, PCT/US2016/068504, dated Jun. 26, 2018, 5 pgs. |
| Energous Corp., IPRP, PCT/US2016/068495, dated Jun. 26, 2018, 7 pgs. |
| Energous Corp., IPRP, PCT/US2016/068551, dated Jun. 26, 2018, 6 pgs. |
| Energous Corp., IPRP, PCT/US2016/068498, dated Jun. 26, 2018, 6 pgs. |
| Energous Corp., IPRP, PCT/US2016/068993, dated Jul. 3, 2018, 10 pgs. |
| Energous Corp., IPRP, PCT/US2016/068565, dated Jun. 26, 2018, 9 pgs. |
| Energous Corp., IPRP, PCT/US2016/068987, dated Jul. 3, 2018, 7 pgs. |
| Energous Corp., IPRP, PCT/US2016/069316 , dated Jul. 3, 2018, 12 pgs. |
| Energous. Corp., IPRP, PCT/US2018/012806 , dated Jul. 9, 2019, 6 pgs. |
| Energous Corp., IPRP, PCT/US2017/046800, dated Feb. 12, 2019, 10 pgs. |
| Energous Corp., ISRWO, PCT/US2018/025465, dated Jun. 22, 2018, 9 pgs. |
| Energous Corp., IPRP, PCT/US2017/065886, dated Jun. 18, 2019, 10 pgs. |
| Energous Corp., ISRWO, PCT/US2018/031768, dated Jul. 3, 2018, 9 pgs. |
| Energous Corp., ISRWO, PCT/US2018/039334, dated Sep. 11, 2018, 9 pgs. |
| Energous Corp., ISRWO, PCT/US2018/051082, dated Dec. 12, 2018, 9 pgs. |
| Energous Corp., ISRWO, PCT/US2018/064289, dated Mar. 28, 2019, 14 pgs. |
| Energous Corp., ISRWO, PCT/US2018/031786, dated Aug. 8, 2018, 9 pgs. |
| Energous Corp., ISRWO, PCT/US2019/021817, dated Apr. 6, 2019, 11 pgs. |
| Energous Corp., ISRWO, PCT/US2018/058178, dated Mar. 13, 2019, 10 pgs. |
| Energous Corp., ISRWO, PCT/US2019/015820, dated May 14, 2019, 9 pgs. |
| European Search Report. EP16882597, dated Aug. 7, 2019, 9 pgs. |
| Energous Corp., Supplementary European Search Report. EP15876043.9, dated Aug. 8, 2018, 9 pgs. |
| Energous Corp. Supplementary European Search Report, EP18204043.6, dated Feb. 14, 2019, 5 pgs. |
| Energous Corp. Supplementary European Search Report, EP 16880153.8, dated Jul. 2, 2019, 9 pgs. |
| Energous Corp., Supplementary European Search Report. EP17840412.5, dated Jul. 15, 2019, 8 pgs. |
| Energous Corp., Supplementary European Search Report. EP16880139-7, dated Jul. 12, 2019, 5 pgs. |
| Energous Corp., Supplementary European Search Report. EP16880158-7, dated Jul. 15, 2019, 5 pgs. |
| Energous Corp., Supplementary European Search Report. EP16882696-4, dated Jul. 3, 2019, 10 pgs. |
| Number | Date | Country | |
|---|---|---|---|
| 20180254639 A1 | Sep 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14748101 | Jun 2015 | US |
| Child | 15884303 | US | |
| Parent | 14587025 | Dec 2014 | US |
| Child | 14748101 | US | |
| Parent | 14585271 | Dec 2014 | US |
| Child | 14748101 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14337002 | Jul 2014 | US |
| Child | 14585271 | US | |
| Parent | 14330931 | Jul 2014 | US |
| Child | 14587025 | US | |
| Parent | 14330936 | Jul 2014 | US |
| Child | 14330931 | US |
