Software updating method, device and vehicle

Abstract

The present disclosure relates to a software updating method, device and vehicle. The method comprises: obtaining stored data to be updated when it is determined that the vehicle is in a high-voltage power supply state; determining first power distribution mode information of a device to be updated corresponding to the data to be updated when it is determined that the data to be updated is data to be backed up; controlling a DCDC in the vehicle to supply power to the device to be updated when the first power distribution mode information is DCDC power distribution, and sending the data to be updated to the device to be updated so that the device to be updated stores the data to be updated in a preset software backup area in the device to be updated, and performs integrity verification on the data to be updated; determining whether the vehicle enters a flameout state in response to receiving a verification completion instruction sent by the device to be updated; and controlling the device to be updated to update the device to be updated according to the data to be updated when it is determined that the vehicle enters a flameout state.

Description

Technical Field

[0001] The present disclosure relates to the field of vehicle technology, and in particular, to a software updating method, device and vehicle. Background Art

[0002] As the level of intelligence of electric vehicles continues to improve, there are more and more electronic control units (ECUs) on electric vehicles, and manufacturers have higher and higher requirements for optimizing the ECUs of aftermarket vehicles. Usually, the software in the ECU is remotely upgraded through OTA (Over-the-air Technology).

[0003] In the related art, when the vehicle electronic control unit (i.e., the device to be updated) is remotely upgraded, the upgrade time required is relatively long. The device to be updated is too dependent on the battery for power supply, and the stability and reliability of the power supply during the upgrade process cannot be guaranteed, which is not conducive to improving the reliability of the entire vehicle. Summary of the invention

[0004] The purpose of the present disclosure is to provide a software updating method, device and vehicle.

[0005] In order to achieve the above-mentioned object, the present disclosure provides a software update method in a first aspect, which is applied to a vehicle-mounted terminal, and the method comprises:

[0006] When it is determined that the vehicle is in a high-voltage power supply state, acquiring the stored data to be upgraded;

[0007] In the case where it is determined that the data to be upgraded is data to be backed up, determining first power distribution mode information of a device to be updated corresponding to the data to be upgraded;

[0008] When the first power distribution mode information is DCDC (Direct Current, direct current voltage converter) power distribution, controlling the DCDC in the vehicle to power the device to be updated, and sending the data to be updated to the device to be updated, so that the device to be updated stores the data to be updated in a preset software backup area in the device to be updated, and performing integrity check on the data to be updated;

[0009] In response to receiving a verification completion instruction sent by the device to be updated, determining whether the vehicle enters an engine-off state;

[0010] When it is determined that the vehicle enters the ignition-off state, the device to be updated is controlled to update the device to be updated according to the data to be upgraded.

[0011] Optionally, before controlling the device to be updated to update the device to be updated according to the data to be upgraded, the method further includes:

[0012] Acquire the second power distribution mode information of the device to be updated;

[0013] When it is determined that the second power distribution mode information is battery power distribution, the power supply mode of the device to be updated is switched from DCDC power supply to battery power supply.

[0014] Optionally, determining that the data to be upgraded is data to be backed up includes:

[0015] Acquire the burning flag information in the data to be upgraded, wherein the burning flag information is used to indicate whether the data to be upgraded is backed up;

[0016] In a case where the burning mark information indicates that the data to be upgraded is backed up, the data to be upgraded is determined to be the data to be backed up.

[0017] Optionally, the controlling the device to be updated to update the device to be updated according to the data to be upgraded includes:

[0018] A copy instruction is sent to the device to be updated, so that the device to be updated stores the data to be upgraded in a preset software storage area in the device to be updated in response to receiving the copy instruction.

[0019] Optionally, the controlling the device to be updated to update the device to be updated according to the data to be upgraded includes:

[0020] A reset signal is sent to the device to be updated, so that the device to be updated restarts the device to be updated to run the data to be upgraded after storing the data to be upgraded in a preset software storage area in the device to be updated.

[0021] Optionally, the method further comprises:

[0022] If it is determined that the first power distribution mode of the device to be updated is battery power distribution, the battery in the vehicle is controlled to power the device to be updated, and when it is determined that the power supply is connected, the data to be upgraded is sent to the device to be updated, so that the device to be updated stores the data to be upgraded in the preset software backup area, and performs integrity verification on the stored data to be upgraded. When it is determined that the verification passes, a verification completion instruction is sent to the vehicle-mounted terminal.

[0023] Optionally, the method further comprises:

[0024] Obtaining current version information corresponding to the software running on the target device in the vehicle;

[0025] Sending the current version information to a target server, so that the target server determines whether there is data to be upgraded according to the current version information, and if it is determined that there is data to be upgraded, sending the data to be upgraded to the vehicle terminal;

[0026] When the vehicle is powered on, the data to be upgraded sent by the target server is received and stored, and a device to be updated is determined from the target devices according to the data to be upgraded.

[0027] Optionally, obtaining the current version information of the software running on the target device in the vehicle includes:

[0028] At every preset time period, when it is determined that the vehicle is in a powered-on state, current version information of software running on a target device in the vehicle is obtained.

[0029] Optionally, obtaining the current version information of the software running on the target device in the vehicle includes:

[0030] When a version acquisition instruction input by a user is received, current version information of software running on a target device in the vehicle is acquired.

[0031] Optionally, after controlling the device to be updated to update the device to be updated according to the data to be upgraded, the method further includes:

[0032] Receiving an update result indication message sent by the device to be updated, where the update result indication message is used to indicate whether the update of the device to be updated is successful or failed;

[0033] The upgrade record of the device to be updated is updated according to the update result indication message.

[0034] In a second aspect of the present disclosure, a software updating device is provided, the device comprising:

[0035] a memory having a computer program stored thereon;

[0036] A processor is used to execute the computer program in the memory to implement the steps of the method described in the first aspect above.

[0037] In a third aspect of the present disclosure, a vehicle is provided, comprising the software updating device described in the second aspect.

[0038] The above technical scheme can, when it is determined that the vehicle is in a high-voltage power supply state, enable the device to be updated to store the data to be upgraded in the preset software backup area, and when it is determined that the vehicle is in an ignition-off state, control the device to be updated to be updated according to the data to be upgraded, and when it is determined that the vehicle is in a high-voltage power supply state, control the DCDC in the vehicle to power the device to be updated, which can not only ensure the stability of power supply when the data to be upgraded is stored in the preset software backup area (backup stage in the software upgrade process), but also avoid the consumption of battery power in the backup stage, which is conducive to ensuring the reliability of power supply to the device to be updated in the process of controlling the device to be updated to perform data update according to the data to be upgraded when it is determined that the vehicle is in an ignition-off state, thereby ensuring the power supply stability and reliability of the device to be updated in the entire software upgrade process, which is conducive to reducing the failure rate of the vehicle during the software upgrade process, thereby helping to improve the reliability of the entire vehicle.

[0039] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific implementation information, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings:

[0041] Figure 1 is a flowchart of a software updating method shown in an exemplary embodiment of the present disclosure;

[0042] Figure 2 is a flowchart of a software updating method shown in another exemplary embodiment of the present disclosure;

[0043] Figure 3 The invention is a block diagram of a software updating device according to an exemplary embodiment.

[0044] Specific implementation information

[0045] The specific implementation information of the present disclosure is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation information described herein is only used to illustrate and explain the present disclosure, and is not used to limit the present disclosure.

[0046] Before introducing the specific implementation of the present disclosure in detail, the application scenario of the present disclosure is first described as follows. The present disclosure can be applied to the process of remotely upgrading the electronic control unit ECU in an electric vehicle, wherein the electronic control unit ECU can be a control module of any device in the electric vehicle (for example, a drive motor, a brake assist device, a ramp assist device, etc.). In the related art, when the ECU in the vehicle is remotely updated through OTA, the entire upgrade process is usually completed within a continuous time period, that is, within a continuous time period, the data to be upgraded corresponding to the ECU is first stored in the preset software backup area in the Flash of the ECU (that is, the data to be upgraded is backed up), and then after determining that the backup is completed, the backed up data to be upgraded is copied to the preset software storage area in the Flash, and the data is run in the preset software storage area, thereby realizing the update of the ECU.

[0047] However, in the related technology, the entire software update process takes a long time, and the battery is used to power the device to be updated during the entire software update process. Usually, the battery powers multiple low-voltage loads in the vehicle at the same time. The stability of the battery supplying power to the device to be updated is easily affected by the number of loads, and the performance of the battery will decay with the extended use time. Therefore, it will cause the problem of low stability and reliability of power supply during the update process of the device to be updated, which is not conducive to improving the reliability of the upgrade of the device to be updated, nor is it conducive to improving the reliability of the entire vehicle.

[0048] In order to solve the above technical problems, the present disclosure provides a software updating method, device and vehicle. The software updating method controls the DCDC to power the device to be updated when the vehicle is in a high-voltage power supply state, and enables the device to be updated to store the data to be updated in the preset software backup area. When the vehicle is in an ignition-off state, the device to be updated copies the data to be updated stored in the preset software backup area to the preset software storage area to complete the update of the device to be updated. In this way, by dividing the entire software upgrade process into two stages (a backup stage under a high-voltage power supply state, and a copying stage under an ignition-off state), and when it is determined that the vehicle is in a high-voltage power supply state (i.e., the backup stage in the software upgrade process), the DCDC in the vehicle is controlled to convert the high-voltage electricity in the high-voltage power battery in the vehicle into low-voltage electricity to power the device to be updated, thereby not only ensuring the stability of the power supply when the data to be upgraded is stored in the preset software backup area, but also avoiding the consumption of battery power, which is conducive to ensuring the reliability of the power supply to the device to be updated in the process of controlling the device to be updated to perform data update according to the data to be upgraded when it is determined that the vehicle is in an ignition-off state (the copying stage in the software upgrade process), thereby ensuring the power supply stability and reliability of the device to be updated in the entire software upgrade process, which is conducive to reducing the failure rate of the vehicle during the software upgrade process, thereby helping to improve the reliability of the vehicle.

[0049] The present disclosure is described below in conjunction with specific embodiments.

[0050] Figure 1 is a flowchart of a software update method shown in an exemplary embodiment of the present disclosure; see Figure 1 The software update method is applied to a vehicle-mounted terminal, and the method may include the following steps:

[0051] Step 101 : when it is determined that the vehicle is in a high voltage power supply state, the stored data to be upgraded is obtained.

[0052] Among them, the high-voltage power supply state may include a state in which the power battery is powered when the vehicle is in a starting state (the ignition lock is in the ON position), or a state in which the power battery is powered when the vehicle is in an off state.

[0053] Step 102: When it is determined that the data to be upgraded is data to be backed up, determine the first power distribution mode information of the device to be updated corresponding to the data to be upgraded.

[0054] The data to be upgraded may include burn-in flag information, and the burn-in flag information indicates whether the data to be upgraded is backed up. The first power distribution mode information may include DCDC power distribution and battery power distribution.

[0055] It should be noted that, during the DCDC power distribution process, the DCDC in the vehicle converts the high voltage power output by the power battery in the vehicle into low voltage power to power the device to be updated. When the battery distributes power, the battery powers the device to be updated.

[0056] Step 103, when the first power distribution mode information is DCDC power distribution, control the DCDC in the vehicle to power the device to be updated, and send the data to be upgraded to the device to be updated, so that the device to be updated stores the data to be upgraded in a preset software backup area in the device to be updated, and perform integrity check on the data to be upgraded.

[0057] Step 104 , in response to receiving the verification completion instruction sent by the device to be updated, determining whether the vehicle enters an ignition-off state.

[0058] When it is determined that the ignition lock of the vehicle is in the OFF position, it can be determined that the vehicle is in an ignition-off state.

[0059] Step 105 , when it is determined that the vehicle is in the engine-off state, controlling the device to be updated to update the device to be updated according to the data to be upgraded.

[0060] In this step, a possible implementation is: sending a copy instruction to the device to be updated, so that the device to be updated stores the data to be upgraded in a preset software storage area in the device to be updated in response to receiving the copy instruction.

[0061] Another possible implementation is: sending a reset signal to the device to be updated, so that the device to be updated restarts the device to be updated to run the data to be upgraded after storing the data to be upgraded in a preset software storage area in the device to be updated.

[0062] The above technical solution can, when it is determined that the vehicle is in a high-voltage power supply state, enable the device to be updated to store the data to be upgraded in the preset software backup area, and when it is determined that the vehicle is in an ignition-off state, control the device to be updated to be updated according to the data to be upgraded, and when it is determined that the vehicle is in a high-voltage power supply state, control the DCDC in the vehicle to power the device to be updated, and can avoid battery power consumption during the backup phase (i.e., in the process of storing the data to be upgraded in the preset software backup area), which is conducive to ensuring the reliability of power supply to the device to be updated in the process of controlling the device to be updated to perform software update according to the data to be upgraded when it is determined that the vehicle is in an ignition-off state, thereby ensuring the power supply stability and reliability of the device to be updated during the entire software upgrade process, which is conducive to reducing the failure rate of the vehicle during the software upgrade process, thereby helping to improve the reliability of the vehicle.

[0063] Figure 2 is a flowchart of a software updating method shown in another exemplary embodiment of the present disclosure; see Figure 2 The method is applied to a vehicle-mounted terminal and may include the following steps:

[0064] Step 201, obtaining the current version information corresponding to the software running on the target device in the vehicle.

[0065] The target device may be an electronic control unit ECU of any device in a vehicle.

[0066] In this step, a possible implementation is: every preset time period, when it is determined that the vehicle is in a powered-on state, obtaining the current version information of the software running on the target device in the vehicle.

[0067] For example, when the vehicle is powered on for the first time every day, the vehicle terminal sends the current version information of the software running in multiple target devices preset in the vehicle (such as drive motor, brake assist device, hill assist device, etc.) to the target server.

[0068] In this step, another possible implementation is: upon receiving a version acquisition instruction input by the user, obtaining the current version information of the software running on the target device in the vehicle.

[0069] For example, when the user wants to actively upgrade the running software of the target device, the user can click a preset button in the target device to obtain the current version information of the running software of the target device.

[0070] Step 202, the current version information is sent to the target server, so that the target server determines whether there is data to be upgraded according to the current version information, and sends the data to be upgraded to the vehicle terminal if it is determined that there is data to be upgraded.

[0071] The vehicle terminal may be a driving recorder, a vehicle navigation system, a vehicle mobile phone, a vehicle tablet, a vehicle watch or other vehicle computer equipment. The data to be upgraded is used to upgrade the current version of the software running in the target device to the update data required for the target version, which is different from the current version. For example, the target version may be higher than the current version or lower than the current version.

[0072] Step 203, when the vehicle is in a powered-on state, receiving and storing the data to be upgraded sent by the target server, and determining the device to be updated from the target device according to the data to be upgraded.

[0073] The vehicle being in a powered-on state may mean that a power battery in the vehicle is in a power supply state, or the vehicle may mean that a low-voltage device in the vehicle is in a powered state.

[0074] In this step, the target device corresponding to the data to be upgraded is determined as the device to be updated, and after receiving the data to be upgraded sent by the target server, the data to be upgraded is stored in a preset storage unit in the vehicle terminal.

[0075] For example, if the data to be upgraded is upgrade data for a hill assist device in a vehicle, the hill assist device is determined to be the device to be updated, wherein the data to be upgraded includes a field for characterizing the corresponding target device, that is, the device to be updated corresponding to the data to be upgraded can be obtained by reading the information content of the field.

[0076] The above steps 201 to 203 can store the upgraded data corresponding to the device to be updated in the preset storage unit of the vehicle terminal when it is determined that the vehicle is powered on, so that the subsequent step 204 reads the upgraded data from the preset storage unit.

[0077] Step 204 : when it is determined that the vehicle is in a high voltage power supply state, the stored data to be upgraded is obtained.

[0078] In a possible implementation of this step, the gear position information of the electric vehicle ignition lock may be obtained, and when it is determined that the ignition lock is in the ON gear, it is determined that the vehicle is in a high voltage power supply state.

[0079] In another possible implementation manner of this step, in the ignition-off state, if it is determined that the power battery is in the power supply state, then it is determined that the vehicle is in the high-voltage power supply state.

[0080] Furthermore, when it is determined that the vehicle is in a high voltage power supply state, the upgrade data can be read from a preset storage unit in the vehicle terminal.

[0081] Step 205, obtaining the burning mark information in the data to be upgraded.

[0082] The burning mark information is used to indicate whether the data to be upgraded is backed up.

[0083] For example, in the character sequence corresponding to the data to be upgraded, if there is a character for indicating that data backup is to be performed, it is determined that data backup is to be performed; if there is no character for indicating that data backup is to be performed, it is determined that data backup is not to be performed. For example, the character "1" is used to indicate that data backup is to be performed, and the character "0" is used to indicate that data backup is not to be performed. When the character sequence corresponding to the data to be upgraded is "1", it indicates that the data to be upgraded needs to be backed up, and when the character sequence corresponding to the data to be upgraded is "0", it indicates that the data to be upgraded does not need to be backed up.

[0084] Step 206, determining whether the burning mark information indicates that the data to be upgraded is to be backed up.

[0085] In this step, if it is determined that the burning mark information indicates that the data to be upgraded needs to be backed up, step 207 is executed; if it is determined that the burning mark information indicates that the data to be upgraded does not need to be backed up, step 213 is executed.

[0086] Wherein, when it is determined that the data to be upgraded does not need to be backed up, the device to be upgraded can be directly controlled to be upgraded according to the data to be upgraded.

[0087] Step 207: determine that the data to be upgraded is the data to be backed up.

[0088] Step 208: Acquire the first power distribution mode information of the device to be updated corresponding to the data to be upgraded.

[0089] The first power distribution mode information includes DCDC power distribution and battery power distribution.

[0090] It should be noted that, during the DCDC power distribution process, the DCDC in the vehicle converts the high voltage electricity output by the power battery in the vehicle into low voltage electricity to power the device to be updated. When the battery distributes power, the battery powers the device to be updated. Optionally, the first power distribution mode in the data to be upgraded corresponding to the software related to the DCDC and high voltage power battery can be set to the battery power distribution in advance, and the first power distribution mode information in the data to be upgraded corresponding to the software other than the software related to the DCDC and high voltage power battery can be set to the DCDC power distribution.

[0091] Step 209, determining whether the first power distribution mode information is DCDC power distribution.

[0092] In this step, when the first power distribution mode information is DCDC power distribution, step 210 is executed, and when the first power distribution mode information is battery power distribution, step 211 is executed.

[0093] Step 210, controlling the DCDC in the vehicle to power the device to be updated, and sending the data to be updated to the device to be updated, so that the device to be updated stores the data to be updated in a preset software backup area in the device to be updated, and performs integrity check on the data to be updated.

[0094] Step 211, control the battery in the vehicle to supply power to the device to be updated, and when it is determined that the power supply is connected, send the data to be updated to the device to be updated, so that the device to be updated stores the data to be upgraded in the preset software backup area, and perform integrity verification on the stored data to be upgraded. When it is determined that the verification passes, send a verification completion instruction to the vehicle-mounted terminal.

[0095] In this way, through the above steps 204 to 211, when it is determined that the vehicle is in a high-voltage power supply state, the DCDC in the vehicle can be controlled to power the device to be updated, and the consumption of battery power can be avoided during the backup phase (i.e., the process of storing the data to be upgraded in the preset software backup area).

[0096] Step 212: In response to receiving the verification completion instruction sent by the device to be updated, determining whether the vehicle has entered an ignition-off state.

[0097] When it is determined that the ignition lock of the vehicle is in the OFF position, it can be determined that the vehicle is in an ignition-off state.

[0098] In this step, if it is determined that the vehicle has entered the flameout state, step 212 is executed. If it is determined that the vehicle has entered the flameout state, the step of determining whether the vehicle has entered the flameout state is continued.

[0099] Step 213, obtaining the second power distribution mode information of the device to be updated.

[0100] The second power distribution mode information includes: DCDC power distribution and battery power distribution.

[0101] Step 214, determining whether the second power distribution mode information is battery power distribution.

[0102] In this step, when it is determined that the second power distribution mode information is battery power distribution, step 215 is executed; when it is determined that the second power distribution mode information is DCDC power distribution, step 216 is executed.

[0103] Step 215: Switch the power supply mode of the device to be updated from DCDC power supply to battery power supply.

[0104] In this step, the switching of the power supply mode can be achieved by cutting off the connection between the DCDC and the device to be updated, and then establishing a connection between the storage battery and the device to be updated.

[0105] Step 216: Control the DCDC to supply power to the device to be updated.

[0106] Step 217: Send a copy instruction to the device to be updated, so that the device to be updated stores the data to be upgraded into a preset software storage area in the device to be updated in response to receiving the copy instruction.

[0107] In one possible implementation, the copy instruction may be the reset signal, which is used to restart the device to be updated. After sending the reset signal to the device to be updated, the device to be updated responds to receiving the reset signal, stores the data to be upgraded in a preset software storage area in the device to be updated, and then restarts the device to be updated to run the data to be upgraded.

[0108] In another possible implementation, the copy instruction is a non-reset signal, which is only used to enable the device to be updated to store the data to be upgraded to a preset software storage area in the device to be updated, and to trigger a reset signal before the data to be upgraded needs to be run subsequently to restart the device to be updated.

[0109] The above steps 212 to 217 can distribute power to the device to be updated according to the second power distribution mode information when it is determined that the vehicle is in the off state, and can ensure the reliability of power supply to the device to be updated during the process of storing the data to be upgraded in the preset software storage area in the device to be updated (i.e., the copying stage in the software upgrade process), thereby ensuring the power supply stability and reliability of the device to be updated during the entire software upgrade process, which is beneficial to reducing the failure rate of the vehicle during the software upgrade process, thereby helping to improve the reliability of the vehicle.

[0110] Step 218: Receive an update result indication message sent by the device to be updated.

[0111] The update result indication message is used to indicate whether the device to be updated is updated successfully or failed.

[0112] It should be noted that after the device to be updated stores the data to be updated in the preset software storage area of ​​the device to be updated, the integrity of the data to be updated stored in the preset software storage area of ​​the device to be updated can be checked. If it is determined that the data to be updated is complete, it is determined that the device to be updated has been successfully updated, and an update success instruction is sent to the vehicle-mounted terminal; if it is determined that the data to be updated is incomplete, it is determined that the update of the device to be updated has failed, and an update failure instruction is sent to the vehicle-mounted terminal.

[0113] Step 219: Update the upgrade record of the device to be updated according to the update result indication message.

[0114] The upgrade record may include the upgrade time of the device to be updated and the software version information after the upgrade.

[0115] The above technical scheme can, when it is determined that the vehicle is in a high-voltage power supply state, enable the device to be updated to store the data to be upgraded in the preset software backup area, and when it is determined that the vehicle is in an ignition-off state, control the device to be updated to be updated according to the data to be upgraded, and when it is determined that the vehicle is in a high-voltage power supply state, control the DCDC in the vehicle to power the device to be updated, which can not only ensure the stability of power supply when the data to be upgraded is stored in the preset software backup area (backup stage in the software upgrade process), but also avoid the consumption of battery power in the backup stage, which is conducive to ensuring the reliability of power supply to the device to be updated in the process of controlling the device to be updated to perform data update according to the data to be upgraded when it is determined that the vehicle is in an ignition-off state, thereby ensuring the power supply stability and reliability of the device to be updated in the entire software upgrade process, which is conducive to reducing the failure rate of the vehicle during the software upgrade process, and thus is conducive to improving the reliability of the entire vehicle.

[0116] Figure 3 FIG. 1 is a block diagram of a software updating device according to an exemplary embodiment. Figure 3 As shown, the software update device 300 may include: a processor 301 and a memory 302. The software update device 300 may also include one or more of a multimedia component 303, an input / output (I / O) interface 304, and a communication component 305.

[0117] The processor 301 is used to control the overall operation of the software update device 300 to complete all or part of the steps in the above-mentioned software update method. The memory 302 is used to store various types of data to support the operation of the software update device 300. For example, these data may include instructions for any application or method used to operate on the software update device 300, and application-related data, such as contact data, sent and received messages, pictures, audio, video, etc. The memory 302 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 memory, flash memory, magnetic disk or optical disk. The multimedia component 303 may include a screen and an audio component. The screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone, which is used to receive external audio signals. The received audio signal may be further stored in the memory 302 or sent through the communication component 305. The audio component also includes at least one speaker for outputting audio signals. The I / O interface 304 provides an interface between the processor 301 and other interface modules, and the above-mentioned other interface modules may be keyboards, mice, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 305 is used for wired or wireless communication between the software update device 300 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 305 may include: Wi-Fi module, Bluetooth module, NFC module.

[0118] In an exemplary embodiment, the software update device 300 can be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), controllers, microcontrollers, microprocessors or other electronic components to execute the above-mentioned software update method.

[0119] In another exemplary embodiment of the present disclosure, a vehicle is provided, the vehicle comprising the above Figure 3 The software updating device.

[0120] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0121] The preferred implementation information of the present disclosure is described in detail above in conjunction with the accompanying drawings. However, the present disclosure is not limited to the specific details in the above implementation information. Within the technical concept of the present disclosure, a variety of simple modifications can be made to the technical solution of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.

[0122] It should also be noted that the various specific technical features described in the above-mentioned specific implementation information can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present disclosure will no longer separately describe the various possible combination information.

[0123] In addition, the various implementation information of the present disclosure may be arbitrarily combined, and as long as it does not violate the concept of the present disclosure, it should also be regarded as the content disclosed by the present disclosure.

Claims

1. A software updating method, characterized in that: Applied to a vehicle-mounted terminal, the method comprises: When it is determined that the vehicle is in a high-voltage power supply state, acquiring the stored data to be upgraded; In the case where it is determined that the data to be upgraded is data to be backed up, determining first power distribution mode information of a device to be updated corresponding to the data to be upgraded; When the first power distribution mode information is DCDC power distribution, controlling the DCDC in the vehicle to power the device to be updated, and sending the data to be updated to the device to be updated, so that the device to be updated stores the data to be updated in a preset software backup area in the device to be updated, and performing integrity check on the data to be updated; In response to receiving a verification completion instruction sent by the device to be updated, determining whether the vehicle enters an engine-off state; When it is determined that the vehicle enters an ignition-off state, controlling the device to be updated to update the device to be updated according to the data to be upgraded; The method further comprises: If it is determined that the first power distribution mode of the device to be updated is battery power distribution, control the battery in the vehicle to power the device to be updated, and when it is determined that the power supply is turned on, send the data to be updated to the device to be updated, so that the device to be updated stores the data to be upgraded in the preset software backup area, and perform integrity check on the stored data to be upgraded, and when it is determined that the check passes, send a check completion instruction to the vehicle terminal; Before controlling the device to be updated to update the device to be updated according to the data to be upgraded, the method further includes: Acquire the second power distribution mode information of the device to be updated; When it is determined that the second power distribution mode information is battery power distribution, the power supply mode of the device to be updated is switched from DCDC power supply to battery power supply.

2. The method according to claim 1, characterized in that The determining that the data to be upgraded is data to be backed up includes: Acquire the burning flag information in the data to be upgraded, wherein the burning flag information is used to indicate whether the data to be upgraded is backed up; In a case where the burning mark information indicates that the data to be upgraded is backed up, the data to be upgraded is determined to be the data to be backed up.

3. The method according to claim 1, characterized in that The controlling the device to be updated to update the device to be updated according to the data to be upgraded comprises: A copy instruction is sent to the device to be updated, so that the device to be updated stores the data to be upgraded in a preset software storage area in the device to be updated in response to receiving the copy instruction.

4. The method according to claim 1, characterized in that: The controlling the device to be updated to update the device to be updated according to the data to be upgraded comprises: A reset signal is sent to the device to be updated, so that the device to be updated restarts the device to be updated to run the data to be upgraded after storing the data to be upgraded in a preset software storage area in the device to be updated.

5. The method according to claim 1, characterized in that: The method further comprises: Obtaining current version information corresponding to the software running on the target device in the vehicle; Sending the current version information to a target server, so that the target server determines whether there is data to be upgraded according to the current version information, and if it is determined that there is data to be upgraded, sending the data to be upgraded to the vehicle terminal; When the vehicle is powered on, the data to be upgraded sent by the target server is received and stored, and a device to be updated is determined from the target devices according to the data to be upgraded.

6. The method according to claim 5, characterized in that The obtaining of the current version information corresponding to the software running on the target device in the vehicle includes: At every preset time period, when it is determined that the vehicle is in a powered-on state, current version information of software running on a target device in the vehicle is obtained.

7. The method according to claim 5, characterized in that The obtaining of the current version information corresponding to the software running on the target device in the vehicle includes: When a version acquisition instruction input by a user is received, current version information of software running on a target device in the vehicle is acquired.

8. The method according to any one of claims 1 to 7, characterized in that: After controlling the device to be updated to update the device to be updated according to the data to be upgraded, the method further includes: Receiving an update result indication message sent by the device to be updated, where the update result indication message is used to indicate whether the update of the device to be updated is successful or failed; The upgrade record of the device to be updated is updated according to the update result indication message.

9. A software updating device, characterized in that: The device comprises: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1 to 8.

10. A vehicle, characterized in that: The software updating device comprises the software updating device as claimed in claim 9 above.

Images