This application is a U.S. national phase application based on International Application No. PCT/CN2015/070468, 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 field, and more specifically, relate to a terminal, a power adapter and a method for handling a charging anomaly.
Typically, a battery in an electronic device is charged by a way of coupling a charging interface of the electronic device with an external power adapter. 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. 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 terminal, a power adapter and a method for handling a charging anomaly.
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, an anomaly detection unit and an anomaly handling unit. The communication unit is configured to receive charging parameter information from the power adapter. The anomaly detection unit is configured to determine, according to the charging parameter information, whether an anomaly occurs on the charging loop. The anomaly handling unit is configured to control the charging loop to enter into a protection state if the anomaly occurs on the charging loop.
In at least one embodiment, a power adapter is provided. The power adapter includes 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 a communication unit and an anomaly handling unit. The communication unit is configured to receive charging protection indication information from the terminal. 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 indication information.
In at least one embodiment, the method further includes: sending, by the terminal, charging protection indication information to the power adapter, so as to indicate the power adapter to control the charging loop to enter into the protection state if the anomaly occurs on the charging loop.
In at least one embodiment, a method for handling a charging anomaly is provided. The method includes: receiving, by a power adapter, charging protection indication information from a terminal; and controlling, by the power adapter, a charging loop between the power adapter and the terminal to enter into a protection state according to an indication of the charging protection indication 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 will be given a clear and complete description with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, 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.
In the embodiments of the present disclosure, the terminal receives the charging parameter information from the power adapter, and determines, according to the charging parameter information, whether the anomaly occurs on the charging loop. The terminal controls the charging loop to enter into the protection state if the anomaly occurs on the charging loop, so as to improve the safety of the charging process.
In at least one embodiment, the communication unit 13 is further configured to send charging protection indication information to the power adapter if the anomaly occurs on the charging loop, so as to indicate the power adapter to control the charging loop to enter into the protection state.
In the embodiments of the present disclosure, when the anomaly occurs on the charging loop, the terminal not only actively controls the charging loop to enter into the protection state, but also notifies the power adapter to control the charging loop to enter into the protection state. In this case, even if the anomaly handling unit of the terminal fails to control the charging loop to enter into the protection state, the power adapter can be still used to control the charging loop to enter into the protection state, thereby further improving the safety of the charging process.
In at least one embodiment, the charging interface includes power wires 122 and data wires 121. The terminal 10 is configured to form the charging loop with the power adapter via the charging interface 12, so as to charge the battery, and specifically to: form the charging loop with the power adapter via the power wires 122 in the charging interface 12, so as to charge the battery. The communication unit 13 is configured to receive the charging parameter information from the power adapter, and specifically to: receive the charging parameter information from the power adapter via the data wires 121 in the charging interface.
For example, the charging interface can be a USB (Universal Serial Bus) interface or a micro USB interface. The above-mentioned power wires can be power wires in the USB interface, such as +5V and −5V power wires; the above-mentioned data wires can be data wires in the USB interface, such as a D+ wire and a D− wire.
In at least one embodiment there may be several reasons causing the anomaly of the charging loop, for example, an overvoltage output and an overcurrent output of the power adapter, etc. The detection and handling manners of different anomalies may be different. An illustration to the detection and handling manners of various anomalies is provided below in conjunction with specific embodiments.
In at least one embodiment, the charging parameter information includes an output voltage of the power adapter. The anomaly detection unit 14 is configured to, according to the charging parameter information, determine whether the anomaly occurs on the charging loop, and specifically to: compare the output voltage with a voltage threshold, and determine the overvoltage output of the power adapter and the anomaly occurring on the charging loop if the output voltage is higher than the voltage threshold.
In at least one embodiment, the above-mentioned voltage threshold can be set according to the specific model of the terminal 10 and the power adapter, or can also be set according to experience.
In at least one an embodiment, the charging parameter information includes an output current of the power adapter. The anomaly detection unit 14 is configured to, according to the charging parameter information, determine whether the anomaly occurs on the charging loop, and specifically to: compare the output current with a current threshold, and determine the overcurrent output and the anomaly occurring on the charging loop if the output current is higher than the current threshold.
In at least one embodiment, the above-mentioned current threshold can be set according to the specific model of the terminal 10 and the power adapter, or can also be set according to experience.
In conjunction with
In the embodiments of the present disclosure, when the anomaly occurs on the charging loop, the communication unit of the power adapter receives the charging protection indication information from the terminal, and controls the charging loop to enter into the protection state according to the indication of the charging protection indication information, thereby improving the safety of the charging process.
In at least one embodiment, the power adapter 20 is contacted with the terminal via the charging interface 22. The charging interface 22 includes power wires 222 for charging and data wires 221. The communication unit 23 is configured to receive the charging protection indication information from the terminal, and specifically to: receive the charging protection indication information from the terminal via the data wires 221 in the charging interface 22.
For example, the charging interface can be a USB (Universal Serial Bus) interface or a micro USB interface. The above-mentioned power wires can be power wires in the USB interface, such as +5V and −5V power wires; the above-mentioned data wires can be data wires in the USB interface, such as a D+ cable and a D− cable.
In at least one embodiment, the communication unit 23 is further configured to send charging parameter information to the terminal. The charging parameter information is used for the terminal to determine whether an anomaly occurs on the charging loop.
In at least one embodiment, the charging parameter information includes at least one of an output voltage and an output current of the power adapter 20.
In conjunction with
In 310, a terminal receives charging parameter information from a power adapter.
In 320, the terminal, according to the charging parameter information, determines whether an anomaly occurs on a charging loop between the terminal and the power adapter.
In 330, the terminal controls the charging loop to enter into a protection state if the anomaly occurs on the charging loop.
In the embodiments of the present disclosure, the terminal receives the charging parameter information, and according to the charging parameter information, determines whether the anomaly occurs on the charging loop. The terminal controls the charging loop to enter into the protection state if the anomaly occurs on the charging loop, so as to improve the safety of the charging process.
In at least one embodiment, the method in
In at least one embodiment, the terminal includes a charging interface. The charging interface includes data wires and power wires for charging. The terminal is configured to receive the charging parameter information from the power adapter, and specifically to receive the charging parameter information from the power adapter via the data wires in the charging interface.
In at least one embodiment, the terminal is configured to control the charging loop to enter into the protection state by an act of reducing an input voltage of the power adapter; or reducing an input current of the power adapter; or disconnecting the charging loop.
In at least one embodiment, the anomaly of the charging loop includes at least one of: overvoltage output and overcurrent output of the power adapter.
In at least one embodiment, the charging parameter information includes an output voltage of the power adapter. Determining, by the terminal according to the charging parameter information, whether the anomaly occurs on the charging loop between the terminal and the power includes: comparing, by the terminal, the output voltage with a voltage threshold; and determining by the terminal, the overvoltage output of the power adapter and the anomaly occurring on the charging loop if the output voltage is higher than the voltage threshold.
In at least one embodiment, the charging parameter information includes an output current of the power adapter. Determining, by the terminal according to the charging parameter information, whether the anomaly occurs on the charging loop between the terminal and the power includes: comparing, by the terminal, the output current with a current threshold; and determining, by the terminal, the overcurrent output of the power adapter and the anomaly occurring on the charging loop if the output current overcurrent is higher than the current threshold.
Referring to
In 410, a power adapter receives charging protection indication information from a terminal;
In 420, the power adapter controls a charging loop between the power adapter and the terminal to enter into a protection state according to an indication of the charging protection indication information.
In the embodiments of the present disclosure, if an anomaly occurs on the charging loop, the power adapter receives the charging protection indication information from the terminal, and according to the indication of the charging protection indication information, controls the charging loop to enter into the protection state, thereby improving the safety of the charging process.
In at least one embodiment, the power adapter is contacted with the terminal via the charging interface. The charging interface includes power wires for charging and data wires. Receiving, by the power adapter, the charging protection indication information from the terminal, includes: receiving, by the power adapter, the charging protection indication information from the terminal via the data wires in the charging interface.
In at least one embodiment, the method of
In at least one embodiment, the charging parameter information includes at least one of an output voltage and an output current of the power adapter.
Those skilled in the art can realize that, the units and algorithm steps in conjunction with all examples described in the embodiments disclosed in this specification are able to be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on specific applications and design constraint conditions of the technical solutions. For each specific application, those skilled in the art can realize the described functions by using different methods, but this realization shall not be considered beyond the scope of the present disclosure.
It would be appreciated by those skilled that, for convenience and simplicity of the description, the specific working process of the systems, devices and units as described above can refer to the corresponding process in the abovementioned method embodiments, and no further details hereto will be given.
In several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be realized by other manners. For example, the above-described embodiments are only schematic; for example, the division of said unit is only a logic function division; there may be additional dividing manners during the actual implementation. For example, multiple units or components may 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 may be via some interfaces, indirect coupling or communication connection of devices or units, in electronic, mechanical, or other forms.
Said unit described as a separation part may be or may not be separated physically; the part displayed as a unit may be or may 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 present 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 present disclosure substantially or its portion that contributes to the prior art or a portion of the technical solution may 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 (may be a personal computer, a server, or a network device, etc.) executes all or some steps 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 present disclosure, but not intended to limit the protection scope of the present disclosure. The variation or replacement easily thought of by those of skill in the art within the technical scope disclosed by the present disclosure, shall fall within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be determined with reference to the protection scope of the claims.
Number | Date | Country | Kind |
---|---|---|---|
201410042541.0 | Jan 2014 | CN | national |
201410043139.4 | Jan 2014 | CN | national |
201410043218.5 | Jan 2014 | CN | national |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/CN2015/070468 | 1/9/2015 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2015/113465 | 8/6/2015 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3927361 | Macharg | Dec 1975 | A |
5028859 | Johnson et al. | Jul 1991 | A |
5229705 | Kato | Jul 1993 | A |
5254931 | Martensson | Oct 1993 | A |
5541489 | Dunstan | Jul 1996 | A |
5905362 | Nagano et al. | May 1999 | A |
6025695 | Friel et al. | Feb 2000 | A |
7271568 | Purdy et al. | Sep 2007 | B2 |
7378755 | Kingsmore, Jr. et al. | May 2008 | B2 |
7932694 | Watanabe et al. | Apr 2011 | B2 |
8098053 | Sato | Jan 2012 | B2 |
8513923 | Wang et al. | Aug 2013 | B2 |
10008868 | Zhang et al. | Jun 2018 | B2 |
10218192 | Zhang et al. | Feb 2019 | B2 |
20010006338 | Yamashita | Jul 2001 | A1 |
20010021092 | Astala | Sep 2001 | A1 |
20020098859 | Murata | Jul 2002 | A1 |
20040189251 | Kutkut | Sep 2004 | A1 |
20050077878 | Carrier et al. | Apr 2005 | 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 |
20070118272 | Shimada | May 2007 | A1 |
20070188134 | Hussain | Aug 2007 | A1 |
20070230227 | Palmer | Oct 2007 | A1 |
20080111520 | Sasaki | May 2008 | A1 |
20080224662 | Hayakawa | Sep 2008 | A1 |
20080224667 | Tanaka | Sep 2008 | A1 |
20080231236 | Watanabe et al. | Sep 2008 | A1 |
20080238370 | Carrier | Oct 2008 | A1 |
20080287080 | Camp, Jr. et al. | Nov 2008 | A1 |
20090135633 | Ikeuchi et al. | May 2009 | A1 |
20090153100 | Okumura et al. | Jun 2009 | A1 |
20090184688 | Kim | Jul 2009 | A1 |
20090243552 | Jakes et al. | Oct 2009 | A1 |
20100033139 | An | Feb 2010 | A1 |
20100045243 | Mizuno et al. | Feb 2010 | A1 |
20100066311 | Bao et al. | Mar 2010 | A1 |
20100085020 | Suzuki et al. | Apr 2010 | A1 |
20100085022 | Shimizu et al. | Apr 2010 | A1 |
20100165528 | Chan | Jul 2010 | A1 |
20100188237 | Monks et al. | Jul 2010 | A1 |
20100253291 | Lin | Oct 2010 | A1 |
20100308775 | Mizutani et al. | Dec 2010 | A1 |
20110057605 | Chung et al. | Mar 2011 | A1 |
20110057620 | Tsai | Mar 2011 | A1 |
20110248670 | Yamazaki et al. | Oct 2011 | A1 |
20110266874 | Soemantri et al. | Nov 2011 | A1 |
20120038317 | Miyamoto | Feb 2012 | A1 |
20120098495 | Yang et al. | Apr 2012 | A1 |
20120133336 | Han et al. | May 2012 | A1 |
20120293009 | Kim et al. | Nov 2012 | A1 |
20130002200 | Kobayishi | Jan 2013 | A1 |
20130007336 | Chun et al. | Jan 2013 | A1 |
20130063271 | Yasuda et al. | Mar 2013 | A1 |
20130082662 | Carré et al. | Apr 2013 | A1 |
20130154547 | Wada | Jun 2013 | A1 |
20130175978 | Hsiao | Jul 2013 | A1 |
20130198535 | Takashima | Aug 2013 | A1 |
20130207592 | Okada | Aug 2013 | A1 |
20130214611 | Bae | Aug 2013 | A1 |
20130254560 | Leung | Sep 2013 | A1 |
20130314830 | Zamprogno | Nov 2013 | A1 |
20140013012 | Terlizzi | Jan 2014 | A1 |
20140181541 | Matsumoto | Jun 2014 | A1 |
20140313794 | Ono et al. | Oct 2014 | A1 |
20160352117 | Zhang | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
1163500 | Oct 1997 | CN |
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 |
101783427 | Jul 2010 | CN |
101888098 | Nov 2010 | CN |
101908771 | Dec 2010 | CN |
101939893 | Jan 2011 | CN |
102013705 | Apr 2011 | CN |
102214941 | Oct 2011 | CN |
202218051 | May 2012 | CN |
102931693 | Feb 2013 | CN |
103178595 | Jun 2013 | CN |
103236568 | Aug 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 |
0 800 253 | Oct 1997 | EP |
0800253 | Oct 1997 | EP |
1455431 | Sep 2004 | EP |
1796243 | Jun 2007 | EP |
1796243 | Jun 2007 | EP |
1 821 384 | Aug 2007 | EP |
1821384 | Aug 2007 | EP |
2071696 | Jun 2009 | EP |
2175542 | Apr 2010 | EP |
2239810 | Oct 2010 | EP |
2256897 | Dec 2010 | EP |
2618419 | Jul 2013 | EP |
2251515 | Jul 1992 | GB |
H09168241 | Jun 1997 | JP |
H11143591 | May 1999 | JP |
H11215727 | Aug 1999 | JP |
2003033034 | Jan 2003 | 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 |
2010093912 | Apr 2010 | JP |
2010154692 | Jul 2010 | JP |
2010165347 | Jul 2010 | JP |
2013108793 | Jun 2013 | JP |
2013-132183 | Jul 2013 | JP |
2013132183 | Jul 2013 | JP |
2013134683 | Jul 2013 | JP |
2013198262 | Sep 2013 | JP |
20040024552 | Mar 2004 | KR |
20080034141 | Apr 2008 | KR |
20130002970 | Jan 2013 | KR |
1999005766 | Feb 1999 | WO |
2007043250 | Apr 2007 | WO |
WO 2010117498 | Oct 2010 | WO |
WO 2012165071 | Dec 2012 | WO |
WO 2013001909 | Jan 2013 | WO |
WO 2014200939 | Dec 2014 | WO |
Entry |
---|
Japanese Patent Application No. 2016-549265 Notification of Reasons for Refusal dated Oct. 31, 2017, 4 pages. |
Japanese Patent Application No. 2016-549265 English translation of Notification of Reasons for Refusal dated Oct. 31, 2017, 3 pages. |
Chilean Patent Application No. 201601924 Office Action dated Sep. 13, 2017, 5 pages. |
Office Action corresponding to Australian Patent Application No. 2015210567, dated Aug. 7, 2017. |
Office Action corresponding to Chinese Patent Application No. 201410043218.5, dated May 25, 2015—Search Results on p. 4 only. |
Office Action corresponding to European Patent Application No. 15744077.7, dated Jul. 3, 2017. |
Office Action corresponding to Japanese Patent Application No. 2016-549265, dated Aug. 2, 2017—with English translation. |
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. |
European Patent Application No. 15744077.7 Office Action dated May 24, 2018, 3 pages. |
Chilean Patent Application No. 201601924 Office Action dated Mar. 7, 2018, 3 pages, 7 pages. |
Translation of the International Search Report and Written Opinion corresponding to International Patent Application No. PCT/CN2015/070468, dated Apr. 13, 2015, 8 pages. |
Canadian Patent Application No. 2937953, Office Action dated Jan. 18, 2018, 5 pages. |
Chinese Patent Application No. 201410042541.0 First Office Action dated Jul. 17, 2015 with English translation, 10 pages. |
Chinese Patent Application No. 201410043139.4 First Office Action dated Dec. 23, 2015 with English translation, 8 pages. |
Canadian Patent Application No. 2,937,953, Office Action dated May 31, 2017, 7 pages. |
Singapore Patent Application No. 1120160219X, Office Action dated Apr. 4, 2017, 13 pages. |
Korean Patent Application No. 10-2016-7023544 English translation of Office Action dated Dec. 14, 2018, 5 pages. |
Korean Patent Application No. 10-2016-7023544 Office Action dated Dec. 14, 2018, 5 pages. |
European Patent Application No. 15744077.7 Office Action dated Oct. 12, 2018, 4 pages. |
Canadian Patent Application No. 2,937,953 Office Action dated Sep. 19, 2018, 5 pages. |
Chinese Patent Application No. 201580005214.0 English translation of Office Action dated Aug. 9, 2017, 6 pages. |
Chinese Patent Application No. 201580005214.0 Office Action dated Aug. 9, 2017, 6 pages. |
Japanese Patent Application No. 2016-549265 English translation of Notice of Allowance dated Dec. 19, 2017, 2 pages. |
Japanese Patent Application No. 2016-549265 Notice of Allowance dated Dec. 19, 2017, 3 pages. |
Brazilian Patent Application No. 11 2016 016943 3 English translation of Office Action dated Feb. 10, 2020, 3 pages. |
Brazilian Patent Application No. 11 2016 016943 3 Office Action dated Feb. 10, 2020, 4 pages. |
Chinese Patent Application No. 201610973222.0 English translation of Office Action dated Jul. 10, 2019, 5 pages. |
Chinese Patent Application No. 201610973222.0 Office Action dated Jul. 10, 2019, 5 pages. |
Indian Patent Application No. 201637028065 Office Action dated May 27, 2019, 5 pages. |
Japanese Patent Application No. 2018-024364 English translation of Office Action dated Mar. 19, 2019, 3 pages. |
Japanese Patent Application No. 2018-024364 Office Action dated Mar. 19, 2019, 3 pages. |
Korean Patent Application No. 10-2018-7013989 first Office Action dated Aug. 14, 2018, 6 pages. |
Korean Patent Application No. 10-2018-7013989 English translation of first Office Action dated Aug. 14, 2018, 6 pages. |
Korean Patent Application No. 10-2018-7013989 second Office Action dated Feb. 28, 2019, 4 pages. |
Korean Patent Application No. 10-2018-7013989 English translation of second Office Action dated Feb. 28, 2019, 4 pages. |
Korean Patent Application No. 10-2018-7013989 third Office Action dated Apr. 24, 2019, 3 pages. |
Korean Patent Application No. 10-2018-7013989 English translation of third Office Action dated Apr. 24, 2019, 13 pages. |
Mexican Patent Application No. MX/a/2016/009853 Office Action dated Mar. 9, 2020, 6 pages. |
Mexican Patent Application No. MX/a/2016/009853 English translation of Office Action dated Mar. 9, 2020, 5 pages. |
Malaysian Patent Application No. PI 2016702707 Office Action dated Jul. 25, 2019, 4 pages. |
Singapore Patent Application No. 11201606223P Office Action dated Oct. 29, 2018, 6 pages. |
U.S. Appl. No. 15/596,950 Office Action dated Nov. 17, 2017, 9 pages. |
U.S. Appl. No. 15/989,363 Office Action dated Oct. 25, 2019, 45 pages. |
U.S. Appl. No. 15/989,363 Office Action dated Apr. 15, 2020, 12 pages. |
U.S. Appl. No. 15/989,363 Office Action dated Jul. 20, 2020, 12 pages. |
Indian Patent Application No. 201637028356 Office Action dated Apr. 26, 2019, 8 pages. |
Korean Patent Application No. 10-2018-7026460 English translation of Notice of Allowance dated May 27, 2019, 3 pages. |
Korean Patent Application No. 10-2018-7026460 Notice of Allowance dated May 27, 2019, 2 pages. |
U.S. Appl. No. 15/115,251 Office Action dated Oct. 16, 2018, 46 pages. |
U.S. Appl. No. 15/115,251 Advisory Action dated Jan. 24, 2019, 3 pages. |
U.S. Appl. No. 15/115,251 Office Action dated Apr. 1, 2019, 39 pages. |
Chinese Patent Application No. 201810220714.1 English translation of Office Action dated Nov. 17, 2020, 20 pages. |
Chinese Patent Application No. 201810220714.1 Office Action dated Nov. 17, 2020, 20 pages. |
U.S. Appl. No. 15/989,363 Office Action dated Nov. 19, 2020, 11 pages. |
European Patent Application No. 15744077.7 Office Action dated Apr. 22, 2020 3 pages. |
Mexican Patent Application No. MXa2016009854 Office Action dated Mar. 10, 2020, 5 pages. |
Mexican Patent Application No. MXa2016009854 English translation of Office Action dated Mar. 10, 2020, 4 pages. |
Philippine Patent Application No. 1-2016-501486 Office Action dated Aug. 20, 2020, 5 pages. |
U.S. Appl. No. 15/989,363 Office Action dated Apr. 23, 2021, 11 pages. |
U.S. Appl. No. 15/900,281 Final Office Action dated Apr. 2, 2021, 46 pages. |
U.S. Appl. No. 15/900,281 Office Action dated Nov. 27, 2020, 38 pages. |
Chinese Patent Application No. 201810220714.1 Office Action dated Jun. 29, 2021, 18 pages. |
Chinese Patent Application No. 201810220714.1 English translation of Office Action dated Jun. 29, 2021, 29 pages. |
European Patent Application No. 15744077.7 Office Action dated Jul. 5, 2021, 4 pages. |
Chinese Patent Application No. 201810220714.1 Decision on Rejection dated Dec. 3, 2021, 13 pages. |
Chinese Patent Application No. 201810220714.1 Decision on Rejection dated Dec. 3, 2021, 15 pages. |
European Patent Application No. 15744077.7, Office Action dated Feb. 14, 2022, 4 pages. |
Chinese Patent Application No. 201810220714.1, Office Action dated Mar. 22, 2022, 22 pages. |
Chinese Patent Application No. 201810220714.1, English translation of Office Action dated Mar. 22, 2022, 26 pages. |
Number | Date | Country | |
---|---|---|---|
20160352117 A1 | Dec 2016 | US |