The present invention relates generally to wireless charging systems and, more particularly, to techniques for detecting the presence of foreign objects in wireless charging systems.
In a conventional wireless charging system, a power source (referred to herein as a power-transmitting node or TX) transmits power wirelessly via inductive coupling to a power sink (referred to herein as a power-receiving node or RX) that is placed on or at least near the TX in order to charge or power the RX. The inductive coupling between a TX and an RX is achieved via resonant transducer circuitry in each node having similar if not identical resonant frequencies. To determine whether an RX is present, the TX will periodically or intermittently execute digital pings and, if present, an RX will respond by transmitting an ack message acknowledging its presence. The term “digital ping” refers to the TX inserting energy into its resonant transducer circuitry, which thereby transfers power to the RX's resonant transducer circuitry, which in turn causes the RX to transmit an ack message back to the TX. After receiving the ack message from the RX, the TX will initiate a power-transfer session to transmit power to the RX. During a power-transfer session, the RX will transmit CEP (control error packet) messages instructing the TX to increase or decrease its transmitted power level.
If a metal foreign objected (FO), like a coin, a key, or other metal object, is placed on or at least near the TX during a power-transfer session, inductive coupling between the TX and the FO may result in the generation of heat in the FO that can be a fire hazard or result in damage to the FO, the TX, and/or the RX. As such, the conventional TX is designed to monitor power loss during its power-transfer sessions, where power loss is defined as the amount of power transmitted by the TX that is not received by the RX.
To enable a TX to determine power loss, a conventional RX monitors its level of received power and periodically or intermittently transmits RP (received power) packets to the TX informing the TX of the RX's received power level. The TX monitors its level of transmitted power and determines the power loss as the difference between the TX's transmitted power level and the RX's received power level. If the TX determines that the power loss exceeds a specified power-loss threshold, then the TX determines that an FO is present, and in such case, the TX terminates the power-transfer session and enters a protection state in which the TX cannot transfer power to the RX.
The conventional RX determines its received power level by monitoring the current and voltage levels within its resonant transducer circuitry. Similarly, a conventional TX determines its transmitted power level by monitoring the current and voltage levels within its own resonant transducer circuitry. Since the RX and TX power levels vary over time, the TX will compare the current value of the RX's received power level with the current value of its own transmitted power level that corresponds to the same time period during which the RX measured its received power level.
When a CEP or RP packet is transferred from an RX to a TX during a power-transfer session, the current and voltage levels in the resonant transducer circuitries of the RX and the TX can be disrupted enough such that the respective determined received and transmitted power levels may be inaccurate. As such, the RX and the TX do not measure their respective received and transmitted power levels during periods of packet transfer.
For example, at the end of transmission of CEP packet #1, the RX resumes accumulating data corresponding to its received power level. Similarly, at the end of receipt of CEP packet #1, the TX resumes accumulating data corresponding to its transmitted power level.
At the beginning of transmission of CEP packet #2, the RX stops accumulating data corresponding to its received power level. Similarly, at the beginning of receipt of CEP packet #2, the TX stops accumulating data corresponding to its transmitted power level.
At the end of transmission of CEP packet #2, the RX resumes accumulating data corresponding to its received power level. Similarly, at the end of receipt of CEP packet #2, the TX resumes accumulating data corresponding to its transmitted power level.
At the beginning of transmission of the RP packet, the RX stops accumulating data corresponding to its received power level. Similarly, at the beginning of receipt of the RP packet, the TX stops accumulating data corresponding to its transmitted power level.
The RX's received power level information contained in the RP packet is generated by the RX based on a subset of its current accumulation of data corresponding to its received power level. In particular, as indicated in
Note that the received and transmitted power levels are generated based on subsets of data accumulated just prior to the most-recent packet without including any data accumulated prior to any previously received packets. For example, in the example of
There are times when a TX does not properly receive a packet transmitted from an RX. In that case, the RX's most-recent accumulated data will not correspond in time with the TX's most-recent accumulated data, so as described further below with respect to
Embodiments of the invention will become more fully apparent from the following detailed description, the appended claims, and the accompanying drawings in which like reference numerals identify similar or identical elements.
Detailed illustrative embodiments of the invention are disclosed herein. However, specific structural and functional details disclosed herein are merely representative for purposes of describing example embodiments of the invention. The invention may be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein. Further, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments of the invention.
As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It further will be understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” specify the presence of stated features, steps, or components, but do not preclude the presence or addition of one or more other features, steps, or components. It also should be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
According to certain embodiments of the present invention, a power-transmitting node (TX) of a wireless charging system continuously accumulates data corresponding to its transmitted power level throughout each power-transfer mode during which the TX transmits power wirelessly to a power-receiving node (RX). The TX detects the end of each received power (RP) packet received from the RX and identifies a subset of its own accumulated data to use to generate its transmitted power level used to detect presence of a foreign object (FO).
Referring now to
The processing performed by the TX of the present invention, however, is different from the processing of the conventional TX. In particular, the TX continuously accumulates data corresponding to its transmitted power level throughout a power-transfer session. The TX also keeps track of the timing of the end of each received packet from the RX. When the TX detects the end of a received RP packet containing the RX's received power level, the TX generates its own transmitted power level using a subset of its accumulated data corresponding to its own transmitted power level. In a presently preferred embodiment, the TX identifies the subset of accumulated data based on the same WINSIZE and OFFSET parameters used by the RX plus a PKTLEN parameter that indicates the known duration of an RP packet. As indicated in
Because the TX processing is triggered by detection of the end of packet receipt rather than the beginning of packet receipt, the processing will not be corrupted by those occurrences when the TX is able to detect the beginning of a particular packet, but not the end of that packet, as compared to the conventional processing of
In some embodiments, the TX stores its transmitted power level data in a circular buffer such that the oldest data is overwritten by the newest data. The TX maintains pointers to keep track of the current location within the circular buffer as well as the locations of the data corresponding to periods of packet receipt.
In other embodiments, the TX stores its transmitted power level data in a non-circular buffer, such as a first-in, first-out (FIFO) linear shift register. Here, too, the TX maintains pointers identifying periods of packet receipt.
Although the invention has been described in the context of a scenario in which the CEP packet just before an RP packet (i.e., CEP packet #2 in
Note that, if an RP packet is not properly received, then the TX will not calculate its transmitted power level, and the TX will not perform its FO detection processing. Instead, the TX will continue to accumulate data corresponding to its transmitted power level, while it waits for proper receipt of a subsequent RP packet.
At step 506, the TX detects the end of a packet received from the RX, and, at step 508, the TX determines whether or not the packet was an RP packet. If the packet was not an RP packet (e.g., a CEP packet), then processing returns to step 504, where the TX continues to accumulate its transmitted power level data during the on-going power-transfer session.
If the TX determines that the packet was an RP packet at step 508, then processing continues to step 510, where the TX identifies the timing window corresponding to the subset of accumulated data in its transmitted power buffer to be used to calculate the transmitted power level.
At step 512, the TX calculates its transmitted power level using the accumulated data identified in step 510.
At step 514, the TX compares its transmitted power level calculated in step 512 to the RX's received power level identified in the RP packet and, at step 516, the TX uses that comparison to determine whether or not an FO is detected (e.g., if the difference between the TX's transmitted power level and the RX's received power level exceeds a specified threshold level, then an FO is detected). If an FO is not detected, then processing returns to step 504, where the TX continues to accumulate its transmitted power level data during the on-going power-transfer session.
If the TX detects the presence of an FO in step 516, then, at step 518, the TX ends the current power-transfer session and, at step 520, the TX transitions to its protection state.
The processor 602 may be implemented using dedicated hardware as well as hardware capable of executing appropriate software. The functions of the processor 602 may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term “processor” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP), network processor, application specific integrated circuit (ASIC), and/or field programmable gate array (FPGA) circuitry. Other hardware, conventional and/or custom, may also be included.
The memory 604 may be any suitable circuitry for storing data and/or software, such as read only memory (ROM), random access memory (RAM), and/or non-volatile storage, and may be integrated with the processor 602 and/or implemented as a distinct component.
Although the invention has been described in the context of a TX determining the end of the timing window by subtracting both the specified PKTLEN parameter and the specified OFFSET parameter from the time of the detected end of the received RP packet, in alternative embodiments, the TX can subtract a single parameter (equal to the sum of the PKTLEN and OFFSET parameters) from the end of the RP packet to determine the end of the timing window.
The invention has been described in the context of an embodiment in which the end of the timing window is determined based on the time of the detected end of the received RP packet. In another embodiment, the TX detects both the beginning and the end of a received RP packet, and uses the detection of the end of the RP packet to trigger the calculation of the TX's transmitted power level, and uses the time of the detected beginning of the RP packet to identify the end of the timing window (i.e., the OFFSET duration prior to the beginning of the RP packet). In such an embodiment, the TX does not need to be programmed with the specified PKTLEN value for the duration of an RP packet.
In some embodiments, a TX transmits power wirelessly to an RX in a wireless charging system. The TX comprises a processor, a memory, a power transmitter, and a signal receiver. The processor (i) accumulates data corresponding to transmitted power level of the TX, (ii) detects an end of an RP packet received from the RX, (iii) then identifies a subset of the accumulated data, and (iv) calculates the transmitted power level of the TX based on the subset of the accumulated data. The memory is used to store the accumulated data, the power transmitter transmits the power wirelessly to the RX, and the signal receiver receives the RP packet from the RX.
In some embodiments, the processor extracts a received power level of the RX from the received RP packet, and compares the transmitted power level of the TX with the received power level of the RX to detect presence of an FO.
In some embodiments, the processor identifies the subset of the accumulated data as the accumulated data within a timing window that ends a known duration prior to the end of the RP packet, while in other embodiments, the processor identifies the subset of the accumulated data as the accumulated data within a timing window that ends a known duration prior to a detected beginning of the RP packet.
In some embodiments, the processor continuously accumulates the data corresponding to the transmitted power level of the TX throughout a power-transfer session of the TX, and stores the accumulated data in a buffer in the memory.
Unless explicitly stated otherwise, each numerical value and range should be interpreted as being approximate as if the word “about” or “approximately” preceded the value or range.
It will be further understood that various changes in the details, materials, and arrangements of the parts which have been described and illustrated in order to explain embodiments of this invention may be made by those skilled in the art without departing from embodiments of the invention encompassed by the following claims.
In this specification including any claims, the term “each” may be used to refer to one or more specified characteristics of a plurality of previously recited elements or steps. When used with the open-ended term “comprising,” the recitation of the term “each” does not exclude additional, unrecited elements or steps. Thus, it will be understood that an apparatus may have additional, unrecited elements and a method may have additional, unrecited steps, where the additional, unrecited elements or steps do not have the one or more specified characteristics.
Reference herein to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments necessarily mutually exclusive of other embodiments. The same applies to the term “implementation.”
Number | Date | Country | Kind |
---|---|---|---|
2017 1 1323963 | Dec 2017 | CN | national |
Number | Name | Date | Kind |
---|---|---|---|
8983374 | Wiley | Mar 2015 | B2 |
9178387 | Mohammadian et al. | Nov 2015 | B2 |
9450648 | Bastami | Sep 2016 | B2 |
9465064 | Roy et al. | Oct 2016 | B2 |
9474031 | Sedzin et al. | Oct 2016 | B1 |
9530558 | Nakano et al. | Dec 2016 | B2 |
9614395 | Chiang | Apr 2017 | B2 |
20130069441 | Verghese | Mar 2013 | A1 |
20130094598 | Bastami | Apr 2013 | A1 |
20130257165 | Singh | Oct 2013 | A1 |
20130257168 | Singh | Oct 2013 | A1 |
20140015329 | Widmer | Jan 2014 | A1 |
20140015522 | Widmer et al. | Jan 2014 | A1 |
20140049422 | Von Novak | Feb 2014 | A1 |
20140084857 | Liu et al. | Mar 2014 | A1 |
20140111019 | Roy | Apr 2014 | A1 |
20140333145 | Lee et al. | Nov 2014 | A1 |
20140361738 | Lee et al. | Dec 2014 | A1 |
20150198640 | Lee | Jul 2015 | A1 |
20150318708 | Bartlett | Nov 2015 | A1 |
20150349543 | Sakata | Dec 2015 | A1 |
20150372493 | Sankar | Dec 2015 | A1 |
20160028443 | Kim | Jan 2016 | A1 |
20160190852 | Chiang et al. | Jun 2016 | A1 |
20170223637 | Wang et al. | Aug 2017 | A1 |
20170264144 | Park | Sep 2017 | A1 |
20180062504 | Mei et al. | Mar 2018 | A1 |
Number | Date | Country |
---|---|---|
205027804 | Feb 2016 | CN |
Number | Date | Country | |
---|---|---|---|
20190181692 A1 | Jun 2019 | US |