The present disclosure relates to electronic devices, and more particularly to electronic devices including one or more chargers for charging a battery.
The background description provided here is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
Electronic devices (e.g., smartphones, tablet or laptop computers, media players, etc.) are typically powered by a rechargeable battery. Accordingly, an electronic device may include a charger for receiving a voltage from an external source (e.g., from a power outlet via a plug-in power supply adapter) and providing current to the battery to recharge the battery.
For example only, in some implementations, a single charger configured for rapid charging may be used to charge the battery. In other implementations, the electronic device may include two or more chargers operating in parallel. The two or more chargers operate, and are controlled by an external processor, independently.
A battery charging system includes a master charger that receives a supply voltage, outputs a master charging current based on the supply voltage, and selectively outputs a slave charger control signal. At least one slave charger receives the slave charger control signal from the master charger, receives the supply voltage, and selectively outputs a slave charging current based on the slave charger control signal and the supply voltage.
A method for operating a battery charging system includes, using a master charger, receiving a supply voltage, outputting a master charging current based on the supply voltage, and selectively outputting a slave charger control signal. The method further includes, using at least one slave charger, receiving the slave charger control signal from the master charger; receiving the supply voltage, and selectively outputting a slave charging current based on the slave charger control signal and the supply voltage.
Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims and the drawings. The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.
The present disclosure will become more fully understood from the detailed description and the accompanying drawings, wherein:
In the drawings, reference numbers may be reused to identify similar and/or identical elements.
A battery charging system of an electronic device according to the principles of the present disclosure implements a first charger and one or more second chargers. The first charger operates as a master device with respect to the second chargers. In other words, the first charger and the second chargers correspond to, respectively, a master charger and slave chargers in a master-slave relationship.
The master charger may communicate with a control module of the electronic device (e.g., a host or application processor). The control module may communicate only with the master charger (e.g., with no direct communication between the control module and the slave chargers) to control operating parameters related to the charging of the battery. The master charger communicates with the slave chargers independently of the control module to selectively adjust operating parameters of the slave chargers. For example, the master charger may selectively enable and disable and adjust a current output of the slave chargers according to type of battery (e.g., high capacity batteries, high charge rate batteries, etc.) and/or other measured or desired operating parameters (e.g., load sharing, thermal balancing, temperature protection, etc.). The slave chargers communicate with the master charger independently of the control module to report various respective operation statuses (e.g., charging current, die temperature, etc.) and fault detection (thermal fault, over-current fault, over-voltage fault, etc.). The master charger alone may communicate with the control module to report the operation status and fault detection of the master charger as well as those of the slave chargers.
The master charger 104 receives a supply voltage (e.g., 5 V, 7 V, 9 V, 12 V, 20 V, etc.) from a voltage source 116. For example, the voltage source 116 corresponds to a plug-in adapter connected to a standard wall outlet or other source. The master charger 104 selectively provides current to charge a battery 120 according to the received supply voltage. As shown, the master charger 104 also provides the supply voltage to the slave charger 108. However, in some examples, the slave charger 108 may independently receive the supply voltage from the voltage source 116. The battery 120 provides power to the electronic device 112. The battery 120 may correspond to a single cell battery, multiple battery cells connected in series, etc.
The master charger 104 communicates with the slave charger 108 to control charging provided from the slave charger 108 to the battery 120. For example, the master charger 104 may communicate with the slave charger 108 via an interface 124, which may correspond to a single pin/wire serial interface or any other suitable communication interface (e.g., a multi-pin/wire interface). The interface 124 may be bi-directional, allowing the slave charger 108 to provide information to the master charger 104. Using the interface 124, the master charger 104 may selectively enable and disable the current output provided by the slave charger 108 for charging the battery 120. In some examples, the slave charger 108 may be further configured to adjust the amount of the current provided to the battery 120 based on commands received from the master charger 104 via the interface 124. For example, the master charger 104 controls the slave charger 108 to selectively enable and disable and/or adjust the current provided by the slave charger 108 according to load sharing requirements, thermal balancing, etc. For example only, in various modes, the current provided by the slave charger 108 may be less than, the same as, or greater than the current provided by the master charger 104.
The master charger 104 may communicate with a control module 128 via an interface 132. For example, the control module 128 may correspond to a host or application processor of the electronic device 112. The interface 132 may correspond to an I2C protocol or other suitable communication interface.
In this manner, the master charger 104 can control the slave charger 108 via the interface 124 to selectively provide a fast charging current to the battery 120. For example only, the master charger 104 may selectively enable and disable the slave charger 108 in various modes or states and based on various operating conditions. For example, the master charger 104 may control the charging provided by the slave charger 108 according to an adaptive input current limit (AICL), which may correspond to an adjustable maximum charging current to be provided to the battery 120. The various modes include, but are not limited to, a dead battery mode, a constant current (CC) mode, a constant voltage (CV) mode, a charge top-off mode, and/or a charging complete mode. For example, the slave charger 108 may be enabled during the CC mode, selectively enabled in the CV mode, and disabled in the dead battery mode, the charge top-off mode, and/or the charging complete mode. Accordingly, the master charger 104 may be configured to determine the AICL and control operation during the dead battery mode, the charge top-off mode, and/or the charging complete mode without the slave charger 108.
In some examples, the slave charger 108 may include one or more controlled current sources configured to selectively provide the charging current to the battery 120. The slave charger 108 may implement various protections including, but not limited to, input under and/or over voltage protection, input to output low headroom protection, battery overvoltage protection, output undervoltage protection, thermal regulation, and/or thermal shutdown protection. In other words, the slave charger 108 may be configured to, independent of the master charger 104 (e.g., commands received from the master charger 104), automatically disable and/or adjust the charging current in response to detecting various conditions.
Referring now to
The master charger 204 includes one or more charging switches 228-1, 228-2, and 228-3, referred to collectively as charging switches 228. Although three of the switches 228 are shown, those skilled in the art can appreciate that another number of switches (e.g., only one or two switches), other types of switches (e.g., NMOS, PMOS, etc.), and/or other configurations of the switches 228 may be used to provide a charging current from the master charger 204 to the battery 224. A master control module 232 selectively turns the switches 228 ON and OFF to control the charging current provided to the battery 224. The master control module 232 may receive feedback from the battery 224 and further control the charging current based on the feedback. For example only, the feedback may include a voltage across a sense resistor 236, which is indicative of a total charging current provided to the battery 224 by the master charger 204 and the slave charger 208. In other examples, the feedback may include other indicators of the total charging current provided to the battery 224, and/or the master control module 232 may implement other methods for sensing the current provided to the battery (e.g., including both lossy and lossless current sensing methods). The feedback may also include a ground sensing signal 240. The master control module 232 may communicate directly with the slave charger 208, and/or the master charger 204 may include a master-slave control module 244 for communicating with the slave charger 208.
The slave charger 208 includes a slave control module 248 for controlling charging switches 252-1 and 252-2, referred to collectively as charging switches 252. Although two of the switches 252 are shown, those skilled in the art can appreciate that another number of switches (e.g., one or three or more switches), other types of switches (e.g., NMOS, PMOS, etc.), and/or other configurations of the switches 252 may be used to provide a charging current from the slave charger 208 to the battery 224. For example, the charging switches 252 may include a switch analogous to the switch 228-3 of the master charger 204. The switches 252 receive the supply voltage from the master charger 204 (via the switch 216) and provide the charging current to the battery 224 accordingly. In other words, the switches 252 operate as a constant current source responsive to the slave control module 248. The total charging current supplied to the battery 224 corresponds to a sum of the charging currents provided by the master charger 204 and the slave charger 208. The charging currents provided by the master charger 204 and the slave charger 208 may be the same or different based on the control of the master charger 204. The battery 224 (and/or the master charger 204) provides power to output node 256 (i.e., to provide power to various components of an electronic device).
The master charger 204 provides commands from the master control module 232 and/or the master-slave control module 244 to the slave charger 208 via interface 260. For example, the master charger 204 selectively enables and disables the slave charger 208 and/or adjusts the charging current output by the slave charger 208 based on various operating modes and conditions. In this manner, the master charger 204, not an external host or application processor, controls operation of the slave charger 208.
In some examples, the battery charging system 200 implements thermal balancing. For example, the master control module 232 and/or the slave control module 248 monitor temperatures of components of the battery charging system 200 and/or components in the electronic device in the vicinity of the battery charging system 200 and adjust respective charging currents of the master charger 204 and the slave charger 208 accordingly. For example only, the battery charging system 200 may decrease the charging current of the slave charger 208 and increase the charging current of the master charger 204 while maintaining the same total charging current to reduce temperatures associated with the slave charger 208. Conversely, the battery charging system 200 may decrease the charging current of the master charger 204 and increase the charging current of the slave charger 208 while maintaining the same total charging current to reduce temperatures associated with the master charger 204.
Referring now to
In embodiments with multiple slave chargers (for example only, two slave chargers), in some modes the maximum charging current provided by the master charger may correspond to a first value (e.g., 3 amps) while the respective maximum charging currents provided by the slave chargers may correspond to a second value (e.g., 1.5 amps). In an example mode, the sum of the maximum respective charging currents provided by the slave chargers may be approximately equal to the maximum charging current provided by the master charger.
In embodiments, the respective charging currents provided by the slave chargers may be automatically adjusted according to the charging current provided by the master charger. For example, the respective charging currents provided by the slave chargers may be automatically adjusted to maintain a relationship where the sum of the respective charging currents provided by the slave chargers corresponds to the charging current provided by the master charger. The charging currents of the master charger and the slave charger may be updated (e.g., decreased) as the state of charge of the battery increases.
In an example shown in
In an example shown in
In an example shown in
In some examples, the battery charging system may store a slave charging current value and a master charger current value (e.g., in respective registers). These values may be compared (e.g., using a comparator) and the lower of these two values is output to the slave charger to control the slave charging current. This selection may be disabled to selectively allow the slave charging current to be greater than the master charging current in various modes.
In this manner, the slave charger 712 can be controlled such that the slave charging current is always less than or equal to the master charging current. In some examples, the output of the comparator 708 may be disabled. For example, a selector, such as a multiplexer 716, may selectively provide the output of the comparator 708 or the slave charging current value according to a disable signal. In other words, a state of the disable signal allows the slave charging current value to be selectively output regardless of whether the slave charging current value is less than the master charging current value. The output of the multiplexer 716 may be provided as feedback, and may be stored in a feedback register 720.
Referring now to
At 816, the method 800 (e.g., the master charger) determines whether to provide a slave charging current. For example, the method 800 determines whether to provide the slave charging current based on a command received from the control module, based on one or more sensed conditions, etc. If true, the method 800 continues to 820. If false, the method 800 continues to 808.
At 820, the method 800 (e.g., the master charger) outputs a slave charger control signal to command a slave charger to output the slave charging current. At 824, the method 800 (e.g., the master charger and/or the slave charger) selectively adjusts the slave charging current. For example, the method 800 adjusts the slave charging current based on a command, one or more sensed conditions, etc. At 828, the method 800 (e.g., the master charger and/or the slave charger) determines whether to disable the slave charging current. If true, the method 800 continues to 832. If false, the method 800 continues to 808. At 832, the method 800 disables the slave charging current and continues to 808.
The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure. Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.
Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.”
In this application, including the definitions below, the term “module” or the term “controller” may be replaced with the term “circuit.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code, a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.
The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces that are connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules that are connected via interface circuits. For example, multiple modules may allow load balancing. In a further example, a server (also known as remote, or cloud) module may accomplish some functionality on behalf of a client module.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. The term shared processor circuit encompasses a single processor circuit that executes some or all code from multiple modules. The term group processor circuit encompasses a processor circuit that, in combination with additional processor circuits, executes some or all code from one or more modules. References to multiple processor circuits encompass multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple modules. The term group memory circuit encompasses a memory circuit that, in combination with additional memories, stores some or all code from one or more modules.
The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium may therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory, tangible computer-readable medium are nonvolatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).
The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. The functional blocks, flowchart components, and other elements described above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.
The computer programs include processor-executable instructions that are stored on at least one non-transitory, tangible computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.
The computer programs may include: (i) descriptive text to be parsed, such as HTML (hypertext markup language) or XML (extensible markup language), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C#, Objective C, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5, Ada, ASP (active server pages), PHP, Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, and Python®.
None of the elements recited in the claims are intended to be a means-plus-function element within the meaning of 35 U.S.C. § 112(f) unless an element is expressly recited using the phrase “means for,” or in the case of a method claim using the phrases “operation for” or “step for.”
This application claims the benefit of U.S. Provisional Application No. 62/187,331, filed on Jul. 1, 2015. The entire disclosure of the application referenced above is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3947705 | Emmons | Mar 1976 | A |
4607208 | Vreeland | Aug 1986 | A |
5166596 | Goedken | Nov 1992 | A |
5281920 | Wurst | Jan 1994 | A |
5563455 | Cheng | Oct 1996 | A |
5670863 | Broell | Sep 1997 | A |
5955867 | Cummings | Sep 1999 | A |
6291972 | Zhang | Sep 2001 | B1 |
6774604 | Matsuda | Aug 2004 | B2 |
7135836 | Kutkut | Nov 2006 | B2 |
7135837 | Patino | Nov 2006 | B2 |
7193392 | King | Mar 2007 | B2 |
7245108 | Chertok | Jul 2007 | B2 |
7378818 | Fowler | May 2008 | B2 |
7511457 | Emori | Mar 2009 | B2 |
7535195 | Horovitz | May 2009 | B1 |
7554292 | Veselic | Jun 2009 | B2 |
7589498 | Choy | Sep 2009 | B2 |
7612539 | Woo | Nov 2009 | B2 |
7615966 | Houldsworth | Nov 2009 | B2 |
7911178 | Kawata | Mar 2011 | B2 |
8013570 | Baxter | Sep 2011 | B2 |
8054034 | Lim | Nov 2011 | B2 |
8093862 | Mariels | Jan 2012 | B2 |
8115453 | Houldsworth | Feb 2012 | B2 |
8129950 | Colin | Mar 2012 | B2 |
8193763 | Kawata | Jun 2012 | B2 |
8212571 | Emori | Jul 2012 | B2 |
8228040 | Utsumi | Jul 2012 | B2 |
8232765 | Billmaier | Jul 2012 | B2 |
8319478 | Humphrey | Nov 2012 | B2 |
8339099 | Emori | Dec 2012 | B2 |
8350529 | Loncarevic | Jan 2013 | B2 |
8401473 | Tang | Mar 2013 | B2 |
8426047 | Emori | Apr 2013 | B2 |
8436575 | Sim | May 2013 | B2 |
8436579 | Veselic | May 2013 | B2 |
8487581 | Tan | Jul 2013 | B2 |
8547065 | Trigiani | Oct 2013 | B2 |
8552589 | Ghosh | Oct 2013 | B2 |
8552704 | Kiadeh | Oct 2013 | B2 |
8648566 | Billmaier | Feb 2014 | B2 |
8723478 | Billmaier | May 2014 | B2 |
8729731 | Roepke | May 2014 | B2 |
8766597 | Nork | Jul 2014 | B2 |
8773078 | Yu | Jul 2014 | B2 |
8786256 | Emori | Jul 2014 | B2 |
8791668 | Emori | Jul 2014 | B2 |
8796990 | Paparo | Aug 2014 | B2 |
8798832 | Kawahara | Aug 2014 | B2 |
8810217 | Malmberg | Aug 2014 | B2 |
RE45208 | Humphrey | Oct 2014 | E |
8884584 | Emori | Nov 2014 | B2 |
8912756 | Emori | Dec 2014 | B2 |
8912758 | Kang | Dec 2014 | B2 |
8994338 | Khan | Mar 2015 | B2 |
9000935 | Dao | Apr 2015 | B2 |
9035600 | Park | May 2015 | B2 |
9093724 | Fujitake | Jul 2015 | B2 |
9276430 | Sporck | Mar 2016 | B2 |
9331497 | Beaston | May 2016 | B2 |
9362759 | Nakao | Jun 2016 | B2 |
9373979 | Ghosh | Jun 2016 | B2 |
9436261 | Yun | Sep 2016 | B2 |
9446679 | Kataoka | Sep 2016 | B2 |
9525293 | Ito | Dec 2016 | B2 |
9537336 | Suzuki | Jan 2017 | B2 |
9537402 | Kurauchi | Jan 2017 | B2 |
9559389 | Greef | Jan 2017 | B2 |
9590436 | Sporck | Mar 2017 | B2 |
9608518 | Yin | Mar 2017 | B2 |
9641002 | Lavender | May 2017 | B2 |
9647463 | Brandl | May 2017 | B2 |
9647475 | Sun | May 2017 | B2 |
9673640 | Kudo | Jun 2017 | B2 |
9748830 | Soleno | Aug 2017 | B1 |
9755517 | Kobayashi | Sep 2017 | B2 |
9780593 | Utsumi | Oct 2017 | B2 |
9899859 | Sporck | Feb 2018 | B2 |
9937812 | Billmaier | Apr 2018 | B1 |
9948094 | Sheng | Apr 2018 | B1 |
20030030412 | Matsuda | Feb 2003 | A1 |
20040135544 | King | Jul 2004 | A1 |
20040189251 | Kutkut | Sep 2004 | A1 |
20050007075 | Woo | Jan 2005 | A1 |
20050024015 | Houldsworth | Feb 2005 | A1 |
20050134219 | Patino | Jun 2005 | A1 |
20050242667 | Emori | Nov 2005 | A1 |
20050242776 | Emori | Nov 2005 | A1 |
20070046261 | Porebski | Mar 2007 | A1 |
20080007218 | Veselic | Jan 2008 | A1 |
20080090133 | Lim | Apr 2008 | A1 |
20080219337 | Kawata | Sep 2008 | A1 |
20080258685 | Choy | Oct 2008 | A1 |
20090085516 | Emori | Apr 2009 | A1 |
20090091332 | Emori | Apr 2009 | A1 |
20090146610 | Trigiani | Jun 2009 | A1 |
20090224769 | Emori | Sep 2009 | A1 |
20090230920 | Veselic | Sep 2009 | A1 |
20100007311 | Colin | Jan 2010 | A1 |
20100019732 | Utsumi | Jan 2010 | A1 |
20100052614 | Mariels | Mar 2010 | A1 |
20100052615 | Loncarevic | Mar 2010 | A1 |
20100109610 | Houldsworth | May 2010 | A1 |
20100134067 | Baxter | Jun 2010 | A1 |
20100198440 | Fujitake | Aug 2010 | A1 |
20110156640 | Moshfeghi | Jun 2011 | A1 |
20110175574 | Sim | Jul 2011 | A1 |
20110187326 | Kawata | Aug 2011 | A1 |
20110204845 | Paparo | Aug 2011 | A1 |
20110221393 | Billmaier | Sep 2011 | A1 |
20110234165 | Palatov | Sep 2011 | A1 |
20110273144 | Yu | Nov 2011 | A1 |
20110313613 | Kawahara | Dec 2011 | A1 |
20120019193 | Yu | Jan 2012 | A1 |
20120038324 | Humphrey | Feb 2012 | A1 |
20120056584 | Mariels | Mar 2012 | A1 |
20120056585 | Mariels | Mar 2012 | A1 |
20120119707 | Utsumi | May 2012 | A1 |
20120126820 | Tan | May 2012 | A1 |
20120161697 | Park | Jun 2012 | A1 |
20120169311 | Malmberg | Jul 2012 | A1 |
20120181983 | Khan | Jul 2012 | A1 |
20120313434 | Billmaier | Dec 2012 | A1 |
20120319649 | Billmaier | Dec 2012 | A1 |
20130057076 | Lavender | Mar 2013 | A1 |
20130099746 | Nork | Apr 2013 | A1 |
20130106356 | Nakao | May 2013 | A1 |
20130113428 | Emori | May 2013 | A1 |
20130119936 | Emori | May 2013 | A1 |
20130187603 | Kadie | Jul 2013 | A1 |
20130187604 | Kadie | Jul 2013 | A1 |
20130207609 | Emori | Aug 2013 | A1 |
20130207613 | Loncarevic | Aug 2013 | A1 |
20130214740 | Emori | Aug 2013 | A1 |
20130249475 | Kang | Sep 2013 | A1 |
20130249480 | Paparo | Sep 2013 | A1 |
20130328530 | Beaston | Dec 2013 | A1 |
20140018990 | Kataoka | Jan 2014 | A1 |
20140028098 | Trigiani | Jan 2014 | A1 |
20140035532 | Brandl | Feb 2014 | A1 |
20140049225 | Utsumi | Feb 2014 | A1 |
20140062401 | Gadh | Mar 2014 | A1 |
20140252847 | Yang | Sep 2014 | A1 |
20140266039 | Dougherty | Sep 2014 | A1 |
20140340042 | Emori | Nov 2014 | A9 |
20140347001 | Sporck | Nov 2014 | A1 |
20140347003 | Sporck | Nov 2014 | A1 |
20140354236 | Kim | Dec 2014 | A1 |
20140361740 | Suzuki | Dec 2014 | A1 |
20140365792 | Yun | Dec 2014 | A1 |
20150333636 | Kurauchi | Nov 2015 | A1 |
20150357851 | Huang | Dec 2015 | A1 |
20160009182 | Nakanishi | Jan 2016 | A1 |
20160049813 | Takizawa | Feb 2016 | A1 |
20160082856 | Baxter | Mar 2016 | A1 |
20160149431 | Sporck | May 2016 | A1 |
20160218618 | Yin | Jul 2016 | A1 |
20170028868 | Minamiura | Feb 2017 | A1 |
20170063123 | Horie | Mar 2017 | A1 |
20170070067 | Suzuki | Mar 2017 | A1 |
20170070068 | Ito | Mar 2017 | A1 |
20170133862 | Jung | May 2017 | A1 |
20180026467 | Shin | Jan 2018 | A1 |
20180097369 | Madhavi | Apr 2018 | A1 |
20180331564 | Song | Nov 2018 | A1 |
20180334051 | Samojeden | Nov 2018 | A1 |
20190013685 | Mallapur | Jan 2019 | A1 |
20190097277 | Fukae | Mar 2019 | A1 |
Number | Date | Country |
---|---|---|
2545923 | Jul 2017 | GB |
Number | Date | Country | |
---|---|---|---|
20170005501 A1 | Jan 2017 | US |
Number | Date | Country | |
---|---|---|---|
62187331 | Jul 2015 | US |