CN112104702A - Power supply management method for vehicle TBOX, and medium - Google Patents

Abstract

The invention relates to a power supply management method of a vehicle TBOX, the vehicle TBOX and a medium, wherein the method comprises the following steps: when the whole vehicle is powered on, if the system voltage of the TBOX is in a normal voltage range, the TBOX enters a full-function working state; when the system voltage of the TBOX exceeds the normal voltage range, the TBOX enters a semi-functional working state; if and only if the TBOX is in a full-function working state, the TBOX enters a local mode to execute a new OTA upgrading task issued by the OTA server; and TBOX enters network mode to maintain CAN network in awake state; when the whole vehicle is powered off, if the whole vehicle meets the preset sleep condition, the TBOX exits from the local mode and the network mode, and a sleep process is executed. The invention can reasonably manage the vehicle TBOX power supply for realizing OTA upgrading of the ECU based on the TBOX.

Description

Power management method of vehicle TBOX, vehicle TBOX, medium

technical field

The present invention relates to the technical field of vehicle TBOX, in particular to a power management method of a vehicle TBOX, a vehicle TBOX, and a computer-readable storage medium.

Background technique

In some vehicle-end platform solutions in which TBOX is used as the main flashing node for OTA upgrade, TBOX is responsible for interacting with the cloud, realizing ECU upgrade software download, storage, secure access, upgrade and upgrade software interface, failure control, upgrade package differential restoration, and upgrade management. and other functions. In the OTA design of the in-vehicle network, TBOX is responsible for upgrade condition detection, upgrade environment preparation, ECU software transmission and refresh, upgrade result reporting, upgrade task exit, etc.

OTA technology was first applied to PCs, and later it was widely used in the mobile phone industry. It has only been widely used in the automotive industry in recent years. At present, most of the OTA upgrade car-end solutions only focus on the interaction between the TBOX terminal and the cloud. The design of the in-vehicle network OTA upgrade scheme does not consider the differences between different types of in-vehicle communication networks, such as Controller Area Network (CAN), Local Internet (LIN), Media-based System Transmission (MOST) and Ethernet; and The specificity of TBOX's power management scheme as a vehicle networking communication terminal is not considered.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a power management method of a vehicle TBOX, a vehicle TBOX, and a computer-readable storage medium, so as to reasonably manage the TBOX power supply of a vehicle that implements OTA upgrade of the ECU based on the TBOX.

In order to achieve the above object, according to the first aspect, an embodiment of the present invention provides a power management method for a vehicle TBOX, including:

When the vehicle is powered on, if the system voltage of the TBOX is within the normal voltage range, the TBOX will enter the full-function working state; if the system voltage of the TBOX exceeds the normal voltage range, the TBOX will enter the semi-functional working state;

When the TBOX is in a fully functional working state, the TBOX receives the new OTA upgrade task notification issued by the OTA server, and determines whether there is an unfinished upgrade task locally according to the notification. If so, the TBOX does not execute the notification corresponding to the notification. A new OTA upgrade task; if not, the TBOX enters the local mode to execute the new OTA upgrade task corresponding to the notification; and, the TBOX enters the network mode to maintain the CAN network in an awake state;

When TBOX is in semi-functional working state, TBOX stops receiving notifications of new OTA upgrade tasks sent by OTA server;

When the whole vehicle is powered off, if the whole vehicle meets the preset sleep conditions, the TBOX will exit the local mode and network mode, and execute the sleep process.

Preferably, performing the new OTA upgrade task corresponding to the notification includes:

TBOX downloads the software upgrade package for the upgrade task from the OTA server according to the notification, and during the downloading process, the TBOX normally performs the function of the Internet of Vehicles;

After completing the download of the software upgrade package, TBOX obtains the current state information of the vehicle, and determines whether the upgrade conditions are met according to the current state information of the vehicle. If so, TBOX requests the whole vehicle to enter the OTA mode, and responds to the request in the whole vehicle When entering the OTA mode, after the TBOX continues to perform the currently unfinished IoV function, it stops the locally running IoV function, and executes a new OTA upgrade task according to the software upgrade package to refresh the target ECU; and, the TBOX Stop responding to any other instruction issued by the OTA server.

Preferably, performing the new OTA upgrade task corresponding to the notification includes:

When the TBOX determines that the target ECU has been successfully refreshed according to the software version number of the ECU, the TBOX requests the vehicle to exit the OTA mode, and when the vehicle enters the OTA mode in response to the request, the TBOX ends the current upgrade task and resumes the IoV function , and respond to the new instruction issued by the OTA server.

Preferably, the TBOX requests the whole vehicle to enter the OTA mode, including:

The TBOX sends the first request information for entering the OTA mode to the central gateway of the vehicle. The request information is used by the central gateway to generate a mode control signal for entering the OTA mode, and broadcast the mode control signal to other functional units of the vehicle so that the entire vehicle can enter the OTA mode. The car enters OTA mode.

Preferably, the TBOX requests the whole vehicle to exit the OTA mode, including:

TBOX sends the second request information for exiting the OTA mode to the central gateway, detects the mode control signal broadcast by the central gateway, and determines whether to end the current upgrade task according to the detected mode control signal; wherein: if the detected mode control signal is to exit OTA If the detected mode control signal is to enter the OTA mode, the second request information for exiting the OTA mode is re-sent to the central gateway, and the mode control signal broadcast by the central gateway is re-detected. The mode control signal to determine whether to end the current upgrade task;

The second request information is used by the central gateway to generate a mode control signal for exiting the OTA mode, and broadcast the mode control signal for exiting the OTA mode to other functional units of the vehicle to make the vehicle exit the OTA mode.

Preferably, performing the new OTA upgrade task corresponding to the notification includes:

When the TBOX determines that the target ECU has been successfully refreshed or failed to be refreshed according to the software version number of the ECU, the TBOX will report the upgrade result of the upgrade task to the OTA server; and, in the process of reporting the upgrade result of the upgrade task to the OTA server , if the TBOX executes the hibernation process, the report of the current upgrade result is abandoned, and the upgrade result is re-reported during the next ignition cycle of the vehicle.

Preferably, performing the new OTA upgrade task corresponding to the notification includes:

If the software of the target ECU cannot be successfully refreshed within the first preset time after starting to refresh the target ECU, the TBOX requests the vehicle to exit the OTA mode, and when the vehicle enters the OTA mode in response to the request, the TBOX ends the current Upgrade the task, resume the operation of the Internet of Vehicles function, and respond to the new instruction issued by the OTA server.

Preferably, performing the new OTA upgrade task corresponding to the notification includes:

If after the vehicle enters the OTA mode, the central gateway does not receive the second request information from the TBOX requesting the vehicle to exit the OTA mode within the second preset time, the central gateway generates a mode control signal for exiting the OTA mode, and sends the mode control signal to the mode. The control signal is broadcast to other functional units of the vehicle to make the vehicle exit the OTA mode.

According to a second aspect, an embodiment of the present invention provides a vehicle TBOX, including: a memory and a processor, where computer-readable instructions are stored in the memory, and when the computer-readable instructions are executed by the processor, the The processor executes the steps of the power management method for the vehicle TBOX according to the first aspect.

According to a third aspect, an embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the power management method for the vehicle TBOX according to the first aspect.

Embodiments of the present invention provide a power management method for a vehicle TBOX, a vehicle TBOX, and a computer-readable storage medium. When the system voltage of the TBOX is within a normal voltage range, the TBOX enters a full-function working state; when the system voltage of the TBOX exceeds the normal voltage range When the TBOX enters the semi-functional working state; only when the TBOX is in the full-functional working state, will the TBOX receive the new OTA upgrade task notification issued by the OTA server, and determine whether there is an unfinished upgrade task locally according to the notification. , the TBOX does not execute the new OTA upgrade task corresponding to the notification; if not, the TBOX enters the local mode to execute the new OTA upgrade task corresponding to the notification; and the TBOX enters the network mode to maintain the CAN network in the Wake-up state; wherein, when the TBOX exits the local mode and the network mode, the TBOX executes the sleep process. When the TBOX is in a semi-functional working state, the TBOX does not receive the new OTA upgrade task notification issued by the OTA server, nor does it execute any OTA upgrade related instructions. Reasonable management of the TBOX power supply of the vehicle based on TBOX to realize the OTA upgrade of the ECU, to ensure that the whole vehicle and the TBOX terminal go into a dormant state after the OTA upgrade process is executed, to avoid the phenomenon of vehicle power loss due to the non-sleep vehicle network or terminal or the like. produce other unsafe effects.

Other features and advantages of the present invention are set forth further in the detailed description section of the specification.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative efforts.

FIG. 1 is a flowchart of a power management method for a vehicle TBOX in an embodiment of the present invention.

FIG. 2 is a schematic diagram of a power management method for a vehicle TBOX in an embodiment of the present invention.

FIG. 3 is a schematic diagram of a network mode and a local mode of a power management method for a vehicle TBOX in an embodiment of the present invention.

Detailed ways

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In addition, in order to better illustrate the present invention, numerous specific details are given in the following specific embodiments. It will be understood by those skilled in the art that the present invention may be practiced without certain specific details. In some instances, means well known to those skilled in the art have not been described in detail in order not to obscure the subject matter of the present invention.

Referring to FIG. 1, an embodiment of the present invention provides a power management method for a vehicle TBOX, including the following steps:

Step S1, when the whole vehicle is powered on, if the system voltage of the TBOX is within the normal voltage range, the TBOX enters the full-function working state; if the system voltage of the TBOX exceeds the normal voltage range, the TBOX enters the semi-functional working state;

Specifically, referring to Fig. 2, when the whole vehicle is powered on, the system voltage of the TBOX is detected to determine whether the system voltage of the TBOX is in the normal voltage range. The normal voltage range is the voltage fluctuation range when the TBOX is working normally. The specific voltage value range is preset according to the actual working voltage data.

Wherein, the full-function working state includes: CAN enable, mobile communication module enable, backup battery charging enable, other peripheral interface enable, vehicle networking full-function enable, OTA enable;

The semi-functional working state includes: CAN enable, mobile communication module enable, backup battery charging enable, only some peripheral interfaces are enabled, some car networking functions are enabled, and OTA is disabled.

Step S21, when the TBOX is in a fully functional working state, the TBOX receives the notification of a new OTA upgrade task issued by the OTA server, and determines whether there is an unfinished upgrade task locally according to the notification, and if so, the TBOX does not execute the notification The corresponding new OTA upgrade task; if not, the TBOX enters the local mode to execute the new OTA upgrade task corresponding to the notification; and the TBOX enters the network mode to maintain the CAN network in an awake state;

Specifically, referring to FIG. 3 , in this embodiment, the OTA upgrade function is enabled only when the TBOX is in a fully functional working state. At this time, the TBOX will load the OTA component, and the OTA component is used to receive new updates from the OTA server. OTA upgrade task notification, and determine whether there is an unfinished upgrade task locally according to the notification, if so, the TBOX does not execute the new OTA upgrade task corresponding to the notification; if not, the TBOX enters the local mode to execute the The new OTA upgrade task corresponding to the notification; and, since the OTA upgrade is to refresh the software of the target ECU through the CAN network, the TBOX also needs to enter the network mode to keep the CAN network in an awake state.

Among them, when the OTA server deploys an upgrade task, or there is an upgrade task locally, after the TBOX and the OTA server complete the security authentication, the OTA can communicate with the OTA server normally. The OTA server cannot actively wake up the TBOX to seek OTA upgrade communication because a new OTA task is deployed in the background. The OTA upgrade task adopts a serial working method. When the T-Box receives a new upgrade task notification, it needs to check whether there are any unfinished upgrade tasks locally. There are only two conditions for the completion of an upgrade task: the upgrade is completed and the task expires. If there are unfinished upgrade tasks locally, a new upgrade task cannot be started. This step will trigger the upgrade task based on the task properties.

Step S22, when the TBOX is in a semi-functional working state, the TBOX stops receiving the new OTA upgrade task notification issued by the OTA server;

Specifically, when the TBOX is in a semi-functional working state, the OTA is not enabled, and the TBOX does not load the OTA components, so it stops receiving notifications of new OTA upgrade tasks sent by the OTA server.

Step S3, when the whole vehicle is powered off, if the whole vehicle satisfies the preset sleep conditions, the TBOX exits the local mode and the network mode, and executes the sleep process.

Specifically, in this embodiment, the OTA component is limited to run in a fully functional state of the TBOX. When the TBOX is in a dormant state or the system voltage is abnormal, the OTA is not enabled. In non-OTA mode, after the OTA component receives the TBOX hibernation request, it needs to save and exit the data immediately. When switching from the full-function state to the sleep state, in addition to judging whether the sleep condition is satisfied, it is also necessary to judge whether the OTA mode has been exited.

In this embodiment, after the entire vehicle is powered off and the vehicle network meets the hibernation condition, the network mode and local mode exit mechanisms are used, regardless of whether the OTA components and OTA upgrade tasks of the TBOX used to perform the OTA upgrade task are in an abnormal state, ensuring that TBOX finally executes the CAN network hibernation and terminal hibernation process, so as to ensure the safety of vehicle and TBOX terminal power management after the OTA upgrade process is executed.

Based on the above description, it can be seen that the method in this embodiment is applied to a vehicle that implements OTA upgrade of ECU based on TBOX, and can reasonably manage the TBOX power supply of this type of vehicle to ensure that the vehicle and the TBOX terminal enter the sleep state after the OTA upgrade process is executed, avoiding the occurrence of The phenomenon of vehicle power loss caused by the non-sleep vehicle network or terminal or other unsafe effects.

In some embodiments, the performing the new OTA upgrade task corresponding to the notification includes:

Step a1, the TBOX downloads the software upgrade package for the upgrade task from the OTA server according to the notification, and during the downloading process, the TBOX normally performs the function of the Internet of Vehicles;

Specifically, after receiving the upgrade package download notification from the OTA server, TBOX will obtain the relevant attributes of the task to be upgraded, including: task ID, upgrade overview, estimated time required for the upgrade, upgrade strategy, upgrade type, target ECU, target version, etc. Then download the software upgrade package of the upgrade task. Among them, the steps of downloading the upgrade package do not affect the normal execution of the TBOX Internet of Vehicles function, and the download of the upgrade package should support the breakpoint resuming of the file. After the upgrade package is downloaded, the upgrade package will be verified. After passing, the T-Box will decide the next action according to the task attribute.

Step a2: After completing the download of the software upgrade package, TBOX obtains the current state information of the vehicle, and determines whether the upgrade conditions are met according to the current state information of the vehicle. If so, TBOX requests the whole vehicle to enter the OTA mode, and responds when the whole vehicle is completed. When the request enters the OTA mode, after the TBOX continues to perform the currently unfinished IoV function, it stops the locally running IoV function, and executes a new OTA upgrade task according to the software upgrade package to refresh the target ECU; And, the TBOX stops responding to any other instruction sent by the OTA server.

Specifically, before performing the upgrade task, it is necessary to prepare the upgrade environment to check whether the upgrade conditions of the vehicle are satisfied, including: key switch state, vehicle speed zero, gear position in park state, sufficient remaining battery power/normal battery voltage, new The energy vehicle is not charging, and the motor/engine is not running. When entering the OTA mode, the vehicle functions are limited, and the TBOX needs to complete the existing IoV functions, and refuses to execute any functions newly issued by the cloud and stop the local operation of IoV functions.

After the upgrade environment is ready, the OTA component will transfer the ECU software file to the MCU side. After the file is transferred, the MCU side will perform a secondary verification of the file integrity. After the verification is passed, the OTA component will be notified of the completion of the ECU software transfer. After the OTA component informs the MCU that the software refresh can be started, the TBOX first stops the sending of all application messages on the CAN network where the target ECU is located, so as to avoid the communication of refresh messages during the refresh and upgrade process. The target software version is refreshed and upgraded. If the refresh fails in the middle, TBOX will initiate refresh retry, up to two times. Similarly, in this step, it is necessary to refuse to execute any functions newly issued by the cloud and stop the locally running IoV functions. In addition, the TBOX must be maintained in a fully functional working state during the entire process of this step, and the CAN network must be kept in a awake state.

In some embodiments, the performing the new OTA upgrade task corresponding to the notification includes:

Step b. After the TBOX determines that the target ECU is successfully refreshed according to the software version number of the ECU, the TBOX requests the vehicle to exit the OTA mode, and when the vehicle enters the OTA mode in response to the request, the TBOX ends the current upgrade task and resumes operation. Internet of Vehicles function, and respond to new instructions issued by the OTA server.

In some embodiments, the TBOX requests the entire vehicle to enter the OTA mode, including:

In step c, the TBOX sends the first request information for entering the OTA mode to the central gateway of the vehicle, and the request information is used by the central gateway to generate a mode control signal for entering the OTA mode, and broadcast the mode control signal to other functional units of the vehicle In order to make the vehicle enter OTA mode.

Specifically, in the step, the TBOX and the central gateway complete the security authentication, request the whole vehicle to enter the OTA upgrade mode, and then the central gateway completes the whole vehicle OTA mode broadcast and entry steps.

In some embodiments, the TBOX requests the vehicle to exit the OTA mode, including:

In step d, the TBOX sends the second request information for exiting the OTA mode to the central gateway of the vehicle, detects the mode control signal broadcast by the central gateway, and determines whether to end the current upgrade task according to the detected mode control signal; wherein: if the detected mode If the control signal is to exit the OTA mode, the current upgrade task is ended; if the detected mode control signal is to enter the OTA mode, the second request information for exiting the OTA mode is re-sent to the central gateway, and the mode control signal broadcast by the central gateway is re-detected. and determine whether to end the current upgrade task according to the re-detected mode control signal;

The second request information is used by the central gateway to generate a mode control signal for exiting the OTA mode, and broadcast the mode control signal for exiting the OTA mode to other functional units of the vehicle to make the vehicle exit the OTA mode.

Specifically, after the TBOX confirms that the refresh is completed, the TBOX sends a request to exit the OTA mode, that is, the second request message, to the central gateway of the vehicle, and detects the mode control broadcast by the central gateway within 3 seconds after the second request message is sent. Signal. If no normal exit is detected within 3s, it will be restarted, and the number of attempts is at most 3 times. Finally, the upgrade task will be ended regardless of whether the exit is correct or not.

In some embodiments, the performing the new OTA upgrade task corresponding to the notification includes:

Step e. After the TBOX determines that the target ECU has been successfully refreshed or failed to be refreshed according to the software version number of the ECU, the TBOX reports the upgrade result of the upgrade task to the OTA server; and, after reporting the upgrade result of the upgrade task to the OTA During the server process, if the TBOX executes the hibernation process, the report of the current upgrade result will be abandoned, and the upgrade result will be re-reported during the next ignition cycle of the vehicle.

Specifically, during the refresh process, the OTA component can maintain normal communication with the server, and periodically report the upgrade progress. After the refresh is completed, before the TBOX performs the hibernation process, the TBOX can confirm whether the upgrade task is completed by reading back the software version number of the target ECU, and report the final upgrade status. If the report of the upgrade result is not completed before hibernation, the report of the upgrade result will be abandoned, and the report will be waited for in the next ignition cycle.

In some embodiments, the performing the new OTA upgrade task corresponding to the notification includes:

Step f. If the software of the target ECU cannot be successfully refreshed within the first preset time after starting to refresh the target ECU, the TBOX requests the vehicle to exit the OTA mode, and when the vehicle enters the OTA mode in response to the request, The TBOX ends the current upgrade task, resumes the operation of the Internet of Vehicles function, and responds to the new instructions issued by the OTA server.

Specifically, if the target ECU cannot be successfully refreshed within the first preset time (for example, the estimated time required for the update multiplied by 3), the TBOX will also send a request to exit the OTA mode to the central gateway. After the vehicle exits the OTA mode, the vehicle functions and network communication return to normal, and the TBOX can independently decide to execute the sleep-wake-up process.

In some embodiments, the performing the new OTA upgrade task corresponding to the notification includes:

Step g. If after the vehicle enters the OTA mode, the central gateway does not receive the second request information from the TBOX requesting the vehicle to exit the OTA mode within the second preset time, then the central gateway generates a mode control signal for exiting the OTA mode, and sends the information to the central gateway. The mode control signal is broadcast to other functional units of the vehicle to make the vehicle exit the OTA mode.

Specifically, if the TBOX fails to initiate a request to exit the OTA mode within the specified time (Tmax, the longest time required for OTA upgrade and retry), the central gateway also needs to broadcast the mode control signal to the vehicle to exit the OTA mode.

From the description of the above embodiments, it can be seen that the embodiments of the present invention design a reasonable power management method for the OTA upgrade scheme, and consider how to ensure that the OTA can operate independently without affecting the normal use of the user's IoV function, and how to ensure that the local ECU automatically The refresh task can be successfully executed. How to ensure the reasonable implementation of the OTA vehicle-side power management scheme, especially the sleep and wake-up process. The car networking function is decoupled from the CAN network through the local mode and network mode, and the CAN network can be woken up and maintained on demand according to the specific car networking function. OTA is classified into the local mode design, and the IoV function and the OTA function are managed collaboratively. When entering the OTA mode, a mutually exclusive design is realized, and the implementation of the IoV function is stopped to ensure the smooth execution of the OTA upgrade task. After the vehicle is powered off and the vehicle network meets the hibernation conditions, the network mode and local mode exit mechanisms ensure that the TBOX finally executes the CAN network hibernation and terminal hibernation processes regardless of whether the OTA components and OTA upgrade tasks are in an abnormal state. Ensure the safety of vehicle and TBOX terminal power management after the OTA upgrade process is executed.

Another embodiment of the present invention further provides a vehicle TBOX, including: a memory and a processor, where computer-readable instructions are stored in the memory, and when the computer-readable instructions are executed by the processor, the processor causes the processor to The steps of the power management method of the vehicle TBOX according to the above embodiments are performed.

Of course, the computer device may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface for input and output, and the computer device may also include other components for implementing device functions, which will not be repeated here.

Exemplarily, the computer program may be divided into one or more units, and the one or more units are stored in the memory and executed by the processor to accomplish the present invention. The one or more units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the computer device.

The processor may be a central processing unit (Central Processing Unit, CPU), other general-purpose processors, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf processor Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The processor is the control center of the computer equipment, and uses various interfaces and lines to connect all parts of the computer equipment. .

The memory can be used to store the computer program and/or unit, and the processor implements the computer by running or executing the computer program and/or unit stored in the memory, and calling the data stored in the memory various functions of the device. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory such as hard disk, internal memory, plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card , a flash memory card (Flash Card), at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

Another embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the power management method for the vehicle TBOX described in the foregoing embodiment.

Specifically, the computer-readable storage medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc.

Various embodiments of the present invention have been described above, and the foregoing descriptions are exemplary, not exhaustive, and not limiting of the disclosed embodiments. Numerous modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the various embodiments, the practical application or technical improvement in the marketplace, or to enable others of ordinary skill in the art to understand the various embodiments disclosed herein.

Claims (10)

1. A power management method for a vehicle TBOX, comprising: When the vehicle is powered on, if the system voltage of the TBOX is within the normal voltage range, the TBOX will enter the full-function working state; if the system voltage of the TBOX exceeds the normal voltage range, the TBOX will enter the semi-functional working state; When the TBOX is in a fully functional working state, the TBOX receives the new OTA upgrade task notification issued by the OTA server, and determines whether there is an unfinished upgrade task locally according to the notification. If so, the TBOX does not execute the notification corresponding to the notification. A new OTA upgrade task; if not, the TBOX enters the local mode to execute the new OTA upgrade task corresponding to the notification; and, the TBOX enters the network mode to maintain the CAN network in an awake state; When TBOX is in semi-functional working state, TBOX stops receiving notifications of new OTA upgrade tasks sent by OTA server; When the whole vehicle is powered off, if the whole vehicle meets the preset sleep conditions, the TBOX will exit the local mode and network mode, and execute the sleep process. 2. The power management method of the vehicle TBOX according to claim 1, wherein the executing the new OTA upgrade task corresponding to the notification comprises: TBOX downloads the software upgrade package for the upgrade task from the OTA server according to the notification, and during the downloading process, the TBOX normally performs the function of the Internet of Vehicles; After completing the download of the software upgrade package, TBOX obtains the current state information of the vehicle, and determines whether the upgrade conditions are met according to the current state information of the vehicle. If so, TBOX requests the whole vehicle to enter the OTA mode, and responds to the request in the whole vehicle When entering the OTA mode, after the TBOX continues to perform the currently unfinished IoV function, it stops the locally running IoV function, and executes a new OTA upgrade task according to the software upgrade package to refresh the target ECU; and, the TBOX Stop responding to any other instruction issued by the OTA server. 3. The power management method of the vehicle TBOX according to claim 2, wherein the executing the new OTA upgrade task corresponding to the notification comprises: After the TBOX determines that the target ECU has been successfully refreshed according to the software version number of the ECU, the TBOX requests the vehicle to exit the OTA mode, and when the vehicle enters the OTA mode in response to the request, the TBOX ends the current upgrade task and resumes the IoV function. , and respond to the new instruction issued by the OTA server. 4. The power management method of the vehicle TBOX according to claim 3, wherein the TBOX requests the whole vehicle to enter the OTA mode, comprising: The TBOX sends the first request information for entering the OTA mode to the central gateway of the vehicle. The request information is used by the central gateway to generate a mode control signal for entering the OTA mode, and broadcast the mode control signal to other functional units of the vehicle so that the entire vehicle can enter the OTA mode. The car enters OTA mode. 5. The power management method of the vehicle TBOX according to claim 3, wherein the TBOX requests the whole vehicle to exit the OTA mode, comprising: TBOX sends the second request information for exiting the OTA mode to the central gateway, detects the mode control signal broadcast by the central gateway, and determines whether to end the current upgrade task according to the detected mode control signal; wherein: if the detected mode control signal is to exit OTA If the detected mode control signal is to enter the OTA mode, the second request information for exiting the OTA mode is re-sent to the central gateway, and the mode control signal broadcast by the central gateway is re-detected. The mode control signal to determine whether to end the current upgrade task; The second request information is used by the central gateway to generate a mode control signal for exiting the OTA mode, and broadcast the mode control signal for exiting the OTA mode to other functional units of the vehicle to make the vehicle exit the OTA mode. 6. The power management method of the vehicle TBOX according to claim 2, wherein the executing the new OTA upgrade task corresponding to the notification comprises: When the TBOX determines that the target ECU has been successfully refreshed or failed to be refreshed according to the software version number of the ECU, the TBOX will report the upgrade result of the upgrade task to the OTA server; and, in the process of reporting the upgrade result of the upgrade task to the OTA server , if the TBOX executes the hibernation process, the report of the current upgrade result is abandoned, and the upgrade result is re-reported during the next ignition cycle of the vehicle. 7. The power management method of the vehicle TBOX according to claim 2, wherein the executing the new OTA upgrade task corresponding to the notification comprises: If the software of the target ECU cannot be successfully refreshed within the first preset time after starting to refresh the target ECU, the TBOX requests the vehicle to exit the OTA mode, and when the vehicle enters the OTA mode in response to the request, the TBOX ends the current Upgrade the task, resume the operation of the Internet of Vehicles function, and respond to the new instruction issued by the OTA server. 8. The power management method of the vehicle TBOX according to claim 2, wherein the executing the new OTA upgrade task corresponding to the notification comprises: If after the vehicle enters the OTA mode, the central gateway does not receive the second request information from the TBOX requesting the vehicle to exit the OTA mode within the second preset time, the central gateway generates a mode control signal for exiting the OTA mode, and sends the mode control signal to the mode. The control signal is broadcast to other functional units of the vehicle to make the vehicle exit the OTA mode. 9. A vehicle TBOX, comprising: a memory and a processor, wherein computer-readable instructions are stored in the memory, and when the computer-readable instructions are executed by the processor, the processor executes the execution according to claim 1- Steps of the power management method of the vehicle TBOX according to any one of 8. 10. A computer-readable storage medium on which a computer program is stored, characterized in that: when the computer program is executed by a processor, the power management method of the vehicle TBOX according to any one of claims 1-8 is implemented. step.

Images