This application is a U.S. national phase application based on International Application No. PCT/CN2015/070469, filed on Jan. 9, 2015, which is based on and claims priority to Chinese Patent Application Nos. 201410042541.0, 201410043139.4, 201410043218.5, all filed on Jan. 28, 2014, the entire contents of which are incorporated herein by reference.
Embodiments of the present disclosure relate to the charging technical field, and more particularly, to a power adapter, a terminal and a method for handling an anomaly in a charging loop.
Currently, batteries in most of electronic devices are connected with external power adapters via charging interfaces of the electronic devices to realize charging. In order to reduce charging time during charging the battery, the charging current can be enhanced for realizing a quick charging on the battery in the related art. However, if an anomaly occurs in a charging loop, for example, an output voltage of the power adapter is an over-voltage and/or an output current of the power adapter is an over-current, the battery will be damaged, no matter whether the battery is charged in a conventional constant voltage mode or with increased charging current. Therefore, the anomaly in the charging loop cannot be detected and handled in the related art, such that the safety during the charging is poor.
Embodiments of the present disclosure provide a power adapter, a terminal and a method for handling an anomaly in a charging loop.
In at least one embodiment, a power adapter is provided, including a power conversion unit and a charging interface. The power conversion unit is configured to form a charging loop with a terminal via the charging interface so as to charge a battery of the terminal. The power adapter further includes: an anomaly detection unit and an anomaly handling unit. The anomaly detection unit is configured to detect whether an anomaly occurs in the charging loop. The anomaly handling unit is configured to control the charging loop to enter into a protection state if the anomaly occurs in the charging loop.
In at least one embodiment, a terminal is provided. The terminal includes a battery and a charging interface. The terminal is configured to form a charging loop with a power adapter via the charging interface so as to charge the battery. The terminal further includes a communication unit and an anomaly handling unit. The communication unit is configured to receive charging protection indicative information from the power adapter if an anomaly occurs in the charging loop. The anomaly handling unit is configured to control the charging loop to enter into a protection state according to an indication of the charging protection indicative information.
In at least one embodiment, a method for handling an anomaly in a charging loop is provided, including: detecting, by a power adapter, whether the anomaly occurs in the charging loop between the power adapter and a terminal; and controlling, by the power adapter, the charging loop to enter into a protection state if the anomaly occurs in the charging loop.
In at least one embodiment, a method for handling an anomaly in a charging loop is provided, including: receiving, by a terminal, charging protection indicative information from a power adapter if the anomaly occurs in the charging loop between the power adapter and the terminal; and controlling, by the terminal, the charging loop to enter into a protection state according to an indication of the charging protection indicative information.
In order to make the technical solutions of embodiments of the present disclosure more clearly, the accompanying drawings used in the description of embodiments of the present disclosure are briefly described hereunder. Obviously, the described drawings are merely some embodiments of present disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without any creative work.
The technical solutions in embodiments of the present disclosure are hereinafter described clearly and completely with reference to the accompanying drawings in embodiments of the present disclosure. Apparently, the described embodiments are merely a part of embodiments of the present disclosure, rather than all embodiments of the present disclosure. All other embodiments obtained by those skilled in the art based on embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure.
The anomaly detection unit 13 is configured to detect whether an anomaly occurs in the charging loop. The anomaly handling unit 14 is configured to control the charging loop to enter into a protection state in event that the anomaly occurs in the charging loop.
In at least one embodiment, the above anomaly handling unit 14 is configured to control the charging loop to enter into the protection state which can be achieved by reducing an output voltage of the power adapter 10, reducing an output current of the power adapter 10, or disconnecting the charging loop.
In embodiments of the present disclosure, the power adapter 10 detects whether the anomaly occurs in the charging loop through the anomaly detection unit 13, and controls the charging loop to enter into the protection state through the anomaly handling unit 14 in event that it is detected that the anomaly occurs in the charging loop.
In at least one embodiment, as shown in
In embodiments of the present disclosure, in event that the anomaly occurs in the charging loop, the power adapter 10 not only actively controls the charging loop to enter into the protection state, but also tells the terminal to control the charging loop to enter into the protection state. In this way, even when the anomaly handling unit 14 of the power adapter 10 loses efficacy and cannot control the charging loop to enter into the protection state, the terminal can control the charging loop to enter into the protection state.
In at least one embodiment, as shown in
In at least one embodiment, the charging interface 12 can be a USB (Universal Serial Bus) interface or a micro USB interface. The power wire in a USB interface can include a +5V power wire and a −5V power wire. The data wire in a USB interface can include a D+ wire and a D− wire.
In at least one embodiment, there can be various reasons resulting in the anomaly in the charging loop, such as an output voltage of the power adapter 10 is an over-voltage, an output current of the power adapter 10 is an over-current, a voltage at two ends of the battery is an over-voltage, a current at two ends of the battery is an over-current, or a temperature of the battery is an over-temperature. Different anomalies can be detected by different detection ways.
In at least one embodiment, the anomaly detection unit 13 is configured to detect whether the anomaly occurs in the charging loop which can be achieved by detecting a value of the output voltage of the power adapter 10, comparing the value of the output voltage of the power adapter 10 with a voltage threshold, determining that the output voltage of the power adapter 10 is the over-voltage and the anomaly occurs in the charging loop in event that the value of the output voltage is greater than the voltage threshold.
In at least one embodiment, the above voltage threshold can be set according to the specific model numbers of the power adapter 10 and the terminal or based on experiences.
Further, the power adapter 10 can further include a communication unit 15. The communication unit 15 is configured to send first indicative information to the terminal in event that the value of the output voltage of the power adapter 10 is less than the voltage threshold. The first indicative information includes the value of the output voltage of the power adapter 10 and is configured to indicate the terminal to determine whether the output voltage of the power adapter 10 is the over-voltage based on a voltage threshold set at the terminal side.
In other words, both the power adapter 10 and the terminal detect whether the output voltage of the power adapter 10 is the over-voltage. In this way, even when a detection result of the power adapter 10 is wrong (for example, the anomaly detection unit 13 of the power adapter 10 has a breakdown), the terminal can detect whether the output voltage of the power adapter 10 is the over-voltage. The terminal can control the charging loop to enter into the protection state. Alternatively, the power adapter 10 and the terminal do not form a complete set, the situation that a safe output voltage defined by the power adapter 10 exceeds an acceptable range of the terminal can occur. Further, the anomaly handling unit 14 can include a redundancy over-voltage processing unit. That is, when one over-voltage processing unit loses efficacy, the anomaly handling unit 14 can control the charging loop to enter into the protection state through other over-voltage processing unit.
In at least one embodiment, the anomaly detection unit 13 is configured to detect whether the anomaly occurs in the charging loop which can be achieved by detecting a value of the output current of the power adapter 10, comparing the value of the output current of the power adapter 10 with a current threshold, determining that the output current of the power adapter 10 is the over-current and the anomaly occurs in the charging loop in event that the output current is greater than the current threshold.
In at least one embodiment, the above current threshold can be set according to the specific model numbers of the power adapter 10 and the terminal or based on experiences.
Further, the power adapter 10 can further include a communication unit 15. The communication unit 15 is configured to send second indicative information to the terminal in event that the value of the output current of the power adapter 10 is less than the current threshold. The second indicative information includes the value of the output current of the power adapter 10 and is configured to indicate the terminal to re-determine whether the output current of the power adapter 10 is the over-current based on a current threshold set at the terminal side.
In other words, both the power adapter 10 and the terminal detect whether the output current of the power adapter 10 is the over-current. In this way, even when a detection result of the power adapter 10 is wrong (for example, a detection circuit of the power adapter 10 has a breakdown), the terminal can detect whether the output current of the power adapter 10 is the over-current, such that the terminal can control the charging loop to enter into the protection state. Alternatively, the power adapter 10 and the terminal do not form a complete set, the situation that a safe output current defined by the power adapter 10 exceeds an acceptable range of the terminal can occur.
In at least one embodiment, the power adapter 10 can further include: a communication unit 15. The communication unit 15 is configured to receive a battery parameter detected by the terminal. The battery parameter is configured to indicate the voltage at two ends of the battery, the current at two ends of the battery or the temperature of the battery. The anomaly detection unit 13 is configured to detect whether the anomaly occurs in the charging loop which can be achieved by determining whether the battery parameter received by the communication unit 15 is greater than a predetermined battery parameter threshold. The anomaly occurs in the charging loop in event that the battery parameter is greater than the predetermined battery parameter threshold.
In at least one embodiment, the battery parameter is the voltage at the two ends of the battery. The anomaly detection unit 13 is configured to determine whether the voltage at the two ends of the battery is greater than a threshold. The anomaly detection unit 13 determines that the voltage at the two ends of the battery is the over-voltage and that the anomaly occurs in the charging loop in event that the voltage at the two ends of the battery is greater than the threshold.
In at least one embodiment, the battery parameter is the current at the two ends of the battery. The anomaly detection unit 13 is configured to determine whether the current at the two ends of the battery is greater than a threshold. The anomaly detection unit 13 is configured to determine that the current at the two ends of the battery is the over-current and that the anomaly occurs in the charging loop in event that the current at the two ends of the battery is greater than the threshold.
In at least one embodiment, the battery parameter is the temperature of the battery. The anomaly detection unit 13 is configured to determine whether the temperature of the battery is greater than a threshold. The anomaly detection unit 13 is configured to determine that the temperature of the battery is the over-temperature and that the anomaly occurs in the charging loop in event that the temperature the battery is greater than the threshold.
The power adapter 10 according to embodiments of the present disclosure is described in detail above by combining with
In at least one embodiment, the above anomaly handling unit 24 is configured to control the charging loop to enter into the protection state according to the indication of the charging protection indicative information which can be achieved by reducing an output current of the power adapter according to the indication of the charging protection indicative information, or reducing an output voltage of the power adapter according to the indication of the charging protection indicative information, or controlling the charging loop to be disconnected according to the indication of the charging protection indicative information.
In embodiments of the present disclosure, in event that the anomaly occurs in the charging loop between the power adapter and the terminal 20, the communication unit 23 of the terminal 20 receives the charging protection indicative information from the power adapter and controls the charging loop to enter into the protection state according the indication of the charging protection indicative information.
In at least one embodiment, as shown in
In at least one embodiment, the charging interface 22 can be a USB (Universal Serial Bus) interface or a micro USB interface. The power wire in the USB interface can include a +5V power wire and a −5V power wire. The data wire in the USB interface can include a D+ wire and a D− wire.
In at least one embodiment, the anomaly in the charging loop includes at least one of the following anomalies that: an output voltage of the power adapter is an over-voltage, an output current of the power adapter is an over-current, a voltage at two ends of the battery 21 is an over-voltage, a current at two ends of the battery 21 is an over-current, and a temperature of the battery 21 is an over-temperature.
In at least one embodiment, as shown in
In block 310, the power adapter detects whether the anomaly occurs in the charging loop between the power adapter and a terminal.
In block 320, in event that the anomaly occurs in the charging loop, the power adapter controls the charging loop to enter into a protection state.
In embodiments of the present disclosure, the power adapter detects whether the anomaly occurs in the charging loop through the anomaly detection unit, and controls the charging loop to enter into the protection state through the anomaly handling unit in event that it is detected that the anomaly occurs in the charging loop.
In at least one embodiment, the method in
In at least one embodiment, the power adapter is contacted with the terminal through a charging interface. The charging interface includes a power wire for charging and a data wire. Sending by the power adapter the charging protection indicative information to the terminal includes: sending by the power adapter the charging protection indicative information to the terminal through the data wire.
In at least one embodiment, controlling by the power adapter the charging loop to enter into the protection state includes: reducing by the power adapter an output voltage of the power adapter; reducing by the power adapter an output current of the power adapter; or disconnecting by the power adapter the charging loop.
In at least one embodiment, the anomaly in the charging loop includes at least one of the following anomalies that: the output voltage of the power adapter is an over-voltage, the output current of the power adapter is an over-current, a voltage at two ends of a battery is an over-voltage, a current at two ends of the battery is an over-current, and a temperature of the battery is an over-temperature.
In at least one embodiment, detecting by the power adapter whether the anomaly occurs in the charging loop between the power adapter and the terminal includes: detecting by the power adapter a value of the output voltage of the power adapter; determining by the power adapter that the value of the output voltage is the over-voltage and that the anomaly occurs in the charging loop in event that the value of the output voltage is greater than a voltage threshold.
In at least one embodiment, the method in
In at least one embodiment, detecting by the power adapter whether the anomaly occurs in the charging loop between the power adapter and the terminal includes: detecting by the power adapter a value of the output current of the power adapter; determining by the power adapter that the output current is the over-current and that the anomaly occurs in the charging loop, if the value of the output current is greater than a current threshold.
In at least one embodiment, the method in
In at least one embodiment, the method in
In block 410, in event that the anomaly occurs in the charging loop between a power adapter and the terminal, the terminal receives charging protection indicative information from the power adapter.
In block 420, the terminal controls the charging loop to enter into a protection state according to an indication of the charging protection indicative information.
In embodiments of the present disclosure, in event that the anomaly occurs in the charging loop between the power adapter and the terminal, the terminal receives the charging protection indicative information from the power adapter and controls the charging loop to enter into the protection state, such that the safety during the charging is improved.
In at least one embodiment, the power adapter is contacted with the terminal through a charging interface. The charging interface includes a power wire for charging and a data wire. Receiving by the terminal the charging protection indicative information from the power adapter includes: receiving by the terminal the charging protection indicative information from the power adapter through the data wire in the charging interface.
In at least one embodiment, the anomaly in the charging loop includes at least one of the following anomalies that: an output voltage of the power adapter is an over-voltage, an output current of the power adapter is an over-current, a voltage at two ends of a battery is an over-voltage, a current at the two ends of the battery is an over-current, and a temperature of the battery is an over-temperature.
In at least one embodiment, the method in
Those skilled in the art can be aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm blocks can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are executed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. Those skilled in the art can use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present disclosure.
It would be appreciated by those skilled in the art that, for the purpose of simplification convenience of description, concerning the specific working process of the above system, device and unit as described above, reference is made to the method embodiments of the present disclosure, which will not be elaborated herein.
In several embodiments provided in the application, it should be understood that the disclosed system, device and method can be realized by other manners. For example, the above-described embodiments are only exemplary; for example, the division of said unit is only a logic function division; there can be additional dividing manners during the actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored, or not implemented. Another point, the displayed or discussed mutual coupling or direct coupling or communication connection can be indirect coupling or communication connection of devices or units via some interfaces, in electronic, mechanical, or other forms.
Said unit described as a separation part can be or can not be separated physically; the part displayed as a unit can be or can not be a physical unit, namely it can be located in one place, or can be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
In addition, all functional units in the embodiments of the disclosure can be integrated in one processing unit, or each unit exists individually in physical form, or two or more units are integrated in one unit.
If said function is realized in the form of software function unit and sold or used as an independent product, it can be stored in a computer readable storage medium. With such an understanding, the technical solution of the disclosure substantially or its portion that contributes to the prior art or a portion of the technical solution can embody in the form of a computer software product which is stored in a memory media, including a plurality of instructions such that a computer (can be a personal computer, a server, or a network device, etc.) executes all or some blocks of the methods described in each of all the embodiments. And the previously mentioned memory media include such media capable of storing program codes as USB flash disk, portable hard drive, read-only memory (ROM), random access memory (RAM), floppy disk or compact disk.
The above descriptions are only specific embodiments of the disclosure, but not intended to limit the protection scope of the disclosure. The variation or replacement easily thought of by those of skill in the art within the technical scope disclosed by the disclosure, shall fall within the protection scope of the disclosure. Therefore, the protection scope of the disclosure shall be determined with reference to the protection scope of the claims.
Number | Date | Country | Kind |
---|---|---|---|
2014 1 0042541 | Jan 2014 | CN | national |
2014 1 0043139 | Jan 2014 | CN | national |
2014 1 0043218 | Jan 2014 | CN | national |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/CN2015/070469 | 1/9/2015 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2015/113466 | 8/6/2015 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5541489 | Dunstan | Jul 1996 | A |
5557738 | Townsley | Sep 1996 | A |
5905362 | Nagano et al. | May 1999 | A |
6018703 | Dodd | Jan 2000 | A |
6501249 | Drori | Dec 2002 | B1 |
7065662 | Chen | Jun 2006 | B2 |
7363518 | Critz | Apr 2008 | B2 |
7378755 | Kingsmore, Jr. et al. | May 2008 | B2 |
7649550 | Ishiyama | Jan 2010 | B2 |
7737590 | Oyama | Jun 2010 | B2 |
8064513 | Yamazaki | Nov 2011 | B2 |
8098053 | Sato | Jan 2012 | B2 |
8261100 | Paniagua, Jr. | Sep 2012 | B2 |
8513923 | Wang et al. | Aug 2013 | B2 |
9020771 | Hardy | Apr 2015 | B1 |
9099864 | Shoykhet | Aug 2015 | B2 |
9337919 | Kikuchi | May 2016 | B2 |
9825348 | Kikuchi | Nov 2017 | B2 |
9859742 | Zhang | Jan 2018 | B2 |
10008868 | Zhang | Jun 2018 | B2 |
20010021092 | Astala | Sep 2001 | A1 |
20020098859 | Murata | Jul 2002 | A1 |
20040090209 | Nishida | May 2004 | A1 |
20040108843 | Lanni | Jun 2004 | A1 |
20050174094 | Purdy et al. | Aug 2005 | A1 |
20060093916 | Howard et al. | May 2006 | A1 |
20060152196 | Matsumoto et al. | Jul 2006 | A1 |
20060170398 | Gangsto et al. | Aug 2006 | A1 |
20060234125 | Valle | Oct 2006 | A1 |
20060284595 | Hsieh | Dec 2006 | A1 |
20080111520 | Sasaki | May 2008 | A1 |
20080224662 | Hayakawa | Sep 2008 | A1 |
20080231236 | Watanabe et al. | Sep 2008 | A1 |
20080287080 | Camp, Jr. et al. | Nov 2008 | A1 |
20090153100 | Okumura et al. | Jun 2009 | A1 |
20090177906 | Paniagua, Jr. | Jul 2009 | A1 |
20090243552 | Jakes et al. | Oct 2009 | A1 |
20100066311 | Bao et al. | Mar 2010 | A1 |
20100077237 | Sawyers | Mar 2010 | A1 |
20100085020 | Suzuki et al. | Apr 2010 | A1 |
20100308775 | Mizutani et al. | Dec 2010 | A1 |
20110248670 | Yamazaki et al. | Oct 2011 | A1 |
20120098495 | Yang et al. | Apr 2012 | A1 |
20120133336 | Han et al. | May 2012 | A1 |
20120268074 | Cooley | Oct 2012 | A1 |
20120293009 | Kim et al. | Nov 2012 | A1 |
20130082662 | Carré et al. | Apr 2013 | A1 |
20130175978 | Hsiao | Jul 2013 | A1 |
20130214611 | Bae | Aug 2013 | A1 |
20130254560 | Leung | Sep 2013 | A1 |
20160336767 | Zane | Nov 2016 | A1 |
20160344227 | Zhang et al. | Nov 2016 | A1 |
Number | Date | Country |
---|---|---|
1499689 | May 2004 | CN |
1950998 | Apr 2007 | CN |
1989675 | Jun 2007 | CN |
101013764 | Aug 2007 | CN |
101026309 | Aug 2007 | CN |
201207574 | Mar 2009 | CN |
201278420 | Jul 2009 | CN |
101651356 | Feb 2010 | CN |
101714772 | May 2010 | CN |
101719685 | Jun 2010 | CN |
101783427 | Jul 2010 | CN |
101888098 | Nov 2010 | CN |
101651356 | Dec 2010 | CN |
101908771 | Dec 2010 | CN |
102013705 | Apr 2011 | CN |
102214941 | Oct 2011 | CN |
202218051 | May 2012 | CN |
102931693 | Feb 2013 | CN |
103178595 | Jun 2013 | CN |
203135543 | Aug 2013 | CN |
103326407 | Sep 2013 | CN |
103370863 | Oct 2013 | CN |
103762691 | Apr 2014 | CN |
103779907 | May 2014 | CN |
103795040 | May 2014 | CN |
203747392 | Jul 2014 | CN |
203747451 | Jul 2014 | CN |
203747452 | Jul 2014 | CN |
203747453 | Jul 2014 | CN |
1455431 | Sep 2004 | EP |
1796243 | Jun 2007 | EP |
1821384 | Aug 2007 | EP |
2071696 | Jun 2009 | EP |
2175542 | Apr 2010 | EP |
2239810 | Oct 2010 | EP |
3101755 | Dec 2016 | EP |
H09168241 | Jun 1997 | JP |
H1027630 | Jan 1998 | JP |
H11143591 | May 1999 | JP |
H11215727 | Aug 1999 | JP |
2004274875 | Sep 2004 | JP |
2007020203 | Jan 2007 | JP |
2007110853 | Apr 2007 | JP |
2007327772 | Dec 2007 | JP |
2008009898 | Jan 2008 | JP |
2008035674 | Feb 2008 | JP |
2008061343 | Mar 2008 | JP |
2008061381 | Mar 2008 | JP |
2010058244 | Mar 2010 | JP |
2010165347 | Jul 2010 | JP |
2012079547 | Apr 2012 | JP |
2013108793 | Jun 2013 | JP |
2013132183 | Jul 2013 | JP |
2013134683 | Jul 2013 | JP |
20040024552 | Mar 2004 | KR |
20080034141 | Apr 2008 | KR |
20130002970 | Jan 2013 | KR |
WO 2010117498 | Oct 2010 | WO |
WO 2012021128 | Feb 2012 | WO |
WO 2012165071 | Dec 2012 | WO |
WO 2013001909 | Jan 2013 | WO |
Entry |
---|
Chinese Patent Application No. 201410042541.0 First Office Action dated Jul. 17, 2015, with English translation, 10 pages. |
Chinese Patent Application No. CN201410043139.4 First Office Action dated Dec. 23, 2015, with English translation, 8 pages. |
Japanese Patent Application No. 2016-549039, Office Action dated Jun. 27, 2017, with English translation, 7 pages. |
Chinese Patent Application No. 201410043218.5 First Office Action dated May 25, 2015, with English translation, 10 pages. |
Translation of the International Search Report and Written Opinion corresponding to International Patent Application PCT/CN2015/070469, dated Apr. 20, 2015, 10 pages. |
European Patent Application No. 15743390.5 extended search and opinion dated Sep. 22, 2017, 8 pages. |
Japanese Patent Application No. 2016-549039 English translation of Notification of Reasons for Refusal dated Sep. 12, 2017, 3 pages. |
Japanese Patent Application No. 2016-549039 Notification of Reasons for Refusal dated Sep. 12, 2017, 4 pages. |
Japanese Patent Application No. 2016549039, English translation of Office Action dated Nov. 28, 2017, 3 pages. |
Japanese Patent Application No. 2016549039, Office Action dated Nov. 28, 2017, 4 pages. |
Chilean Patent Application No. 201601915 Office Action dated Oct. 19, 2017, 7 pages. |
Chilean Patent Application No. 201700970 Office Action dated Apr. 19, 2018, 9 pages. |
Chinese Patent Application No. 201410042541.0 Office Action dated Jul. 17, 2015, 5 pages. |
Chinese Patent Application No. 201410042541.0 English translation of Office Action dated Jul. 17, 2015, 5 pages. |
Chinese Patent Application No. 201410042541.0 Office Action dated Mar. 16, 2016, 3 pages. |
Chinese Patent Application No. 201410042541.0 English translation of Office Action dated Mar. 16, 2016, 4 pages. |
Chinese Patent Application No. 201410043139.4 Office Action dated Dec. 23, 2015, 3 pages. |
Chinese Patent Application No. 201410043139.4 English translation of Office Action dated Dec. 23, 2015, 5 pages. |
Chinese Patent Application No. 201410043218.5 Office Action dated May 25, 2015, 5 pages. |
Chinese Patent Application No. 201410043218.5 English translation of Office Action dated May 25, 2015, 5 pages. |
Chinese Patent Application No. 201610763798.4 Office Action dated Jun. 15, 2017, 5 pages. |
Chinese Patent Application No. 201610763798.4 English translation of Office Action dated Jun. 15, 2017, 8 pages. |
Chinese Patent Application No. 201610763798.4 Office Action dated Sep. 19, 2017, 6 pages. |
Chinese Patent Application No. 201610763798.4 English translation of Office Action dated Sep. 19, 2017, 9 pages. |
Chinese Patent Application No. 201610763798.4 Office Action dated Jan. 11, 2018, 5 pages. |
Chinese Patent Application No. 201610763798.4 English translation of Office Action dated Jan. 11, 2018, 5 pages. |
Chinese Patent Application No. 201610973222.0 Office Action dated Jun. 1, 2017, 4 pages. |
Chinese Patent Application No. 201610973222.0 English translation of Office Action dated Jun. 1, 2017, 6 pages. |
Chinese Patent Application No. 201610973222.0 Office Action dated Jul. 13, 2017, 4 pages. |
Chinese Patent Application No. 201610973222.0 English translation of Office Action dated Jul. 13, 2017, 6 pages. |
Chinese Patent Application No. 201610973222.0 Office Action dated Sep. 25, 2017, 6 pages. |
Chinese Patent Application No. 201610973222.0 English translation of Office Action dated Sep. 25, 2017, 9 pages. |
European Patent Application No. 14881017.9 extended Search and Opinion dated Nov. 23, 2017, 7 pages. |
European Patent Application No. 14881229.0 extended Search and Opinion dated Sep. 6, 2017, 8 pages. |
European Patent Application No. 14880730.8 extended Search and Opinion dated Oct. 24, 2017, 7 pages. |
European Patent Application No. 18174633.0 extended Search and Opinion dated Aug. 9, 2018, 7 pages. |
Japanese Patent Application No. 2016549501 Office Action dated Nov. 14, 2017, 2 pages. |
Japanese Patent Application No. 2016549501 English translation of Office Action dated Nov. 14, 2017, 2 pages. |
Japanese Patent Application No. 2016549390 Office Action dated Aug. 8, 2017, 3 pages. |
Japanese Patent Application No. 2016549390 English translation of Office Action dated Aug. 8, 2017, 3 pages. |
Japanese Patent Application No. 2017215256 Office Action dated Dec. 5, 2017, 3 pages. |
Japanese Patent Application No. 2017215256 English translation of Office Action dated Dec. 5, 2017, 3 pages. |
Korean Patent Application No. 20167023621 Office Action dated Aug. 9, 2017, 3 pages. |
Korean Patent Application No. 20167023621 English translation of Office Action dated Aug. 9, 2017, 2 pages. |
Korean Patent Application No. 20167023621 Office Action dated Feb. 27, 2018, 2 pages. |
Korean Patent Application No. 20167023621 English translation of Office Action dated Feb. 27, 2018, 2 pages. |
Korean Patent Application No. 20167023636 Office Action dated Jul. 24, 2018, 2 pages. |
Korean Patent Application No. 20167023636 English translation of Office Action dated Jul. 24, 2018, 1 page. |
Singapore Patent Application No. 11201606223P Office Action dated May 19, 2017, 8 pages. |
Singapore Patent Application No. 11201606223P Office Action dated Jan. 9, 2018, 6 pages. |
U.S. Appl. No. 15/115,045 Office Action dated Nov. 22, 2017, 15 pages. |
U.S. Appl. No. 15/114,929 Office Action dated Jun. 22, 2018, 27 pages. |
U.S. Appl. No. 15/115,251 Office Action dated Oct. 13, 2017, 42 pages. |
U.S. Appl. No. 15/115,251 Office Action dated Feb. 20, 2018, 45 pages. |
U.S. Appl. No. 15/115,251 Office Action dated Jun. 5, 2018, 47 pages. |
U.S. Appl. No. 15/666,881 Office Action dated Jan. 22, 2018, 22 pages. |
PCT/CN2014/076974 International Search Report dated Oct. 29, 2014, 4 pages. |
PCT/CN2014/076974 English translation of International Search Report dated Oct. 29, 2014, 2 pages. |
PCT/CN2014/077287 International Search Report dated Oct. 29, 2014, 4 pages. |
PCT/CN2014/077287 English translation of International Search Report dated Sep. 29, 2014, 2 pages. |
PCT/CN201/4077474 International Search Report dated Nov. 14, 2014, 5 pages. |
PCT/CN201/4077474 English translation of International Search Report dated Nov. 14, 2014, 3 pages. |
Texas Instruments: “USB Dedicated Charging Port Controller and Current Limiting Power Switch Check for Samples: TPS2511-Q1”, Jun. 30, 2013 (Jun. 30, 2013), XP055420944, Retrieved from the Internet: URL:http://www.ti.com/lit/ds/symlink/tps25II-q1.pdf, cited in European Patent Application; 18174633; 28 pages. |
Chinese Patent Application No. 201580005233.3, Office Action dated Aug. 30, 2018, 7 pages. |
Chinese Patent Application No. 201580005233.3, English translation of Office Action dated Aug. 30, 2018, 8 pages. |
Korean Patent Application No. 10-2016-7023514, English translation of Office Action dated Dec. 14, 2018, 6 pages. |
Korean Patent Application No. 10-2016-7023514, Office Action dated Dec. 14, 2018, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20160344228 A1 | Nov 2016 | US |