Patent Grant
10424954
This application is a U.S. national phase application based on International Application No. PCT/CN2014/090845, filed on Nov. 11, 2014, the entire contents of which are incorporated herein by reference.
The present disclosure relates to field of charging, and more particularly, to a power adaptor, a terminal and a charging system.
At present, a smart phone is increasingly favored by consumers. However, generally it is required to charge the smart phone frequently because the smart phone has big power consumption. In addition, with an increasing battery capacity of the smart phone, a charging period of time can become longer correspondingly. How to realize quick-charging needs to be solved.
It can realize the quick-charging by increasing an output current via a power adaptor. However, when performing the quick-charging on a battery by a manner of increasing the output current, phenomenon, such as too high temperature, an overvoltage, an overcurrent, an interface burning and the like, can occur in the power adaptor or in the smart phone, thereby causing damage of the power adaptor or of the smart phone.
Embodiments of the present disclosure provide a power adaptor, a terminal and a charging system.
In at least one embodiment, a power adaptor is provided. The power adaptor includes a power conversion unit and a charging interface. The charging interface includes a power line. The power conversion unit is configured to charge a terminal via the power line. The power adaptor further includes a communication unit. The charging interface further includes a data line. The communication unit is configured to communicate with the terminal via the data line when the power adaptor is coupled to the terminal.
In at least one embodiment, a terminal is provided. The terminal includes a battery and a charging interface. The charging interface includes a power line. The terminal is configured to introduce a charging current from a power adapter via the power line so as to charge the battery. The terminal further includes a communication unit. The charging interface further includes a data line. The communication unit is configured to communicate with the power adaptor via the data line when the terminal is coupled to the power adaptor.
In at least one embodiment, a charging system is provided. The charging system includes a power adaptor according to the first aspect or any of implementations thereof and a terminal according to the second aspect or any of the implementations thereof.
In order to make technique solutions according to embodiments of the present disclosure more apparent, drawings needed to be used in descriptions of the embodiments will be illustrated in the following. Obviously, the drawings to be illustrated in the following only represent some embodiments of the present disclosure, and other drawings can be obtained according these drawings by those having ordinary skills in the related art without making creative labors.
The technical solutions in embodiments of the present disclosure will be described clearly and completely hereinafter with reference to accompanying drawings in embodiments of the present disclosure. Apparently, embodiments described are a part of embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments in the present disclosure without creative labor shall fall in the protection scope of the present disclosure.
In at least one embodiment, the power conversion unit 110 is configured to convert alternating current to direct current. For example, the power conversion unit 110 can convert 220V utility power to 5V direct-current power.
The number of the power line 121 can be one or more than one. The number of the data line 122 can be one or more than one.
The charging interface 120 can be a USB interface. The data line 122 can be at least one of a D+ line and a D− line of the USB interface. Furthermore, the power adaptor 100 in embodiments of the present disclosure can be integrated with a USB cable, or can include a USB connector and coupled to the terminal via a USB cable. In at least one embodiment, the USB interface can be a normal USB interface or also can be a micro USB interface.
In at least one embodiment, the power adaptor 100 can perform one or more handshakes with the terminal when it is coupled to the terminal. After the handshake, the power adaptor 100 starts to charge the terminal. The so-called “handshake” herein refers to that the power adaptor 100 and the terminal send messages (or signals) to each other so as to perform interactions on various required information before charging. The various required information can be, such as, a version or a type of the power adaptor 100, a version or a type of the terminal, a working state of the power adaptor 100, a value of battery temperature of the terminal, a charging mode supported by the power adaptor 100 and by the terminal, a capability of the power adaptor 100 for outputting a voltage and a current, a capability of the terminal for receiving a voltage and a current and the like. The power adaptor 100 negotiates with the terminal on a charging mode and a charging parameter by performing interactions on that information. For example, the charging mode includes a quick-charging mode and a common charging mode; and the charging parameter includes a charging voltage (such as an initial charging voltage), and a charging current (such as an initial charging current).
As known from the above, communication between the communication unit 130 and the terminal can occur during a process of negotiation before the power adaptor 100 charges the terminal (the power adaptor 100 does not output the charging current to the terminal yet at this moment). However, in embodiments of the present disclosure, it is not limited thereto. The communication between the communication unit 130 and the terminal can occur during a process of charging the terminal by the power adaptor 100 (that is, during a process of outputting the charging current to the terminal by the power adaptor 100). For example, a value of a battery voltage is received from the terminal during charging; or from the terminal, an input voltage value or an input current value of the power adaptor 100 detected by the terminal is received during charging; or an interaction with the terminal on information, such as an overcurrent/overvoltage, is performed during charging. Furthermore, the communication between the communication unit 130 and the terminal can occur at the end of the charging. For example, the power adaptor 100 negotiates with the terminal to finish charging.
In embodiments of the present disclosure, the power adaptor 100 charges the terminal still using the power line 121. Furthermore, the power adaptor 100 can communicate with the terminal via the data line 122 when the power adaptor 100 is coupled to the terminal. Compared with the method of data and power time-division multiplexing the power line 121, it is effectively avoided the heating phenomenon of the power line 121 caused by an excessively high load of a signal isolation unit.
In at least one embodiment, as an embodiment, the communication unit 130 is configured to perform two-way communication with the terminal via the data line 122.
In detail, the communication unit 130 and the terminal can perform interactions on parameters thereof with each other. For example, the communication unit 130 sends an output current value or voltage value of the power adaptor 100 to the terminal during charging, and the terminal also sends an input current value and voltage value received from the power adaptor 100 by the terminal to the communication unit 130. For another example, the communication unit 130 sends a handshake request message to the terminal to ask whether the terminal supports the quick-charging mode, and the terminal sends a handshake response message to the communication unit 130 to notify the power adaptor 100 of the charging mode supported by the terminal.
In at least one embodiment, as an embodiment, the communication unit 130 is configured to negotiate with the terminal on the charging mode of the terminal before the terminal is charged. The charging mode includes a quick-charging mode and a common charging mode.
In detail, the communication unit 130 and the terminal send handshake signals to each other, so as to negotiate on the charging mode of the terminal. The handshake signal can be sent by the communication unit 130 to the terminal, or also can be sent by the terminal to the communication unit 130.
In at least one embodiment, as an implementation, the communication unit 130 is configured to negotiate with the terminal on the charging mode by acts of: sending, by the communication unit 130, a handshake request message to the terminal; receiving, by the communication unit 130, a handshake response message from the terminal, in which the handshake response message indicates that the terminal supports the quick-charging mode; and determining, by the communication unit 130, to charge the terminal with accordance to the quick-charging mode according to the handshake response message.
It is to be understood that, the handshake request message can indicate that the power adaptor 100 is a power adaptor supporting the quick-charging mode. That is, it is known that the power adaptor 100 supports the quick-charging mode correspondingly when the terminal receives the handshake request message sent by the power adaptor 100. Or, the handshake request message does not carry with any information and is merely a request for communicating with the terminal. The power adaptor 100 further negotiates with the terminal on the charging mode, the charging parameter and such information after the terminal responds with the handshake request message.
In at least one embodiment, as another implementation, the communication unit 130 is configured to negotiate with the terminal on the charging mode by acts of: sending, by the communication unit 130, a handshake request message to the terminal; and determining, by the communication unit 130, to charge the terminal with accordance to the common charging mode when a handshake response message sent by the terminal does not received.
For example, the power adaptor 100 sends the handshake request message to the terminal and the terminal responds with the handshake response message when both of the power adaptor 100 and the terminal support the quick-charging mode. However, the power adaptor 100 charges the terminal as default with accordance to the common charging mode when the terminal does not respond with the handshake response message. In at least one embodiment, there are a plurality of reasons that the terminal does not respond with the handshake response message back. For example, the terminal does not support the quick-charging mode so as not to recognize the handshake request message; or it is not satisfied a quick-charging condition according to a working condition thereof although the terminal recognizes the handshake request message, so as to abandon sending the handshake response message to the power adaptor 100. For example, the terminal finds that the electric quantity of the battery is too low to enter the quick-charging mode immediately. Then, the terminal will not respond with the handshake response message, and the power adaptor 100 charges the terminal with accordance to the common charging mode.
In at least one embodiment, as another implementation, the communication unit 130 is configured to negotiate with the terminal on the charging mode by acts of: sending, by the communication unit 130, a handshake request message to the terminal; receiving, by the communication unit 130, a handshake response message from the terminal, in which the handshake response message includes a charging mode supported by the terminal and a current working parameter of the terminal; determining, by the communication unit 130, to charging the terminal with accordance to the quick-charging mode when both of the power adaptor 100 and the terminal support the quick-charging mode and the current working parameter of the terminal satisfies a quick-charging condition; and determining, by the communication unit 130, to charge the terminal with accordance to the common charging mode when both of the power adaptor 100 and the terminal support the quick-charging mode and the current working parameter of the terminal does not satisfy a quick-charging condition.
In detail, the power adaptor 100 judges whether the terminal supports the quick-charging condition firstly after receiving the handshake response message. It further judges whether the current working parameter of the terminal satisfies the quick-charging condition when the terminal supports the quick-charging mode. For example, whether the value of the battery temperature of the terminal satisfies temperature value required by the quick-charging mode; whether the value of the battery voltage of the terminal satisfies a minimum value of the voltage required by the quick-charging mode, and the like. It is charged with accordance to the quick-charging mode when the current working parameter of the terminal satisfies the quick-charging condition, otherwise, it is charged with accordance to the common charging mode.
In at least one embodiment, the quick-charging mode and the common charging mode are two relative concepts. In at least one embodiment, the period of time spent by the quick-charging mode is less than that spent by the common charging mode when it is needed to charge the battery from a first electricity to a second electricity (the second electricity is greater than the first electricity). There are a plurality of implementation forms of the quick-charging mode. For example, compared with the common charging mode, it provides a bigger voltage or current to the terminal.
In at least one embodiment, the negotiation between the power adaptor 100 and the terminal before charging is not limited to the negotiation on the charging mode. The negotiation can be on the charging voltage, the charging current and such parameters.
In at least one embodiment, as an embodiment, the communication unit 130 is configured to negotiate with the terminal on the charging parameter before the terminal is charged. The charging parameter includes at least one of followings: the charging voltage and the charging current.
Taking an example to illustrate, the communication unit 130 sends a handshake request message to the terminal. And then the communication unit 130 receives a handshake response message of the terminal, in which the handshake response message includes at least one of following information: a version of the terminal, an identifier of the terminal, a value of battery temperature of the terminal, and a maximum value of the charging voltage supported by the terminal and a maximum value of the charging current supported by the terminal. Further, the communication unit 130 determines the charging parameter according to information in the handshake response message.
For example, the communication unit 130 acquires that the terminal supports the quick-charging mode from the handshake response message. And then the communication unit 130 determines a voltage/current value of the terminal with the version during quick-charging according to the version of the terminal. Or, the communication unit 130 determines an initial voltage/current value of the quick-charging mode according to a value of a current electric quantity of the battery.
In at least one embodiment, as an embodiment, the communication unit 130 is configured to keep communication with the terminal during a procedure of outputting the charging current to the terminal by the power adaptor 100.
In at least one embodiment, one-way communication between the communication unit 130 and the terminal may be performed during the procedure of outputting the charging current to the terminal by the power adaptor 100. For example, a value of the battery voltage is acquired from the terminal, and an output voltage and current are adjusted according thereto. Two-way communication between the communication unit 130 and the terminal also may be performed. For example, the power adaptor 100 sends an output voltage value and current value to the terminal, and from the terminal, receives a voltage value and current value input by the power adaptor 100 and detected by the terminal.
In at least one embodiment, as illustrated in
The power adaptor 100 can adjust the output voltage by acquiring the value of the current battery voltage of the terminal from the terminal. It can be avoided that the voltage applied on the battery of the terminal exceeds a safe charging voltage of the battery. As a result, it can improve safety while charging using the power adaptor 100 of embodiments of the present disclosure.
In at least one embodiment, as illustrated in
The terminal can determine whether the input voltage or current matches to the voltage or current output by the power adaptor 100 by sending a message indicating the voltage value and current value output by the power adaptor 100 to the terminal. It can be further determined whether there is a fault in coupling between the power adaptor 100 and the terminal (such as a short circuit). As a result, it can further improve safety while charging using the power adaptor 100 of embodiments of the present disclosure.
In at least one embodiment, as illustrated in
The power adaptor 100 can determine whether the output voltage or current matches to the voltage and current input into the terminal by receiving a message indicating the voltage value or current value input into the terminal sent by the terminal. It can be further determined whether there is a fault in coupling between the power adaptor 100 and the terminal (such as a short circuit). As a result, it can further improve safety while charging using the power adaptor 100 of embodiments of the present disclosure.
In at least one embodiment, as the coupling between the power adaptor 100 and the terminal is generally realized via the charging interface 120, the circuit on the charging interface 120 can have impedance. Therefore, a voltage/current value output to the terminal by the power adaptor 100 cannot always be equal to a voltage/current value received from the power adaptor 100 by the terminal. The voltage/current value output by the power adaptor 100 is different greatly from the voltage/current received by the terminal when the impedance of the circuit on the charging interface 120 is very high. Therefore, an interaction on the voltage/current value can provide support for finding and excluding a fault subsequently.
In at least one embodiment, as illustrated in
In at least one embodiment, as illustrated in
In at least one embodiment, as an embodiment, the communication unit 130 is configured to receive a sixth message from the terminal via the data line 122 before charging the terminal. The sixth message indicates a value of battery temperature of the terminal.
The power adaptor 100 can determine a state of the battery by acquiring the value of the current battery temperature of the terminal from the terminal. For example, the terminal determines the safety of the battery low so as to stop power outputting when the value of the battery temperature is higher than a preset threshold. As a result, it can improve safety while charging using the power adaptor 100 of embodiments of the present disclosure.
In at least one embodiment, as an embodiment, the communication unit 130 is configured to send a seventh message to the terminal via the data line 122 before charging the terminal. The seventh message indicates an identifier or a version of the power adaptor 100.
The terminal can determine the coupled device is the power adaptor 100 by sending a message indicating the identifier or the version of the power adaptor 100 to the terminal. Thus, the phone can be triggered into a processing of a charging state (the processing can be similar to the prior art, herein, in order to avoid repeating again, detailed introduction can be omitted). It can be avoided a fault caused by the phone mistaken assuming the coupled device to be a computer or other terminals.
In at least one embodiment, as illustrated in
The power adaptor 100 can determine a battery parameter used by terminal (such as whether it is supported the quick-charging, a rated charging voltage or the like) according to a pre-stored data by receiving data of the identifier or the version of the terminal from the terminal. Further, the terminal can output a power corresponding to the parameter of the battery to the terminal. As a result, it can improve safety while charging using the power adaptor 100 of embodiments of the present disclosure.
The description combined with the
In embodiments of the present disclosure, the power adaptor charges the terminal 200 still using the power line 221. Furthermore, the power adaptor can communicate with the terminal 200 via the data line 222 when the power adaptor is coupled to the terminal 200. Compared with the method of data and power time-division multiplexing the power line 221, it is effectively avoided the heating phenomenon of the power line 221 caused by an excessively high load of a signal isolation unit.
In at least one embodiment, as an embodiment, the communication unit 230 is configured to negotiate with the power adaptor on a charging mode of the terminal 200 before the terminal 200 is charged. The charging mode can include a quick-charging mode and a common charging mode.
In at least one embodiment, as an embodiment, the communication unit 230 is configured to negotiate with the power adaptor on the charging mode of the terminal 200 by acts of: receiving, by the communication unit 230, a handshake request message from the power adaptor, in which the handshake request message can indicate that the power adaptor supports the quick-charging mode; and sending, by the communication unit 230, a handshake response message to the power adaptor, in which the handshake response message can indicate the power adaptor to charge the terminal 200 with accordance to the quick-charging mode.
In at least one embodiment, as an embodiment, the communication unit 230 is configured to negotiate with the power adaptor on the charging mode of the terminal 200 by acts of: receiving, by the communication unit 230, a handshake request message from the power adaptor, in which the handshake request message can indicate that the power adaptor supports the quick-charging mode; sending, by the communication unit 230, a handshake response message to the power adaptor when a current working parameter of the terminal 200 satisfies a quick-charging condition, in which the handshake response message can indicate the power adaptor to charge the terminal 200 with accordance to the quick-charging mode; and sending, by the communication unit 230, a handshake response message to the power adaptor when a current working parameter of the terminal 200 does not satisfy a quick-charging condition, in which the handshake response message can indicate the power adaptor to charge the terminal 200 with accordance to the common charging mode.
In at least one embodiment, as an embodiment, the communication unit 230 is configured to negotiate with the power adaptor on a charging parameter before charging the terminal 200. The charging parameter can include at least one of following parameters: a charging voltage and a charging current.
In at least one embodiment, as an embodiment, the communication unit 230 is configured to negotiate with the power adaptor on the charging parameter by acts of: receiving, by the communication nit 230, a handshake request message form the power adaptor, in which the handshake request message can include at least one of following information: a version of the power adaptor, an identifier of the power adaptor, a working state of the power adaptor, and a maximum value of an output voltage supported by the power adaptor and a maximum value of an output current supported by the power adaptor; determining, by the communication nit 230, the charging parameter according to information in the handshake request message; and sending, by the communication unit 230, a handshake response message to the power adaptor, in which the handshake response message can indicate the power adaptor to charge the terminal 200 with accordance to the charging parameter.
In at least one embodiment, as an embodiment, the charging interface 220 can be a USB interface.
In at least one embodiment, as an embodiment, the data line 222 can be at least one of a D+ line and a D− line of the USB interface.
In at least one embodiment, as an embodiment, the communication unit 230 is configured to keep communication with the power adaptor via the data line 222 during a procedure of receiving a charging current from the power adaptor by the terminal 200.
In at least one embodiment, as illustrated in
In at least one embodiment, as illustrated in
In at least one embodiment, as illustrated in
In at least one embodiment, as illustrated in
In at least one embodiment, as illustrated in
In at least one embodiment, as an embodiment, the terminal 200 can be a smart phone.
In at least one embodiment, the mentioned smart phone is merely one example of the terminal 200. Embodiments of the present disclosure are not limited thereto. Technical solutions of the present disclosure can be applied in various devices of finishing functions with power supplied by the battery 210. For example, a tablet computer, a portable computing device, a message displaying device, an image shooting device, a messaging device or the like.
In at least one embodiment, as an embodiment, communication between the communication unit 230 and the power adaptor can be two-way communication.
The power adaptor 100 includes a first power conversion unit 110′, a first charging interface including a first power line 121′ and a first data line 122′, and a first communication unit 130′. The terminal 200 includes a battery 210′, a second charging interface including a second power line 221′ and a second data line 222′, and a second communication unit 230′.
The first power conversion unit 110′ is configured to charge the terminal 200 via the first power line 121′. The first communication unit 130′ is configured to communicate with the terminal 200 via the first data line 122′ when the power adaptor 100 is coupled to the terminal 200.
The terminal 200 is configured to introduce a charging current from the power adaptor 100 via the second power line 221′ to charge the battery 210′. The second communication unit 230′ is configured to communicate with the power adaptor 200 via the second data line 222′ when the terminal 200 is coupled to the power adapter 100.
The first power conversion unit 110′ can refer to the power conversion unit 110 described above. The first power line 121′ can refer to the power line 121 described above. The first data line 122′ can refer to the data line 122 described above. The first communication unit 130′ can refer to the communication unit 130 described above.
The second power line 221′ can refer to the power line 221 described above. The second data line 222′ can refer to the data line 222 described above. The second communication unit 230′ can refer to the communication unit 230 described above.
It is to be understood that, term “and/or” mentioned is merely a purpose for describing an association between associated objects, which represents three relations. For example, A and/or B, can represent three conditions: A existing alone, A and B both existing at a same moment, and B existing alone. Furthermore, character “/” mentioned merely represents a “or” relation between an object in front thereof and another object thereafter.
It is to be understood that, in various embodiments of the present disclosure, sequence number of each process does not refer to a performance order. The performance order of each process is determined by functions and internal logic thereof, but does not limit the implementation process of embodiments of the present disclosure.
Those skilled in the art can be aware that, units and algorithm steps in respective examples described with reference to embodiments disclosed in the present disclosure can be realized by electronic hardware or combination of computer software and electronic hardware. Executing these functions in hardware or software depends on particular applications and design constraint conditions of the technical solutions. Technology professionals can use different methods to realize the described functions for each particular application, which should be regarded as being within the scope of the present disclosure.
Those skilled in the art can understand clearly that, for convenience and simplicity of description, specific working process of the above system, devices and units can refer to corresponding process in the above method embodiments, which will not be elaborated herein.
It should be understood that, the system, devices and method disclosed in several embodiments provided by the present disclosure can be realized in any other manner. For example, the device embodiments described above can be merely exemplary, for example, the units are just divided according to logic functions. In practical implementation, the units can be divided in other manners, for example, multiple units or components can be combined or integrated into another system, or some features can be omitted or not executed. In addition, the mutual coupling or direct coupling or communication connection described or discussed can be via some interfaces, and indirect coupling or communication connection between devices or units can be electrical, mechanical or of other forms.
The units illustrated as separate components can be or not be separated physically, and components described as units can be or not be physical units, i.e., can be located at one place, or can be distributed onto multiple network units. It is possible to select some or all of the units according to actual needs, for realizing the objective of embodiments of the present disclosure.
In addition, respective functional units in respective embodiments of the present disclosure can be integrated into one processing unit, or can be present as separate physical entities. It is also possible that two or more than two units are integrated into one unit.
If the functions are realized in form of functional software units and are sold or used as separate products, they can be stored in a computer readable storage medium. Based on this understanding, the parts of the technical solutions or the essential parts of the technical solutions (i.e. the parts making a contribution to the related art) can be embodied in form of software product, which is stored in a storage medium, and includes several instruction used for causing a computer device (for example, a personal computer, a server or a network device) to execute all or part of steps in the methods described in respective embodiments of the present disclosure. The above storage medium can be any medium capable of storing program codes, including a USB flash disk, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a disc, or a light disk.
The forgoing description is only directed to preferred embodiments of the present disclosure, but not used to limit the present disclosure. All modifications, equivalents, variants and improvements made within the spirit and principle of the present disclosure shall fall within the protection scope of the present disclosure. Thus, the protection scope of the present disclosure shall be limited by the protection scope of the claims.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2014/090845 | 11/11/2014 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2016/074158 | 5/19/2016 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 4811154 | Trenkler | Mar 1989 | A |
| 5541489 | Dunstan | Jul 1996 | A |
| 5617003 | Odachi | Apr 1997 | A |
| 5656917 | Theobald | Aug 1997 | A |
| 5767781 | Yavelberg | Jun 1998 | A |
| 6097175 | Yoon | Aug 2000 | A |
| 6873135 | Nakatsuji | Mar 2005 | B2 |
| 7145439 | Darshan | Dec 2006 | B2 |
| 7461194 | Ohara | Dec 2008 | B2 |
| 7495416 | Sato | Feb 2009 | B2 |
| 7531986 | Eager | May 2009 | B2 |
| 7615965 | Popescu-Stanesti | Nov 2009 | B2 |
| 7906937 | Bhade | Mar 2011 | B2 |
| 7977919 | Jaoude | Jul 2011 | B1 |
| 8013568 | Park | Sep 2011 | B2 |
| 8022662 | Eager | Sep 2011 | B2 |
| 8072184 | Bhade | Dec 2011 | B2 |
| 8169189 | Eto | May 2012 | B2 |
| 8234509 | Gioscia | Jul 2012 | B2 |
| 8261100 | Paniagua, Jr. | Sep 2012 | B2 |
| 8300666 | Karam | Oct 2012 | B2 |
| 8358107 | Nguyen | Jan 2013 | B2 |
| 8386814 | Tom | Feb 2013 | B2 |
| 8432136 | Ashida | Apr 2013 | B2 |
| 8527688 | Chatterjee | Sep 2013 | B2 |
| 8536837 | Jaoude | Sep 2013 | B1 |
| 8541986 | Hiraoka | Sep 2013 | B2 |
| 8686682 | Eager | Apr 2014 | B2 |
| 8810192 | Bridges | Aug 2014 | B2 |
| 8860368 | Ohtomo | Oct 2014 | B2 |
| 8892912 | Lai | Nov 2014 | B2 |
| 8994321 | Knowlton | Mar 2015 | B2 |
| 9018918 | Nguyen | Apr 2015 | B2 |
| 9113017 | Ishikawa | Aug 2015 | B2 |
| 9153984 | Ono | Oct 2015 | B2 |
| 9252615 | Chen | Feb 2016 | B2 |
| 9274577 | Lai | Mar 2016 | B2 |
| 9321350 | Yokoyama | Apr 2016 | B2 |
| 9395778 | Fritchman | Jul 2016 | B2 |
| 9424122 | Dolfi | Aug 2016 | B2 |
| 9438064 | Keeling | Sep 2016 | B2 |
| 9444278 | Baurle | Sep 2016 | B2 |
| 9488997 | Dwelley | Nov 2016 | B1 |
| 9496726 | Frid | Nov 2016 | B2 |
| 9584016 | Motoki | Feb 2017 | B2 |
| 9651593 | Sims | May 2017 | B2 |
| 9669723 | Sugeno | Jun 2017 | B2 |
| 9711983 | Winger | Jul 2017 | B2 |
| 9787112 | Sukup | Oct 2017 | B2 |
| 9789779 | Shimizu | Oct 2017 | B2 |
| 9893540 | Zhang | Feb 2018 | B2 |
| 9899848 | Hu | Feb 2018 | B2 |
| 9899854 | Wei | Feb 2018 | B2 |
| 9935490 | Zhang | Apr 2018 | B2 |
| 9985449 | Zhang | May 2018 | B2 |
| 9997933 | Huang | Jun 2018 | B2 |
| 9998611 | Zhang | Jun 2018 | B2 |
| 10033204 | Huang | Jul 2018 | B2 |
| 10044204 | Hu | Aug 2018 | B2 |
| 10050452 | Zhang | Aug 2018 | B2 |
| 10050466 | Hu | Aug 2018 | B2 |
| 10056779 | Hu | Aug 2018 | B2 |
| 10090700 | Zhang | Oct 2018 | B2 |
| 10097032 | Hu | Oct 2018 | B2 |
| 10116157 | Lei | Oct 2018 | B2 |
| 10122190 | Zhang | Nov 2018 | B2 |
| 10122201 | Zhang | Nov 2018 | B2 |
| 10141766 | Zhang | Nov 2018 | B2 |
| 10189360 | Ohtomo | Jan 2019 | B2 |
| 10205332 | Lei | Feb 2019 | B2 |
| 10211656 | Zhang | Feb 2019 | B2 |
| 10224725 | Zhang | Mar 2019 | B2 |
| 10270269 | Zhang | Apr 2019 | B2 |
| 10277052 | Li | Apr 2019 | B2 |
| 20020101218 | Koenck | Aug 2002 | A1 |
| 20020195996 | Nakatsuji | Dec 2002 | A1 |
| 20050099156 | Brenner | May 2005 | A1 |
| 20060082220 | Karam | Apr 2006 | A1 |
| 20060284595 | Hsieh et al. | Dec 2006 | A1 |
| 20070194626 | Eager | Aug 2007 | A1 |
| 20070194750 | Eager | Aug 2007 | A1 |
| 20080136372 | Eto | Jun 2008 | A1 |
| 20080303479 | Park | Dec 2008 | A1 |
| 20090200988 | Bridges | Aug 2009 | A1 |
| 20090309547 | Nakatsuji | Dec 2009 | A1 |
| 20100013442 | Yamazaki | Jan 2010 | A1 |
| 20100070659 | Ma | Mar 2010 | A1 |
| 20100104031 | Lacour | Apr 2010 | A1 |
| 20100131691 | Chatterjee | May 2010 | A1 |
| 20100146308 | Gioscia | Jun 2010 | A1 |
| 20100188054 | Asakura | Jul 2010 | A1 |
| 20100201308 | Lindholm | Aug 2010 | A1 |
| 20100264877 | Ashida | Oct 2010 | A1 |
| 20100268492 | Matsuura | Oct 2010 | A1 |
| 20100301809 | Bhade | Dec 2010 | A1 |
| 20110016341 | Tom | Jan 2011 | A1 |
| 20110095723 | Bhade | Apr 2011 | A1 |
| 20110248670 | Yamazaki | Oct 2011 | A1 |
| 20110267001 | Hiraoka | Nov 2011 | A1 |
| 20120007546 | Eager | Jan 2012 | A1 |
| 20120141847 | Amagai | Jun 2012 | A1 |
| 20120210146 | Lai | Aug 2012 | A1 |
| 20120253715 | Ohtomo | Oct 2012 | A1 |
| 20130076301 | Bastami | Mar 2013 | A1 |
| 20130127414 | Ohtomo | May 2013 | A1 |
| 20130241469 | Ono | Sep 2013 | A1 |
| 20130249283 | Yokoyama | Sep 2013 | A1 |
| 20130249479 | Partovi | Sep 2013 | A1 |
| 20130271069 | Partovi | Oct 2013 | A1 |
| 20130285604 | Partovi | Oct 2013 | A1 |
| 20130285605 | Partovi | Oct 2013 | A1 |
| 20140136863 | Fritchman | May 2014 | A1 |
| 20140239985 | Sims | Aug 2014 | A1 |
| 20140285133 | Toledo | Sep 2014 | A1 |
| 20140285845 | Ishikawa | Sep 2014 | A1 |
| 20140300321 | Kim | Oct 2014 | A1 |
| 20140320075 | Baurle | Oct 2014 | A1 |
| 20140335919 | Stewart | Nov 2014 | A1 |
| 20150061578 | Keeling | Mar 2015 | A1 |
| 20150074438 | Lai | Mar 2015 | A1 |
| 20150077056 | Bridges | Mar 2015 | A1 |
| 20150180244 | Jung | Jun 2015 | A1 |
| 20150256018 | Wei | Sep 2015 | A1 |
| 20150311729 | Ono | Oct 2015 | A1 |
| 20150339181 | Dolfi | Nov 2015 | A1 |
| 20160036256 | Sukup | Feb 2016 | A1 |
| 20160052413 | Shimizu | Feb 2016 | A1 |
| 20160064962 | Huang | Mar 2016 | A1 |
| 20160064963 | Huang | Mar 2016 | A1 |
| 20160064979 | Huang | Mar 2016 | A1 |
| 20160068073 | Taylor | Mar 2016 | A1 |
| 20160126756 | Okubo | May 2016 | A1 |
| 20160288658 | Rudolph | Oct 2016 | A1 |
| 20160344210 | Zhang | Nov 2016 | A1 |
| 20160344211 | Zhang | Nov 2016 | A1 |
| 20160344227 | Zhang | Nov 2016 | A1 |
| 20160372963 | Sankar | Dec 2016 | A1 |
| 20160380462 | Zhang | Dec 2016 | A1 |
| 20170012451 | Zhang | Jan 2017 | A1 |
| 20170040804 | Hu | Feb 2017 | A1 |
| 20170040814 | Hu | Feb 2017 | A1 |
| 20170040821 | Li | Feb 2017 | A1 |
| 20170113563 | Lee | Apr 2017 | A1 |
| 20170207648 | Xiao | Jul 2017 | A1 |
| 20170250557 | Zhang | Aug 2017 | A1 |
| 20170346313 | Yao | Nov 2017 | A1 |
| 20170358945 | Zhang | Dec 2017 | A1 |
| 20180019585 | Koga | Jan 2018 | A1 |
| 20180131207 | Zhang | May 2018 | A1 |
| 20180175659 | Zhang | Jun 2018 | A1 |
| 20180212435 | Li | Jul 2018 | A1 |
| 20180278070 | Zhang | Sep 2018 | A1 |
| 20190036361 | Zhang | Jan 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 202268816 | Jun 2012 | CN |
| 102957193 | Mar 2013 | CN |
| 103066340 | Apr 2013 | CN |
| 103762702 | Apr 2014 | CN |
| 104065147 | Sep 2014 | CN |
| 104079743 | Oct 2014 | CN |
| 104092274 | Oct 2014 | CN |
| 104124483 | Oct 2014 | CN |
| H11150883 | Jun 1999 | JP |
| 2005245078 | Sep 2005 | JP |
| 2005287278 | Oct 2005 | JP |
| 2006203980 | Aug 2006 | JP |
| 2007288889 | Nov 2007 | JP |
| 2007327772 | Dec 2007 | JP |
| 2008035674 | Dec 2008 | JP |
| 2009112111 | May 2009 | JP |
| 2010263735 | Nov 2010 | JP |
| 2013108793 | Jun 2013 | JP |
| 2013198262 | Sep 2013 | JP |
| 2014187575 | Oct 2014 | JP |
| 20140120699 | Oct 2014 | KR |
| 20150073677 | Jul 2015 | KR |
| WO 2013178191 | Dec 2013 | WO |
| WO 2014097640 | Jun 2014 | WO |
| Entry |
|---|
| Chinese Patent Application No. 201480075503.3 First Office Action dated Aug. 7, 2017 with English translation, 12 pages. |
| Japanese Patent Application No. 2016-573967 Notification of Reasons for Refusal dated Sep. 5, 2017 with English translation, 7 pages. |
| PCT/CN2014/090845 English Translation of the International Search Report & Written Opinion dated Aug. 14, 2015, 7 pages. |
| European Patent Application No. 14905952.9 extended European Search and Opinion dated Sep. 11, 2017, pages. |
| Australian Patent Application No. 2014411185 examination report dated Jul. 28, 2017, 3 pages. |
| Singapore Patent Application No. 11201609280R Invitation to Respond to Written Opinion, and Search Report dated Aug. 10, 2017, 10 pages. |
| Korean Patent Application No. 20167035467 Office Action dated Jan. 29, 2018, 6 pages. |
| Korean Patent Application No. 20167035467 English translation of Office Action dated Jan. 29, 2018, 6 pages. |
| Japanese Patent Application No. 2018026554 Office Action dated Dec. 4, 2018, 6 pages. |
| Japanese Patent Application No. 2018026554 English translation of Office Action dated Dec. 4, 2018, 4 pages. |
| Korean Patent Application No. 20187025357 Office Action dated Nov. 6, 2018, 5 pages. |
| Korean Patent Application No. 20187025357 English translation of Office Action dated Nov. 6, 2018, 4 pages. |
| European Patent Application No. 18206783.5 extended Search and Opinion dated Mar. 25, 2019, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170279286 A1 | Sep 2017 | US |
