Charging control method and device, electronic equipment and readable storage medium
By receiving and sending specific pulse signals, the instructing device supports the fused fast charging protocol, which solves the problem that the two-way charging device cannot establish a UFCS handshake, and realizes the fused fast charging handshake and efficient charging between devices.
Patent Information
- Application Number
- CN202411353008.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-26
- Publication Date
- 2025-01-03
AI Technical Summary
In the prior art, devices that support the two-way charging function cannot be charged based on the UFCS protocol, resulting in low charging efficiency and the inability to establish a fused fast charging handshake between devices.
By receiving and sending specific pulse signals, the instructing device to support the fused fast charging protocol, establish a fused fast charging handshake, and realize charging based on the UFCS protocol.
The integrated fast charging handshake between devices has been successfully established, which has improved charging efficiency and achieved fast, safe and compatible charging between devices with two-way charging functions.
Smart Images

Figure CN119253794A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of charging technology, and specifically relates to a charging control method, device, electronic device and readable storage medium. Background Art
[0002] With the popularity of mobile devices and the rapid development of fast charging technology, the incompatibility of fast charging protocols between different device manufacturers has become a major problem that troubles users. At present, in order to solve this problem, the Unified Fast Charging Standard (UFCS) came into being.
[0003] In the related technology, for two devices that support the UFCS protocol and have bidirectional charging functions, it is currently impossible to establish a UFCS integrated fast charging handshake, which makes it impossible to perform UFCS fast charging. Therefore, how to establish a UFCS integrated fast charging handshake between devices is a problem that needs to be solved urgently. Summary of the invention
[0004] The purpose of the embodiments of the present application is to provide a charging control method, device, electronic device and readable storage medium, which can successfully establish a UFCS-based integrated fast charging handshake between two electronic devices.
[0005] In a first aspect, an embodiment of the present application provides a charging control method, the method comprising: receiving a first pulse signal from a second device; the first pulse signal is used to indicate that the second device supports the converged fast charging protocol; when the first device supports the converged fast charging protocol, sending a second pulse signal or the first pulse signal to the second device; the second pulse signal is used to indicate that the first device supports the converged fast charging protocol.
[0006] In a second aspect, an embodiment of the present application provides a charging control method, the method comprising: sending a first pulse signal to a first device; the first pulse signal is used to indicate that the second device supports the integrated fast charging protocol; when the integrated fast charging handshake conditions are met, sending a integrated fast charging handshake request to the first device; wherein the integrated fast charging handshake conditions include any one of the following: the second device receives the first pulse signal sent by the first device; the second device receives the second pulse signal sent by the first device; the second pulse signal is used to indicate that the first device supports the integrated fast charging protocol.
[0007] In the third aspect, an embodiment of the present application provides a charging control device, which includes a receiving module and a sending module, wherein: the above-mentioned receiving module is used to receive a first pulse signal from a second device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; the above-mentioned sending module is used to send a second pulse signal or a first pulse signal to the second device when the first device supports the fusion fast charging protocol; the above-mentioned second pulse signal is used to indicate that the first device supports the fusion fast charging protocol.
[0008] In a fourth aspect, an embodiment of the present application provides a charging control device, which includes a sending module; the sending module is used to send a first pulse signal to a first device; the first pulse signal is used to indicate that the second device supports the integrated fast charging protocol; the sending module is also used to send a integrated fast charging handshake request to the first device when the integrated fast charging handshake conditions are met; wherein the integrated fast charging handshake conditions include any one of the following: the second device receives the first pulse signal sent by the first device; the second device receives the second pulse signal sent by the first device; the second pulse signal is used to indicate that the first device supports the integrated fast charging protocol.
[0009] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.
[0010] In a sixth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.
[0011] In the seventh aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect or the second aspect.
[0012] In an eighth aspect, an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the first aspect or the second aspect.
[0013] The embodiment of the present application provides a charging control method, in which a first device receives a first pulse signal from a second device, and the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol. When the first device supports the fusion fast charging protocol, a second pulse signal or the above-mentioned first pulse signal is sent to the second device, and the second pulse signal is used to indicate that the second device supports the fusion fast charging protocol. Through this method, after receiving the first pulse signal from the second device, the first device can send the second pulse signal to the second device, or send the received first pulse signal to the second device, to indicate that it also supports the fusion fast charging protocol, thereby establishing a fusion fast charging handshake based on the fusion fast charging protocol with the second device, and charging can be performed based on the fusion fast charging protocol after successfully establishing the fusion fast charging handshake. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 One of the flow charts of the charging control method provided in the embodiment of the present application;
[0015] Figure 2 One of the structural schematic diagrams of the first device provided in the embodiment of the present application;
[0016] Figure 3 A second structural diagram of a first communication device provided in an embodiment of the present application;
[0017] Figure 4 A schematic diagram of a signal path formed by D+ and D- signal lines provided in an embodiment of the present application;
[0018] Figure 5 The second flowchart of the charging control method provided in the embodiment of the present application;
[0019] Figure 6 A schematic diagram of a fused fast charge handshake detection waveform provided in an embodiment of the present application;
[0020] Figure 7 A third structural diagram of the second device provided in an embodiment of the present application;
[0021] Figure 8 The third flowchart of the charging control method provided in the embodiment of the present application;
[0022] Fig. 9 One of the structural schematic diagrams of the charging control device provided in the embodiment of the present application;
[0023] Fig.10 The second structural diagram of the charging control device provided in the embodiment of the present application;
[0024] Fig.11 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;
[0025] Fig.12 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0026] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0027] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0028] The terms "at least one (item)", "at least one of" and the like in the specification and claims of the present application refer to any one, any two or a combination of more than two of the objects included therein. For example, at least one (item) of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c" and "a, b and c", where a, b, and c can be single or multiple. Similarly, "at least two (items)" refers to two or more, and its meaning is similar to that of "at least one (item)".
[0029] The nouns and terms involved in the embodiments of the present application are explained below.
[0030] Converged Fast Charging Protocol: The Converged Fast Charging Protocol is the Universal Fast Charging Specification (UFCS). The Converged Fast Charging Protocol is a new generation of converged fast charging protocol jointly developed by multiple companies. The protocol aims to solve the problem of incompatibility between fast charging between mobile terminal devices and create a fast, safe and compatible charging environment for terminal users. The UFCS protocol defines a set of unified charging standards and protocol handshake mechanisms, so that mobile terminal devices of different brands and models can use the same charger to achieve fast charging.
[0031] Universal Serial Bus (USB): USB is a widely used serial communication protocol and standard for transmitting data and power between computers and external devices. The USB interface has the characteristics of plug-and-play and hot-swap, allowing users to connect or disconnect devices without turning off the computer power. The USB interface has gone through multiple versions of iterations, including USB 1.0, USB 2.0, USB 3.0, etc., and each version has improved in speed, power consumption and transmission capacity.
[0032] UFCS communication handshake: that is, the communication handshake during UFCS charging. The UFCS communication handshake is a key step to ensure that the charger and the powered device can correctly identify and start the fast charging process. This process is similar to a "dialogue" between the charger and the device, and a series of signal interactions are used to confirm the charging capabilities and protocol support of both parties. The following is the main process of the communication handshake during UFCS charging:
[0033] Voltage detection: First, the charger detects the output voltage to ensure it is within a safe charging range.
[0034] Handshake and feature detection: The charger and the powered device will perform handshake and feature detection to confirm whether both parties support the UFCS protocol and their respective charging capabilities. During this process, the charger and the powered device will send a series of signals to each other, including voltage, current and other parameter information.
[0035] Protocol switching: If the detection is successful, both parties will switch to UFCS protocol mode and start the fast charging process. In this process, the charger will dynamically adjust the output voltage and current according to the charging requirements of the powered device and the battery capacity to achieve the best charging effect.
[0036] At present, with the advancement of electronic equipment technology, the functions of electronic equipment are becoming more and more powerful, which also makes the standby time of electronic equipment shorter and shorter. When users pay more and more attention to the standby time, increasing the battery capacity is the first solution that mobile phone manufacturers think of. When battery manufacturers are unable to overcome battery technology, fast charging solutions came into being. Now each terminal manufacturer has proposed its own fast charging protocol, and the fast charging protocols of each terminal manufacturer are incompatible with each other. For example, the charger of manufacturer A cannot charge the mobile phone of manufacturer B at high power, which invisibly affects the fast charging experience of mobile phone consumers.
[0037] UFCS is a new generation of converged fast charging protocol completed by the joint efforts of multiple terminal, chip companies and industry partners. The protocol aims to formulate converged fast charging standards for mobile terminals, solve the incompatibility problem of interoperable fast charging, and create a fast, safe and compatible charging environment for terminal users.
[0038] At present, the UFCS protocol uses the original USB DP and DM data lines for communication, which is consistent with the traditional USB communication method, that is, it also uses differential signals to transmit data, where DM is the negative end of the signal (Data Minus), also known as D-, and DP is the positive end of the signal (Data Positive), also known as D+. This makes UFCS compatible with the USB interface and uses these two data lines for communication handshakes and charging negotiations. UFCS communication stipulates that DP on the power supply side is TX, DM is RX, and DP on the charging side is RX (receive) and DM is TX (transport). However, the current charging based on the UFCS protocol is only applicable to fast charging between the charger and the charging device. For two devices that support bidirectional charging function, such as two mobile power supplies, two terminal devices, or a mobile power supply and a terminal device, it is currently impossible to charge based on the UFCS function, but can only be charged based on the traditional USB protocol, resulting in low charging efficiency.
[0039] In the charging control method provided in the embodiment of the present application, the first device receives a first pulse signal from the second device, and the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol. When the first device supports the fusion fast charging protocol, the second device sends a second pulse signal or the above-mentioned first pulse signal to the second device, and the second pulse signal is used to indicate that the second device supports the fusion fast charging protocol. Through this method, after receiving the first pulse signal from the second device, the first device can send the second pulse signal to the second device, or send the received first pulse signal to the second device, to indicate that it also supports the fusion fast charging protocol, thereby establishing a fusion fast charging handshake based on the fusion fast charging protocol with the second device, and charging can be performed based on the fusion fast charging protocol after successfully establishing the fusion fast charging handshake.
[0040] The executor of the charging control method provided in the embodiment of the present application may be a charging control device, which may be an electronic device, or a functional module or functional entity in the electronic device.
[0041] The charging control method provided in the embodiment of the present application is described in detail below through specific embodiments and application scenarios in conjunction with the accompanying drawings.
[0042] Figure 1 A flow chart of a charging control method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the charging control method may include the following steps 201 and 202:
[0043] Step 201: A first device receives a first pulse signal from a second device.
[0044] Among them, the above-mentioned first pulse signal is used to indicate that the second device supports the fusion fast charging protocol.
[0045] In some embodiments of the present application, the first device and the second device may be devices having bidirectional charging capabilities or supporting bidirectional charging.
[0046] It should be noted that having bidirectional charging capability or supporting bidirectional charging means that it can both charge and discharge. That is, if a device can be used as a charging device for charging and as a power supply device to charge other devices, then this device is a device with bidirectional charging capability or supporting bidirectional charging.
[0047] In some embodiments of the present application, the first device and the second device may be dual role port (DRP) devices.
[0048] It should be noted that DRP is a port that can be used as both a DFP (Downstream Facing Port, i.e., a host port) and an UFP (Upstream Facing Port, i.e., a slave port), and can dynamically switch between the two. DRP devices can flexibly change their roles according to the roles and needs of connected devices, thereby providing a more flexible and convenient communication and charging experience.
[0049] In some embodiments of the present application, the first device and the second device support a fusion fast charging protocol.
[0050] It should be noted that the explanation of UFCS can be found in the above description and will not be repeated here.
[0051] In some embodiments of the present application, the first device may include any one of the following: a mobile power supply, an electronic device, a computer, etc.
[0052] In some embodiments of the present application, the second device may include any one of the following: a mobile power supply, an electronic device, a computer, etc.
[0053] In some embodiments of the present application, the above-mentioned electronic device may include a smart phone, a tablet computer, a laptop computer, a Bluetooth headset, etc.
[0054] In some embodiments of the present application, the first device may be a power supply device, that is, a power supply end.
[0055] In some embodiments of the present application, the second device may be a charging device, that is, a charging terminal.
[0056] It should be noted that after the first device and the second device are connected via a Type-C cable, it is possible to automatically identify which device is used as the power supply device and which device is used as the charging device.
[0057] Exemplarily, the first device is a mobile power supply, and the second device is a smart phone. The mobile power supply outputs electric energy to power the smart phone, and the smart phone receives electric energy from the mobile power supply and charges its battery.
[0058] As another example, the first device is a smartphone 1, and the second device is a smartphone 2. The smartphone 1 outputs electrical energy to power the smartphone 2, and the smartphone 2 receives electrical energy from the smartphone 1 and charges its battery.
[0059] As another example, the first device is a smart phone, and the second device is a mobile power supply. The smart phone outputs electrical energy to supply power to the mobile power supply, and the mobile power supply receives electrical energy from the smart phone and charges its battery.
[0060] In some embodiments of the present application, after the first device and the second device establish a connection via a USB, the first device and the second device can identify their own identities and the identities of the other end, that is, whether they serve as a power supply end or a charging end.
[0061] It should be noted that after two devices are connected via a USB (such as Type-c to Type-c) cable, the device can automatically identify itself as a power supply or a charging terminal through the Troggle function of type-c. Specifically, after two DRP devices are connected via a USB cable, each device sends high and low level pulses respectively, which are similar to square wave pulses, and then identifies the identities of both parties through pulses. For example, after device A is connected to device B, after sending a high level pulse to device B, it detects whether the pulse continues to be high level. If not, it means that device B sent a low level pulse to lower the level of the pulse sent by device A. Device A then believes that device B is a charging device and immediately configures itself as a power supply device. The same is true for device B.
[0062] In some embodiments of the present application, when the first device and the second device recognize their own identities or the identities of the other end, they can configure themselves as charging ends or power supply ends according to the user's selection operation.
[0063] Exemplarily, after the first device is connected to the second device via a USB cable, a prompt pop-up window is displayed, which may include a "power supply" option and a "charging" option. If the user selects the "power supply" option, the first device will configure it as a power supply end.
[0064] In some embodiments of the present application, the first device may receive a first pulse signal from the second device through a first signal receiving end.
[0065] In some embodiments of the present application, the first pulse signal may be a pulse signal of a preset sequence.
[0066] Exemplarily, the first pulse signal may be a "2828" pulse.
[0067] It should be noted that the "2828" pulse is a handshake pulse required by the UFCS standard protocol. The handshake pulse starts with an initial 2ms high level, followed by an 8ms low level, followed by another 2ms high level, and finally ends with a 2ms low level.
[0068] In some embodiments of the present application, the first signal receiving end may be a signal negative end DM of the first device, that is, D-.
[0069] In some embodiments of the present application, the second device may send a first pulse signal to the first device through a second signal sending end.
[0070] In some embodiments of the present application, the second signal sending end may be a signal negative end DM of the second device, that is, D-.
[0071] Step 202: When the first device supports the integrated fast charging protocol, the first device sends a second pulse signal or a first pulse signal to the second device, where the second pulse signal is used to indicate that the first device supports the integrated fast charging protocol.
[0072] In some possible implementations, after receiving the first pulse signal, the first device may actively send a second pulse signal to the second device to indicate through the second pulse signal that it supports the fusion fast charging protocol, so as to identify the capabilities of both parties.
[0073] In some embodiments of the present application, the second pulse signal may be a pulse signal of a preset type.
[0074] Exemplarily, the second pulse signal may be a “2828” pulse.
[0075] It should be noted that both the first pulse signal and the second pulse signal can be UFCS handshake pulses.
[0076] In some embodiments of the present application, the signal waveform of the second pulse signal may be the same as that of the first pulse signal, or different from that of the first pulse signal.
[0077] In one embodiment, the method further includes: upon receiving the converged fast charging handshake request sent by the second device, the first device establishes a converged fast charging connection with the second device.
[0078] In some embodiments of the present application, when the first device receives a converged fast charging handshake request sent by the second device, it can establish a converged fast charging handshake with the second device, and confirm the success of the handshake through a handshake message, and establish a converged fast charging connection between the first device and the second device. Furthermore, the first device can prepare to receive power supply from the second device, and the second device will start to output power according to the negotiated parameters to charge the first device.
[0079] In the charging control method provided in the embodiment of the present application, the first device receives a first pulse signal from the second device, and the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol. When the first device supports the fusion fast charging protocol, the second pulse signal or the above-mentioned first pulse signal is sent to the second device, and the second pulse signal is used to indicate that the second device supports the fusion fast charging protocol. When the first device receives the fusion fast charging handshake request sent by the second device, the first device establishes a fusion fast charging connection with the second device. Through this method, after receiving the first pulse signal from the second device, the first device can send the second pulse signal to the second device, or send the received first pulse signal to the second device, to indicate that it also supports the fusion fast charging protocol, thereby establishing a fusion fast charging handshake based on the fusion fast charging protocol with the second device, and charging can be performed based on the fusion fast charging protocol after successfully establishing the fusion fast charging handshake.
[0080] In some embodiments of the present application, the above step 201 can be implemented by the following step 201a, and the process of sending the second pulse signal to the second device in the above step 202 can be implemented by the following step 202a.
[0081] Step 201a: The first device receives a first pulse signal through a first signal receiving end of the first device.
[0082] Step 202a: The first device sends a second pulse signal to the second device through the first signal sending end of the first device.
[0083] In some embodiments of the present application, the first signal sending end may be a signal positive end DM, namely D+.
[0084] In some embodiments of the present application, the second device may receive the second pulse signal from the first device through the second signal receiving end.
[0085] In some embodiments of the present application, the second signal receiving end may be a signal positive end DP, ie, D+, of the second device.
[0086] For example, taking the first device as device A and the second device as device B, after device A and device B are connected through a Type-cTO Type-c USB cable, the devices first perform identity identification through the type-c specification. Assuming that the identification result is that device A is the power supply end and device B is the charging end, device B first initiates UFCS identification and sends a "2828" pulse to device A through D-. After device A receives the "2828" pulse through D-, it sends a new "2828" pulse (i.e., the second pulse signal) to device B through D+ to support its own support for UFCS.
[0087] In the related art, after two devices with bidirectional charging functions are connected through a cable, if one of the devices (such as a smart phone) is used as a power supply end (i.e., a power supply end device), the D+ / D- of the mobile phone are disconnected by default. After the device configured as the charging end (i.e., the charging end device) sends a handshake pulse to the power supply end device, the power supply end device cannot respond to the handshake pulse of the charging end device, so that the charging end device and the power supply end device cannot establish a communication handshake, thereby failing to complete the UFCS reverse charging.
[0088] In an embodiment of the present application, while the charging end device is sending a handshake pulse on D-, it simultaneously monitors whether a handshake pulse is sent on the D+ signal line; if the D- signal line fails to send a handshake pulse, but at this time a UFCS handshake pulse (i.e., a second pulse signal) is sent on the D+ signal line, the charging end device can learn from the UFCS handshake pulse that the power supply end device supports UFCS, and can initiate a UFCS handshake instruction, and then complete the UFCS communication handshake, thereby completing the UFCS reverse charging.
[0089] In some embodiments of the present application, the above step 201 can be implemented by the following step 201b, and the process of sending the first pulse signal to the second device in the above step 202 can be implemented by the following step 202b.
[0090] Step 201b: The first device receives a first pulse signal through a first signal receiving end of the first device.
[0091] There is a conduction control between the first signal receiving end and the first signal sending end of the first device.
[0092] Step 202b: When the conduction control of the first device is in an on state, the first device sends a first pulse signal to the second device through the first signal sending end.
[0093] In some other possible implementations, after receiving the first pulse signal, the first device may transmit the first pulse signal back to the second device to indicate that it supports UFCS by transmitting the first pulse signal back, so as to identify the capabilities of both parties.
[0094] It should be noted that the first pulse signal transmitted back by the first device to the second device has the same waveform as the first pulse signal sent by the second device to the first device, and the changes in timing are consistent.
[0095] It should be noted that the first device transmits the first pulse signal back to the second device in response to the received first pulse signal. In this process, the first device does not need to actively send a pulse signal, but transmits the first pulse signal to the second device through a conductive path.
[0096] like Figure 2 As shown, the first device may include a first signal transmitting end (TX) 301, a first signal receiving end (RX) 302 and a control unit 303. The first device may control the first signal receiving end 302 to receive a first pulse signal, and control the first signal transmitting end 301 to send a first pulse signal or a second pulse signal through the control unit 303.
[0097] In some embodiments of the present application, in combination with the above Figure 2 ,like Figure 3 As shown, a conduction control 304 is arranged between the first signal receiving end and the first signal sending end, the first end of the conduction control 304 is connected to the first signal sending end 301, and the second end of the conduction control 401 is connected to the first signal receiving end 302; the control unit 303 is also used to control the closing of the conduction control 304 to conduct the first signal sending end 301 and the first signal receiving end 302, so as to transmit the first pulse signal received by the first signal receiving end to the first signal sending end, and transmit the signal to the second signal receiving end of the second device through the first signal sending end.
[0098] like Figure 4 As shown, taking the first device as device A and the second device as device B as an example, device A and device B communicate through two signal paths formed by D+ and D- signal lines. A conduction control 51 is connected between D+ and D- of device A. The conduction control 51 is in an open state by default. After receiving the "2828" pulse from device B, device A controls the conduction control 51 to close to conduct D+ and D-.
[0099] It should be noted that the conduction control of the first device may be in an open state by default, and after receiving the first pulse signal of the second device, the first device controls the conduction control to close.
[0100] For example, taking the first device as device A, the second device as device B, and device A as the power supply end and device B as the charging end, after device A receives the "2828" handshake pulse from device B through D-, it connects D+ and D- by closing the built-in switch, and then transmits the "2828" handshake pulse back to D+ of device B through D+ to indicate that it supports UFCS.
[0101] In some embodiments of the present application, the first device may continuously detect the signal of the first signal receiving end. Once it is detected that the second device has sent a first pulse signal, the first device may disconnect the connection between the first signal receiving end and the first signal sending end, and switch the first signal receiving end and the first signal sending end to UFCS mode within a predetermined time. At this time, the UFCS protocol handshake detection is successful.
[0102] For example, taking the first device as power supply device A and the second device as charging device B, power supply device A continuously detects the D- signal. Once it detects that charging device B sends a predetermined sequence on D-, it disconnects D+ and D-, and switches the D+D- pins to UFCS mode within the tDataRoleSwicch time, and the protocol handshake detection is successful.
[0103] In some embodiments of the present application, before the first pulse signal is sent to the second device through the first signal sending end in the above step 202b, the charging control method provided in the embodiment of the present application may further include the following step 204:
[0104] Step 204: The first device controls the conduction control to be in an on state.
[0105] Exemplarily, after receiving the first pulse signal from the second device, the first device determines that the first device supports the fusion fast charging protocol, and controls the conduction control to turn on, so as to transmit the first pulse signal received by the first signal receiving end to the first signal sending end through the conduction control, thereby sending the first pulse signal to the second device through the first signal sending end.
[0106] In some embodiments of the present application, after the first pulse signal is sent to the second device through the first signal sending end in the above step 202b, the charging control method provided in the embodiment of the present application may further include the following step 205:
[0107] Step 205: The first device controls the conduction control to be in a closed state.
[0108] Exemplarily, after receiving the first pulse signal from the second device, if the first device determines that the first device supports the fusion fast charging protocol, the first device controls the conduction control to turn on, so as to transmit the first pulse signal received through the first signal receiving end to the first signal sending end through the conduction control, and after sending the first pulse signal to the second device through the first signal sending end, the conduction control is controlled to turn off to disconnect the connection between the first signal receiving end and the first signal sending end.
[0109] In some embodiments of the present application, the conduction control is an electronic switch control; illustratively, the step 204 can be implemented by the following step 204a.
[0110] Step 204a: The first device applies a first electrical signal to the control end of the electronic switch control to control the electronic switch control to close.
[0111] In some embodiments of the present application, the above-mentioned electronic switch controls include but are not limited to field effect tubes, transistors, thyristors, relays, and various special types of electronic switches.
[0112] Exemplarily, the electronic switch control may be a Metal-Oxide-Semiconductor Field-Effect Transistor (MOSFET).
[0113] In some embodiments of the present application, the first electrical signal may be an electrical signal of a high level or a specified voltage value.
[0114] Exemplarily, the first device may apply a first electrical signal of a high level (or a specified voltage value) to a control terminal of an electronic switch control (such as a MOSFET) through a controller to close the electronic switch control, thereby allowing current to pass through the electronic switch control. For example, a high level voltage is applied to the gate of the MOSFET as the first electrical signal to control the MOSFET to close, thereby realizing the on state of the conduction control.
[0115] In some embodiments of the present application, the above-mentioned conduction control is an electronic switch control; illustratively, the above-mentioned step 205 of controlling the conduction control to be in a closed state can be implemented by the following step 205a.
[0116] Step 205a: The first device applies a second electrical signal to the control end of the electronic switch control to control the electronic switch control to be disconnected.
[0117] It should be noted that the explanation of the electronic switch control can be found in the description of the above embodiments and will not be repeated here.
[0118] In some embodiments of the present application, the first electrical signal may be an electrical signal of a low level or a specified voltage value.
[0119] Exemplarily, the first device may apply a second electrical signal of a low level (or another specified voltage value) to the control terminal of the electronic switch control through the controller to disconnect the electronic switch control and cut off the current in the conduction control. For example, a low level voltage is applied to the gate of a MOSFET as the second electrical signal to control the MOSFET to be cut off, thereby realizing the closed state of the conduction control.
[0120] In some embodiments of the present application, after the above step 203, the charging control method provided in the embodiment of the present application may further include the following step 206:
[0121] Step 206: The first device charges the second device.
[0122] For example, after the first device establishes a fusion fast charging handshake with the second device, the first device (as a power supply device) can output power to the second device (as a powered device) according to the negotiated charging parameters. Furthermore, when the second device is fully charged or reaches the preset charging condition, the charging process ends.
[0123] In some embodiments of the present application, the charging control method provided in the embodiments of the present application may further include the following steps 207 and 208:
[0124] Step 207: The first device receives a first input when establishing a charging connection with the second device.
[0125] Step 208: The first device sends a second charging request to the second device in response to the first input; the second charging request is used to request the second device to charge the first device.
[0126] It should be noted that the above steps 207 and 208 may be performed after the above step 203 , or after the above step 201 .
[0127] In some embodiments of the present application, the second charging request may be a third pulse signal.
[0128] In an embodiment of the present application, the first input may be a key input or a touch input of a user to the first device. For example, the key input may be an input to a physical key, and the touch input may be an input to a window control.
[0129] Exemplarily, after the first device charges the second device, if the second device needs to charge the first device, the first input can be used to trigger the first device to send a third pulse signal to the second device. Then, the second device can send the same third pulse signal or fourth pulse signal to the first device, indicating that it agrees to charge the first device and charges the first device.
[0130] Figure 5 A flow chart of a charging control method provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the charging control method may include the following steps 301 and 302:
[0131] Step 301: The second device sends a first pulse signal to the first device; the first pulse signal is used to indicate that the second device supports the integrated fast charging protocol.
[0132] Step 302: When the converged fast charge handshake condition is met, the second device sends a converged fast charge handshake request to the first device.
[0133] The above-mentioned integrated fast charging handshake request is used to request to establish an integrated fast charging handshake with the first device.
[0134] Among them, the above-mentioned fusion fast charging handshake conditions include any of the following:
[0135] The second device receives the first pulse signal sent by the first device;
[0136] The second device receives a second pulse signal sent by the first device, where the second pulse signal is used to indicate that the second device supports the fusion fast charging protocol.
[0137] It should be noted that the explanation of the second device and the first pulse signal can be found in the description of the above embodiment and will not be repeated here.
[0138] In some embodiments of the present application, the above-mentioned fused fast charging handshake request may be a handshake instruction, such as a handshake ping.
[0139] In some embodiments of the present application, the second device may send a fusion fast charge handshake request to the first device after a preset delay if the fusion fast charge handshake condition is met. Exemplarily, the preset delay may be 100ms.
[0140] In some embodiments of the present application, the second device can send a first pulse signal to the first device through the negative terminal (D-) of the signal. At the same time, the second device detects whether the pulse signal at the positive terminal (D+) of the signal is consistent with the first pulse signal. If they are consistent, it indicates that the power supply device has successfully received and responded to the first pulse signal; or, the second device sends a first pulse signal to the first device through D-, and when a second pulse signal identical to the first pulse signal sent by the first device is detected on D+ within a certain period of time, it indicates that the first device has successfully received and responded to the first pulse signal, and then the second device can send a handshake instruction to the first device to establish a communication handshake with the first device.
[0141] It should be noted that the second device can determine whether the first pulse is detected on the D+ signal within a certain period of time, and this time can be set to 10 to 20 ms by default.
[0142] In some possible implementations, after the second device sends a first pulse signal to the first device through the second signal sending end, if the second signal receiving end detects the first pulse signal returned by the first device, a fusion fast charging handshake request is sent to the first device.
[0143] It should be noted that after the first pulse signal of the first device is transmitted back to the second device, the second device can detect a pulse signal at the second signal receiving end that is consistent with the first pulse signal and follows the changes of the first pulse signal in timing.
[0144] Exemplarily, in combination with the above example, device B first initiates UFCS identification and sends a "2828" pulse to device A through D-. After device A receives the "2828" handshake pulse from device B through D-, it connects D+ and D- by closing the built-in switch, and then transmits the "2828" handshake pulse back to D+ of device B through D+. After device B detects the "2828" handshake pulse on D+, it sends a handshake instruction to device A to establish a communication handshake with device A.
[0145] In some other possible implementations, after the second device sends a first pulse signal to the first device through the second signal sending end, if the second pulse signal sent by the first device is received through the second signal receiving end, a fusion fast charging handshake request is sent to the first device.
[0146] Exemplarily, in combination with the above example, device B first initiates the identification of UFCS and sends a "2828" pulse to device A through D-. After device A receives the "2828" pulse through D-, it sends a new "2828" pulse (i.e., the second pulse signal) to the D+ of device B through D+ to support its own support for UFCS. After device B detects the "2828" handshake pulse actively sent by device A on D+, it sends a handshake instruction to device A to establish a fused fast charging handshake with device A.
[0147] Figure 6 A schematic diagram of a UFCS fast charge handshake detection waveform provided in an embodiment of the present application, such as Figure 6 As shown, the charging device (i.e., the second device) sends a handshake pulse on D-, which starts with an initial high level, which lasts for tDet1, followed by a low level lasting for tDet2, followed by a high level lasting for tDet3, and then a low level lasting for tDet4. When the power supply device is in the DCP state, it continuously detects the D- signal. Once it detects that the charging device sends a predetermined sequence on D-, it disconnects D+D- and switches the D+D- pins to UFCS mode within tDataRoleSwitch time. The protocol handshake detection is successful. Next, after the charging device detects that D+ is pulled up to a high level within the set time window, it confirms that the protocol handshake detection is successful, switches the D+D- pins to UFCS mode within the tDataRoleSwitch time, and sends a ping message (i.e., a fused fast charging handshake request) to the power supply device within the tWaitping time. After the power supply device succeeds in the protocol handshake detection, if it receives a ping message from the charging device within the tWaitping time, the UFCS handshake is completed and UFCS charging begins.
[0148] In an embodiment of the present application, after the second device sends a first pulse signal to the first device, upon detecting the first pulse signal returned by the first device or receiving the second pulse signal sent by the first device, the second device sends a handshake instruction to the first device, thereby completing the establishment of a communication handshake based on UFCS charging with the second device, and performing UFCS-based fast charging after successfully establishing the communication handshake, thereby improving the charging efficiency.
[0149] In some embodiments of the present application, the second device receives the first pulse signal or the second pulse signal through the second signal receiving end.
[0150] In some embodiments of the present application, the second signal receiving end may be a signal positive end DP, ie, D+, of the second device.
[0151] In some embodiments of the present application, the above step 301 can be implemented by the following step 301a.
[0152] Step 301a: The second device sends a first pulse signal to the first device through the second signal sending end of the second device.
[0153] In some embodiments of the present application, the second signal sending end may be a signal negative end DM of the second device, that is, D-.
[0154] like Figure 7 As shown, the second device includes a second signal transmitting end (TX) 401 and a second signal receiving end (RX) 402; the second signal transmitting end 401 is used to send the above-mentioned first pulse signal to the first device, and the second signal transmitting end 401 is also used to send a fusion fast charging handshake request to the first device when the fusion fast charging handshake establishment conditions are met, and the second signal receiving end 402 is used to receive the first pulse signal or the second pulse signal from the first device.
[0155] It should be noted that the process of sending the first pulse signal to the first device through the negative signal terminal DM of the second device can refer to the description of the above embodiment, which will not be repeated here.
[0156] In some embodiments of the present application, after the above step 301, the charging control method provided in the embodiment of the present application may further include the following step 303:
[0157] Step 303: When the fusion fast charging handshake condition is not met, the first device sends the first pulse signal again.
[0158] In some embodiments of the present application, the first device may repeatedly send the first pulse signal to the second device for multiple times. For example, the first device continuously sends the first pulse signal to the second device 10 times.
[0159] In some embodiments of the present application, after sending a first pulse signal to the first device, the second device detects whether the first device returns the first pulse signal. If the first pulse signal returned by the first device is not detected, the second device repeatedly sends the first pulse signal to the second device; or if the first pulse signal returned by the first device is detected, a fused fast charging handshake request is sent to the second device.
[0160] It should be noted that if the second device detects the first pulse signal sent back by the first device, it means that the first device supports UFCS, indicating that the first device has met the fusion fast charging handshake conditions.
[0161] For example, taking the first device as device A and the second device as device B, after device B sends the "2828" handshake pulse at D-, it detects whether the D+ of device A follows the "2828" pulse. If the D+ of device A follows the "2828" pulse, B is set to perform a normal UFCS handshake operation. If the D+ of device A does not follow the "2828" pulse and remains at a low level, the "2828" pulse is repeatedly sent to device A.
[0162] In an embodiment of the present application, after the second device sends a first pulse signal to the first device, if the first pulse signal returned by the first device is not detected, the second device may repeatedly send the first pulse signal to the first device. On the one hand, this avoids the failure of communication handshake establishment caused by the first device not returning the first pulse signal to the second device when the first device fails to receive the first pulse signal due to signal interference or poor physical connection. On the other hand, by repeatedly sending the first pulse signal to the first device, the probability of the first device receiving the first pulse signal is increased, thereby effectively ensuring communication efficiency.
[0163] In some embodiments of the present application, after the above step 302, the charging control method provided in the embodiment of the present application may further include the following step 304:
[0164] Step 304: When receiving the second pulse signal or the first pulse signal sent by the first device, stop sending the first pulse signal and send a fusion fast charging handshake request to the first device.
[0165] In some embodiments of the present application, after the second device sends a first pulse signal to the first device, if it is not detected that the first device returns the first pulse signal or the first device actively sends a second pulse signal, the first pulse signal is repeatedly sent to the first device; if after repeatedly sending the first pulse signal, the second pulse signal sent by the first device is received, the first pulse signal is stopped and a fusion fast charging handshake request is sent to the first device.
[0166] It should be noted that after the first device repeatedly sends the first pulse signal, if the second device receives the second pulse signal sent by the first device, it means that the first device has responded to the handshake pulse of the second device and indicated that it also supports UFCS. At this time, it indicates that the first device meets the conditions for the integrated fast charging handshake.
[0167] Exemplarily, in combination with the above example, after device B repeatedly sends the "2828" pulse, it detects the D+ of device A at the same time. If device B detects that the "2828" pulse is sent on the D+ of device A, device B stops sending the "2828" pulse and sends the UFCS handshake pulse to device A after 100ms.
[0168] In an embodiment of the present application, when the second device sends a first pulse signal to the first device multiple times, it can simultaneously detect whether a second pulse signal from the first device is received, and when the second pulse signal is detected, stop sending the first pulse signal and establish a UFCS communication handshake with the first device, thereby effectively ensuring communication efficiency.
[0169] In some embodiments of the present application, after the above step 302, the charging control method provided in the embodiment of the present application may further include the following step 305:
[0170] Step 305: When the second device establishes a converged fast charging connection with the first device, the second device receives the charging current from the first device.
[0171] In some embodiments of the present application, the second device sends a converged fast charging handshake request to the first device. After the first device responds to the converged fast charging handshake request and completes the converged fast charging handshake, the first device and the second device establish a converged fast charging connection, and the two perform fast charging based on UFCS. During this process, the first device can output charging current to the second device according to the negotiated charging parameters, and the second device can receive the charging current from the first device, and use the electrical energy to charge its own battery or for other purposes.
[0172] Exemplarily, in combination with the above example, after device B sends the UFCS handshake instruction, it waits for the response of device A. After receiving the response of device A, device B establishes a handshake with device A and enters the UFCS fast charging protocol for fast charging.
[0173] Specifically, after the handshake is completed, the second device (i.e., the charging device) will send an instruction to the first device (i.e., the power supply device) to inquire about the power, software version, output voltage, output current and other information of the power supply device, and the power supply device will respond normally to the request instruction of the charging device; at this time, the charging device requests the power supply device to issue a voltage and current instruction that meets the requirements of the charging device based on its own power and other information; then the charging device inquires about the output voltage and current of the power supply device again, and the power supply device returns its own voltage and current, and then enters the normal charging stage. In this stage, the charging device continuously adjusts the voltage and current, and continuously inquires about the output voltage and output current of the power supply device until charging is completed. Finally, after charging is completed, the charging device will send an instruction to exit fast charging. After the power supply device receives the instruction to exit the protocol, the power supply device returns to the default voltage and current, and the communication signal line returns to the initial state.
[0174] In some embodiments of the present application, the charging control method provided in the embodiments of the present application may further include the following step 306:
[0175] Step 306: Upon receiving the second charging request sent by the first device, the second device charges the first device.
[0176] The second charging request is used to request the second device to charge the first device.
[0177] It should be noted that the explanation of the second charging request can be found in the description of the above embodiment and will not be repeated here.
[0178] In some embodiments of the present application, upon receiving the second charging request sent by the first device, the second device may send a charging response to the first device, where the charging response is used to indicate that the second device agrees to charge the first device.
[0179] Exemplarily, after receiving the charging request from the first device, the second device outputs current to the first device according to parameters such as the power, software version, output voltage, and output current of the power supply device of the first device.
[0180] It should be noted that the above step 306 can be performed after step 302 or before step 302 .
[0181] In some embodiments of the present application, before the above step 301, the charging control method provided in the embodiment of the present application may include the following step A1. Combined with the above step A1, the above step 301 may be implemented by the following step B1.
[0182] Step A1: The second device receives a second input.
[0183] Step B1: The second device sends a first pulse signal to the first device in response to the second input
[0184] In some embodiments of the present application, the second input may be a key input by a user or a touch input to a pop-up window control.
[0185] In some embodiments of the present application, the second input is used to trigger configuration of the second device as a charging device and send a first pulse signal to the first device.
[0186] For example, taking the first device as terminal 1 and the second device as terminal 2, after terminal 1 and the first terminal 2 are connected via a Type-C cable, terminal 2 displays a prompt pop-up window, which is used for the user to confirm whether terminal 2 needs to be charged through terminal 1. After the user clicks the "Confirm" button in the prompt pop-up window, terminal 2 configures itself as a charging device and sends a "2828" pulse signal to terminal 1, thereby initiating a fusion fast charging handshake process.
[0187] In the embodiment of the present application, the user can actively choose whether to use the device as a charging device and start the charging process, avoiding unnecessary charging operations, thereby improving the flexibility and autonomy of user operations.
[0188] The above-mentioned method embodiments, or various possible implementation methods in each method embodiment, can be executed separately, or, under the premise that there is no contradiction, can also be executed in combination with each other. The specific implementation can be determined according to actual usage requirements, and the embodiments of the present application do not limit this.
[0189] The charging control method provided in the embodiment of the present application is described below through specific examples.
[0190] Embodiment 1: Taking the first device as device A and the second device as device B as an example, the charging control method is described. Figure 8 As shown, the charging control method may include the following steps 21 to 28:
[0191] Step 21: Device A and Device B are connected.
[0192] Step 22: Distinguish device A as a power supply device and device B as a charging device.
[0193] Step 23: Device B sends a "2828" pulse.
[0194] Step 24: Determine whether the D+ of device A follows the "2828" pulse. If not, execute step 25; if so, execute step 26.
[0195] For example, device B sends a "2828" handshake pulse at D-, and detects whether the D+ of device A follows the "2828" pulse. If the D+ of device A follows the "2828" pulse, set B to perform normal UFCS handshake operation; if the D+ of device A does not follow the "2828" pulse and remains at a low level, perform the following steps 25:
[0196] Step 25: Determine whether D+ of device A sends 2828 pulses. If so, execute step 26; if not, execute step 27.
[0197] Step 26: Device B sends a UFCS handshake ping.
[0198] For example, after device B sends the UFCS handshake ping, device A responds normally to the handshake ping of device B, indicating that the UFCS detection is successful and the UFCS fast charging protocol is entered normally.
[0199] Step 27: Determine whether the number of times device B repeatedly sends the "2828" pulse is less than 6 times. If so, continue to execute the above step 23. If not, it indicates that the UFCS detection fails.
[0200] Embodiment 2: Taking the first device as device A and the second device as device B as an example, the charging control method is described. The charging control method may include the following steps 31 to 34:
[0201] Step 31: Device A is identified as a power supply device and device B is identified as a charging device.
[0202] Step 32: Device A connects the D+ / D- cables through the built-in switch.
[0203] Step 33: Device B sends a handshake pulse "2828" to enter normal UFCS handshake recognition.
[0204] Step 34: After UFCS handshake recognition is successful, enter normal UFCS fast charging.
[0205] The charging control method provided in the embodiment of the present application can solve the problem that the charging device defaults to D+ / D- disconnection and cannot perform UFCS fast charging recognition when performing UFCS fast charging based on a type-c to type-c cable, thereby enabling reverse charging based on UFCS between two devices with bidirectional charging functions and improving charging efficiency.
[0206] The charging control method provided in the embodiment of the present application can be executed by a charging control device. In the embodiment of the present application, the charging control device provided in the embodiment of the present application is described by taking the charging control method executed by the charging control device as an example.
[0207] Fig. 9 A schematic diagram of the structure of the charging control device provided in the embodiment of the present application is shown in FIG. Fig. 9 As shown, the charging control device 600 may include: a receiving module 601 and a sending module 602, wherein: the receiving module 601 is used to receive a first pulse signal from a second device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; the sending module 602 is used to send a second pulse signal or the first pulse signal to the second device when the first device supports the fusion fast charging protocol; the second pulse signal is used to indicate that the first device supports the fusion fast charging protocol.
[0208] In some embodiments of the present application, the charging control device may further include: a processing module, the processing module being configured to establish a converged fast charging connection with the second device upon receiving a converged fast charging handshake request sent by the second device.
[0209] In some embodiments of the present application, the above-mentioned receiving module is specifically used to receive the above-mentioned first pulse signal through the first signal receiving end of the above-mentioned first device; the above-mentioned sending module is specifically used to send the above-mentioned second pulse signal to the above-mentioned second device through the first signal sending end of the above-mentioned first device.
[0210] In some embodiments of the present application, the above-mentioned receiving module is specifically used to receive the above-mentioned first pulse signal through the first signal receiving end of the above-mentioned first device; there is a conduction control between the above-mentioned first signal receiving end and the first signal sending end of the above-mentioned first device; the above-mentioned sending module is specifically used to send the above-mentioned first pulse signal to the above-mentioned second device through the above-mentioned first signal sending end when the above-mentioned conduction control is in the on state.
[0211] In some embodiments of the present application, the processing module is further used to control the conduction control to be in an on state before sending the first pulse signal to the second device through the first signal sending end.
[0212] In some embodiments of the present application, the processing module is further used to control the conduction control to be in a closed state after sending the first pulse signal to the second device through the first signal sending end.
[0213] In some embodiments of the present application, the conduction control is an electronic switch control; the processing module is specifically used to apply a first electrical signal to the control end of the electronic switch control to control the electronic switch control to close;
[0214] In some embodiments of the present application, the above-mentioned conduction control is an electronic switch control; the above-mentioned processing module is specifically used to apply a second electrical signal to the control end of the above-mentioned electronic switch control to control the above-mentioned electronic switch control to be disconnected.
[0215] In some embodiments of the present application, the processing module is further used to charge the second device after establishing a fusion fast charging connection with the second device.
[0216] In some embodiments of the present application, the above-mentioned receiving module is also used to receive the first input when establishing a converged fast charging connection with the above-mentioned second device; the above-mentioned sending module is also used to send a second charging request to the above-mentioned second device in response to the above-mentioned first input received by the above-mentioned receiving module; the above-mentioned second charging request is used to request the above-mentioned second device to charge the above-mentioned first device.
[0217] The embodiment of the present application provides a charging control device, which receives a first pulse signal from a second device, and the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol. When the first device supports the fusion fast charging protocol, the second pulse signal or the first pulse signal is sent to the second device, and the second pulse signal is used to indicate that the second device supports the fusion fast charging protocol. In this way, after receiving the first pulse signal from the second device, the first device can send the second pulse signal to the second device, or send the received first pulse signal to the second device, to indicate that it also supports the fusion fast charging protocol, thereby establishing a fusion fast charging handshake based on the fusion fast charging protocol with the second device, and charging can be performed based on the fusion fast charging protocol after the fusion fast charging handshake is successfully established.
[0218] Fig.10 A schematic diagram of the structure of the charging control device provided in the embodiment of the present application is shown in FIG. Fig.10 As shown, the charging control device 700 may include a sending module 701, wherein the sending module is used to send a first pulse signal to the first device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; the sending module 701 is also used to send a fusion fast charging handshake request to the first device when the fusion fast charging handshake condition is met; wherein the fusion fast charging handshake condition includes any one of the following: the second device receives the first pulse signal sent by the first device; the second device receives the second pulse signal sent by the first device; the second pulse signal is used to indicate that the first device supports the fusion fast charging protocol.
[0219] In some embodiments of the present application, the sending module is specifically configured to send the first pulse signal to the first device via the second signal sending end of the second device.
[0220] In some embodiments of the present application, the second device receives the first pulse signal or the second pulse signal through a second signal receiving end.
[0221] In some embodiments of the present application, the sending module is further used to send the first pulse signal to the first device again after sending the first pulse signal to the first device if the fusion fast charging handshake condition is not met.
[0222] In some embodiments of the present application, the above-mentioned sending module is also used to, after sending the above-mentioned first pulse signal to the above-mentioned first device again when the above-mentioned integrated fast charging handshake condition is not met, stop sending the above-mentioned first pulse signal when receiving the above-mentioned second pulse signal or the above-mentioned first pulse signal sent by the above-mentioned first device, and send a integrated fast charging handshake request to the above-mentioned first device.
[0223] In some embodiments of the present application, the above-mentioned device also includes: a processing module; the above-mentioned processing module is used to receive the charging current from the first device when establishing a fusion fast charging connection with the first device.
[0224] In some embodiments of the present application, the processing module is further used to charge the first device upon receiving a second charging request sent by the first device; the second charging request is used to request the second device to charge the first device.
[0225] In some embodiments of the present application, the above-mentioned receiving module is also used to receive a second input; the above-mentioned sending module is specifically used to send the above-mentioned first pulse signal to the above-mentioned first device in response to the above-mentioned second input received by the above-mentioned receiving module.
[0226] The charging control device provided in the embodiment of the present application sends a first pulse signal to the first device, and then sends a handshake instruction to the first device when the first pulse signal sent by the first device is received or the second pulse signal sent by the first device is received, thereby completing the establishment of a fused fast charging handshake based on the fused fast charging protocol with the second device, and performing fast charging based on the fused fast charging protocol after successfully establishing the fused fast charging handshake.
[0227] The charging control device in the embodiment of the present application can be an electronic device or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc. It can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0228] The charging control device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0229] The charging control device provided in the embodiment of the present application can implement various processes of the above method embodiment, and to avoid repetition, they will not be described again here.
[0230] Alternatively, if Fig.11 As shown, an embodiment of the present application further provides an electronic device 800, including a processor 801 and a memory 802, wherein the memory 802 stores a program or instruction that can be executed on the processor 801, and when the program or instruction is executed by the processor 801, each step of the above-mentioned charging control method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0231] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.
[0232] Fig.12 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.
[0233] The electronic device 100 includes but is not limited to components such as a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.
[0234] Those skilled in the art will appreciate that the electronic device 100 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.12 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0235] In some possible implementations, the interface unit 108 is used to receive a first pulse signal from a second device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; the interface unit 108 is used to send a second pulse signal or the first pulse signal to the second device when the first device supports the fusion fast charging protocol; the second pulse signal is used to indicate that the first device supports the fusion fast charging protocol.
[0236] In some embodiments of the present application, the processor 110 is configured to establish a converged fast charging connection with the second device upon receiving a converged fast charging handshake request sent by the second device.
[0237] In some embodiments of the present application, the above-mentioned interface unit 108 is specifically used to receive the above-mentioned first pulse signal through the first signal receiving end of the above-mentioned first device; the above-mentioned interface unit 108 is specifically used to send the above-mentioned second pulse signal to the above-mentioned second device through the first signal sending end of the above-mentioned first device.
[0238] In some embodiments of the present application, the above-mentioned interface unit 108 is specifically used to receive the above-mentioned first pulse signal through the first signal receiving end of the above-mentioned first device; there is a conduction control between the above-mentioned first signal receiving end and the first signal sending end of the above-mentioned first device; the above-mentioned interface unit 108 is specifically used to send the above-mentioned first pulse signal to the above-mentioned second device through the above-mentioned first signal sending end when the above-mentioned conduction control is in the on state.
[0239] In some embodiments of the present application, the processor 110 is further configured to control the conduction control to be in an on state before sending the first pulse signal to the second device through the first signal sending end.
[0240] In some embodiments of the present application, the processor 110 is further configured to control the conduction control to be in a closed state after sending the first pulse signal to the second device through the first signal sending end.
[0241] In some embodiments of the present application, the conduction control is an electronic switch control; the processor 110 is specifically used to apply a first electrical signal to the control end of the electronic switch control to control the electronic switch control to close;
[0242] In some embodiments of the present application, the conduction control is an electronic switch control; the processor 110 is specifically used to apply a second electrical signal to the control end of the electronic switch control to control the electronic switch control to be disconnected.
[0243] In some embodiments of the present application, the processor 110 is further configured to charge the second device after establishing a converged fast charging connection with the second device.
[0244] In some embodiments of the present application, the above-mentioned interface unit 108 is also used to receive a first input when establishing a converged fast charging connection with the above-mentioned second device; the above-mentioned interface unit 108 is also used to send a second charging request to the above-mentioned second device in response to the above-mentioned first input received by the above-mentioned interface unit 108; the above-mentioned second charging request is used to request the above-mentioned second device to charge the above-mentioned first device.
[0245] An embodiment of the present application provides an electronic device, which receives a first pulse signal from a second device, and the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol. When the first device supports the fusion fast charging protocol, the electronic device sends a second pulse signal or the above-mentioned first pulse signal to the second device, and the second pulse signal is used to indicate that the second device supports the fusion fast charging protocol. In this way, after receiving the first pulse signal from the second device, the first device can send the second pulse signal to the second device, or send the received first pulse signal to the second device, to indicate that it also supports the fusion fast charging protocol, thereby establishing a fusion fast charging handshake based on the fusion fast charging protocol with the second device, and charging can be performed based on the fusion fast charging protocol after the fusion fast charging handshake is successfully established.
[0246] In some other possible implementations, the interface unit 108 is used to send a first pulse signal to the first device; the first pulse signal is used to indicate that the second device supports the integrated fast charging protocol; the interface unit 108701 is also used to send a integrated fast charging handshake request to the first device when the integrated fast charging handshake conditions are met; wherein the integrated fast charging handshake conditions include any one of the following: the second device receives the first pulse signal sent by the first device; the second device receives the second pulse signal sent by the first device; the second pulse signal is used to indicate that the first device supports the integrated fast charging protocol.
[0247] In some embodiments of the present application, the interface unit 108 is specifically configured to send the first pulse signal to the first device via the second signal sending end of the second device.
[0248] In some embodiments of the present application, the second device receives the first pulse signal or the second pulse signal through a second signal receiving end.
[0249] In some embodiments of the present application, the above-mentioned interface unit 108 is also used to send the above-mentioned first pulse signal to the above-mentioned first device again after sending the first pulse signal to the first device if the above-mentioned fusion fast charging handshake condition is not met.
[0250] In some embodiments of the present application, the above-mentioned interface unit 108 is also used to, after sending the above-mentioned first pulse signal to the above-mentioned first device again when the above-mentioned fusion fast charging handshake condition is not met, stop sending the above-mentioned first pulse signal when receiving the above-mentioned second pulse signal or the above-mentioned first pulse signal sent by the above-mentioned first device, and send a fusion fast charging handshake request to the above-mentioned first device.
[0251] In some embodiments of the present application, the processor 110 is configured to receive a charging current from the first device when a converged fast charging connection is established with the first device.
[0252] In some embodiments of the present application, the processor 110 is further used to charge the first device upon receiving a second charging request sent by the first device; the second charging request is used to request the second device to charge the first device.
[0253] In some embodiments of the present application, the interface unit 108 is further used to receive a second input; the interface unit 108 is specifically used to send the first pulse signal to the first device in response to the second input received by the interface unit 108.
[0254] The electronic device provided in the embodiment of the present application, after sending a first pulse signal to the first device, sends a handshake instruction to the first device when receiving the first pulse signal sent by the first device or receiving the second pulse signal sent by the first device, thereby completing the establishment of a fusion fast charging handshake based on the fusion fast charging protocol with the second device, and performing fast charging based on the fusion fast charging protocol after successfully establishing the fusion fast charging handshake.
[0255] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and at least one of other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0256] The memory 109 can be used to store software programs and various data. The memory 109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 109 may include a volatile memory or a non-volatile memory, or the memory 109 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0257] The processor 110 may include one or more processing units; optionally, the processor 110 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 110.
[0258] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned charging control method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0259] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
[0260] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned charging control method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0261] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0262] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned charging control method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0263] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0264] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0265] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
Claims
1. A charging control method, applied to a first device, characterized in that: The method comprises: Receiving a first pulse signal from a second device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; When the first device supports the integrated fast charging protocol, a second pulse signal or the first pulse signal is sent to the second device; the second pulse signal is used to indicate that the first device supports the integrated fast charging protocol.
2. The method according to claim 1, characterized in that The method further comprises: Upon receiving the converged fast charging handshake request sent by the second device, a converged fast charging connection is established with the second device.
3. The method according to claim 1, characterized in that The receiving a first pulse signal from a second device comprises: receiving the first pulse signal through a first signal receiving end of the first device; Sending a second pulse signal to the second device includes: The second pulse signal is sent to the second device through the first signal sending end of the first device.
4. The method according to claim 1, characterized in that: The receiving a first pulse signal from a second device comprises: The first pulse signal is received through a first signal receiving end of the first device; a conduction control is provided between the first signal receiving end and a first signal sending end of the first device; Sending the first pulse signal to the second device includes: When the conduction control is in an on state, the first pulse signal is sent to the second device through the first signal sending end.
5. The method according to claim 4, characterized in that Before sending the first pulse signal to the second device through the first signal sending end, the method further includes: The conduction control is controlled to be in an on state.
6. The method according to claim 5, characterized in that After sending the first pulse signal to the second device through the first signal sending end, the method further includes: The conduction control is controlled to be in a closed state.
7. The method according to claim 6, characterized in that The conduction control is an electronic switch control; The controlling the conduction control to be in an on state includes: A first electrical signal is applied to the control end of the electronic switch control to control the electronic switch control to close.
8. The method according to claim 6, characterized in that The conduction control is an electronic switch control; The controlling the conduction control to be in a closed state includes: A second electrical signal is applied to the control end of the electronic switch control to control the electronic switch control to be disconnected.
9. The method according to claim 2, characterized in that: After establishing the fused fast charging connection with the second device, the method further includes: The first device charges the second device.
10. The method according to claim 2, characterized in that The method further comprises: receiving a first input while establishing a converged fast charging connection with the second device; In response to the first input, a second charging request is sent to the second device; the second charging request is used to request the second device to charge the first device.
11. A charging control method, applied to a second device, characterized in that: The method comprises: Sending a first pulse signal to the first device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; When the converged fast charge handshake condition is met, sending a converged fast charge handshake request to the first device; The fusion fast charge handshake condition includes any of the following: The second device receives the first pulse signal sent by the first device; The second device receives a second pulse signal sent by the first device; the second pulse signal is used to indicate that the first device supports the fusion fast charging protocol.
12. The method according to claim 11, characterized in that The sending a first pulse signal to the first device includes: The first pulse signal is sent to the first device through the second signal sending end of the second device.
13. The method according to claim 11, characterized in that The second device receives the first pulse signal or the second pulse signal through a second signal receiving end.
14. The method according to claim 11, characterized in that After sending the first pulse signal to the first device, the method further includes: When the fused fast charge handshake condition is not met, the first pulse signal is sent to the first device again.
15. The method according to claim 14, characterized in that After the first pulse signal is sent again to the first device when the fusion fast charge handshake condition is not met, the method further includes: When the second pulse signal or the first pulse signal sent by the first device is received, stop sending the first pulse signal and send a fusion fast charging handshake request to the first device.
16. The method according to claim 11, characterized in that After sending the fusion fast charge handshake request to the first device when the fusion fast charge handshake condition is met, the method further includes: When establishing a converged fast charging connection with the first device, receiving a charging current from the first device.
17. The method according to claim 11, characterized in that The method further comprises: Upon receiving a second charging request sent by the first device, charging the first device; the second charging request is used to request the second device to charge the first device.
18. The method according to claim 11, characterized in that Before the step of sending the first pulse signal to the first device, the method further includes: receiving a second input; The sending a first pulse signal to the first device includes: In response to the second input, the first pulse signal is sent to the first device.
19. A charging control device, characterized in that: The device comprises: a receiving module and a sending module, wherein: The receiving module is used to receive a first pulse signal from a second device; the first pulse signal is used to indicate that the second device supports the fusion fast charging protocol; The sending module is used to send a second pulse signal or the first pulse signal to the second device when the first device supports the integrated fast charging protocol; the second pulse signal is used to indicate that the first device supports the integrated fast charging protocol.
20. An electronic device, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the charging control method as described in any one of claims 1 to 10 or implements the steps of the charging control method as described in any one of claims 11 to 18.
