Patent Description:
Nowadays, terminal devices, such as smartphones and tablet computers, are increasingly widely used. In addition, current terminal devices all use rechargeable batteries, which can be charged cyclically for use. This greatly facilitates people's life.

However, in an existing charging manner, regardless of a wired charging manner or a wireless charging manner, a generated charging signal may be coupled to a module component in a terminal device (the module component may be a component or a part of one or more functional modules in the terminal device), for example, a display module (liquid crystal display (Liquid Crystal Display, LCD)), a touch module (touch panel (Touch Panel, TP)), a camera module, a fingerprint module, and the like. When the terminal device is charged in the wired charging manner, a charging signal generated by a charging device (for example, a wired charger) is coupled to a module component in a conduction manner. When the terminal device is charged in the wireless charging manner, a charging signal generated by a charging device (for example, a wireless charging device) is spatially coupled to a module component.

Consequently, when a frequency of the charging signal coincides with (or is close to) an operating frequency (or harmonic) of the module component, an abnormality may occur when the module component operates. For example, touch sensitivity of the TP is decreased, a color stripe or a ripple appears on the camera module, or an unlocking success rate of the fingerprint module is decreased. This affects user experience.

<CIT> describes a technique for adjusting characteristics of a touch sensing device in the presence of a wireless power field. The presence of a wireless power field may be detected, and a characteristic of a touch sensing device may be adjusted to reduce interference of the wireless power field with the touch sensing device.

<CIT> describes a technique for reducing interference in an inductive charging system. A chargeable device is inductively charged with an inductive charger. The operation of a receiver in an AM band is detected. At least one of a frequency band employed by the charger and an amount of power provided to the chargeable device by the charger is adjusted based on the operation of the receiver in the AM band.

Embodiments of this application provide a charging method and device, to reduce interference generated on a module component in a terminal device in a process in which the charging device charges the terminal device.

According to a first aspect, an embodiment of this application provides a charging method, including: obtaining, by the sensitive module component, a working status of the sensitive module component; sending, by the sensitive module component, the working status to the charging module, where the sensitive module component is a module component that is interfered with in a process in which a charging device charges the terminal device at a sensitive frequency, and the sensitive frequency is within a range of a charging frequency band of the charging device; when the working status is an enabled state, determining, by the charging module, a safe charging parameter, where the safe charging parameter includes at least one of a safe charging frequency, a safe charging current, and a safe charging voltage; and sending, by the charging module, the safe charging parameter to the charging device, so that the charging device charges the terminal device by using the safe charging parameter, where in a process in which the charging device charges the terminal device by using the safe charging parameter, the sensitive module component operates normally.

In a possible design, when the sensitive module component can obtain an operating frequency of the sensitive module component, the method further includes: obtaining, by the sensitive module component, the operating frequency of the sensitive module component, where the operating frequency is the sensitive frequency; and sending, by the sensitive module component, the obtained operating frequency to the charging module; and the determining, by the charging module, a safe charging parameter includes: selecting, by the charging module, a frequency other than the obtained operating frequency from the charging frequency band as the safe charging frequency; and determining, by the charging module, the safe charging voltage or the safe charging current based on a pre-stored first mapping relationship, where the first mapping relationship includes a correspondence between the sensitive module component and at least one of the safe charging voltage and the safe charging current when the sensitive module component is in an enabled state.

In a possible design, the determining, by the charging module, a safe charging parameter includes: determining, by the charging module based on a pre-stored second mapping relationship, a safe charging frequency, a safe charging voltage, or a safe charging current that corresponds to the sensitive module component, where the second mapping relationship includes a correspondence between the sensitive module component and at least one of the safe charging frequency, the safe charging voltage, and the safe charging current when the sensitive module component is in an enabled state.

In a possible design, when there are a plurality of sensitive module components in an enabled state, the method further includes: determining an intermediate frequency of safe charging frequencies corresponding to the plurality of sensitive module components as the safe charging frequency; determining a minimum charging voltage in safe charging voltages corresponding to the plurality of sensitive module components as the safe charging voltage; or determining a minimum charging current in safe charging currents corresponding to the plurality of sensitive module components as the safe charging voltage.

The sending, by the sensitive module component, the working status to the charging module includes writing, by the sensitive module component, the working status into a node file, where the charging module obtains the working status from the node file.

According to a second aspect, an embodiment of this application provides a terminal device. The terminal device has a function of implementing behavior of the terminal device in the method in the first aspect. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or the software includes one or more modules corresponding to the foregoing function.

The structure of the terminal device includes a charging module and a sensitive module component. The charging module and the sensitive module component are configured to support the terminal device in performing a corresponding function in the method in the first aspect.

In the following, some terms of the embodiments of this application are described, so as to help a person skilled in the art has a better understanding.

In a process in which a wireless charging device charges the terminal device, to ensure charging stability, charging power of the wireless charging device needs to be adjusted. For example, when being located at different locations on the wireless charging device, the terminal device requires different charging powers. In an example, when a center location of the terminal device coincides with that of the wireless charging device, relatively small charging power can meet a charging requirement of the terminal device. When the center location of the terminal device deviates from that of the wireless charging device, only relatively high charging power can meet a charging requirement of the terminal device. In addition, the terminal device requires different charging powers in different charging phases. In an example, when a battery level of the terminal device is relatively low, for example, the battery level remains at <NUM>%, only relatively high charging power can meet a charging requirement of the terminal device. When the battery level of the terminal device is relatively high, for example, the battery level remains at <NUM>%, relatively low charging power can meet a charging requirement of the terminal device. The following provides current main wireless charging solutions and a manner of adjusting charging power in each wireless charging solution.

In this wireless charging solution, an operating frequency of the wireless charging device is not fixed, in other words, the operating frequency of the wireless charging device changes within a frequency band. For example, a frequency F1 in the frequency band is used for charging in first <NUM> minutes during charging, a frequency F2 in the frequency band is used for charging in next <NUM> minutes during charging, and a frequency F3 in the frequency band is used for charging in last <NUM> minutes during charging. <FIG> is a schematic diagram of frequency domain when a wireless charging device using the frequency sweeping wireless charging solution operates. In the wireless charging solution, a charging module of the wireless charging device can adjust the operating frequency of the wireless charging device, so as to adjust the charging power of the wireless charging device.

Both the wireless charging solution <NUM> and the wireless charging solution <NUM> have advantages and disadvantages. For example, in the wireless charging solution <NUM>, the operating frequency of the wireless charging device remains stable, so that interference to a module component in the terminal device can be avoided. However, because the transformer is added, manufacturing costs of the wireless charging device and a size of the wireless charging device are increased. In the wireless charging solution <NUM>, no transformer is used, so that the manufacturing costs of the wireless charging device and the size of the wireless charging device are reduced. However, because the operating frequency of the wireless charging device changes within the frequency band, when an operating frequency or a frequency multiplication of the module component in the terminal device coincides with or approaches at least one frequency in the frequency band, the module component is easily interfered with.

Technical solutions provided in this application may be applied to a wired charging scenario or a wireless charging scenario, and are preferably applied to the wireless charging scenario.

<FIG> is a system architecture diagram of a charging system according to an embodiment of this application. In <FIG>, a terminal device <NUM> and a charging device <NUM> are included.

The charging device <NUM> may be a wired charging device, or may be a wireless charging device. In <FIG>, the terminal device <NUM> and the charging device <NUM> are connected through a dashed line, indicating that the terminal device <NUM> and the charging device <NUM> are connected in a wireless manner. In <FIG>, the terminal device <NUM> and the charging device <NUM> may be alternatively connected by using a solid line (not shown in the figure), indicating that the terminal device <NUM> and the charging device <NUM> are connected in a wired manner.

Herein, that the charging device <NUM> is a wireless charging device is used as an example. The wireless charging device charges the terminal device <NUM> only when determining that the terminal device <NUM> is already in a wireless charging area of the wireless charging device and identity identification succeeds. Herein, the wireless charging device may specifically determine, by using a sensor or a wireless communications module configured in the wireless charging device, whether the terminal device <NUM> is located in the wireless charging area. For example, an infrared sensor is used to detect whether the terminal device <NUM> is placed in the wireless charging area. Alternatively, a distance between an ultrasonic transmitter and a receive end is compared by using an ultrasonic sensor, to determine whether the terminal device <NUM> is placed in the wireless charging area. A process in which the wireless charging device performs identity identification may be as follows: When detecting that the terminal device <NUM> is already in the wireless charging area, the wireless charging device sends, to the terminal device <NUM>, an instruction for requesting an identification number. After receiving and parsing the instruction, the terminal device <NUM> sends a feedback instruction to the wireless charging device. The wireless charging device receives and parses the feedback instruction. If an identification number carried in the feedback instruction is the same as an identification number stored in the wireless charging device, it indicates that an identity of the terminal device <NUM> is authorized.

The terminal device <NUM> includes a sensitive module component <NUM> and a charging module <NUM>. Certainly, the terminal device <NUM> may further include another component or module. Examples are not given one by one herein. The charging module <NUM> may actively or passively obtain related information of the sensitive module component <NUM>, the related information being a working status of the sensitive module component <NUM>. The wireless charging device may actively or passively obtain the related information of the sensitive module component <NUM> from the charging module <NUM>, and charge the terminal device <NUM> based on the obtained related information. In an example, during the passive obtaining, the charging module <NUM> sends an instruction to the wireless charging device in a wireless manner, where the instruction carries the related information of the sensitive module component <NUM>. During the active obtaining, the wireless charging device sends, to the charging module <NUM> in a wireless manner, an instruction for requesting the related information. There may be an electrical connection or no electrical connection between the charging module <NUM> and the sensitive module component <NUM>. The related information is transmitted between the charging module <NUM> and the sensitive module component <NUM> by using a node file. This is described in detail in the following, and details are not described herein. A wireless communication manner of the charging module <NUM> and the wireless charging device may be wireless-fidelity (Wireless-Fidelity, Wi-Fi), Bluetooth (Bluetooth), zigbee (Zigbee), a long range (Long Range, Lora) wireless technology, near field communication (Near Field Communication, NFC), amplitude shift keying (Amplitude Shift Keying, ASK), frequency shift keying (Frequency Shift Keying, FSK), or the like.

The following describes the technical solutions in the embodiments of this application in detail with reference to the accompanying drawings in this specification and specific implementations. In the following descriptions, an example in which the technical solutions provided in the embodiments of this application are applied to an application scenario shown in <FIG> is used. An example in which the charging device <NUM> included in the application scenario is a wireless charging device is used.

Referring to <FIG>, only S401 is included in the charging method of claim <NUM>. The charging method is applied to the terminal device <NUM>. The terminal device <NUM> includes the sensitive module component <NUM> and the charging module <NUM>. A process of the method is mainly described as follows:.

S401: The charging module <NUM> obtains a working status of the sensitive module component <NUM>.

The sensitive module component <NUM> is a module component that is interfered with in a process in which the wireless charging device charges the terminal device <NUM> at a sensitive frequency. The sensitive frequency is within a range of a wireless charging frequency band. A Qi standard is used as an example herein. The wireless charging frequency band may be a frequency band f<NUM>KHz-f<NUM>KHz at <NUM> to <NUM>. The sensitive frequency may be one or more frequencies in f<NUM>KHz-f<NUM>KHz, or may be one or more frequency bands in f<NUM>KHz-f<NUM>KHz.

The sensitive module component <NUM> may be an LCD, a TP, a camera module, a fingerprint module, an NFC, an audio module, a radio frequency module, or the like. The following uses an example in which the sensitive module component <NUM> is the camera module, to describe frequencies or frequency bands at which noise interference causes the camera module to be abnormal. <FIG> is a waveform diagram of anti-interference of a camera module. A horizontal axis represents frequency (KHz), and a vertical axis represents voltage (millivolt (mV)), which may be understood as noise. When a noise level is <NUM> mV, intersection points of the straight line whose V=<NUM> mV and the waveform diagram are at troughs of the waveform diagram, and frequencies corresponding to the intersection points are f<NUM> and f<NUM>. This indicates that the camera module becomes abnormal at the frequencies f<NUM> and f<NUM> when the noise level is <NUM> mV, and the camera module does not become abnormal at other frequencies when the noise level is <NUM> mV. When a noise level is <NUM> mV, frequencies corresponding to intersection points of a straight line whose V=<NUM> mV and the waveform diagram are f<NUM>, f<NUM>, f<NUM>, and f<NUM>. This indicates that the camera module becomes abnormal in frequency bands f<NUM>-f<NUM> and f<NUM>-f<NUM> when the noise level is <NUM> mV, and the camera module does not become abnormal at other frequencies when the noise level is <NUM> mV.

The working status of the sensitive module component <NUM> includes an enabled state and a disabled state. The enabled state means that the sensitive module component <NUM> is in a running state, and the disabled state means that the sensitive module component <NUM> is in a non-running state. When the working status of the sensitive module component <NUM> is the enabled state, an enabling moment of the sensitive module component <NUM> may be in a process in which the wireless charging device charges the terminal device <NUM>, or may be before the wireless charging device charges the terminal device <NUM>.

According to the invention, the sensitive module component <NUM> sends the working status to the charging module <NUM> in the following manner <NUM>. Manner <NUM> is provided as another example, but is not used in the invention to send the working status.

Manner <NUM>: The sensitive module component <NUM> directly sends the working status of the sensitive module component <NUM> to the charging module <NUM>.

In Manner <NUM>, there may be an electrical connection between the sensitive module component <NUM> and the charging module <NUM>. For example, an inter-integrated circuit (Inter-Integrated Circuit, I2C) bus interface on the sensitive module component <NUM> is connected to an I2C interface on the charging module <NUM> through an I2C bus. In this way, when the wireless charging device charges the terminal device <NUM>, the sensitive module component <NUM> sends the working status to the charging module <NUM> through the I2C bus. In a specific implementation process, the sensitive module component <NUM> sends an indication instruction to the charging module <NUM> through the I2C bus. The indication instruction may be used to indicate the working status of the sensitive module component <NUM>. For example, the sensitive module component <NUM> sends an indication instruction <NUM> to the charging module <NUM> through the I2C bus, where the indication instruction <NUM> may be used to indicate that the working status of the sensitive module component <NUM> is the enabled state. Alternatively, the sensitive module component <NUM> sends an indication instruction <NUM> to the charging module <NUM> through the I2C bus, where the indication instruction <NUM> may be used to indicate that the working status of the sensitive module component <NUM> is the disabled state.

It should be noted that the charging module <NUM> may actively obtain the working status of the sensitive module component <NUM> from the sensitive module component <NUM>. For example, when the wireless charging device charges the terminal device <NUM>, the charging module <NUM> sends, to the sensitive module component <NUM> through the I2C bus, an instruction for requesting to obtain the working status of the sensitive module component <NUM>. After receiving the instruction, the sensitive module component <NUM> sends the working status to the charging module <NUM> through the I2C bus.

Manner <NUM>: The charging module <NUM> obtains the working status of the sensitive module component <NUM> by using a node file.

In Manner <NUM>, there may be an electrical connection or no electrical connection between the sensitive module component <NUM> and the charging module <NUM>. In a specific implementation process, the charging module <NUM> may provide the node file. The node file may be understood as storage space provided by the charging module <NUM>. The storage space may be storage space in the charging module <NUM>, or may be storage space applied for by the charging module <NUM> to a memory (not shown in the figure) of the terminal device <NUM>. The storage space may be divided into a plurality of storage subspaces. Each storage subspace corresponds to one storage address. Each storage address corresponds to one sensitive module component <NUM>, and is used by the sensitive module component <NUM> to write information.

In the embodiments of this application, a quantity of sensitive module components <NUM> is not limited. There may be one or more sensitive module components <NUM>. When there are a plurality of sensitive module components <NUM>, there may be one or more sensitive module components <NUM> in an enabled state. In an example, the sensitive module components <NUM> include a sensitive module component A, a sensitive module component B,. , and a sensitive module component N. When the sensitive module component A and the sensitive module component B are in the enabled state, the sensitive module component A and the sensitive module component B write working statuses into the node file. The sensitive module component A writes, into corresponding storage subspace based on a storage address, 0x01 used to represent the sensitive module component A and 0xFE used to represent the working status of the sensitive module component A. The sensitive module component B writes, into corresponding storage subspace based on a storage address, 0x02 used to represent the sensitive module component B and 0xFD used to represent the working status of the sensitive module component B.

For the charging module <NUM>, the charging module <NUM> may read content in the node file at a specific period, to determine whether new information is written into the node file, so as to parse the content stored in the node file. Specifically, the charging module <NUM> parses 0x01 to obtain the A, and parses 0xFE to obtain that the working status of the sensitive module component A is the enabled state. The charging module <NUM> parses 0x02 to obtain the B, and parses 0xFD to obtain that the working status of the sensitive module component B is the enabled state. After completing parsing, the charging module <NUM> may send information obtained through parsing to the wireless charging device, or may store information obtained through parsing in storage space. In an example, the enabled state of the A that is obtained through parsing is stored in a high bit (bit), and the enabled state of the B that is obtained through parsing is stored in a bit following the high bit. The enabled state may be represented by <NUM>, and the disabled state may be represented by <NUM>.

When the charging module <NUM> receives the working status sent by the sensitive module component <NUM>, the sensitive module component <NUM> may write the working status into the node file at a specific period. Alternatively, when the working status of the sensitive module component <NUM> changes, the sensitive module component <NUM> writes the working status into the node file. For example, when the working status of the sensitive module component <NUM> is adjusted from the enabled state to the disabled state, the sensitive module component <NUM> writes, to the node file, the current working status which is the disabled state. Alternatively, when the working status of the sensitive module component <NUM> is adjusted from the disabled state to the enabled state, the sensitive module component <NUM> writes, to the node file, the current working status which is the enabled state.

S402: The charging module <NUM> sends the working status of the sensitive module component <NUM> to the wireless charging device.

It should be noted that the wireless charging device may actively obtain the working status from the charging module <NUM>. For example, the wireless charging device sends, to the charging module <NUM> in a wireless manner, an instruction for requesting to obtain the working status of the sensitive module component <NUM>. After receiving the instruction, the charging module <NUM> may send the working status to the wireless charging device in a wireless manner.

The charging module <NUM> may directly transmit the working status to the wireless charging device in a wireless manner. Alternatively, the charging module <NUM> may send the working status to the wireless charging device in a wireless manner only when determining that the wireless charging device charges the terminal device <NUM>. In this way, when the wireless charging device does not charge the terminal device <NUM>, the charging module <NUM> is prevented from sending the working status to the wireless charging device. This reduces power consumption of the terminal device <NUM>.

Based on the foregoing descriptions of step S401 and step S402, when the working status of the sensitive module component <NUM> is transferred between the sensitive module component <NUM> and the charging module <NUM> in Manner <NUM>, which is not covered by the appended claims, for a communication process of the sensitive module component <NUM>, the charging module <NUM>, and the wireless charging device, refer to <FIG>. When the working status of the sensitive module component <NUM> is transferred between the sensitive module component <NUM> and the charging module <NUM> by using the node file in Manner <NUM>, for a communication process of the sensitive module component <NUM>, the charging module <NUM>, and the wireless charging device, refer to <FIG>.

S403: When the working status of the sensitive module component <NUM> is the enabled state, the wireless charging device charges the terminal device <NUM> by using a safe charging parameter, where in a process in which the wireless charging device charges the terminal device <NUM> by using the safe charging parameter, the sensitive module component <NUM> operates normally.

It should be noted that the safe charging parameter includes at least one of a safe charging frequency, a safe charging voltage, or a safe charging current. The safe charging frequency is a frequency that does not cause interference to the sensitive module component <NUM> in the process in which the wireless charging device charges the terminal device <NUM>. The safe charging voltage is a charging voltage that does not cause interference to the sensitive module component <NUM> in the process in which the wireless charging device charges the terminal device <NUM>. The safe charging current is a charging current that does not cause interference to the sensitive <NUM> in the process in which the wireless charging device charges the terminal device <NUM>.

That the sensitive module component <NUM> can operate normally means that after the sensitive module component <NUM> is enabled, a related function of the sensitive module component <NUM> can be implemented, and no abnormality occurs. For example, the sensitive module component <NUM> is a TP. When the TP is in an enabled state, the TP does not encounter an abnormal state in which touch sensitivity decreases. If the sensitive module component <NUM> is an LCD, when the LCD is in an enabled state, an abnormal state such as a color stripe or a ripple does not appear on the LCD. If the sensitive module component <NUM> is a fingerprint module component, when the fingerprint module component is in an enabled state, the fingerprint module component does not encounter an abnormal state in which fingerprint recognition sensitivity decreases. If the sensitive module component <NUM> is an NFC, when the NFC is in an enabled state, an abnormal state of communication interruption does not occur in the NFC. If the sensitive module component <NUM> is a camera module, when the camera module is in an enabled state, an abnormal state such as a color stripe or a ripple does not occur in a preview mode of a camera or a photographed picture.

According to the invention, the safe charging parameter is obtained by the charging device from the terminal device <NUM>. In another example, not covered by the claims, it is determined by the wireless charging device. The following provides separate description, when using the wireless charging device.

The sensitive module component <NUM> may be classified into two types of sensitive module components: an operating frequency that can be obtained and an operating frequency that cannot be obtained. The operating frequency that can be obtained means that the sensitive module component <NUM> can obtain an operating frequency of the sensitive module component <NUM>. The operating frequency that cannot be obtained means that the sensitive module component <NUM> cannot obtain an operating frequency of the sensitive module component <NUM>. The following separately describes processes in which the charging module <NUM> in the two types determines the safe charging parameter and sends the safe charging parameter to the wireless charging device when the sensitive module component <NUM> is in an enabled state.

In an example, the sensitive module component <NUM> learns of the operating frequency (that is, the sensitive frequency) of the sensitive module component <NUM>, and sends the operating frequency of the sensitive module component <NUM> to the charging module <NUM> in Manner <NUM> or Manner <NUM>. The charging module <NUM> obtains the safe charging frequency based on the operating frequency. Herein, a process in which the charging module <NUM> obtains the safe charging frequency based on the operating frequency may be that the charging module <NUM> selects a frequency other than the operating frequency from the wireless charging frequency band as the safe charging frequency. The foregoing example continues to be used. It is assumed that the wireless charging frequency band is f<NUM>KHz-f<NUM>KHz, and the operating frequency is a single frequency fm kHz. In a specific implementation process, the wireless charging device selects another frequency other than the operating frequency fm from f<NUM>KHz-f<NUM>KHz as the safe charging frequency. For example, the determined safe charging frequency may be [f<NUM>, fm), (fm, f<NUM>], or [f<NUM>, fm)-f<NUM>], or may be a single frequency other than fm in the frequency band f<NUM>KHz-f<NUM>KHz. In an example, if f<NUM>=<NUM>, f<NUM>=<NUM>, and fm=<NUM>, the determined safe charging frequency may be [<NUM>, <NUM>), (<NUM>, <NUM>], [<NUM>, <NUM>) -(<NUM>, <NUM>], <NUM>, <NUM>, or <NUM>.

The charging module <NUM> then obtains the safe charging voltage and/or the safe charging current based on a pre-stored first correspondence, that is, based on a pre-stored correspondence between the sensitive module component and the safe charging voltage and/or the safe charging current. Refer to Table <NUM>, this table stores a safe charging voltage and/or a safe charging current of the charging device <NUM> when each sensitive module component <NUM> is in an enabled state.

In a specific implementation process, different safe charging parameters may be preset for different sensitive module components <NUM> based on an actual requirement. For example, the safe charging voltage is preset for the TP, the safe charging current is preset for the LCD, and the safe charging voltage and the safe charging current are preset for the NFC.

It should be noted herein that the safe charging voltage and/or the safe charging current of the sensitive module component <NUM> may be alternatively obtained by the charging module <NUM> from the sensitive module component <NUM>.

In another example, the sensitive module component <NUM> may alternatively obtain, based on a pre-stored correspondence between the sensitive module component and a safe charging frequency, a safe charging voltage, and/or a safe charging current, a safe charging frequency, a safe charging voltage, and/or a safe charging current corresponding to the sensitive module component <NUM>.

(<NUM>) The sensitive module component <NUM> is a sensitive module component whose operating frequency cannot be obtained, for example, a camera module.

In an example, the charging module <NUM> needs to obtain the safe charging frequency, the safe charging voltage, and/or the safe charging current based on a pre-stored second correspondence, that is, a pre-stored correspondence between the sensitive module component and a safe charging frequency, a safe charging voltage, and/or a safe charging current. Refer to Table <NUM>, this table stores a safe charging frequency, a safe charging voltage, and/or a safe charging current of the charging device <NUM> when each sensitive module component <NUM> is in an enabled state.

In a specific implementation process, the camera module has a relatively large quantity of sensitive frequencies and is also relatively sensitive to a noise. Consequently, all of the safe charging frequency, the safe charging voltage, and the safe charging current usually need to be set, or both the safe charging frequency and the safe charging voltage need to be set, or both the safe charging frequency and the safe charging current need to be set. In this example, the correspondence between the sensitive module component and the safe charging parameter may be stored in the charging module <NUM> in a form of a table or in a form of a file.

In another example, the charging module <NUM> needs to obtain, based on a pre-stored correspondence between the sensitive module component and a sensitive frequency, a safe charging voltage, and/or a safe charging current, a sensitive frequency, a safe charging voltage, and/or a safe charging current corresponding to the sensitive module component <NUM>. Then, the charging module <NUM> determines the safe charging frequency based on the sensitive frequency of the sensitive module component <NUM> in an enabled state.

It should be noted herein that the safe charging frequency/sensitive frequency, the safe charging voltage, and/or the safe charging current may be alternatively obtained by the charging module <NUM> from the sensitive module component <NUM>.

In a specific implementation process, a correspondence between a plurality of sensitive module components and a safe charging voltage and/or a safe charging current may be further pre-stored in Table <NUM>. A correspondence between a plurality of sensitive module components and a safe charging frequency, a safe charging voltage, and/or a safe charging current may be further pre-stored in Table <NUM>. In an example that the correspondence between a plurality of sensitive module components and a safe charging frequency, a safe charging voltage, and/or a safe charging current is pre-stored in Table <NUM>, before pre-storage, the charging module <NUM> needs to first determine a safe charging frequency, a safe charging voltage, and/or a safe charging current of a plurality of sensitive module components <NUM>.

A safe operating frequency of the plurality of sensitive module components <NUM> may be an intermediate frequency of safe charging frequencies of the plurality of sensitive module components <NUM>. The intermediate frequency herein may be understood as an intermediate value of the safe charging frequencies of the plurality of sensitive module components <NUM>. When the wireless charging device charges the terminal device <NUM> at an operating frequency corresponding to the intermediate value, the wireless charging device still causes interference to the plurality of sensitive module components, but the interference is within an acceptable range. The foregoing example continues to be used. The wireless charging frequency band is f<NUM>KHz-f<NUM>KHz, the sensitive module components <NUM> are the sensitive module component A and the sensitive module component B. When a safe charging frequency of the sensitive module component A is fmA, and a safe charging frequency of the sensitive module component B is fmB, the safe charging frequency of the sensitive module component A and the sensitive module component B may be an intermediate frequency fz of fmA and fmB. In an example, when fmA=<NUM>KHz and fmB=<NUM>KHz, fz=<NUM>KHz. In this case, the safe charging frequency of the sensitive module component A and the sensitive module component B is <NUM>.

The safe charging current of the plurality of sensitive module components <NUM> is determined.

The safe charging current of the plurality of sensitive module components <NUM> may be a minimum charging current in safe charging currents of the plurality of sensitive module components <NUM>. The foregoing example continues to be used. The sensitive module components <NUM> are the sensitive module component A and the sensitive module component B. When a safe charging current of the sensitive module component A is <NUM> A, and a safe charging current of the sensitive module component B is <NUM> A, a minimum charging current in <NUM> A and <NUM> A is used as the safe charging current of the sensitive module component A and the sensitive module component B.

The safe charging voltage of the plurality of sensitive module components <NUM> is determined.

The safe charging voltage of the plurality of sensitive module components <NUM> may be a minimum charging voltage in safe charging voltages of the plurality of sensitive module components <NUM>. The foregoing example continues to be used. The sensitive module components <NUM> are the sensitive module component A and the sensitive module component B. When a safe charging voltage of the sensitive module component A is <NUM> V, and a safe charging voltage of the sensitive module component B is <NUM> V, a minimum charging voltage in <NUM> V and <NUM> V is used as the safe charging voltage of the sensitive module component A and the sensitive module component B.

The safe charging frequency and the safe charging voltage of the plurality of sensitive module components <NUM> are determined. For this process, refer to determining processes in A and C.

The safe charging frequency and the safe charging current of the plurality of sensitive module components <NUM> are determined. For this process, refer to determining processes in A and B.

The safe charging voltage and the safe charging current of the plurality of sensitive module components <NUM> are determined. For this process, refer to determining processes in B and C.

The safe charging frequency, the safe charging current, and the safe charging voltage of the plurality of sensitive module components <NUM> are determined. For this process, refer to determining processes in A, B, and C. Details are not described.

After the charging module <NUM> determines the safe charging frequency, the safe charging voltage, and/or the safe charging current of the sensitive module component <NUM>, the charging module <NUM> sends the obtained safe charging frequency, the obtained safe charging voltage, and/or the obtained safe charging current of the sensitive module component to the wireless charging device. The parameters may be sent one by one, or a plurality of parameters may be sent together. This is not specifically limited in the embodiments of this application.

It should be noted herein that when there are a plurality of sensitive module components <NUM>, the charging module <NUM> further needs to obtain identification information of the sensitive module components <NUM> from the sensitive module components <NUM> in an active or passive manner. The identification information may be a digit, a letter, a combination of a digit and a letter, or a combination of a digit, a letter, and a character. The sensitive module component A and the sensitive module component B are still used as an example, identification information of the sensitive module component A may be represented as <NUM>, and identification information of the sensitive module component B may be represented as <NUM>. Herein, a process in which the charging module <NUM> obtains the identification information from the sensitive module components <NUM> in an active or passive manner is similar to a process in which the charging module <NUM> obtains the working status from the sensitive module component <NUM> in an active or passive manner.

It should be noted herein that when the correspondence between a plurality of sensitive module components and a safe charging voltage and/or a safe charging current is not pre-stored in Table <NUM>, and the correspondence between a plurality of sensitive module components and a safe charging frequency, a safe charging voltage, and/or a safe charging current is not pre-stored in Table <NUM>, the charging module <NUM> may alternatively search Table <NUM> and Table <NUM> for a respective safe charging parameter of the sensitive module components <NUM>, determine the safe charging parameter of the plurality of sensitive module components <NUM> based on the respective safe charging parameter, and finally send the safe charging parameter to the wireless charging device.

The safe charging parameter is determined by the wireless charging device. This way of determining the safe charging parameter is not covered by the appended claims.

Manners in which the wireless charging device determines the safe charging parameter include but are not limited to the following two manners. A first implementation is similar to a process in which the charging module <NUM> determines the safe charging parameter. In a second manner, the charging module <NUM> sends parameter information of the sensitive module component <NUM> that is preset by the charging module <NUM> or obtained from the sensitive module component <NUM> to the wireless charging device, and the wireless charging device determines the safe charging parameter. Details are described below.

When the sensitive module component <NUM> is in different types, there are also different processes in which the charging module <NUM> sends the parameter information to the wireless charging device. The following separately describes the processes.

In an example, the sensitive module component <NUM> learns of the operating frequency of the sensitive module component <NUM>, and sends the operating frequency of the sensitive module component <NUM> to the charging module <NUM>. Then, the charging module <NUM> obtains, based on a pre-stored correspondence between the sensitive module component and a safe charging voltage and/or a safe charging current, a safe charging voltage and/or a safe charging current corresponding to the sensitive module component <NUM>. The charging module <NUM> sends the operating frequency, the safe charging voltage, and/or the safe charging current of the sensitive module component <NUM> to the wireless charging device.

It should be noted that the safe charging voltage and/or the safe charging current may be alternatively obtained by the charging module <NUM> from the sensitive module component <NUM>.

In another example, the charging module <NUM> may alternatively obtain the safe charging frequency, a charging voltage of the terminal device <NUM>, and/or a charging current of the terminal device <NUM> based on a pre-stored correspondence between the sensitive module component and the safe charging frequency, the charging voltage of the terminal device <NUM>, and/or the charging current of the terminal device <NUM>. The charging module <NUM> sends the safe charging frequency, the charging voltage of the terminal device <NUM>, and/or the charging current of the terminal device <NUM> to the wireless charging device. The charging voltage of the terminal device <NUM> may be understood as a charging voltage that the sensitive module component <NUM> requires the terminal device <NUM> to meet in the process in which the wireless charging device charges the terminal device <NUM>. The charging current of the terminal device <NUM> may be understood as a charging current that the sensitive module component <NUM> requires the terminal device <NUM> to meet in the process in which the wireless charging device charges the terminal device <NUM>.

It should be noted that the safe charging frequency, the charging voltage of the terminal device <NUM>, and/or the charging current of the terminal device <NUM> may be alternatively obtained by the charging module <NUM> from the sensitive module component <NUM>.

In an example, the charging module <NUM> needs to obtain, based on a pre-stored correspondence between the sensitive module component and the sensitive frequency, a safe charging voltage, and/or a safe charging current, a sensitive frequency, a safe charging voltage, and/or a safe charging current corresponding to the sensitive module component <NUM>. The charging module <NUM> sends the sensitive frequency, the safe charging voltage, and/or the safe charging current to the wireless charging device.

It should be noted that the sensitive frequency, the safe charging voltage, and/or the safe charging current may be alternatively obtained by the charging module <NUM> from the sensitive module component <NUM>.

In another example, the sensitive module component needs to obtain, based on a pre-stored correspondence between the sensitive module component and the safe charging frequency, a charging voltage of the terminal device <NUM>, and/or a charging current of the terminal device <NUM>, a safe charging frequency corresponding to the sensitive module component <NUM>, the charging voltage of the terminal device <NUM> and/or the charging current of the terminal device <NUM>.

It should be noted that the safe charging frequency, the charging voltage of the terminal device <NUM>, and/or the charging current of the terminal device <NUM> may be obtained by the charging module <NUM> from the sensitive module component <NUM>.

Correspondingly, when the charging module <NUM> sends different requirements of charging parameters to the wireless charging device, there are different processes in which the wireless charging device determines the safe charging parameter. The following separately describes the processes.

Case <NUM>: The charging module <NUM> sends the sensitive frequency, the safe charging voltage, and/or the safe charging current to the wireless charging device.

The wireless charging device needs to determine the safe charging frequency based on the sensitive frequency of the sensitive module component <NUM>. A determining process herein is similar to a process in which the charging module <NUM> determines the safe charging frequency based on the operating frequency of the sensitive module component <NUM>.

If there are a plurality of sensitive module components <NUM> in an enabled state, the wireless charging device further needs to determine a safe charging parameter of the plurality of sensitive module components <NUM> in the enabled state. This process is similar to a process in which the charging module <NUM> determines the safe charging parameter of the plurality of sensitive module components <NUM>.

It should be noted herein that when there are the plurality of sensitive module components <NUM> in the enabled state, the wireless charging device may alternatively select, from the wireless charging frequency band, a frequency other than a sensitive frequency of the plurality of sensitive module components <NUM> in the enabled state as the safe charging frequency.

Case <NUM>: The charging module <NUM> sends the safe charging frequency, the charging voltage of the terminal device <NUM>, and/or the charging current of the terminal device <NUM> to the wireless charging device.

The wireless charging device needs to convert the charging voltage of the terminal device <NUM> into the safe charging voltage, so that charging power of the wireless charging device can meet a charging requirement of the terminal device <NUM>. For example, the charging voltage of the terminal device <NUM> is <NUM> V, and the wireless charging device needs to convert <NUM> V into <NUM> V. For a process in which the wireless charging device converts <NUM> V into <NUM> V, refer to a conversion process in which the charging voltage of the terminal device <NUM> is converted into a charging voltage of the wireless charging device in the prior art.

The wireless charging device needs to convert the charging current of the terminal device <NUM> into the safe charging current, so that charging power of the wireless charging device can meet a charging requirement of the terminal device <NUM>. For example, the second required charging current is <NUM> A, and the wireless charging device needs to convert <NUM> A into <NUM> A. For a conversion process in which the wireless charging device converts <NUM> A into <NUM> A, refer to a conversion process in which the charging current of the terminal device <NUM> is converted into a charging current of the wireless charging device in the prior art.

When there are a plurality of sensitive module components <NUM> in an enabled state, the wireless charging device needs to determine a safe charging parameter of the sensitive module components <NUM> in the enabled state. This process is similar to a process in which the charging module <NUM> determines the safe charging parameter of the plurality of sensitive module components <NUM>.

Certainly, in this embodiment of this application, the charging module <NUM> may alternatively send the sensitive frequency, the charging voltage of the terminal device <NUM>, and/or the charging current of the terminal device <NUM> to the wireless charging device. In this case, for a process in which the wireless charging device determines the safe charging parameter, refer to Case <NUM> and Case <NUM>.

After determining the safe charging parameter, the wireless charging device may charge the terminal device <NUM> by using the safe charging parameter.

It should be noted herein that the charging method provided above can also be applied to wired charging, and details are not described herein.

The following describes, with reference to the accompanying drawings, the apparatuses provided in this application, to implement the foregoing method embodiments of this application.

<FIG> is a schematic structural diagram of a charging device <NUM>, which is not covered by the appended claims. The charging device <NUM> may include an obtaining unit <NUM>, a determining unit <NUM>, and a charging unit <NUM>. The obtaining unit <NUM> may be configured to perform S402 in the method shown in <FIG>, and/or configured to support another process of the technology described in this application. The determining unit <NUM> and the charging unit <NUM> may be configured to perform S403 shown in <FIG>, and/or configured to support another process of the technology described in this application. All related content of the steps in the foregoing methods may be cited in function descriptions of the corresponding functional modules.

<FIG> is a schematic structural diagram of a charging device <NUM>, which is not covered by the appended claims. The charging device <NUM> may include a processor <NUM>, a communications interface <NUM>, and a memory <NUM>. The communications interface <NUM> and the memory <NUM> are coupled to the processor <NUM>. The processor <NUM> may be a central processing unit (central processing unit, CPU), or an application-specific integrated circuit (application-specific integrated circuit, ASIC), or may be one or more integrated circuits configured to control program execution, or may be a baseband chip, or the like. There may be one or more memories. The memory may be a read-only memory (read-only memory, ROM), a random access memory (random access memory, RAM), a magnetic disk memory, or the like.

By designing and programming the processor <NUM>, code corresponding to the foregoing charging method may be solidified into a chip, so that the chip can perform, when running, a function performed by the charging device in the charging method provided in the embodiment shown in <FIG>. How to design and program the processor <NUM> is a technology well known to a person skilled in the art.

<FIG> is a schematic structural diagram of a terminal device <NUM> according to an embodiment. The terminal device includes a charging module <NUM> and a sensitive module component <NUM>. The charging module <NUM> and the sensitive module component <NUM> are configured to perform S401 shown in <FIG>, and configured to support another process of the technology described in the embodiments of this application.

An embodiment of this application further provides a computer storage medium. The storage medium may include a memory. The memory may store a program. When the program is executed, all steps performed by the charging device <NUM> and the terminal device <NUM> recorded in the method embodiment shown in <FIG> are performed.

An embodiment of this application further provides a computer program product. When the program product is invoked and executed by a computer, the computer may be enabled to perform the method shown in <FIG>.

An embodiment of this application further provides a chip system. The chip system includes a processor, configured to support the charging device <NUM> and the terminal device <NUM> in implementing the method shown in <FIG>, for example, generating or processing data and/or information in the method provided in <FIG>. The chip system further includes a memory. The memory is configured to store a program instruction and data that are necessary for the charging device <NUM> and the terminal device <NUM>. The processor in the chip system may invoke the program instruction and the data stored in the memory in the chip system, so that the chip system can implement functions that can be implemented by the charging device and the terminal device. The chip system may include a chip, or may include a chip and another discrete device.

This application is described with reference to the flowcharts and/or block diagrams of the method, the device (system), and the computer program product according to the embodiments of this application. It should be understood that computer program instructions may be used to implement each process and/or each block in the flowcharts and/or the block diagrams and a combination of a process and/or a block in the flowcharts and/or the block diagrams. These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of any other programmable data processing device to generate a machine, so that the instructions executed by a computer or a processor of any other programmable data processing device generate an apparatus for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

Claim 1:
A charging method, applied to a terminal device, wherein the terminal device comprises a charging module and a sensitive module component, and the method comprises:
obtaining, by the sensitive module component, a working status of the sensitive module component;
sending, by the sensitive module component, the working status to the charging module, wherein the sensitive module component is a module component that is interfered with in a process in which a charging device charges the terminal device at a sensitive frequency, and the sensitive frequency is within a range of a charging frequency band of the charging device;
when the working status is an enabled state, determining, by the charging module, a safe charging parameter, wherein the safe charging parameter comprises at least one of a safe charging frequency, a safe charging current, and a safe charging voltage; and
sending, by the charging module, the safe charging parameter to the charging device, so that the charging device charges the terminal device by using the safe charging parameter, wherein in a process in which the charging device charges the terminal device by using the safe charging parameter, the sensitive module component operates normally;
wherein the sending, by the sensitive module component, the working status to the charging module comprises writing, by the sensitive module component, the working status into a node file, wherein the charging module obtains the working status from the node file.