Vehicle power management methods, systems, devices, storage media, and software products

Abstract

This application provides a vehicle power management method, system, device, storage medium, and program product. It includes: a power monitoring module detecting the battery's pre-charging charge level; and when the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, waking up the PEPS controller to send a first message to the PEPS controller. The first message requests intelligent vehicle start to charge the battery. The PEPS controller sends the first message to a user terminal. Upon receiving the charging command from the user terminal, the PEPS controller unlocks the vehicle's electronic steering column lock. When the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start to charge the battery. This method proactively prompts the user that the battery needs charging, and with the user's permission, allows for remote vehicle start-up to charge the battery, eliminating the need for the user to periodically start the vehicle to charge the battery.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a vehicle power management method, system, device, storage medium, and program product. Background Technology

[0002] With the rapid development of electronic and intelligent technologies in commercial vehicles, the number of electronic components integrated inside vehicles is increasing daily. This not only enhances the functionality and intelligence of vehicles but also places more stringent demands on the vehicle's power management system. The vehicle battery, as a core component for vehicle starting, directly affects whether the vehicle can start smoothly.

[0003] However, when batteries are left unused for extended periods, they will naturally discharge. Furthermore, some users may improperly use in-vehicle electrical appliances when the engine is not running, which will accelerate battery depletion and, in severe cases, deplete the battery completely, thus affecting the vehicle's starting ability. Current technology primarily guides users on proper operation through the user manual and recommends that users periodically start the vehicle to charge the battery to ensure normal vehicle starting.

[0004] However, when users are away on business trips or when the vehicle is not used frequently, they may forget to start the vehicle regularly to charge the battery, which can lead to the battery running out of power and ultimately prevent the vehicle from starting. Summary of the Invention

[0005] This application provides a vehicle power management method, system, device, storage medium, and program product, which enables the vehicle to actively detect the battery level and proactively prompt the user when the user cannot start the vehicle regularly to charge the battery. With the user's permission, the vehicle can be remotely started to charge the battery.

[0006] In a first aspect, embodiments of this application provide a vehicle power management method applied to a vehicle power management system. The power management system includes: a power monitoring module, a keyless entry and exit system (PEPS) controller, a central gateway controller, a vehicle black box (TBOX), a cloud server, and a user terminal. The power monitoring module is communicatively connected to the PEPS controller via a LIN bus. The central gateway controller is connected to both the PEPS controller and the TBOX via a CAN bus. The cloud server is communicatively connected to both the TBOX and the user terminal. The method includes:

[0007] The power monitoring module detects the pre-charging charge level of the vehicle's battery. When the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, the module wakes up the PEPS controller to send a first message to the PEPS controller. The first message is used to request the intelligent start of the vehicle to charge the battery. The second charge threshold is less than the first charge threshold.

[0008] The PEPS controller sends the first message to the user terminal sequentially via the central gateway controller, the TBOX, and the cloud server;

[0009] When the PEPS controller receives a charging command sent sequentially by the user terminal via the cloud server, the TBOX, and the central gateway controller, it unlocks the electronic steering column lock of the vehicle.

[0010] When the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start in order to charge the battery.

[0011] In one possible implementation, the PEPS controller controls the vehicle's engine to start in order to charge the battery, including:

[0012] During the charging process, the power monitoring module continuously monitors the charging progress and sends the charging progress to the PEPS controller. The charging progress includes at least one of the following: charging time and charging progress.

[0013] When the charging progress meets the preset conditions, the PEPS controller controls the engine to continue running. The preset conditions include at least one of the following: the charging time is less than or equal to a preset time threshold, the amount of electricity being charged is less than or equal to a third electricity threshold, and the third electricity threshold is greater than the first electricity threshold.

[0014] When the charging progress does not meet the preset conditions, the PEPS controller controls the engine to stop running.

[0015] In one possible implementation, the PEPS controller controls the engine to stop operating, including:

[0016] The PEPS controller sequentially sends a second message to the user terminal via the central gateway controller, the TBOX, and the cloud server. The second message is used to request whether to end charging and includes the charging progress.

[0017] When the user terminal receives a charging control command input by the user, it sequentially sends charging control information to the PEPS controller via the cloud server, the TBOX, and the central gateway controller.

[0018] When the charging control information is charging completion information, the engine is controlled to stop running;

[0019] When the charging control information is charging continue, the engine is controlled to continue running until the vehicle's charging charge is fully charged, at which point the engine is controlled to stop running.

[0020] In one possible implementation, the method further includes:

[0021] When the engine is stopped, the PEPS controller locks the electronic steering column and switches the main switch of the battery to the off state. When the main switch of the battery is off, the battery stops supplying power to the vehicle's electrical equipment.

[0022] In one possible implementation, it also includes:

[0023] When the electronic steering column lock fails to unlock, the PEPS controller sends a third message to the user terminal via the central gateway controller, the TBOX, and the cloud server in sequence, and controls the electronic steering column lock to lock. The third message is used to indicate that the reason for the charging failure is that the electronic steering column lock failed to unlock.

[0024] In one possible implementation, when the battery charge is less than or equal to the second charge threshold before charging, the power monitoring module wakes up the PEPS controller to send a fourth message to the PEPS controller, wherein the second charge threshold is less than the first charge threshold, and the fourth message is used to indicate that the battery charge is insufficient to intelligently start the vehicle.

[0025] The PEPS controller sends the fourth message sequentially to the user terminal via the central gateway controller, the TBOX, and the cloud server, and adjusts the battery status to the off state.

[0026] In one possible implementation, the user terminal receives setting information input by the user, the setting information including at least one of the following: a first control parameter of the power monitoring module, or a second control parameter of the PEPS controller, the first control parameter including at least one of the following: a first power threshold, a second power threshold, the second control parameter including at least one of the following: a preset duration threshold, a third power threshold, and one or more information templates, the information templates being used to indicate the format of any information in the first message, the second message, the third message, or the fourth message;

[0027] The user terminal sends the setting information sequentially through the cloud server, the TBOX, and the central gateway controller to the PEPS controller;

[0028] When the setting information includes the first control parameter, the PEPS controller forwards the first control parameter to the power monitoring module.

[0029] In one possible implementation, it also includes:

[0030] If the power monitoring module does not receive the charging command, it returns to the step of detecting the pre-charging charge level of the vehicle's battery.

[0031] Secondly, embodiments of this application provide a vehicle power management system, including: a power monitoring module, a keyless entry system PEPS controller, a central gateway controller, a vehicle black box TBOX, a cloud server, and a user terminal;

[0032] The power monitoring module is used to detect the pre-charging charge level of the vehicle's battery, and when the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, wake up the PEPS controller to send a first message to the PEPS controller. The first message is used to request the intelligent start of the vehicle to charge the battery, and the second charge threshold is less than the first charge threshold.

[0033] The PEPS controller is used to send the first message to the user terminal sequentially via the central gateway controller, the TBOX, and the cloud server.

[0034] The PEPS controller is used to unlock the electronic steering column lock of the vehicle when it receives a charging command sent by the user terminal sequentially via the cloud server, the TBOX, and the central gateway controller.

[0035] When the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start in order to charge the battery.

[0036] In a vehicle power management system provided in this application:

[0037] During the charging process, the power monitoring module is used to continuously monitor the charging progress and send the charging progress to the PEPS controller. The charging progress includes at least one of the following: charging time and charging power.

[0038] When the charging progress meets the preset conditions, the PEPS controller is used to control the engine to continue running. The preset conditions include at least one of the following conditions: the charging time is less than or equal to a preset time threshold, the charging charge is less than or equal to a third charge threshold, and the third charge threshold is greater than the first charge threshold.

[0039] When the charging progress does not meet the preset conditions, the PEPS controller is used to control the engine to stop running.

[0040] In a vehicle power management system provided in this application:

[0041] The PEPS controller is used to send a second message to the user terminal sequentially via the central gateway controller, the TBOX, and the cloud server. The second message is used to request whether to end charging and includes the charging progress.

[0042] The user terminal is used to send charging control information to the PEPS controller sequentially via the cloud server, the TBOX, and the central gateway controller when it receives a charging control command input by the user.

[0043] When the charging control information is charging completion information, the engine is controlled to stop running;

[0044] When the charging control information is charging continue, the engine is controlled to continue running until the vehicle's charging charge is fully charged, at which point the engine is controlled to stop running.

[0045] In a vehicle power management system provided in this application:

[0046] When the engine is stopped, the PEPS controller controls the electronic power steering column lock to lock and switches the main switch of the battery to the off state. When the main switch of the battery is off, the battery stops supplying power to the vehicle's electrical equipment.

[0047] In a vehicle power management system provided in this application:

[0048] When the electronic steering column lock fails to unlock, the PEPS controller is used to send a third message to the user terminal in sequence via the central gateway controller, the TBOX, and the cloud server, and control the electronic steering column lock to lock. The third message is used to indicate that the reason for the charging failure is that the electronic steering column lock failed to unlock.

[0049] In a vehicle power management system provided in this application:

[0050] When the battery level is less than or equal to the second battery level threshold before charging, the power monitoring module is used to wake up the PEPS controller and send a fourth message to the PEPS controller. The second battery level threshold is less than the first battery level threshold. The fourth message is used to indicate that the battery level is insufficient to start the vehicle intelligently.

[0051] The PEPS controller is used to send the fourth message to the user terminal sequentially via the central gateway controller, the TBOX, and the cloud server, and adjust the state of the battery to the off state.

[0052] In a vehicle power management system provided in this application:

[0053] The user terminal is used to receive setting information input by the user. The setting information includes at least one of the following: a first control parameter of the power monitoring module or a second control parameter of the PEPS controller. The first control parameter includes at least one of the following: a first power threshold and a second power threshold. The second control parameter includes at least one of the following: a preset duration threshold, a third power threshold, and one or more information templates. The information templates are used to indicate the format of any information in the first message, the second message, the third message, or the fourth message.

[0054] The user terminal is used to send the setting information to the PEPS controller via the cloud server, the TBOX, and the central gateway controller in sequence.

[0055] When the setting information includes the first control parameter, the PEPS controller is used to forward the first control parameter to the power monitoring module.

[0056] In a vehicle power management system provided in this application:

[0057] The power monitoring module is used to return to the step of detecting the pre-charging power level of the vehicle's battery when no charging command is received.

[0058] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0059] The memory stores computer-executed instructions;

[0060] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0061] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0062] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0063] This application provides a vehicle power management method, system, device, storage medium, and program product. A power monitoring module detects the pre-charging battery charge level of the vehicle's battery. When the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, the module wakes up the PEPS controller to send a first message to the PEPS controller. The first message requests intelligent vehicle start to charge the battery. The second charge threshold is less than the first charge threshold. The PEPS controller sequentially sends the first message to the user terminal via the central gateway controller, TBOX, and cloud server. Then, upon receiving the charging command sent by the user terminal sequentially via the cloud server, TBOX, and central gateway controller, the PEPS controller unlocks the vehicle's electronic steering column lock. Finally, when the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start to charge the battery. Compared to existing technologies that require users to periodically visit the vehicle to start and charge the battery, this application's power monitoring module continuously monitors the battery's charge level. When the battery charge is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, it sends a message to the user terminal to remind the user that the vehicle needs charging. Upon receiving the charging instruction, the user sends a charging command to the PEPS controller, causing the PEPS controller to start the vehicle's engine to charge the battery. This eliminates the need for users to periodically visit the vehicle to start and charge the battery. Instead, by actively monitoring the battery charge level and proactively reminding the user that the battery needs charging, the user can remotely start the vehicle to charge the battery with their permission. Attached Figure Description

[0064] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0065] Figure 1 This is a schematic diagram illustrating an application scenario of the vehicle power management method applicable to embodiments of this application;

[0066] Figure 2 A flowchart illustrating an embodiment of a vehicle power management method provided in this application;

[0067] Figure 3 A flowchart illustrating a second embodiment of a vehicle power management method provided in this application;

[0068] Figure 4 A flowchart illustrating a third embodiment of a vehicle power management method provided in this application;

[0069] Figure 5 A flowchart illustrating a fourth embodiment of a vehicle power management method provided in this application;

[0070] Figure 6 A flowchart illustrating a fifth embodiment of a vehicle power management method provided in this application;

[0071] Figure 7 A schematic diagram of a vehicle power management system provided in an embodiment of this application;

[0072] Figure 8 A schematic diagram of the structure of the electronic device provided in this application.

[0073] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0074] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0075] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0076] In existing technologies, user manuals are needed to guide users to operate the vehicle correctly, and it is recommended that users start the vehicle regularly to charge the battery. However, in scenarios such as business trips or infrequent vehicle use, users may forget to start the vehicle regularly to charge the battery, resulting in the battery being depleted and ultimately preventing the vehicle from starting normally.

[0077] Based on this, the inventive concept of this application lies in providing a vehicle power management method that eliminates the need for users to periodically start the vehicle to charge the battery. Instead, it allows users to remotely start the vehicle to charge the battery when it needs charging. Specifically, a power monitoring module continuously monitors the battery level. When the battery level is low, a message is sent to the user terminal to remind them to start the vehicle to charge the battery. When the user agrees to charge the battery via their terminal, the PEPS controller automatically starts the vehicle's engine to charge the battery. Therefore, it eliminates the need for users to periodically start the vehicle to charge the battery, preventing situations where, due to infrequent vehicle use, forgetting to start the vehicle can lead to a depleted battery and ultimately prevent the vehicle from starting normally.

[0078] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0079] Figure 1 This is a schematic diagram illustrating an application scenario of the vehicle power management method applicable to embodiments of this application, such as... Figure 1 As shown, the power monitoring module is responsible for continuously monitoring the battery's charge level. When the battery charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, it wakes up the PEPS controller and sends a message to the PEPS controller requesting the vehicle to start charging the battery. After receiving the message, the PEPS controller sends it to the user terminal via the central gateway controller, TBOX, and cloud server for the user to view. After receiving the message requesting the vehicle to start charging the battery, the user enters a charging command on the user terminal. The charging command is then sent to the PEPS controller via the cloud server, TBOX, and central gateway controller. After receiving the charging command, the PEPS controller controls the vehicle's generator to start to charge the battery.

[0080] Figure 2 A flowchart illustrating an embodiment of a vehicle power management method provided in this application is shown below. Figure 2 As shown, the method includes the following steps:

[0081] S201: The power monitoring module detects the pre-charging charge level of the vehicle's battery. When the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, the module wakes up the PEPS controller to send a first message to the PEPS controller. The first message is used to request intelligent vehicle start to charge the battery. The second charge threshold is less than the first charge threshold.

[0082] In this embodiment, the vehicle power management method is applied to the vehicle power management system, which includes: a power monitoring module, a keyless entry system (PEPS) controller, a central gateway controller, a vehicle black box (TBOX), a cloud server, and a user terminal.

[0083] The power monitoring module is responsible for continuously or periodically monitoring the pre-charging battery level of the vehicle. The pre-charging battery level refers to the remaining battery power before the vehicle is started for charging. When the power monitoring module detects that the pre-charging battery level is less than or equal to a first battery level threshold and greater than or equal to a second battery level threshold (optionally, the first threshold is 30% of the battery capacity and the second threshold is 10% of the battery capacity), the power monitoring module wakes up the PEPS controller via the Local Area Network Bus (LIN) and sends a first message to the PEPS controller via the LIN bus to request intelligent vehicle start to charge the battery.

[0084] For example, the power monitoring module sends a specific wake-up frame to wake up the PEPS controller via the Local Interconnect Network (LIN) bus. After receiving the wake-up frame, the PEPS controller exits the sleep mode and enters the working state. Subsequently, the power monitoring module constructs a message frame containing the first message according to the LIN protocol specification. When the PEPS controller receives the message frame containing the first message, it parses it and then requests the intelligent start of the vehicle to charge the battery based on the first message.

[0085] S202: The PEPS controller sends the first message to the user terminal sequentially via the central gateway controller, TBOX, and cloud server.

[0086] In this embodiment, after receiving the first message, the PEPS controller sequentially sends it to the user terminal via the central gateway controller, the TBOX, and the cloud server. Specifically, when the PEPS controller sends the first message to the user terminal, it first sends it to the central gateway controller via the local area network CAN line. The central gateway controller then sends it to the TBOX via the local area network CAN line. After receiving the first message, the TBOX sends it to the cloud server. The cloud server is the central node for data exchange and storage between the vehicle and the outside world. After receiving the first message, the cloud server forwards it to the user terminal via SMS, email, or APP push to inform the user of the vehicle's battery status. Optionally, the TBOX communicates with the cloud server using cellular networks or other wireless communication technologies, and the cloud server can also communicate with the user terminal using cellular networks or other wireless communication technologies. The PEPS controller and the central gateway controller, as well as the central gateway controller and the TBOX, mutually authenticate each other before transmitting information via the CAN line.

[0087] S203: When the PEPS controller receives a charging command sent sequentially from the user terminal via the cloud server, TBOX, and central gateway controller, it unlocks the vehicle's electronic steering column lock.

[0088] In this embodiment, after receiving the first message from the PEPS controller, the user terminal can send a charging command to the PEPS controller. After receiving the charging command, the PEPS controller will first verify the legality and validity of the command. If the verification is successful, the PEPS controller will send an unlocking command to the Electronic Steering Column Lock (ESCL). After receiving the unlocking command, the Electronic Steering Column Lock will perform an unlocking operation to allow the steering wheel to be turned, thereby starting the engine.

[0089] The path by which the user terminal sends the charging command to the PEPS controller is as follows: the user terminal sends the charging command to the cloud server via cellular network or other wireless communication technology. After receiving the charging command, the cloud server also sends it to the TBOX via cellular network or other wireless communication technology. When the TBOX receives the charging command, it sends the charging command to the central gateway controller via the local area network CAN line. When the central gateway controller receives the charging command, it then sends the charging command to the PEPS controller via the local area network CAN line.

[0090] When the power monitoring module does not receive a charging command, it returns to the step of checking the battery level of the vehicle before charging.

[0091] In this embodiment, when the power monitoring module does not receive the charging instruction in the first message, the power monitoring module returns to step S201, that is, the power monitoring module continues to perform its function of detecting the pre-charging charge level of the vehicle's battery, ensuring the continuous operation of the vehicle power management system and real-time monitoring of the battery charge level, providing users with a more reliable and safer vehicle usage experience.

[0092] S204: When the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start in order to charge the battery.

[0093] In this embodiment of the application, when the electronic steering column lock is successfully unlocked, (other conditions are checked: whether the vehicle is in a safe state, the PEPS controller controls the vehicle's engine to start in order to charge the battery).

[0094] When the electronic steering column lock fails to unlock, it also includes:

[0095] When the electronic steering column lock fails to unlock, the PEPS controller sends a third message to the user terminal via the central gateway controller, TBOX, and cloud server in sequence, and controls the electronic steering column lock to lock. The third message is used to indicate that the reason for the charging failure is that the electronic steering column lock failed to unlock.

[0096] In this embodiment, when the electronic steering column lock fails to unlock, the PEPS controller sends a third message to the user terminal, indicating a charging failure to the user. This prompts the user to manually start the vehicle for charging. The PEPS controller also keeps the electronic steering column lock locked to prevent vehicle theft or accidental operation, ensuring the safety of the vehicle and its occupants. The third message indicates to the user that the charging failure is due to the electronic steering column lock failing to unlock. The PEPS controller sends the third message to the user terminal sequentially via the central gateway controller, TBOX, and cloud server.

[0097] In this embodiment, the power monitoring module detects the pre-charging charge level of the vehicle's battery. When the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, the module wakes up the PEPS controller to send a first message to the PEPS controller. The first message requests intelligent vehicle start to charge the battery. The second charge threshold is less than the first charge threshold. The PEPS controller sends the first message sequentially to the user terminal via the central gateway controller, TBOX, and cloud server. Then, when the PEPS controller receives the charging command sent by the user terminal sequentially via the cloud server, TBOX, and central gateway controller, it unlocks the vehicle's electronic steering column lock. Finally, when the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start to charge the battery. Compared to existing technologies that require users to periodically start the vehicle to charge the battery, the power monitoring module of this application continuously monitors the battery level. When the battery level is less than or equal to a first power threshold and greater than or equal to a second power threshold, it sends a message to the user terminal to remind the user that the vehicle needs charging. Upon receiving the charging instruction, the user sends a charging command to the PEPS controller, causing the PEPS controller to start the vehicle's engine to charge the battery. This eliminates the need for the user to go to the vehicle's location to periodically start the vehicle to charge the battery. Instead, by actively monitoring the battery level and proactively reminding the user that the battery needs charging, the user can remotely start the vehicle to charge the battery with their permission.

[0098] Figure 3 This is a flowchart illustrating a second embodiment of a vehicle power management method provided in this application. Figure 2 Based on the illustrated embodiment, one specific implementation of step S204 is as follows:

[0099] S301: During the charging process, the power monitoring module continuously monitors the charging progress and sends the charging progress to the PEPS controller. The charging progress includes at least one of the following: charging time and charging power.

[0100] In this embodiment of the application, when the engine is charging the battery, the power monitoring module continuously monitors the charging progress, which includes the charging duration and / or the amount of electricity being charged. The power monitoring module also sends the charging duration and / or the amount of electricity being charged to the PEPS controller via the Local Interconnect Network Bus (LIN).

[0101] S302: When the charging progress meets the preset conditions, the PEPS controller controls the engine to continue running. The preset conditions include at least one of the following: the charging time is less than or equal to a preset time threshold, the charging power is less than or equal to a third power threshold, and the third power threshold is greater than the first power threshold.

[0102] In this embodiment, when the charging progress meets preset conditions, the PEPS controller controls the engine to continue running to complete the charging process. Optionally, the preset conditions are: the charging time is less than or equal to a preset time threshold, and the charging charge is less than or equal to a third charge threshold, wherein the third charge threshold is greater than a first charge threshold. In other words, charging completion can be ensured by setting a charging time or by monitoring the charging charge. The preset charging time threshold can be determined based on the average of typical charging times, and the third charge threshold is greater than 30% of the battery capacity. Optionally, the third charge threshold is 100% or 90% of the battery charge.

[0103] S303: When the charging progress does not meet the preset conditions, the PEPS controller controls the engine to stop running.

[0104] In this embodiment of the application, when the charging progress does not meet the preset conditions, that is, the charging time is greater than the preset time threshold, and / or the charging power is greater than the third power threshold, the PEPS controller controls the engine to stop running in order to cut off the charging of the battery.

[0105] After the PEPS controller stops the engine from running when the charging progress does not meet the preset conditions, it also includes:

[0106] When the engine is stopped, the PEPS controller locks the electronic power steering column and switches the main battery switch to the off state. With the main battery switch off, the battery stops supplying power to the vehicle's electrical equipment.

[0107] In this embodiment, when the engine stops running and ceases charging the battery, the PEPS controller locks the electronic power steering column to prevent vehicle theft or accidental operation after the engine stops. The PEPS controller then switches the battery's main power switch (KL30 electromagnetic switch) to the off state. At this time, the battery stops supplying power to the vehicle's electrical equipment, preventing it from continuing to discharge when the engine is not running, ensuring sufficient battery charge, and thus extending battery life.

[0108] Optionally, the PEPS controller can also control the switching of the ACC relay, IGN1 relay, and IGN2 relay. For example, during ignition, since the power consumption is relatively large, the PEPS controller can control the ACC relay and IGN1 relay to turn off to stop powering the large screen and other devices, while only turning on the IGN2 relay to power the ignition device.

[0109] In this embodiment, during the charging process, the power monitoring module continuously monitors the charging progress and sends the charging progress to the PEPS controller. The charging progress includes at least one of the following: charging time and charging charge level. When the charging progress meets preset conditions, the PEPS controller controls the engine to continue running. The preset conditions include at least one of the following: charging time is less than or equal to a preset time threshold, charging charge level is less than or equal to a third charge level threshold, and the third charge level threshold is greater than a first charge level threshold. When the charging progress does not meet the preset conditions, the PEPS controller controls the engine to stop running. By continuously monitoring the charging progress during the charging process, the power monitoring module ensures that the battery reaches the target state during charging, and when the target state is reached, the PEPS controller controls the engine to stop running, thereby saving energy and avoiding overcharging that could damage the battery, thus ensuring the efficiency and safety of the battery charging process.

[0110] Figure 4 This is a flowchart illustrating a third embodiment of a vehicle power management method provided in this application. Figure 3 Based on the illustrated embodiment, one specific implementation of step S303 is as follows:

[0111] S401: The PEPS controller sends a second message to the user terminal sequentially via the central gateway controller, TBOX, and cloud server. The second message is used to request whether to end charging and includes the charging progress.

[0112] In this embodiment, during the charging process, the power monitoring module continuously monitors the charging progress and sends it to the PEPS controller. The PEPS controller then transmits the charging progress to the user terminal via the central gateway controller, TBOX, and cloud server. Specifically, after receiving the charging progress from the power monitoring module, the PEPS controller sends it to the central gateway controller via the local area network CAN line. The central gateway controller then sends it to the TBOX via the local area network CAN line. Upon receiving the charging progress, the TBOX sends it to the cloud server. The cloud server, upon receiving the charging progress, forwards it to the user terminal to inform the user of the vehicle's charging progress.

[0113] Optionally, the PEPS controller can periodically send a second message to the user terminal to remind the user whether the battery charging process needs to be terminated.

[0114] S402: When the user terminal receives the charging control command input by the user, it sends the charging control information to the PEPS controller in sequence through the cloud server, TBOX, and central gateway controller.

[0115] In this embodiment, after receiving the charging progress, the user terminal displays the current charging progress to the user and waits for the user to input a charging control command. The charging control command is used to instruct charging control information according to the user's needs. The charging control information is then sent to the PEPS controller via the cloud server, TBOX, and central gateway controller. Specifically, after the user terminal generates charging control information based on the user's input charging control command, the user terminal sends the charging control information to the cloud server via a cellular network or other wireless communication technology. After receiving the charging control information, the cloud server also sends it to the TBOX via a cellular network or other wireless communication technology. When the TBOX receives the charging control information, it sends the charging control information to the central gateway controller via the local area network CAN line. When the central gateway controller receives the charging control information, it then sends the charging command to the PEPS controller via the local area network CAN line.

[0116] S403: When the charging control information is charging complete, control the engine to stop running.

[0117] In this embodiment of the application, when the charging control information is charging end information, the PEPS controller will control the engine to stop running in order to end the charging of the battery.

[0118] S404: When the charging control information is "charging continue", the engine is controlled to continue running until the vehicle's charging charge is fully charged, at which point the engine is controlled to stop running.

[0119] In this embodiment, when the charging control information is charging continue information, the PEPS controller will control the engine to continue running until the vehicle's charging charge is fully charged. Only then will the PEPS controller control the engine to stop running, thereby ending the charging of the battery.

[0120] In this embodiment, the PEPS controller sequentially sends a second message to the user terminal via the central gateway controller, TBOX, and cloud server. The second message requests whether to end charging and includes the charging progress. When the user terminal receives the user's charging control command, it sequentially sends charging control information to the PEPS controller via the cloud server, TBOX, and central gateway controller. When the charging control information indicates charging is complete, the engine stops running; when it indicates charging continues, the engine continues running until the vehicle is fully charged, at which point the engine stops running. By sending the charging progress to the user terminal, users can flexibly decide whether to end charging based on their time and power needs, improving charging convenience. Furthermore, users can rationally plan their charging time based on the charging progress, choosing to charge during periods of lower electricity prices, reducing charging costs and also lessening the load on the power grid.

[0121] Figure 5 A flowchart illustrating a fourth embodiment of a vehicle power management method provided in this application is shown below. Figure 5 As shown, the method includes the following steps:

[0122] S501: When the battery charge is less than or equal to the second charge threshold before charging, the power monitoring module wakes up the PEPS controller to send a fourth message to the PEPS controller. The second charge threshold is less than the first charge threshold. The fourth message is used to indicate that the battery charge is insufficient to start the vehicle intelligently.

[0123] In this embodiment of the application, when the power monitoring module detects that the charge level before charging is less than or equal to the second charge threshold, that is, when the charge level before charging is less than or equal to 10% of the battery charge, the power monitoring module will wake up the PEPS controller. After the PEPS controller is woken up, it will send a response to the power monitoring module to indicate that the PEPS controller is ready to receive messages. The power monitoring module then sends a fourth message to the PEPS controller to indicate that the battery charge is insufficient to start the vehicle intelligently.

[0124] S502: The PEPS controller sends the fourth message sequentially to the user terminal via the central gateway controller, TBOX, and cloud server, and adjusts the battery status to the off state.

[0125] In this embodiment of the application, after receiving the fourth message, PEPS will send the fourth message to the user terminal in sequence through the central gateway controller, TBOX, and cloud server. The PEPS controller will adjust the battery status to the off state, that is, cut off the KL30 electromagnetic power main switch of the battery to reduce unnecessary power consumption, and then wait for the user to go to the vehicle location to start the vehicle with the physical key.

[0126] In this embodiment, when the battery level is less than or equal to a second battery level threshold before charging, the power monitoring module wakes up the PEPS controller to send a fourth message to the PEPS controller. The second battery level threshold is less than the first battery level threshold. The fourth message indicates that the battery power is insufficient for intelligent vehicle start. Then, the PEPS controller sends the fourth message sequentially to the user terminal via the central gateway controller, TBOX, and cloud server, and adjusts the battery status to the off state. This avoids battery damage or vehicle start failure due to depletion of battery power. By sending a notification to the user terminal when the battery power drops to a low level but is not yet depleted, the user can go to the vehicle's location and use the physical key to start the vehicle when intelligent start is not possible, avoiding the embarrassing situation of the user being unable to start the vehicle due to depletion of battery power.

[0127] Figure 6 A flowchart illustrating a fifth embodiment of a vehicle power management method provided in this application is shown below. Figure 6 As shown, the method includes the following steps:

[0128] S601: The user terminal receives setting information input by the user. The setting information includes at least one of the following: a first control parameter of the power monitoring module or a second control parameter of the PEPS controller. The first control parameter includes at least one of the following: a first power threshold and a second power threshold. The second control parameter includes at least one of the following: a preset duration threshold, a third power threshold, and one or more information templates. The information templates are used to indicate the format of any information in the first message, second message, third message, or fourth message.

[0129] In this embodiment, the user can input setting information through a user terminal. This setting information is used to adjust relevant parameters of the vehicle power management system. The setting information includes: first control parameters of the power monitoring module and / or second control parameters of the PEPS controller. The first parameters include: a first power threshold and / or a second power threshold, which are used to trigger the alarm mechanism of the power monitoring module. The second parameters include: a preset duration threshold, a third power threshold, and one or more information templates, which are used to define the format of a first, second, third, or fourth message sent to the user.

[0130] S602: The user terminal sends the setting information to the PEPS controller via the cloud server, TBOX, and central gateway controller in sequence.

[0131] In this embodiment, the user terminal sends the setting information to the PEPS controller via the cloud server, TBOX, and central gateway controller, so that the PEPS controller adjusts the relevant parameters of the vehicle power management system according to the setting information.

[0132] S603: When the setting information includes the first control parameter, the PEPS controller forwards the first control parameter to the power monitoring module.

[0133] In this embodiment, when the PEPS controller receives the setting information input by the user terminal, it determines whether the setting information includes a first control parameter. If the setting information includes the first control parameter, the PEPS controller forwards the first control parameter to the power monitoring module, so that the power monitoring module can trigger the alarm mechanism of the power monitoring module according to the first power threshold and the second power threshold in the first parameter.

[0134] In this embodiment, the user terminal receives setting information input by the user. This setting information includes at least one of the following: a first control parameter of the power monitoring module or a second control parameter of the PEPS controller. The user terminal then sequentially sends the setting information through the cloud server, TBOX, and central gateway controller to the PEPS controller. When the setting information includes the first control parameter, the PEPS controller forwards the first control parameter to the power monitoring module. This allows users to customize the relevant parameters of the power management system according to their needs and preferences through the user terminal, thus adapting to different user habits and vehicle usage scenarios.

[0135] Figure 7 This is a schematic diagram of a vehicle power management system provided in an embodiment of this application. Figure 7 As shown, the vehicle's power management system includes: a power monitoring module 701, a keyless system PEPS controller 702, a central gateway controller 703, a vehicle black box TBOX 704, a cloud server 705, and a user terminal 706.

[0136] The power monitoring module 701 is used to detect the pre-charging charge level of the vehicle's battery. When the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, it wakes up the PEPS controller 702 to send a first message to the PEPS controller 702. The first message requests intelligent vehicle start to charge the battery. The second charge threshold is less than the first charge threshold. The PEPS controller 702 is used to send the first message sequentially to the user terminal 706 via the central gateway controller 703, TBOX 704, and cloud server 705. When the PEPS controller 702 receives the charging command sent by the user terminal 706 sequentially via the cloud server 705, TBOX 704, and central gateway controller 703, it unlocks the vehicle's electronic steering column lock. When the electronic steering column lock is successfully unlocked, the PEPS controller 702 controls the vehicle's engine to start to charge the battery.

[0137] The vehicle power management system provided in this application embodiment can be used to execute the technical solution of the vehicle power management method in the above embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0138] Figure 8 A schematic diagram of the structure of the electronic device provided in this application. Figure 8 As shown, the electronic device 80 provided in this embodiment includes at least one processor 801 and a memory 802. Optionally, the device 80 further includes a communication component 803. The processor 801, memory 802, and communication component 803 are connected via a bus 804.

[0139] In a specific implementation, at least one processor 801 executes computer execution instructions stored in memory 802, causing at least one processor 801 to perform the above-described method.

[0140] The specific implementation process of processor 801 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0141] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0142] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0143] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0144] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0145] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0146] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0147] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0148] The division of units is merely 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 system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0149] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0150] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0151] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0152] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0153] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A vehicle power management method, characterized in that, A power management system for vehicles, comprising: a power monitoring module, a keyless entry and exit system (PEPS) controller, a central gateway controller, a vehicle black box (TBOX), a cloud server, and a user terminal. The power monitoring module and the PEPS controller are communicatively connected via a LIN bus. The central gateway controller is connected to both the PEPS controller and the TBOX via a CAN bus. The cloud server is communicatively connected to both the TBOX and the user terminal. The method includes: The power monitoring module detects the pre-charging charge level of the vehicle's battery. When the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, the module wakes up the PEPS controller to send a first message to the PEPS controller. The first message is used to request the intelligent start of the vehicle to charge the battery. The second charge threshold is less than the first charge threshold. The PEPS controller sends the first message to the user terminal sequentially via the central gateway controller, the TBOX, and the cloud server; When the PEPS controller receives a charging command sent sequentially by the user terminal via the cloud server, the TBOX, and the central gateway controller, it unlocks the electronic steering column lock of the vehicle. When the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start to charge the battery, including: during the charging process, the power monitoring module continuously monitors the charging progress and sends the charging progress to the PEPS controller, the charging progress including at least one of the following: charging time, charging charge level; when the charging progress meets preset conditions, the PEPS controller controls the engine to continue running, the preset conditions including at least one of the following: the charging time is less than or equal to a preset time threshold, the charging charge level is less than or equal to a third charge level threshold, and the third charge level threshold is greater than the first charge level threshold; when the charging progress does not meet the preset conditions, the PEPS controller controls the engine to stop running.

2. The method according to claim 1, characterized in that, The PEPS controller controls the engine to stop running, including: The PEPS controller sequentially sends a second message to the user terminal via the central gateway controller, the TBOX, and the cloud server. The second message is used to request whether to end charging and includes the charging progress. When the user terminal receives a charging control command input by the user, it sequentially sends charging control information to the PEPS controller via the cloud server, the TBOX, and the central gateway controller. When the charging control information is charging completion information, the engine is controlled to stop running; When the charging control information is charging continue, the engine is controlled to continue running until the vehicle's charging charge is fully charged, at which point the engine is controlled to stop running.

3. The method according to claim 1, characterized in that, The method further includes: When the engine is stopped, the PEPS controller locks the electronic steering column and switches the main switch of the battery to the off state. When the main switch of the battery is off, the battery stops supplying power to the vehicle's electrical equipment.

4. The method according to claim 2, characterized in that, Also includes: When the electronic steering column lock fails to unlock, the PEPS controller sends a third message to the user terminal via the central gateway controller, the TBOX, and the cloud server in sequence, and controls the electronic steering column lock to lock. The third message is used to indicate that the reason for the charging failure is that the electronic steering column lock failed to unlock.

5. The method according to claim 4, characterized in that, Also includes: When the battery level is less than or equal to the second battery level threshold before charging, the power monitoring module wakes up the PEPS controller to send a fourth message to the PEPS controller. The second battery level threshold is less than the first battery level threshold. The fourth message is used to indicate that the battery level is insufficient to start the vehicle intelligently. The PEPS controller sends the fourth message sequentially to the user terminal via the central gateway controller, the TBOX, and the cloud server, and adjusts the battery status to the off state.

6. The method according to claim 5, characterized in that, Also includes: The user terminal receives setting information input by the user. The setting information includes at least one of the following: a first control parameter of the power monitoring module or a second control parameter of the PEPS controller. The first control parameter includes at least one of the following: a first power threshold and a second power threshold. The second control parameter includes at least one of the following: a preset duration threshold, a third power threshold, and one or more information templates. The information templates are used to indicate the format of any information in the first message, the second message, the third message, or the fourth message. The user terminal sends the setting information sequentially through the cloud server, the TBOX, and the central gateway controller to the PEPS controller; When the setting information includes the first control parameter, the PEPS controller forwards the first control parameter to the power monitoring module.

7. The method according to any one of claims 1 to 3, characterized in that, Also includes: If the power monitoring module does not receive the charging command, it returns to the step of detecting the pre-charging charge level of the vehicle's battery.

8. A power management system for a vehicle, characterized in that, include: Power monitoring module, keyless entry system PEPS controller, central gateway controller, vehicle black box TBOX, cloud server and user terminal; The power monitoring module is used to detect the pre-charging charge level of the vehicle's battery, and when the pre-charging charge level is less than or equal to a first charge threshold and greater than or equal to a second charge threshold, wake up the PEPS controller to send a first message to the PEPS controller. The first message is used to request the intelligent start of the vehicle to charge the battery, and the second charge threshold is less than the first charge threshold. The PEPS controller is used to send the first message to the user terminal sequentially via the central gateway controller, the TBOX, and the cloud server. The PEPS controller is used to unlock the electronic steering column lock of the vehicle when it receives a charging command sent by the user terminal sequentially via the cloud server, the TBOX, and the central gateway controller. When the electronic steering column lock is successfully unlocked, the PEPS controller controls the vehicle's engine to start to charge the battery, including: during the charging process, the power monitoring module continuously monitors the charging progress and sends the charging progress to the PEPS controller, the charging progress including at least one of the following: charging time, charging charge level; when the charging progress meets preset conditions, the PEPS controller controls the engine to continue running, the preset conditions including at least one of the following: the charging time is less than or equal to a preset time threshold, the charging charge level is less than or equal to a third charge level threshold, and the third charge level threshold is greater than the first charge level threshold; when the charging progress does not meet the preset conditions, the PEPS controller controls the engine to stop running.

9. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-7.

Images