Charging method and vehicle

Abstract

The invention provides a charging method and a vehicle, the method is applied to the field of vehicle control, the vehicle comprises a charging interface and a Bluetooth module, and the method comprises the steps that under the condition that a mobile terminal is electrically connected with the charging interface, equipment information of the mobile terminal is acquired through the Bluetooth module; obtaining a target charging protocol parameter corresponding to the equipment information from a server; and charging the mobile terminal based on the target charging protocol parameter. According to the method, the adaptability and the intelligent degree of vehicle-mounted charging can be improved.

Description

A charging method and a vehicle Technical Field

[0001] This application relates to the field of vehicle control, and more specifically, to a charging method and a vehicle in the field of vehicle control. Background Technology

[0002] Users can charge their mobile devices using the vehicle's onboard charging equipment while driving.

[0003] Currently, vehicle chargers typically use fixed protocol chips, which means that the charging protocol is pre-stored in the memory chip to realize the charging function. Specifically, the device identifier of the mobile terminal is identified through the Universal Serial Bus (USB) interface, and the appropriate charging protocol is determined in the memory chip based on the device identifier to perform charging.

[0004] In the above solutions, the USB interface has a weak ability to recognize device identifiers, which limits charging efficiency. In addition, after a long productization process, car chargers using fixed protocol chips cannot be adapted to the latest mobile terminal charging protocols after mass production and market launch, resulting in poor compatibility. Summary of the Invention

[0005] In view of this, this application provides a charging method and a vehicle that can improve the efficiency, compatibility and intelligence of on-board charging.

[0006] In a first aspect, a charging method is provided, which is applied to a vehicle, the vehicle including a charging interface and a Bluetooth module. The method includes: when a mobile terminal is electrically connected to the charging interface, obtaining device information of the mobile terminal through the Bluetooth module; obtaining target charging protocol parameters corresponding to the device information from a server; and charging the mobile terminal based on the target charging protocol parameters.

[0007] In the above technical solution, acquiring mobile terminal device information via the vehicle's Bluetooth module achieves high accuracy and can identify relatively rich device information, such as the mobile terminal's brand, model, name, and Bluetooth address. This supports intelligent charging scenarios; for example, based on device name or Bluetooth address, different mobile terminals can be accurately identified, thus understanding their corresponding charging habits. Based on this understanding, more suitable charging strategies can be developed. Furthermore, the server can store multiple charging protocols. The target charging protocol parameters corresponding to the device information can be retrieved from the server, and the mobile terminal can be charged based on these parameters. In this way, the vehicle can be compatible with the charging functions of various mobile terminals, improving the compatibility and intelligence of the vehicle's charging capabilities.

[0008] In conjunction with the first aspect, in some possible implementations, obtaining the device information of the mobile terminal through the Bluetooth module includes: triggering a Bluetooth connection between the mobile terminal and the Bluetooth module; and obtaining the device information of the mobile terminal through the Bluetooth module during the process of establishing a Bluetooth connection between the mobile terminal and the Bluetooth module.

[0009] The above technical solution allows the Bluetooth module to obtain device information from the mobile terminal during the Bluetooth connection process, without having to wait for the Bluetooth connection to succeed. This shortens the device information acquisition time, improves the efficiency of device information acquisition, and reduces user waiting time. In addition, users only need to enable the Bluetooth function of the mobile terminal without performing any additional operations, thus enhancing the user experience.

[0010] In conjunction with the first aspect, in some possible implementations, the device information includes the device brand and device model. Obtaining the target charging protocol parameter corresponding to the device information from the server includes: sending an acquisition request to the server so that the server determines whether a first charging protocol parameter exists in the cloud charging protocol library based on the acquisition request. The first charging protocol parameter is a charging protocol parameter that matches both the device brand and the device model. If the first charging protocol parameter exists in the cloud charging protocol library, receiving the first charging protocol parameter returned by the server. If the first charging protocol parameter does not exist in the cloud charging protocol library, receiving a second charging protocol parameter returned by the server. The second charging protocol parameter is a charging protocol parameter determined according to a preset priority order, and the second charging protocol parameter is different from the first charging protocol parameter.

[0011] In conjunction with the first aspect, in some possible implementations, the second charging protocol parameter includes one of the following: a same-brand charging protocol parameter, a preset fast charging protocol parameter, and a preset slow charging protocol parameter; wherein, the preset priority order is as follows: the same-brand charging protocol parameter has a higher priority than the preset fast charging protocol parameter, and the preset fast charging protocol parameter has a higher priority than the preset slow charging protocol parameter; the same-brand charging protocol parameter is a charging protocol parameter in the cloud charging protocol library that matches the device brand but does not match the device model.

[0012] In the above technical solution, the first charging protocol parameter that matches the device brand and model of the mobile terminal can be regarded as the target charging protocol parameter that is optimally adapted to the mobile terminal. After the vehicle sends a request to the server, if the first charging protocol parameter exists in the cloud charging protocol library stored in the server, the server can send the first charging protocol parameter to the vehicle to charge the mobile terminal according to the first charging protocol parameter.

[0013] In addition, the aforementioned preset priority order refers to the order of compatibility between different charging protocols (such as the same brand charging protocol, preset fast charging protocol, and preset slow charging protocol) in the cloud charging protocol library and the mobile terminal; if the aforementioned first charging protocol parameter does not exist in the cloud protocol library, the server can determine the second charging protocol corresponding to the mobile terminal according to the preset compatibility order (such as compatibility from high to low), and send the second charging protocol to the vehicle, and the vehicle charges the mobile terminal according to the second charging protocol.

[0014] In summary, the above technical solution provides redundant backup of the charging protocol. The first charging protocol parameters and the second charging protocol parameters can form a dual guarantee, improving the universality and compatibility of vehicle charging of mobile terminals and realizing intelligent management of mobile terminal charging.

[0015] In conjunction with the first aspect, in some possible implementations, charging the mobile terminal based on the target charging protocol parameters includes: determining whether the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal supports charging with the target charging protocol parameters, charging the mobile terminal based on the target charging protocol parameters; if the mobile terminal does not support charging with the target charging protocol parameters, charging the mobile terminal according to preset slow charging protocol parameters stored in the local charging protocol library.

[0016] In the above technical solution, determining whether the mobile terminal supports charging with the target charging protocol parameters can be understood as judging whether the mobile terminal has the capability to use the target charging protocol parameters at both the hardware and software levels. If the mobile terminal has the capability to charge with the target charging protocol parameters, it can be charged with the target charging protocol parameters to achieve fast charging with optimal voltage, optimal current, or high power, reducing energy loss. If the mobile terminal does not have the capability to charge with the target charging protocol parameters, it will be charged with preset slow charging protocol parameters. In this way, the mobile terminal can be prevented from being subjected to power beyond its rated range, improving the safety and compatibility of vehicle charging of the mobile terminal.

[0017] In conjunction with the first aspect, in some possible implementations, the vehicle includes a LIN transceiver. Determining whether the mobile terminal supports charging with the target charging protocol parameters includes: sequentially sending the target charging protocol parameters to the mobile terminal via the LIN transceiver and the charging interface; determining that the mobile terminal supports charging with the target charging protocol parameters if the mobile terminal returns a first type of response information; and determining that the mobile terminal supports charging with the target charging protocol parameters if the mobile terminal returns a second type of response information.

[0018] In the above technical solution, after the vehicle receives the target charging protocol parameters (i.e., the first charging protocol parameters or the second charging protocol parameters) sent by the server, it can send the target charging protocol parameters to the mobile terminal through the LIN transceiver and the charging interface to trigger protocol negotiation and determine whether the mobile terminal supports charging with the target charging protocol parameters. Based on the LIN transceiver, the communication between the vehicle and the mobile terminal can avoid parameter transmission errors and improve the reliability of the vehicle charging process.

[0019] In conjunction with the first aspect, in some possible implementations, the target charging protocol parameters include at least a target charging voltage and a target charging current, and charging the mobile terminal based on the target charging protocol parameters includes: charging the mobile terminal based on the target charging voltage and the target charging current.

[0020] The above technical solutions can charge mobile terminals with the optimal charging voltage and current, maximizing charging power. For example, it can enable high-power charging equipment on vehicles to output full power under certain conditions, thereby significantly shortening charging time and improving charging efficiency. In addition, it can reduce battery aging of mobile terminals and extend battery life.

[0021] In conjunction with the first aspect, in some possible implementations, the charging method provided by this application further includes: when charging the mobile terminal based on the target charging protocol parameters, monitoring the indicator parameters of a preset indicator corresponding to the charging interface; and when the indicator parameters do not meet the preset conditions, charging the mobile terminal according to a preset output strategy.

[0022] In the above scheme, the preset indicators corresponding to the charging interface refer to the output characteristics of the charging interface during the charging process, such as the output voltage, output current and / or real-time temperature of the charging interface; that is, during the charging process, the parameters corresponding to the output characteristics of the charging interface are detected in real time to see if they meet the preset conditions. If the preset conditions are not met, the output of the charging interface is adjusted to ensure safe charging and improve the charging safety of the vehicle to the mobile terminal.

[0023] In conjunction with the first aspect, in some possible implementations, obtaining the target charging protocol parameters corresponding to the device information from the server includes: encrypting the device information; and obtaining the target charging protocol parameters corresponding to the device information from the server based on the encrypted device information.

[0024] In the above technical solution, encrypting the device information and then obtaining the corresponding target charging protocol parameters from the server based on the encrypted device information can prevent the device information from being tampered with during transmission and improve the security of the vehicle charging the mobile terminal.

[0025] In a second aspect, a charging device is provided, which is applied to a vehicle, the vehicle including a charging interface and a Bluetooth module, the device including: an acquisition unit and a charging unit;

[0026] The acquisition unit is used to acquire device information of the mobile terminal through the Bluetooth module when the mobile terminal is electrically connected to the charging interface; the acquisition unit is also used to acquire target charging protocol parameters corresponding to the device information from the server; the charging unit is used to charge the mobile terminal based on the target charging protocol parameters.

[0027] In conjunction with the second aspect, in some possible implementations, the acquisition unit is specifically used to trigger the Bluetooth connection between the mobile terminal and the Bluetooth module; during the process of establishing a Bluetooth connection between the mobile terminal and the Bluetooth module, the device information of the mobile terminal is acquired through the Bluetooth module.

[0028] In conjunction with the second aspect, in some possible implementations, the device information includes the device brand and device model. The acquisition unit is specifically used to send an acquisition request to the server, so that the server determines whether a first charging protocol parameter exists in the cloud charging protocol library based on the acquisition request. The first charging protocol parameter is a charging protocol parameter that matches both the device brand and the device model. If the first charging protocol parameter exists in the cloud charging protocol library, the server returns the first charging protocol parameter. If the first charging protocol parameter does not exist in the cloud charging protocol library, the server returns a second charging protocol parameter. The second charging protocol parameter is a charging protocol parameter determined according to a preset priority order, and the second charging protocol parameter is different from the first charging protocol parameter.

[0029] In conjunction with the second aspect, in some possible implementations, the second charging protocol parameter includes one of the following: a same-brand charging protocol parameter, a preset fast charging protocol parameter, and a preset slow charging protocol parameter; wherein, the preset priority order is as follows: the same-brand charging protocol parameter has a higher priority than the preset fast charging protocol parameter, and the preset fast charging protocol parameter has a higher priority than the preset slow charging protocol parameter; the same-brand charging protocol parameter is a charging protocol parameter in the cloud charging protocol library that matches the device brand but does not match the device model.

[0030] In conjunction with the second aspect, in some possible implementations, the charging unit is specifically used to determine whether the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal supports charging with the target charging protocol parameters, the mobile terminal is charged based on the target charging protocol parameters; if the mobile terminal does not support charging with the target charging protocol parameters, the mobile terminal is charged according to the preset slow charging protocol parameters stored in the local charging protocol library.

[0031] In conjunction with the second aspect, in some possible implementations, the vehicle includes a LIN transceiver and a charging unit, and is specifically used to send the target charging protocol parameters to the mobile terminal sequentially through the LIN transceiver and the charging interface; if the mobile terminal returns a first type of response information, it is determined that the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal returns a second type of response information, it is determined that the mobile terminal supports charging with the target charging protocol parameters.

[0032] In conjunction with the second aspect, in some possible implementations, the target charging protocol parameters include at least a target charging voltage and a target charging current, and a charging unit specifically used to charge the mobile terminal based on the target charging voltage and the target charging current.

[0033] In conjunction with the second aspect, in some possible implementations, the charging unit is also used to monitor the indicator parameters of the preset indicators corresponding to the charging interface when charging the mobile terminal based on the target charging protocol parameters; and to charge the mobile terminal according to the preset output strategy when the indicator parameters do not meet the preset conditions.

[0034] In conjunction with the second aspect, in some possible implementations, the acquisition unit is specifically used to encrypt the device information; based on the encrypted device information, it retrieves the target charging protocol parameters corresponding to the device information from the server.

[0035] Thirdly, a vehicle is provided, comprising: a memory for storing executable program code; and a processor for calling and running the executable program code from the memory, causing the vehicle to perform methods as described in the first aspect or any one of the first aspects.

[0036] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0037] Fifthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 is a schematic diagram of an on-board charging system involved in a charging method provided in an embodiment of this application; Figure 2 is a schematic flowchart of a charging method provided in an embodiment of this application; Figure 3 is a structural schematic diagram of a charging device provided in an embodiment of this application; Figure 4 is a structural schematic diagram of a vehicle provided in an embodiment of this application. Detailed Implementation

[0040] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0041] It should be noted that the terms "first," "second," "third," etc., in the claims, specification, and drawings of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. Such data are interchangeable where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown or described herein. Furthermore, the terms "comprising," "having," and their variations are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0042] It should be understood that in the embodiments of this application, "at least one" refers to one or more, "several" refers to one or more, and "more than" refers to two or more. "And / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "Contains A, B, and / or C" means containing any one, two, or three of A, B, and C.

[0043] It should be understood that in the embodiments of this application, "B corresponding to A", "B corresponding to A", "A corresponds to B" or "B corresponds to A" means that B is associated with A, and B can be determined based on A. Determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0044] While driving, users can charge their mobile devices using the vehicle's onboard charging equipment. Currently, onboard chargers typically use fixed protocol chips, meaning the charging protocol is pre-stored in a memory chip, resulting in a fixed protocol chip. Examples include PD protocol chips that integrate the Power Delivery (PD) protocol, and QC protocol chips that integrate the Quick Charge (QC) protocol.

[0045] The above methods rely on fixed protocol chips to charge mobile terminals. After a long productization process, they cannot be adapted to the latest mobile terminals after mass production and market launch. It is necessary to upgrade hardware devices to adapt to new proprietary protocols or new protocols, resulting in insufficient vehicle compatibility with mobile terminals.

[0046] Furthermore, in related technologies, when a mobile terminal is plugged into an in-vehicle charging device, the device identifier of the mobile terminal can be identified through the USB interface of the in-vehicle charging device. Based on this device identifier, the appropriate voltage and current are determined in the fixed protocol chip for charging. However, the USB interface has a weak ability to identify device identifiers and cannot accurately identify the device identifier of the mobile terminal. When the device identifier of the mobile terminal is not accurately identified, the in-vehicle charging device is prone to charging the mobile terminal in a slow charging mode, resulting in limited charging efficiency. That is, the high-power charging equipment of the vehicle cannot output full power.

[0047] To address the aforementioned technical problems, this application provides a charging method and a vehicle.

[0048] Referring to Figure 1, a schematic diagram of an on-board charging system involved in a charging method provided by an exemplary embodiment is shown. Referring to Figure 1, the on-board charging system 100 includes a vehicle 10, a mobile terminal 20, and a server 30.

[0049] The vehicle 10 is equipped with a charging interface, a Bluetooth module, and a LIN transceiver. The charging interface is used to electrically connect to the mobile terminal 20 and charge the mobile terminal 20. The Bluetooth module is used to obtain device information of the mobile terminal 20 so that the vehicle 10 can obtain target charging protocol parameters from the server 30 based on the device information. The LIN transceiver is used to send the target charging protocol parameters to the mobile terminal 20 through the charging interface, triggering protocol negotiation between the vehicle 10 and the mobile terminal 20 to determine whether the mobile terminal 20 supports charging with the target charging protocol parameters.

[0050] Mobile terminal 20 may be, for example, a smartphone, tablet, smartwatch, personal digital assistant (PDA), etc.

[0051] Server 30 is communicatively connected to vehicle 10 and provides related services to vehicle 10. Specifically, server 30 and vehicle 10 can communicate via WiFi, 4G, or 5G networks. Server 30 stores a cloud-based charging protocol library. When vehicle 10 charges mobile terminal 20, it can obtain the corresponding target charging protocol parameters from server 30, enabling vehicle 10 to charge mobile terminal 20 according to the obtained target charging protocol parameters.

[0052] The charging method of this application embodiment is described in detail below with reference to Figure 2. The subject of this charging method is a vehicle, specifically a controller in the vehicle.

[0053] Figure 2 is a schematic flowchart of a charging method provided in an embodiment of this application. It should be noted that the steps shown may be executed in a different logical order than that shown in the flowchart. For example, this charging method can be applied to a vehicle, which includes a charging interface and a Bluetooth module. As shown in Figure 1, the method steps of this charging method may include the following S110~S130.

[0054] S110 obtains device information of the mobile terminal via Bluetooth module when the mobile terminal is electrically connected to the charging interface.

[0055] In this application, the mobile terminal is a device such as a smartphone, tablet computer, smartwatch, or PDA with Bluetooth functionality.

[0056] Electrical connection between a mobile terminal and a charging interface refers to a connection between the mobile terminal and the charging interface that allows for the conduction of current or electrical signals. For example, when the charging interface is a USB socket, detecting that the mobile terminal is plugged into the USB socket via a USB data cable indicates that the mobile terminal is electrically connected to the charging interface.

[0057] The aforementioned Bluetooth module is configured with the Bluetooth protocol to enable data interaction between the Bluetooth module and the mobile terminal based on the Bluetooth protocol. For example, the Bluetooth protocol may include the Bluetooth Low Energy (BLE) protocol.

[0058] In some possible implementations, the "obtaining device information of the mobile terminal via the Bluetooth module" in S110 above can be specifically implemented through the following S111~S112.

[0059] S111 triggers the Bluetooth connection between the mobile terminal and the Bluetooth module.

[0060] S112, during the process of establishing a Bluetooth connection between the mobile terminal and the Bluetooth module, the device information of the mobile terminal is obtained through the Bluetooth module.

[0061] In this implementation, when the mobile terminal is electrically connected to the charging interface, a Bluetooth connection between the mobile terminal and the Bluetooth module is triggered.

[0062] The process of establishing a Bluetooth connection between a mobile terminal and a Bluetooth module refers to the preparatory stage before a successful Bluetooth connection is established between the mobile terminal and the Bluetooth module.

[0063] The device information of the aforementioned mobile terminal may include, but is not limited to, at least one of the following: device name, device brand, device model, and remaining battery power. The device name may be the default name set by the manufacturer of the mobile terminal, or it may be a username modified by the user; the device brand is used to identify the origin of the mobile terminal, such as identifying the manufacturer; and the device model is used to identify the unique identifier code of the mobile terminal's technical specifications, configuration, or functions.

[0064] It should be understood that when the Bluetooth function of a mobile terminal is not enabled, the Bluetooth module sends a prompt message to the mobile terminal to enable the Bluetooth function, so that the user can enable the Bluetooth function of the mobile terminal based on the prompt message. When the Bluetooth function of the mobile terminal is enabled, the mobile terminal will continuously send broadcast data packets in the broadcast channel specified by the BLE protocol. The broadcast data packets may include, but are not limited to, at least one of the following information: a Bluetooth address that uniquely identifies the mobile terminal, a short device name of the mobile terminal, device type, connection identifier (whether it is connectable), a universally unique identifier (UUID), transmit power, and received signal strength (RSSI), etc.

[0065] Specifically, after the vehicle is started and powered on, the system detects whether a mobile terminal has established an electrical connection with the charging interface. If the mobile terminal has established an electrical connection with the charging interface, the Bluetooth module is triggered to actively scan within a preset range based on the BLE protocol. That is, it listens to the broadcast channel specified by the BLE protocol. After scanning the broadcast data packet sent by the mobile terminal, the module sends a scan request to the mobile terminal. The mobile terminal responds to the scan request and returns a scan response packet to the Bluetooth module. The scan response packet may include, but is not limited to, the mobile terminal's device model, device brand, complete device name, detailed service list, hardware version, software version, and remaining battery power.

[0066] In this implementation, device information of the mobile terminal is obtained through the vehicle's Bluetooth module. This method boasts high accuracy and can identify relatively rich device information, such as the mobile terminal's brand, model, name, and Bluetooth address. It supports intelligent charging scenarios; for example, based on device name or Bluetooth address, it can accurately identify different mobile terminals, thereby understanding their corresponding charging habits and developing more suitable charging strategies. Compared to obtaining device information through a pre-installed USB interface, obtaining device information via the BLE protocol offers stronger compatibility with mobile terminals, improving the compatibility and intelligence of the vehicle's charging function.

[0067] In addition, during the Bluetooth connection process between the Bluetooth module and the mobile terminal, the device information of the mobile terminal can be obtained through the Bluetooth module instead of waiting for the Bluetooth connection to be successful. This shortens the device information acquisition time, improves the efficiency of device information acquisition, and reduces the user's waiting time. Furthermore, the user only needs to turn on the Bluetooth function of the mobile terminal without performing any additional operations, thus enhancing the user experience.

[0068] S120: Obtain the target charging protocol parameters corresponding to the device information from the server.

[0069] In this application, a cloud charging protocol library is stored in the server. The cloud charging protocol library stores multiple charging protocol parameters and device information corresponding to each charging protocol parameter. That is, the charging protocol parameters and device information in the cloud charging protocol library have a corresponding relationship.

[0070] The charging protocol parameters stored in this cloud-based charging protocol library include, but are not limited to, those of general charging protocols and proprietary charging protocols. General charging protocol parameters include, but are not limited to: PD charging protocol parameters and Battery Charge (BC) protocol parameters; proprietary charging protocol parameters include, but are not limited to: Voltage Open Loop Multi-step Constant-Current Charging (VOOC) protocol parameters, Super Charge Protocol (SCP) parameters, Fast Charger Protocol (FCP) parameters, Adaptive Fast Charge (AFC) protocol parameters, MediaTek Pump Express (MTK PE) protocol parameters, and QC charging protocol parameters.

[0071] Specifically, for each of the above charging protocol parameters, the cloud-based charging protocol library can store different versions of them. For example, as shown in Table 1, Table 1 provides examples of different versions of QC charging protocol parameters stored in the cloud-based charging protocol library.

[0072] Table 1

[0073] As shown in Table 1, the cloud-based charging protocol library can store QC protocol versions 1.0 to 4.0. Among them, the charging protocol parameters of QC version 1.0 include: charging voltage 5V, charging current 2A; the charging protocol parameters of QC version 2.0 include: 5V / 2A, 9V / 2A, 12V / 1.5A, etc.; the charging protocol parameters of QC version 3.0 include: 3.6V~6.5V / 3A, 6.5V~9V / 2A, 9V~12V / 1.5A, etc.; and the charging protocol parameters of QC version 4.0 include: 5V / (4.7A~5.6A)~9V / 3A, etc.

[0074] The charging protocol parameters stored in the cloud charging protocol library shown in Table 1 above are merely examples and do not constitute a limitation on this application.

[0075] Therefore, the target charging protocol parameters corresponding to the aforementioned device information refer to the charging protocol parameters in the latest version of the target charging protocol obtained from the cloud charging protocol library. For example, the target charging protocol parameters could be the charging protocol parameters corresponding to QC4.0.

[0076] Thus, the implementation method provided in this application supports vehicles using both proprietary and universal protocols to charge different mobile terminals, resulting in stronger compatibility.

[0077] In some possible implementations, when the device information includes the device brand and device model, the steps of obtaining the target charging protocol from the server can be implemented through the following steps S121~S123.

[0078] S121, a request is sent to the server so that the server can determine whether the first charging protocol parameter exists in the cloud charging protocol library based on the request. The request includes device information, and the first charging protocol parameter is a charging protocol parameter that matches both the device brand and the device model.

[0079] In this implementation, after the Bluetooth module obtains the device information of the mobile terminal, it sends the device information to the vehicle controller. The controller generates an acquisition request based on the device information. The acquisition request is used to request the server to determine whether the first charging protocol parameter exists in the cloud charging protocol library.

[0080] After the vehicle controller generates an acquisition request, it sends the acquisition request to the server. The server parses the acquisition request to obtain the device brand and device model included in the acquisition request. Then, it queries the cloud charging protocol library to see if there is a first charging protocol parameter that matches both the device brand and device model.

[0081] Based on the query results, the server returns different charging protocol parameters to the vehicle's controller.

[0082] S122, if the first charging protocol parameter exists in the cloud charging protocol library, receive the first charging protocol parameter returned by the server.

[0083] That is, if a first charging protocol parameter exists in the cloud charging protocol library that matches the device brand and model of the mobile terminal, the first charging protocol parameter is returned to the vehicle controller, and the vehicle controller uses the first charging protocol parameter as the target charging protocol parameter to charge the mobile terminal.

[0084] S123, if the first charging protocol parameter does not exist in the cloud charging protocol library, receive the second charging protocol parameter returned by the server. The second charging protocol parameter is a charging protocol parameter determined according to a preset priority order, and the second charging protocol parameter is different from the first charging protocol parameter.

[0085] The aforementioned preset priority order refers to the sorting of each charging protocol parameter according to the degree of compatibility between different versions of charging protocol parameters and mobile terminals.

[0086] For example, in this application, the preset priority order is as follows: the priority of the same-brand charging protocol parameter is higher than the priority of the preset fast charging protocol parameter, and the priority of the preset fast charging protocol parameter is higher than the priority of the preset slow charging protocol parameter. Specifically, the same-brand charging protocol parameter is a charging protocol parameter in the cloud-based charging protocol library that matches the device brand but not the device model; the preset fast charging protocol parameter is a charging protocol parameter in the cloud-based charging protocol library that enables fast charging; for example, the preset fast charging protocol parameter can be a PD charging protocol parameter, with the corresponding preset fast charging protocol parameter being 20V / 3A; the preset slow charging protocol parameter is a charging protocol parameter for basic speed charging in the cloud-based protocol library; for example, the preset slow charging protocol parameter is 5V / 1A.

[0087] Specifically, if the first charging protocol is not present in the cloud charging protocol library, based on the aforementioned preset priority order, it is determined whether the cloud charging protocol library contains a charging protocol parameter of the same brand as the mobile terminal. If the cloud charging protocol library contains a charging protocol parameter of the same brand that matches the device brand of the mobile terminal but does not match the device model, the charging protocol parameter of the same brand is sent to the vehicle controller as the second charging protocol parameter. The controller then uses the second charging protocol parameter as the target charging protocol parameter to charge the mobile terminal.

[0088] If the same brand's charging protocol parameters are not found in the cloud charging protocol library, but the preset fast charging protocol parameters supported by the mobile terminal are available, the preset fast charging protocol parameters supported by the mobile terminal are sent to the vehicle's controller as the second charging protocol parameters. The controller then uses the second charging protocol parameters as the target charging protocol parameters to charge the mobile terminal.

[0089] If the preset fast charging protocol parameters supported by the mobile terminal are not found in the cloud charging protocol library, the preset slow charging protocol parameters are sent to the vehicle controller as the second charging protocol parameters. The controller then uses the second charging protocol parameters as the target charging protocol parameters to charge the mobile terminal.

[0090] That is, in this exemplary implementation, the second charging protocol parameter includes one of the following: same-brand charging protocol parameter, preset fast charging protocol parameter, and preset slow charging protocol parameter.

[0091] In summary, the above technical solution provides redundant backup of the charging protocol. The first charging protocol parameters and the second charging protocol parameters can form a dual guarantee, improving the universality and compatibility of vehicle charging of mobile terminals and realizing intelligent management of mobile terminal charging.

[0092] Alternatively, in one possible implementation, after the vehicle obtains the device information of the mobile terminal via the Bluetooth module, the device information is encrypted; based on the encrypted device information, the target charging protocol parameters corresponding to the device information are obtained from the server.

[0093] In a specific example, after obtaining the device information of the mobile terminal, the Bluetooth module encrypts the device information based on a preset encryption algorithm to obtain encrypted device information, and then sends the encrypted device information to the vehicle controller. The preset encryption algorithm may include, but is not limited to, Advanced Encryption Standard (AES)-128, AES-256, and Data Encryption Standard (DES) algorithms.

[0094] After receiving the encrypted device information, the vehicle controller generates an acquisition request and sends it to the server via WiFi, 4G, or 5G network. The acquisition request includes the encrypted device information. After receiving the acquisition request, the server decrypts the encrypted device information, determines whether the first charging protocol parameter exists in the cloud charging protocol library based on the decrypted device information, and executes the above steps S122~S123 to query the first charging protocol parameter or the second charging protocol parameter.

[0095] In the above technical solution, encrypting the device information and then obtaining the corresponding target charging protocol parameters from the server based on the encrypted device information can prevent the device information from being tampered with during transmission and improve the security of the vehicle charging the mobile terminal.

[0096] In some possible implementations, after decrypting the encrypted device information, the server verifies the legitimacy of the mobile terminal based on that device information. Specifically, it determines whether the mobile terminal is an authorized device by the vehicle manufacturer based on the device information. If the mobile terminal is an authorized device by the vehicle manufacturer, then the mobile terminal passes the legitimacy verification; if the mobile terminal is not an authorized device by the vehicle manufacturer, then the mobile terminal fails the legitimacy verification.

[0097] If the mobile terminal passes the legitimacy verification, the system determines whether the first charging protocol parameter exists in the cloud charging protocol library based on the decrypted device information. If the mobile terminal fails the legitimacy verification, the system sends a preset slow charging protocol parameter to the vehicle controller, which then charges the mobile terminal based on the preset slow charging protocol parameter. Alternatively, the server sends a control command to prohibit charging, and the vehicle controller stops charging the mobile terminal based on the control command.

[0098] S130 charges the mobile terminal based on the target charging protocol parameters.

[0099] In some possible implementations, the target charging protocol parameters include at least a target charging voltage and a target charging current. Specifically, charging the mobile terminal based on the target charging protocol parameters means charging the mobile terminal based on the target charging voltage and target charging current. For example, when the target charging protocol parameters are 9V / 6A, the vehicle's controller controls the vehicle's DC-DC converter to convert the high-voltage DC power output from the vehicle's power battery into a low-voltage DC power of 9V / 6A, which is then output through the aforementioned charging interface to charge the mobile terminal.

[0100] In some possible implementations, the process of charging the mobile terminal based on the target charging protocol parameters can be specifically implemented through the following steps S131 to S133.

[0101] S131, determine whether the mobile terminal supports charging with the target charging protocol parameters.

[0102] Determining whether a mobile terminal supports charging using the target charging protocol parameters can be understood as judging whether the mobile terminal has the capability to use the target charging protocol parameters at both the hardware and software levels. Based on the judgment result, a charging strategy for charging the mobile terminal is determined, realizing intelligent management of the charging process.

[0103] In some possible implementations, the vehicle includes a LIN transceiver. Specifically, it can be determined whether the mobile terminal supports charging with the target charging protocol parameters as follows: after the vehicle obtains the target charging protocol parameters from the server, it sends the target charging protocol parameters to the mobile terminal sequentially through the LIN transceiver and the charging interface; if the mobile terminal returns a first type of response information, it is determined that the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal returns a second type of response information, it is determined that the mobile terminal does not support charging with the target charging protocol parameters.

[0104] The aforementioned LIN transceiver establishes a connection with the mobile terminal through a preset pin (such as the CC pin) of the charging interface. After the vehicle controller obtains the target charging protocol parameters from the server, it sends the target charging protocol parameters to the mobile terminal to trigger protocol negotiation.

[0105] This LIN transceiver enables communication between the vehicle and the mobile terminal, avoiding parameter transmission errors and improving the reliability of the vehicle charging process.

[0106] Specifically, the protocol negotiation process is as follows: Based on its own supported protocol parameter list and its own battery status (such as temperature, remaining power, etc.), the mobile terminal selects the optimal protocol parameters (such as optimal charging voltage and optimal charging current) that are compatible with both parties from the target charging protocol parameters, and returns response information to the vehicle controller based on the selection results. The vehicle controller adjusts the output of the DC-DC converter based on the response information.

[0107] The response information may include a first type of response information and a second type of response information. The first type of response information indicates successful negotiation and the optimal charging protocol parameters supported by the mobile terminal, meaning the mobile terminal hardware and software support charging with the target charging protocol parameters. The second type of response information indicates negotiation failure, meaning the mobile terminal hardware or software does not support charging with the target charging protocol parameters.

[0108] S132, if the mobile terminal supports charging with the target charging protocol parameters, charge the mobile terminal based on the target charging protocol parameters.

[0109] S133, If the mobile terminal does not support charging with the target charging protocol parameters, the mobile terminal is charged according to the preset slow charging protocol parameters stored in the local charging protocol library.

[0110] For example, when the target charging protocol parameters are the QC4.0 version charging protocol parameters shown in Table 1: 5V / (4.7A~5.6A)~9V / 3A, the QC4.0 version charging protocol parameters are sent to the mobile terminal. If the mobile terminal determines that the optimal charging protocol parameter is 9V / 3A based on its own supported protocol parameter list and its own battery status, the mobile terminal returns a first type of response information to the vehicle. The first type of response information may include the following information: supporting charging with the QC4.0 version charging protocol parameters, and the optimal charging protocol parameter is 9V / 3A; the vehicle's controller controls the vehicle's DC-DC controller to output a current of 9V / 3A based on the first type of response information to charge the mobile terminal; if the mobile terminal only supports slow charging protocol parameters, the mobile terminal can determine that it does not support the above-mentioned QC4.0 version charging protocol parameters, and then charges the mobile terminal based on the preset slow charging protocol parameters (such as 5V / 1A).

[0111] In summary, when the mobile terminal has the capability to charge using the target charging protocol parameters, it can be charged using these parameters to achieve fast charging with optimal voltage, optimal current, or high power, reducing energy loss. When the mobile terminal does not have the capability to charge using the target charging protocol parameters, it can be charged using preset slow charging protocol parameters. This avoids subjecting the mobile terminal to power exceeding its rated range, improving the safety and compatibility of vehicle charging of the mobile terminal.

[0112] In some possible implementations, the charging method provided in this application further includes the following steps: S140~150.

[0113] S140, when charging the mobile terminal based on the target charging protocol parameters, monitor the indicator parameters of the preset indicators corresponding to the charging interface.

[0114] In this implementation, the preset indicators corresponding to the charging interface refer to the output characteristics of the charging interface during the charging process, such as the output voltage, output current, and / or the real-time temperature of the charging interface. That is, during the charging process, the parameters corresponding to the output characteristics of the charging interface are detected in real time to see if they meet the preset conditions. If the parameters of the preset indicators meet the preset conditions, the mobile terminal is charged based on the target charging protocol parameters.

[0115] S150 charges the mobile terminal according to a preset output strategy when the indicator parameters do not meet the preset conditions.

[0116] That is, if the parameters of the preset indicator do not meet the preset conditions, the output of the charging interface is adjusted to charge the device while ensuring safety, thereby improving the charging safety of the vehicle for the mobile terminal.

[0117] In some possible implementations, the target charging protocol parameters mentioned above may also include voltage thresholds, current thresholds, and / or temperature thresholds. It should be understood that the corresponding voltage thresholds, current thresholds, and temperature thresholds differ across different charging protocols.

[0118] For example, when the preset indicator includes the output voltage of the charging interface, the output voltage of the charging interface is monitored in real time; when the output voltage is less than or equal to a voltage threshold (such as 25V), it is determined that the preset indicator meets the preset condition, and the mobile terminal is charged based on the output voltage; when the output voltage is greater than the voltage threshold, it is determined that the preset indicator does not meet the preset condition, and the charging of the mobile terminal is stopped.

[0119] If the preset indicator includes the output current of the charging interface, the output current of the charging interface is monitored in real time; if the output current is less than or equal to the current threshold (such as 5A), it is determined that the preset indicator meets the preset condition, and the mobile terminal is charged based on the output current; if the output current is greater than the current threshold, it is determined that the preset indicator does not meet the preset condition, the output current of the charging interface is reduced, and the current limiting mode is entered.

[0120] If the preset parameters include the real-time temperature of the charging interface, the temperature of the charging interface is monitored in real time using a negative temperature coefficient thermistor (NTC). If the real-time temperature is less than or equal to a temperature threshold (e.g., 80°C), it is determined that the preset parameters meet the preset conditions, and the mobile terminal continues to be charged using the target charging protocol parameters. If the real-time temperature is greater than the temperature threshold, it is determined that the preset parameters do not meet the preset conditions, and the DC-DC controller is controlled to reduce power to charge the mobile terminal with lower power. For example, if the vehicle is charging the mobile terminal with 9V / 6A DC power, and the real-time temperature of the charging interface is detected to reach 85°C, which is greater than the aforementioned temperature threshold of 80°C, the DC-DC controller is controlled to output 8V / 4A DC power to charge the mobile terminal.

[0121] Figure 3 is a schematic diagram of the structure of a charging device provided in an embodiment of this application.

[0122] For example, as shown in FIG3, the charging device 200 is applied to a vehicle, which includes a charging interface and a Bluetooth module. The charging device 200 includes: an acquisition unit 201 and a charging unit 202; the acquisition unit 201 is used to acquire device information of the mobile terminal through the Bluetooth module when the mobile terminal is electrically connected to the charging interface; the acquisition unit 201 is also used to acquire target charging protocol parameters corresponding to the device information from a server; the charging unit 202 is used to charge the mobile terminal based on the target charging protocol parameters.

[0123] In one possible implementation, the acquisition unit 201 is specifically used to trigger the Bluetooth connection between the mobile terminal and the Bluetooth module; during the process of establishing a Bluetooth connection between the mobile terminal and the Bluetooth module, the device information of the mobile terminal is acquired through the Bluetooth module.

[0124] In one possible implementation, the device information includes the device brand and device model. The acquisition unit 201 is specifically used to send an acquisition request to the server, so that the server determines whether a first charging protocol parameter exists in the cloud charging protocol library based on the acquisition request. The first charging protocol parameter is a charging protocol parameter that matches both the device brand and the device model. If the first charging protocol parameter exists in the cloud charging protocol library, the server returns the first charging protocol parameter. If the first charging protocol parameter does not exist in the cloud charging protocol library, the server returns a second charging protocol parameter. The second charging protocol parameter is a charging protocol parameter determined according to a preset priority order, and the second charging protocol parameter is different from the first charging protocol parameter.

[0125] In some possible implementations, the second charging protocol parameter includes one of the following: a same-brand charging protocol parameter, a preset fast charging protocol parameter, and a preset slow charging protocol parameter; wherein the preset priority order is as follows: the same-brand charging protocol parameter has a higher priority than the preset fast charging protocol parameter, and the preset fast charging protocol parameter has a higher priority than the preset slow charging protocol parameter; the same-brand charging protocol parameter is a charging protocol parameter in the cloud charging protocol library that matches the device brand but does not match the device model.

[0126] In some possible implementations, the charging unit 202 is specifically used to determine whether the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal supports charging with the target charging protocol parameters, the mobile terminal is charged based on the target charging protocol parameters; if the mobile terminal does not support charging with the target charging protocol parameters, the mobile terminal is charged according to the preset slow charging protocol parameters stored in the local charging protocol library.

[0127] In some possible implementations, the vehicle includes a LIN transceiver and a charging unit 202, and is specifically configured to send the target charging protocol parameters to the mobile terminal sequentially through the LIN transceiver and the charging interface; if the mobile terminal returns a first type of response information, it is determined that the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal returns a second type of response information, it is determined that the mobile terminal supports charging with the target charging protocol parameters.

[0128] In some possible implementations, the target charging protocol parameters include at least a target charging voltage and a target charging current, and the charging unit 202 is specifically used to charge the mobile terminal based on the target charging voltage and the target charging current.

[0129] In some possible implementations, the charging unit 202 is further configured to monitor the indicator parameters of a preset indicator corresponding to the charging interface when charging the mobile terminal based on the target charging protocol parameters; and to charge the mobile terminal according to a preset output strategy when the indicator parameters do not meet the preset conditions.

[0130] In some possible implementations, the acquisition unit 201 is specifically used to encrypt the device information; based on the encrypted device information, the target charging protocol parameters corresponding to the device information are obtained from the server.

[0131] It should be noted that the charging device provided in the above embodiments is only an example of the division of the above functional units. In actual applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the computer device can be divided into different functional units to complete all or part of the functions described above.

[0132] The device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0133] In addition, the device provided in the embodiments of this application may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute a charging method provided in the above embodiments.

[0134] Furthermore, the charging device and charging method embodiments provided above belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here. It should be understood that the device provided in this embodiment is used to execute one of the above-described charging methods, and therefore can achieve the same effect as the above-described implementation method.

[0135] This application also protects an electronic device that may include a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform a charging method provided in this application.

[0136] This application also protects a vehicle that may include the aforementioned electronic equipment. As shown in Figure 4, Figure 4 is a structural schematic diagram of a vehicle provided in an embodiment of this application.

[0137] For example, as shown in FIG4, the vehicle 300 includes a memory 301 and a processor 302, wherein the memory 301 stores executable program code 303, and the processor 302 is used to call and execute the executable program code 303 to perform a charging method.

[0138] Furthermore, embodiments of this application also protect an apparatus that may include a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform a charging method provided in embodiments of this application.

[0139] Those skilled in the art will understand that Figure 4 is merely an example of vehicle 300 and does not constitute a limitation on vehicle 300. It may include more or fewer components than shown, or combine certain components, or different components. For example, vehicle 300 may also include input / output devices, network access devices, buses, etc.

[0140] The processor 302 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0141] The memory 301 can be an internal storage unit of the vehicle 300, such as a hard drive or RAM. The memory 301 can also be an external storage device of the vehicle 300, such as a plug-in hard drive, smart media card (SMC), secure digital card (SD), flash card, etc., installed on the vehicle 300. Furthermore, the memory 301 can include both internal and external storage units of the vehicle 300. The memory 301 is used to store the computer program and other programs and data required by the terminal device. The memory 301 can also be used to temporarily store data that has been output or will be output.

[0142] This embodiment also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, the computer executes the above-described related method steps to implement a charging method provided in the above embodiment.

[0143] The computer-readable storage medium can be volatile or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), and enhanced synchronous dynamic random access memory.

[0144] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement a charging method provided in the above embodiment.

[0145] In this embodiment, the apparatus, electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0146] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A charging method, characterized in that, Applied to a vehicle, the vehicle including a charging interface and a Bluetooth module, the method includes: when a mobile terminal is electrically connected to the charging interface, obtaining device information of the mobile terminal through the Bluetooth module; obtaining target charging protocol parameters corresponding to the device information from a server; and charging the mobile terminal based on the target charging protocol parameters.

2. The method according to claim 1, characterized in that, The step of obtaining the device information of the mobile terminal through the Bluetooth module includes: triggering a Bluetooth connection between the mobile terminal and the Bluetooth module; and obtaining the device information of the mobile terminal through the Bluetooth module during the process of establishing a Bluetooth connection between the mobile terminal and the Bluetooth module.

3. The method according to claim 1, characterized in that, The device information includes the device brand and device model. Obtaining the target charging protocol parameter corresponding to the device information from the server includes: sending an acquisition request to the server so that the server determines whether a first charging protocol parameter exists in the cloud charging protocol library based on the acquisition request; the acquisition request includes the device information, and the first charging protocol parameter is a charging protocol parameter that matches both the device brand and the device model; if the first charging protocol parameter exists in the cloud charging protocol library, receiving the first charging protocol parameter returned by the server; if the first charging protocol parameter does not exist in the cloud charging protocol library, receiving a second charging protocol parameter returned by the server, the second charging protocol parameter being a charging protocol parameter determined according to a preset priority order, and the second charging protocol parameter being different from the first charging protocol parameter.

4. The method according to claim 3, characterized in that, The second charging protocol parameters include one of the following: same-brand charging protocol parameters, preset fast charging protocol parameters, and preset slow charging protocol parameters; wherein, the preset priority order is as follows: the same-brand charging protocol parameters have a higher priority than the preset fast charging protocol parameters, and the preset fast charging protocol parameters have a higher priority than the preset slow charging protocol parameters; the same-brand charging protocol parameters are charging protocol parameters in the cloud charging protocol library that match the device brand but do not match the device model.

5. The method according to claim 1, characterized in that, The step of charging the mobile terminal based on the target charging protocol parameters includes: determining whether the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal supports charging with the target charging protocol parameters, charging the mobile terminal based on the target charging protocol parameters; if the mobile terminal does not support charging with the target charging protocol parameters, charging the mobile terminal according to preset slow charging protocol parameters stored in the local charging protocol library.

6. The method according to claim 5, characterized in that, The vehicle includes a LIN transceiver. Determining whether the mobile terminal supports charging with the target charging protocol parameters includes: sequentially sending the target charging protocol parameters to the mobile terminal through the LIN transceiver and the charging interface; if the mobile terminal returns a first type of response information, determining that the mobile terminal supports charging with the target charging protocol parameters; if the mobile terminal returns a second type of response information, determining that the mobile terminal does not support charging with the target charging protocol parameters.

7. The method according to claim 1, characterized in that, The target charging protocol parameters include at least a target charging voltage and a target charging current. Charging the mobile terminal based on the target charging protocol parameters includes charging the mobile terminal based on the target charging voltage and the target charging current.

8. The method according to claim 1, characterized in that, The method further includes: when charging the mobile terminal based on the target charging protocol parameters, monitoring the indicator parameters of a preset indicator corresponding to the charging interface; and when the indicator parameters do not meet the preset conditions, charging the mobile terminal according to a preset output strategy.

9. The method according to claim 1, characterized in that, The step of obtaining the target charging protocol parameters corresponding to the device information from the server includes: encrypting the device information; and obtaining the target charging protocol parameters corresponding to the device information from the server based on the encrypted device information.

10. A vehicle, characterized in that, The vehicle includes: a memory for storing executable program code; and a processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 9.

Images