The present disclosure relates to wireless power outlets, and to methods of transferring power thereby.
The use of a wireless non-contact system for the purposes of automatic identification or tracking of items is an increasingly important and popular functionality.
Inductive power coupling allows energy to be transferred from a power supply to an electric load without a wired connection therebetween. An oscillating electric potential is applied across a primary inductor. This sets up an oscillating magnetic field in the vicinity of the primary inductor. The oscillating magnetic field may induce a secondary oscillating electrical potential in a secondary inductor placed close to the primary inductor. In this way, electrical energy may be transmitted from the primary inductor to the secondary inductor by electromagnetic induction without a conductive connection between the inductors.
When electrical energy is transferred from a primary inductor to a secondary inductor, the inductors are said to be inductively coupled. An electric load wired in series with such a secondary inductor may draw energy from the power source wired to the primary inductor when the secondary inductor is inductively coupled thereto.
In order to take advantage of the convenience offered by inductive power coupling, inductive outlets having primary inductors may be installed in different locations that people typically use to rest their devices, such that they may be charged while at rest.
According to one aspect of the presently disclosed subject matter, there is provided a wireless power receiver configured to receive power from a wireless power outlet and to communicate with a host for providing electrical power thereto, the wireless power receiver comprising:
The host control interface may further comprise a secondary power contact configured to facilitate the host to provide electrical power to the wireless power receiver.
The wireless power receiver may further comprise a controller, wherein the secondary power contact is configured to supply electrical power thereto.
The information-carrying contacts may comprise:
The wireless power receiver may be configured to provide a regulated voltage to the host on the supply input and power supply ground contacts when the secondary coil forms an inductive couple with a primary coil of a wireless power outlet.
The wireless power receiver may be configured to generate an INTERRUPT signal and transmit it to the host via the interrupt-signal contact.
The wireless power receiver may be configured to accept an ENABLE signal from the host via the enable-signal contact, and to modify its behavior based on the value of the ENABLE signal.
The wireless power receiver may further comprise a set of 16-bit internal registers, the wireless power receiver being configured to control its operation based on values stored in at least some of the registers.
The wireless power receiver may be configured to facilitate one or more of the following based on the values stored in the registers:
The registers may comprise one or more of the following:
For a better understanding of the embodiments and to show how it may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings.
With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of selected embodiments only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects. In this regard, no attempt is made to show structural details in more detail than is necessary for a fundamental understanding; the description taken with the drawings making apparent to those skilled in the art how the several selected embodiments may be put into practice. In the accompanying drawings:
As illustrated in
The secondary unit 200 is configured to operate with an electronic device (referred to herein as a “host”), such as a mobile telephone, a computer, a tablet, etc., and constitutes an inductive receiver thereof. (Herein the specification and claims, the terms “receiver”, “wireless receiver”, “wireless power receiver”, and “secondary unit” may be used interchangeably with one another.) It may be functionally connected thereto using any suitable arrangement. According to one non-limiting example, the secondary unit may be embedded in the host. According to another non-limiting example, the secondary unit 200 may be implemented on external hardware, such as a card or module, configured to interface with the host for providing electrical power thereto, such as described in the applicant's co-pending United States Patent Publication Number US 2014/0302782, which is incorporated herein by reference in its entirety.
The secondary unit 200 comprises a secondary inductive coil 210 configured to form an inductive couple with the primary inductive coil 110, thereby facilitating the secondary unit to draw power from the power source 120. The secondary unit 200 further comprises a host control interface (HCI) 220, configured to facilitate communication (e.g., power transfer, data transfer, etc.) between the secondary inductive coil 210 and components of the host, such as a power supply (e.g., a battery), host controller, etc. The secondary unit 200 further comprises a secondary controller 230, configured to direct operation thereof.
According to some non-limiting embodiments of the presently disclosed subject matter, the HCI 220 comprises seven electrical contacts 240a-240g (hereafter, when appropriate, indicated collectively by reference numeral 240) to permit communication between the secondary inductive coil 210 and the host. Each of the contacts 240 may terminate at a pin (not illustrated) at one or both sides, in order to facilitate physical connection thereof to a suitable portion of the host. Alternatively, the electrical contacts may each consist of a conducting line from the host to the HCI providing a conductive path therebetween.
According to some examples of the presently disclosed subject matter, the HCI may be configured to carry clock and/or data signals between the secondary unit 200 and the host. Accordingly, information-carrying contacts, e.g., a clock signal contact 240a (SCL contact) and a data signal contact 240b (SDA contact) may be provided. These contacts may be configured to facilitate communication, and especially clock and data signals, respectively, between the host and the secondary unit 200. The clock and/or data signals may conform to any suitable standard. For example, they may be compatible with NXP Semiconductor's Inter-Integrated Circuit protocol (hereafter referred to as “I2C protocol”), the specifications of which (published as “I2C-Bus Specification and User Manual” and available on NXP Semiconductor's website) are incorporated herein by reference.
The clock signal contact 240a and/or the data signal contact 240b may further be configured to provide a communication channel from the secondary unit 200 to the host battery.
Pull-up resistors (not illustrated), for example connected to a power supply of the host, may be provided to weakly “pull” the signals from the secondary unit 200. The host and secondary unit may each be configured to actively pull signals to a low state for ‘0’ state, and float a thereof bus for ‘1’.
The secondary unit 200 may be configured to serve as a slave under the standard to which it conforms. Alternatively, it may be configured to serve as a master, or selectively as either a master or a slave. For example, it may be configured to operate as a slave when communicating with the host, or as a master when communicating with the host's battery.
The HCI 220 may be provided to carry power signals between the host and the secondary unit 200. In order to facilitate this, the HCI 220 may comprise a power supply input contact 240c (VOUT) and a power supply ground contact 240d (GND) may be provided. Together, they are configured to cooperate to provide current between the host and the secondary unit 200. The secondary unit 200 may be configured to provide a regulated voltage on these contacts 240c, 240d whenever it forms an inductive couple with a suitable wireless power outlet 100, and is enabled by a control bus or a suitable control signal. The secondary unit 200 may be configured to decrease the voltage on these contacts 240c, 240d, for example by applying current limiting.
The secondary unit 200 may be configured to support optional generation of an INTERRUPT signal from it to the host. In order to facilitate this, the HCI 220 may comprise an interrupt-signal contact 240e (INT) to carry the INTERRUPT signal. The secondary receiver is configured to pull the INTERRUPT signal to zero to indicate that its status has changed, if generation thereof is enabled. The host may then use a transaction, e.g., supported by the standard to which it conforms, to query the secondary unit 200 for its exact status. The INTERRUPT signal may be cleared (i.e., returned to a logic ‘1’ state) by the host when a status register returned by the secondary unit 200 is read.
The host may be configured to send an ENABLE signal to the secondary unit 200 to enable or disable (i.e., by pulling the signal to ‘0’) charging. In order to facilitate this, the HCI 220 may comprise an enable-signal contact 240f (ENABLE). The secondary is configured to behave (e.g., to modify it behavior if necessary) in response to the ENABLE signal depending on its operational state (i.e., whether or not it forms an inductive couple (herein referred to as being “active with”) with a suitable wireless power outlet 100) and on a host setting of a “terminate” register of the secondary unit, as follows:
The host may be configured to supply electrical power to the secondary controller 230, e.g., when it is not drawing power from the wireless power outlet 100. In order to facilitate this, the HCI 220 may comprise an optional secondary power supply contact 240g (VCC contact). This may facilitate, e.g., the host to communicate with the secondary controller 230, for example to learn its capabilities.
It will be appreciated that as the secondary power supply contact 240g is optional, according to some non-limiting embodiments of the presently disclosed subject matter, the HCI 220 comprises six electrical contacts, i.e., a clock signal contact 240a, a data signal contact 240b, a power supply input contact 240c, a power supply ground contact 240d, an interrupt-signal contact 240e, and an enable-signal contact 240f, all as described above, mutatis mutandis.
The secondary unit 200 may be configured to communicate with the host using the contacts 240 as described above. Similarly, the host may be configured to communicate with the secondary unit 200 using the contacts are described above.
The host and secondary unit 200 may be co-configured to communicate with one another in a predefined way. For example, they may be co-configured to allow any one or more of the following:
The host and secondary unit 200 may be configured to communicate with one another based on the I2C protocol, for example with the secondary unit operating as a slave as defined therein. According to examples wherein the secondary unit 200 is implemented on external hardware, it may use a memory address of 0x1010111. A hardware bus may be provided, operating at a speed not exceeding 400 kHz. 7-bit addressing mode and ACK bits may be enabled. The secondary unit 200 may use the Read and Write word protocol option of the I2C protocol.
The secondary unit 200 may comprise a set of 16-bit internal registers to control it. The registers may be read or written via transactions defined in the I2C protocol.
The host and/or secondary unit 200 may be configured to execute “write” operations according to the following:
The host and/or secondary unit 200 may be configured to execute “read” operations. For each “read” operation, two transactions take place according to the following:
If a “read” operation needs to be repeated on the same register (e.g., polling of a register), the pointer does not need to be set again, as the pointer is already set. Similarly, if a register has been written using a “write” transaction, the same register may be read without the need to perform the pointer setting of the “write” transaction.
The “read” and “write” registers of the HCI 220 may comprise one or more of the following registers:
The identification and capability registers may comprise the following registers, all of which may be “read” registers:
The general status register may comprise a “receiver status” register, e.g. at register number 0x10, which stores values relating to the status and control of the receiver function. It may be a “read/write” register.
The receiver detectors configuration registers may comprise the following registers, all of which may be “read/write” registers:
The receiver to transmitter communication register may comprise a “receiver COM” register, e.g. at register number 0x1F, which stores values relating to access to 16 word FIFO of data received/transmitted from the transmitter host targeted to the receiver host. It may be a “read/write” register.
The firmware upgrade registers may comprise the following registers:
The transmitter advertising register may comprise a “transmitter advertising” register, e.g. at register number 0x50, which stores values relating to advertising provided by transmitter during a digital ping phase. It may be a “read” register.
The firmware upgrade registers may comprise the following registers:
The bits of the receiver capabilities register, which may be a “read” register, may store values relating to different capabilities of the receiver, as follows:
The remainder of the bits (according to the present example, bits 7, 8, and 11-15) of the receiver capabilities register may be reserved for future use.
The bits of the receiver standard register, which may be a “read” register, may store values relating to standards support of the receiver. One bit (e.g., bit ‘0’) may indicate whether the receiver is compatible with the PMA standard “PMA Receiver Specification” published by the Power Matters Alliance, the full contents of which are incorporated herein by reference (hereafter, “PMA standard”; it will be appreciated that the term “PMA standard” includes any document which subsequently supersedes it). The remainder of the bits (according to the present example, bits 1-15) of the receiver standard register may be reserved for future use.
The bits of the receiver status register for read operation, which may be a “read” register, may store values relating to the status of the receiver for read operations, as follows:
The remainder of the bits (according to the present example, bits 2-9) of the receiver status register for read operation may be reserved for future use.
The bits of the receiver status register for write operation, which may be a “write” register, may store values relating to the status of the receiver for write operations, as follows:
The remainder of the bits (according to the present example, bits 1-14) of the receiver status register for write operation may be reserved for future use.
The bits of the receiver firmware status register for read access, which may be a “read” register, may be as follows:
The remainder of the bits (according to the present example, bits 12 and 13) of the receiver firmware status register for read access may be reserved for future use.
The bits of the receiver firmware status register for write access, which may be a “write” register, may be as follows:
The remainder of the bits (according to the present example, bits 12 and 13) of the receiver firmware status register for write access may be reserved for future use.
The bits of the transmitter advertising register, which may be a “read” register, may be as follows:
The remainder of the bits (according to the present example, bits 12-14) of the transmitter advertising register may be reserved for future use.
Those skilled in the art to which this invention pertains will readily appreciate that numerous changes, variations and modifications can be made without departing from the scope of the invention mutatis mutandis.
Technical and scientific terms used herein should have the same meaning as commonly understood by one of ordinary skill in the art to which the disclosure pertains. Nevertheless, it is expected that during the life of a patent maturing from this application many relevant systems and methods will be developed. Accordingly, the scope of the terms such as computing unit, network, display, memory, server and the like are intended to include all such new technologies a priori.
The terms “comprises”, “comprising”, “includes”, “including”, “having” and their conjugates mean “including but not limited to” and indicate that the components listed are included, but not generally to the exclusion of other components. Such terms encompass the terms “consisting of” and “consisting essentially of”.
The phrase “consisting essentially of” means that the composition or method may include additional ingredients and/or steps, but only if the additional ingredients and/or steps do not materially alter the basic and novel characteristics of the composition or method.
As used herein, the singular form “a”, “an” and “the” may include plural references unless the context clearly dictates otherwise. For example, the term “a compound” or “at least one compound” may include a plurality of compounds, including mixtures thereof.
The word “optionally” is used herein to mean “is provided in some embodiments and not provided in other embodiments”. Any particular embodiment of the disclosure may include a plurality of “optional” features unless such features conflict.
Whenever a numerical range is indicated herein, it is meant to include any cited numeral (fractional or integral) within the indicated range. The phrases “ranging/ranges between” a first indicate number and a second indicate number and “ranging/ranges from” a first indicate number “to” a second indicate number are used herein interchangeably and are meant to include the first and second indicated numbers and all the fractional and integral numerals therebetween. It should be understood, therefore, that the description in range format is merely for convenience and brevity and should not be construed as an inflexible limitation on the scope of the disclosure. Accordingly, the description of a range should be considered to have specifically disclosed all the possible subranges as well as individual numerical values within that range. For example, description of a range such as from 1 to 6 should be considered to have specifically disclosed subranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6 etc., as well as individual numbers within that range, for example, 1, 2, 3, 4, 5, and 6 as well as non-integral intermediate values. This applies regardless of the breadth of the range.
It is appreciated that certain features of the disclosure, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the disclosure, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination or as suitable in any other described embodiment of the disclosure. Certain features described in the context of various embodiments are not to be considered essential features of those embodiments, unless the embodiment is inoperative without those elements.
Although the disclosure has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the disclosure.
All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present disclosure. To the extent that section headings are used, they should not be construed as necessarily limiting.
The present application is a continuation of U.S. patent application Ser. No. 14/665,762, filed Mar. 23, 2015, which is in turn based upon and claims the benefit of the priority of U.S. Provisional Patent Application Ser. No. 61/969,159, filed Mar. 23, 2014, each of which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3414796 | Henquet | Dec 1968 | A |
3771085 | Hojo et al. | Nov 1973 | A |
3938018 | Dahl | Feb 1976 | A |
4160193 | Richmond | Jul 1979 | A |
4349814 | Akehurst | Sep 1982 | A |
RE31524 | Hoebel | Feb 1984 | E |
4431948 | Elder et al. | Feb 1984 | A |
4580062 | MacLaughlin | Apr 1986 | A |
4754180 | Kiedrowski | Jun 1988 | A |
4977515 | Rudden et al. | Dec 1990 | A |
5221877 | Falk | Jun 1993 | A |
5278771 | Nyenya | Jan 1994 | A |
5367242 | Hulman | Nov 1994 | A |
5455466 | Parks et al. | Oct 1995 | A |
5455467 | Young et al. | Oct 1995 | A |
5486394 | Stough | Jan 1996 | A |
5528113 | Boys et al. | Jun 1996 | A |
5550452 | Shirai et al. | Aug 1996 | A |
5600225 | Goto | Feb 1997 | A |
5713939 | Nedungadi et al. | Feb 1998 | A |
5734254 | Stephens | Mar 1998 | A |
5762250 | Carlton et al. | Jun 1998 | A |
5821728 | Schwind | Oct 1998 | A |
5821731 | Kuki et al. | Oct 1998 | A |
5880035 | Fukuda | Mar 1999 | A |
5907285 | Toms et al. | May 1999 | A |
5929598 | Nakama et al. | Jul 1999 | A |
5949214 | Broussard et al. | Sep 1999 | A |
6042005 | Basile et al. | Mar 2000 | A |
6127799 | Krishnan | Oct 2000 | A |
6211649 | Matsuda | Apr 2001 | B1 |
6230029 | Hahn et al. | May 2001 | B1 |
6396935 | Makkonen | May 2002 | B1 |
6436299 | Baarman et al. | Aug 2002 | B1 |
6441589 | Frerking et al. | Aug 2002 | B1 |
6484260 | Scott et al. | Nov 2002 | B1 |
6532298 | Cambier et al. | Mar 2003 | B1 |
6586909 | Trepka | Jul 2003 | B1 |
6624616 | Frerking et al. | Sep 2003 | B1 |
6644557 | Jacobs | Nov 2003 | B1 |
6673250 | Kuennen et al. | Jan 2004 | B2 |
6721540 | Kayakawa | Apr 2004 | B1 |
6731071 | Baarman | May 2004 | B2 |
6766040 | Catalano et al. | Jul 2004 | B1 |
6803744 | Sabo | Oct 2004 | B1 |
6825620 | Kuennen et al. | Nov 2004 | B2 |
6888438 | Hui et al. | May 2005 | B2 |
6894457 | Germagian et al. | May 2005 | B2 |
D519275 | Shertzer | Apr 2006 | S |
7043060 | Quintana | May 2006 | B2 |
7126450 | Baarman et al. | Oct 2006 | B2 |
7132918 | Baarman et al. | Nov 2006 | B2 |
7164255 | Hui | Jan 2007 | B2 |
7180248 | Kuennen et al. | Feb 2007 | B2 |
7180265 | Naskali et al. | Feb 2007 | B2 |
7224086 | Germagian et al. | May 2007 | B2 |
7233319 | Johnson et al. | Jun 2007 | B2 |
D553852 | Brandenburg | Oct 2007 | S |
7278310 | Rice et al. | Oct 2007 | B1 |
7385357 | Kuennen et al. | Jun 2008 | B2 |
7392068 | Dayan et al. | Jun 2008 | B2 |
7405535 | Frerking et al. | Jul 2008 | B2 |
7462951 | Baarman | Dec 2008 | B1 |
D586809 | Jones et al. | Feb 2009 | S |
7518267 | Baarman | Apr 2009 | B2 |
7522878 | Baarman | Apr 2009 | B2 |
7576514 | Hui | Aug 2009 | B2 |
D599735 | Amidei et al. | Sep 2009 | S |
D599736 | Ferber et al. | Sep 2009 | S |
D599737 | Amidei et al. | Sep 2009 | S |
D599738 | Amidei et al. | Sep 2009 | S |
D603603 | Laine et al. | Nov 2009 | S |
7612528 | Baarman et al. | Nov 2009 | B2 |
D607879 | Ferber et al. | Jan 2010 | S |
D611407 | Webb | Mar 2010 | S |
D611408 | Ferber et al. | Mar 2010 | S |
8049370 | Azancot | Nov 2011 | B2 |
8787848 | Kielb | Jul 2014 | B2 |
8847571 | Kielb | Sep 2014 | B2 |
9331750 | Mach | May 2016 | B2 |
20020057584 | Brockmann | May 2002 | A1 |
20020158512 | Mizutani et al. | Oct 2002 | A1 |
20030042740 | Holder | Mar 2003 | A1 |
20030210106 | Cheng et al. | Nov 2003 | A1 |
20040023633 | Gordon | Feb 2004 | A1 |
20040195767 | Randall | Oct 2004 | A1 |
20040203537 | Yoshida et al. | Oct 2004 | A1 |
20040242264 | Cho | Dec 2004 | A1 |
20040261802 | Griffin et al. | Dec 2004 | A1 |
20050007067 | Baarman et al. | Jan 2005 | A1 |
20050083020 | Baarman | Apr 2005 | A1 |
20050130593 | Michalak | Jun 2005 | A1 |
20050164636 | Palermo et al. | Jul 2005 | A1 |
20050169506 | Fenrich et al. | Aug 2005 | A1 |
20050174473 | Morgan | Aug 2005 | A1 |
20050189910 | Hui | Sep 2005 | A1 |
20050192062 | Michkle et al. | Sep 2005 | A1 |
20050233768 | Guo et al. | Oct 2005 | A1 |
20060022214 | Morgan | Feb 2006 | A1 |
20060028176 | Tang et al. | Feb 2006 | A1 |
20060043927 | Beart et al. | Mar 2006 | A1 |
20060052144 | Seil et al. | Mar 2006 | A1 |
20060061325 | Tang et al. | Mar 2006 | A1 |
20060071632 | Ghabra et al. | Apr 2006 | A1 |
20060091222 | Leung et al. | May 2006 | A1 |
20060093132 | Desormiere et al. | May 2006 | A1 |
20060202665 | Hsu | Sep 2006 | A1 |
20070023559 | Scapillato et al. | Feb 2007 | A1 |
20070057763 | Blattner et al. | Mar 2007 | A1 |
20070076459 | Limpkin | Apr 2007 | A1 |
20070103110 | Sagoo | May 2007 | A1 |
20070136593 | Plavcan et al. | Jun 2007 | A1 |
20070165371 | Brandenburg | Jul 2007 | A1 |
20070182367 | Partovi | Aug 2007 | A1 |
20070210889 | Baarman et al. | Sep 2007 | A1 |
20070279002 | Partovi | Dec 2007 | A1 |
20080001922 | Johnson et al. | Jan 2008 | A1 |
20080030985 | Jeon et al. | Feb 2008 | A1 |
20080049988 | Basile et al. | Feb 2008 | A1 |
20080055047 | Osada et al. | Mar 2008 | A1 |
20080079388 | Sarnowsky et al. | Apr 2008 | A1 |
20080132293 | Gundlach et al. | Jun 2008 | A1 |
20080157715 | Rosenboom et al. | Jul 2008 | A1 |
20080223926 | Miller et al. | Sep 2008 | A1 |
20080258680 | Frerking et al. | Oct 2008 | A1 |
20080265835 | Reed et al. | Oct 2008 | A1 |
20090026959 | Lin et al. | Jan 2009 | A1 |
20090040807 | Doumae et al. | Feb 2009 | A1 |
20090047768 | Jain | Feb 2009 | A1 |
20090047769 | Bhat et al. | Feb 2009 | A1 |
20090075704 | Wang | Mar 2009 | A1 |
20090079387 | Jin et al. | Mar 2009 | A1 |
20090084705 | Justiss | Apr 2009 | A1 |
20090097221 | Sayed et al. | Apr 2009 | A1 |
20090102416 | Burley | Apr 2009 | A1 |
20090134972 | Wu, Jr. et al. | May 2009 | A1 |
20090146608 | Lee | Jun 2009 | A1 |
20090153098 | Toya et al. | Jun 2009 | A1 |
20090153297 | Gardner | Jun 2009 | A1 |
20090174263 | Baarman et al. | Jul 2009 | A1 |
20090203355 | Clark | Aug 2009 | A1 |
20090212639 | Johnson | Aug 2009 | A1 |
20090226050 | Hughes | Sep 2009 | A1 |
20090243791 | Partin et al. | Oct 2009 | A1 |
20090251102 | Hui | Oct 2009 | A1 |
20090273891 | Peiker | Nov 2009 | A1 |
20090278494 | Randall | Nov 2009 | A1 |
20100039066 | Yuan et al. | Feb 2010 | A1 |
20110036659 | Erjawetz et al. | Feb 2011 | A1 |
20110128694 | Saito | Jun 2011 | A1 |
20130043833 | Katz | Feb 2013 | A1 |
20130285606 | Ben-Shalom | Oct 2013 | A1 |
20140035521 | Endo | Feb 2014 | A1 |
20140057575 | Ayukawa | Feb 2014 | A1 |
20140142876 | John | May 2014 | A1 |
20140176076 | Momo | Jun 2014 | A1 |
20140184162 | Takahashi | Jul 2014 | A1 |
20140184165 | Takahashi | Jul 2014 | A1 |
20140184172 | Momo | Jul 2014 | A1 |
20140203661 | Dayan | Jul 2014 | A1 |
20140302782 | Raab | Oct 2014 | A1 |
20140349572 | Ben-Shalom | Nov 2014 | A1 |
Number | Date | Country |
---|---|---|
0160990 | Nov 1985 | EP |
0160990 | Jan 1991 | EP |
0558316 | Sep 1993 | EP |
1220150 | Jul 2002 | EP |
1990734 | Nov 2008 | EP |
2399466 | Sep 2004 | GB |
2399466 | Nov 2005 | GB |
2429372 | Feb 2007 | GB |
04-156242 | May 1992 | JP |
07-039078 | Feb 1995 | JP |
2001-309579 | Nov 2001 | JP |
2005-006440 | Jan 2005 | JP |
2005-110412 | Apr 2005 | JP |
2006-102055 | Apr 2006 | JP |
2007-529110 | Oct 2007 | JP |
9602879 | Feb 1996 | WO |
0201557 | Jan 2002 | WO |
0215320 | Feb 2002 | WO |
2005041281 | May 2005 | WO |
2005043775 | May 2005 | WO |
2006015143 | Feb 2006 | WO |
2006037972 | Apr 2006 | WO |
2008030985 | Mar 2008 | WO |
2008086080 | Jul 2008 | WO |
2008093334 | Aug 2008 | WO |
2008114268 | Sep 2008 | WO |
2009040807 | Apr 2009 | WO |
2009047768 | Apr 2009 | WO |
2009047769 | Apr 2009 | WO |
2009049657 | Apr 2009 | WO |
2009108958 | Sep 2009 | WO |
2010025156 | Mar 2010 | WO |
2010025157 | Mar 2010 | WO |
2011036659 | Mar 2011 | WO |
Entry |
---|
Office Action dated Mar. 22, 2013, for Mexican Application MX/a/2011/003088. |
Office Action dated Feb. 5, 2013, for Chinese Application 201110058458.7 |
Office Action dated May 28, 2013, for Japanese Application 2010-526422. |
Office Action dated May 28, 2013, for Japanese Application 2010-528526. |
Office Action dated May 21, 2013, for Japanese Application 2011-500345. |
International Search Report for International Application No. PCT/IL2012/050544 dated Jun. 8, 2013. |
Liu et al. “An Analysis of Double-layer Electromagnetic Shield for a Universal Contactless Battery Charging Platform”, IEEE 2005, p. 1767-1772. |
Hui et al. “A New Generation of Universal Contactless Battery Charging Platform for Portable Consumer Electronic Equipment”, IEEE Transactions on Power Electronics May 2005, vol. 20, No. 3, p. 620-627. |
Liu et al. “Equivalent Circuit Modeling of a Multiplayer Planar Winding Array Structure for Use in a Universal Contactless Battery Charging Platform”, IEEE Transactions on Power Electronics Jan. 2007, vol. 22, No. 1, p. 21-29. |
Tang et al. “Evaluation of the Shielding Effects on Printed-Circuit-Board Transformers Using Ferrite Plates and Copper Sheets”, IEEE Transactions on Power Electronics Nov. 2002, vol. 17, No. 6, p. 1080-1088. |
Su et al. “Extended Theory on the Inductance Calculation of Planar Spiral Windings Including the Effect of Double-layer Electromagnetic Shield”, IEEE 2007, p. 3022-3028. |
Liu et al. “Optimal Design of a Hybrid Winding Structure for Planar Contactless Battery Charging Platform”, IEEE Transactions of Power Electronics Jan. 2008, vol. 23, No. 1, p. 455-463. |
Liu et al. “Simulation Study and Experimental Verification of a Universal Contactless Battery Charging Platform WIth Localized Charging Features”, IEEE Transactions on Power Electronics Nov. 2007, vol. 22, No. 6, p. 2202-2210. |
International Search Report for PCT/IL2009/000915 Completed by the European Patent Office on Mar. 15, 2010, 3 Pages. |
Search report and Written Opinion for PCT/IL2008/001282, Both completed by the US Patent Office on Feb. 25, 2009, 9 pages all together. |
Search Report and Written Opinion for PCT/IL2008/001347, Both completed by the US Patent Office on Feb. 2, 2009, 10 Pages all together. |
Search Report and Written Opinion for PCT/IL2008/001348, Both completed by the US Patent Office on Jan. 28, 2009, 9 Pages all together. |
International Search Report for PCT/IL2008/01641, Completed by the US Patents and Trademark Office on May 21, 2009, 3 Pages. |
International Search Report on Patentability dated Sep. 21, 2010, for Corresponding Application PCT/IL2008/001641. |
Number | Date | Country | |
---|---|---|---|
20160204657 A1 | Jul 2016 | US |
Number | Date | Country | |
---|---|---|---|
61969159 | Mar 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14665762 | Mar 2015 | US |
Child | 15078561 | US |