Vehicle upgrading method and device, vehicle-mounted terminal, storage medium and program product

Abstract

The invention relates to a vehicle upgrading method and device, a vehicle-mounted terminal, a storage medium and a program product. In the upgrading process of the target component in the cab of the target vehicle, executing an operation of obtaining a heartbeat message sent by the target component; wherein the target component comprises at least one of a central controller, an instrument and a user interface engine; if the heartbeat message sent by the target component is not received within the first preset duration, restarting the to-be-upgraded version program of the target component; in a second preset duration, under the condition that the number of times of restarting the to-be-upgraded version program of the target component exceeds a preset threshold value, running a historical version program of the target component; wherein the second preset duration is greater than the first preset duration. According to the scheme, re-upgrading is tried under the condition that the to-be-upgraded program fails to be upgraded, and the historical version program is operated under the condition that the re-upgrading frequency exceeds the preset threshold value, so that the problem of program instability caused by the failed upgrading of the to-be-upgraded program is avoided, and the user experience is further improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle upgrading method, device, vehicle-mounted terminal, storage medium and program product. Background Art

[0002] The goal is to improve the performance, comfort, safety, and personalization of the vehicle, and the applications in the vehicle will be continuously updated.

[0003] In traditional technology, if the upgrade fails during the vehicle upgrade process, it may cause the vehicle's application to run unstably, thereby reducing the user experience. Summary of the invention

[0004] Based on this, it is necessary to provide a vehicle upgrade method, device, vehicle-mounted terminal, storage medium and program product to address the above-mentioned technical problems, so as to avoid instability in the vehicle's application program during the vehicle upgrade process, thereby improving the user experience.

[0005] In a first aspect, the present application provides a vehicle upgrading method, the method comprising:

[0006] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0007] If the heartbeat message sent by the target component is not received within the first preset time period, restarting the program of the to-be-upgraded version of the target component;

[0008] If the number of restarts of the target component's to-be-upgraded version program exceeds a preset threshold within a second preset time period, the target component's historical version program is run; wherein the second preset time period is greater than the first preset time period.

[0009] In one embodiment, after running the historical version program of the target component, the method further includes:

[0010] Verifying the version information of the program to be upgraded; wherein the version information includes the target version number and the target version content;

[0011] When the version information of the program to be upgraded passes the verification, controlling the target component to re-run the program to be upgraded;

[0012] When the version information verification of the version program to be upgraded fails, a request for re-obtaining the version program to be upgraded is sent to the server, so that the server sends a new version program to be upgraded to the target vehicle.

[0013] In one embodiment, the verifying the version information of the program to be upgraded includes:

[0014] Compare the target version number with the historical version number of the historical version program to obtain a first comparison result;

[0015] Compare the target check value corresponding to the target version content with the preset check value to obtain a second comparison result;

[0016] When the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target check value is consistent with the preset check value, it is determined that the version information verification of the version program to be upgraded has passed.

[0017] In one embodiment, controlling the target component to re-run the program of the to-be-upgraded version includes:

[0018] Obtaining an event identifier of a running event in a historical version program of the target component;

[0019] In the case where the event identifier represents that the running event is an interruptible event, the target component is controlled to re-run the version of the program to be upgraded.

[0020] In one embodiment, the method further comprises:

[0021] If the heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

[0022] In one of the embodiments, the historical version program of the target component is a pre-stored historical version program that the target component runs before upgrading.

[0023] In a second aspect, the present application further provides a vehicle upgrading device, the device comprising:

[0024] An execution module, used for executing an operation of acquiring a heartbeat message sent by a target component during an upgrade process of a target component in a cockpit of a target vehicle; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0025] A restart module, used for restarting the program of the to-be-upgraded version of the target component if no heartbeat message sent by the target component is received within a first preset time period;

[0026] The running module is used to run the historical version program of the target component when the number of restarts of the upgraded version program of the target component exceeds a preset threshold within a second preset time period; wherein the second preset time period is greater than the first preset time period.

[0027] In a third aspect, the present application further provides a vehicle-mounted terminal, the vehicle-mounted terminal comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0028] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0029] If the heartbeat message sent by the target component is not received within the first preset time period, restarting the program of the to-be-upgraded version of the target component;

[0030] If the number of restarts of the target component's upgraded version program exceeds a preset threshold within a second preset time period, the target component's historical version program is run; wherein the second preset time period is greater than the first preset time period.

[0031] In a fourth aspect, the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0032] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0033] If the heartbeat message sent by the target component is not received within the first preset time period, restarting the program of the to-be-upgraded version of the target component;

[0034] If the number of restarts of the target component's upgraded version program exceeds a preset threshold within a second preset time period, the target component's historical version program is run; wherein the second preset time period is greater than the first preset time period.

[0035] In a fifth aspect, the present application further provides a computer program product, the computer program product comprising a computer program, which implements the following steps when executed by a processor:

[0036] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0037] If the heartbeat message sent by the target component is not received within the first preset time period, restarting the program of the to-be-upgraded version of the target component;

[0038] If the number of restarts of the target component's upgraded version program exceeds a preset threshold within a second preset time period, the target component's historical version program is run; wherein the second preset time period is greater than the first preset time period.

[0039] The above-mentioned vehicle upgrade method, device, vehicle-mounted terminal, storage medium and program product, during the upgrade process of the target component in the cockpit of the target vehicle, executes the operation of obtaining the heartbeat message sent by the target component; wherein the target component includes at least one of the central control, instrument and user interface engine; if the heartbeat message sent by the target component is not received within the first preset time, the target component's version of the program to be upgraded is restarted; within the second preset time, if the number of restarts of the target component's version of the program to be upgraded exceeds a preset threshold, the target component's historical version of the program is run; wherein the second preset time is greater than the first preset time. The above scheme, in the case of a failure to upgrade the program to be upgraded, attempts to upgrade again, and in the case of a number of re-upgrades exceeding a preset threshold, runs the historical version of the program, thereby avoiding the problem of program instability caused by a failure to upgrade the program to be upgraded, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An application environment diagram of a vehicle upgrading method in an embodiment;

[0041] Figure 2 A schematic diagram of a process flow of a vehicle upgrading method in one embodiment;

[0042] Figure 3 A schematic diagram of a flow chart of re-upgrading a program to be upgraded in one embodiment;

[0043] Figure 4 A schematic diagram of a flow chart of verifying version information of a program to be upgraded in one embodiment;

[0044] Figure 5 A schematic diagram of a flow chart of re-running a program of a version to be upgraded in one embodiment;

[0045] Figure 6 A schematic flow chart of a vehicle upgrading method in another embodiment;

[0046] Figure 7 is a structural block diagram of a vehicle upgrading device in one embodiment;

[0047] Figure 8 FIG. 4 is a diagram showing the internal structure of a vehicle-mounted terminal in one embodiment. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0049] The vehicle upgrade method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown in the figure. When the operator in the vehicle triggers the software upgrade instruction through the human-machine interface (HMI) of the central control, the Over-The-Air Update (OMU) client program embedded in the central control program will notify the central control OMU master program to send an upgrade request message to the server through the network. When the server receives the application upgrade request message, it returns the version information of the central control program, the version information of the instrument program, and the version information and file list of the user interface (UI) engine program on the server. Then the central control OMU master program compares the version information of the central control program, the version information of the instrument program, and the version information of the UI engine program returned by the server with the local version information of the central control program, the version information of the instrument program, and the version information of the UI engine program, and downloads the program files with different version information. Then, the different program files are loaded into the program running area, and the current historical version of the corresponding component is stored in the program rollback area; and the corresponding component is controlled to run the different program files to complete the program upgrade.

[0050] The method provided in the embodiment of the present application can be executed by an on-board terminal in a vehicle, specifically by an OMU main control program in the on-board terminal.

[0051] In one embodiment, Figure 2 As shown, a vehicle upgrade method is provided, which is described by taking the method applied to a vehicle-mounted terminal as an example, and includes the following steps:

[0052] S201, during the upgrade process of a target component in a cockpit of a target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed.

[0053] The target component includes at least one of a central control, an instrument, and a user interface engine. The target vehicle is a vehicle for component upgrade. After the server sends the upgraded version of the program to the vehicle, the OMU program controls the target component in the cockpit of the target vehicle to perform program upgrade.

[0054] During the target component upgrade process in the cockpit of the target vehicle, the operation of obtaining the heartbeat message sent by the target component is performed. If the upgraded version of the target component is successfully upgraded, the OMU program can obtain the heartbeat message sent by the target component.

[0055] S202: If no heartbeat message is received from the target component within a first preset time period, restart the program of the target component to be upgraded.

[0056] Exemplarily, if the heartbeat message sent by the target component is not received within the first preset time, it is determined that the upgrade of the target component's upgraded version program has failed, and the target component's upgraded version program can be restarted and the upgrade operation of the target component's upgraded version program can be performed again. The first preset time can be set to 10 seconds.

[0057] In some optional implementations, if a heartbeat message sent by the target component is received within a first preset time period, it is determined that the to-be-upgraded version of the target component is successfully upgraded.

[0058] S203, within the second preset time period, when the number of restarts of the to-be-upgraded version program of the target component exceeds a preset threshold, running the historical version program of the target component.

[0059] Exemplarily, after the program of the version to be upgraded of the target component is restarted, the counter can be controlled to increase by one. A preset threshold value of the number of upgrade restarts can be preset, for example, it can be set to 3 times. Within the second preset time period, if the number of restarts of the program of the version to be upgraded of the target component exceeds the preset threshold value, it is considered that the upgrade of the program of the version to be upgraded of the target component has failed, and the historical version program of the target component can be run at this time.

[0060] The second preset duration is greater than the first preset duration. The historical version program of the target component may be a pre-stored historical version program that the target component runs before the upgrade. For example, it may be stored in the program rollback area, and the program execution area is used to execute the update of the target component's to-be-upgraded version program.

[0061] The above vehicle upgrade method, during the upgrade process of the target component in the cockpit of the target vehicle, performs an operation of obtaining the heartbeat message sent by the target component; wherein the target component includes at least one of the central control, instrument and user interface engine; if the heartbeat message sent by the target component is not received within the first preset time, the target component's version of the program to be upgraded is restarted; within the second preset time, if the number of restarts of the target component's version of the program to be upgraded exceeds a preset threshold, the target component's historical version of the program is run; wherein the second preset time is greater than the first preset time. In the above scheme, in the case of a failure to upgrade the program to be upgraded, an attempt is made to upgrade again, and in the case of a number of re-upgrades exceeding a preset threshold, the historical version of the program is run, thereby avoiding the problem of program instability caused by a failure to upgrade the program to be upgraded, thereby improving the user experience.

[0062] In some optional implementations, after the historical version program of the target component is run, the version program to be upgraded may be verified, and a re-upgrade operation may be performed based on the verification result.

[0063] Based on this, see Figure 3 , Figure 3 A flowchart for re-upgrading a program to be upgraded is provided, which specifically includes the following steps:

[0064] S301, verifying the version information of the program to be upgraded.

[0065] Among them, the version information of the program to be upgraded includes the target version number and the target version content; for example, the target version number in the version information of the program to be upgraded can be the version information 00.21 of the instrument program to be upgraded, or the version information 00.33 of the central control program to be upgraded, or the version information 00.18 of the UI program to be upgraded, etc.

[0066] Exemplarily, in the file of the version of the program to be upgraded, the first and second bytes store the target version number, the third and fourth bytes store the preset check value, and the fifth byte and thereafter are the file content.

[0067] Exemplarily, the version information of the program to be upgraded may be verified, for example, to verify whether the target version number is the latest version number, and to verify whether the content of the target version is correct and complete.

[0068] S302, when the version information verification of the version program to be upgraded passes, controlling the target component to re-run the version program to be upgraded.

[0069] Exemplarily, when the version information verification of the program to be upgraded passes, it means that there is no problem with the version information of the program to be upgraded. The upgrade failure may be due to program or network abnormalities. In this case, the upgrade can be retried, that is, the target component can be controlled to re-run the program to be upgraded.

[0070] S303: When the version information verification of the program to be upgraded fails, a request for re-obtaining the program to be upgraded is sent to the server, so that the server sends a new program to be upgraded to the target vehicle.

[0071] If the version information verification of the program to be upgraded fails, it may be that the target version number of the program to be upgraded is not the latest, or the target version content is damaged during the transmission process, making the target version content incomplete. Therefore, a request to re-obtain the program to be upgraded can be sent to the server, so that the server can send a new program to be upgraded to the target vehicle.

[0072] In the embodiment of the present application, by verifying the version of the program to be upgraded, the reason for the unsuccessful upgrade can be determined, and corresponding measures can be taken to achieve a successful upgrade of the version of the program to be upgraded.

[0073] In some optional implementations, see Figure 4 , Figure 4 A flowchart for verifying the version information of a program to be upgraded is provided, which specifically includes the following steps:

[0074] S401, compare the target version number with the historical version number of the historical version program to obtain a first comparison result.

[0075] Exemplarily, the target version number may be compared with the historical version number of the historical version program to determine whether the target version number is the latest version number, thereby obtaining a first comparison result.

[0076] S402, comparing the target check value corresponding to the target version content with the preset check value to obtain a second comparison result.

[0077] Optionally, the target check value corresponding to the target version content may be compared with a preset check value to determine whether the target check value is consistent with the preset check value, thereby obtaining a second comparison result. The target check value corresponding to the target version content may be calculated using a checksum algorithm.

[0078] S403, when the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target check value is consistent with the preset check value, it is determined that the version information check of the version program to be upgraded passes.

[0079] Furthermore, if the first comparison result is that the target version number is greater than the historical version number, it means that the target version number is the latest version number, and the second comparison result is that the target verification value is consistent with the preset verification value, it means that the target version content is correct and complete, and it can be determined that the version information verification of the version program to be upgraded has passed.

[0080] The embodiment of the present application determines whether the version information verification of the version program to be upgraded passes by comparing the target version number with the historical version number, and comparing the target verification value with the preset verification value, thereby providing a reference for determining the reason for the upgrade failure of the version program to be upgraded.

[0081] Further, see Figure 5 , Figure 5 A flowchart of re-running a program to be upgraded is provided, which specifically includes the following steps:

[0082] S501, obtaining an event identifier of a running event in a historical version program of a target component.

[0083] The event identifier may be an event type, an event name or an event code, etc., which is used to represent different events. The event identifier of the running event in the historical version program of the target component may be obtained.

[0084] S502: When the event identifier indicates that the running event is an interruptible event, the target component is controlled to re-run the program of the version to be upgraded.

[0085] Furthermore, it is possible to determine whether the running event corresponding to the event identifier is an interruptible event based on the correspondence between each event identifier and whether the running event is allowed to be interrupted. Alternatively, the event identifier may also include a field for whether it is interruptible, and then it is possible to directly determine whether the running event corresponding to the event identifier is an interruptible event based on the event identifier. For example, if the running event is background music loading, it can be determined that the running event is an interruptible event; if the running event is a panoramic image, it can be determined that the running event is a non-interruptible event.

[0086] Exemplarily, when the event identifier represents that the running event is an interruptible event, the target component can be controlled to re-run the program of the to-be-upgraded version, and after the program of the to-be-upgraded version is successfully upgraded, the running event can be continued.

[0087] In the embodiment of the present application, when it is determined that the current running event is an interruptible event, the control target component is allowed to re-run the version of the program to be upgraded, thereby achieving the re-upgrade of the version of the program to be upgraded without affecting the timely response to the running event.

[0088] In some optional implementations, see Figure 6 , Figure 6A flow chart of another vehicle upgrade method is provided, which specifically includes the following steps:

[0089] S601, during the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed.

[0090] S602: If no heartbeat message is received from the target component within a first preset time period, restart the program of the target component to be upgraded.

[0091] S603, when the number of restarts of the to-be-upgraded version of the target component exceeds a preset threshold within a second preset time period, the target version number is compared with the historical version number of the historical version program to obtain a first comparison result.

[0092] S604: Compare the target check value corresponding to the target version content with the preset check value to obtain a second comparison result.

[0093] S605, when the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target check value is consistent with the preset check value, it is determined that the version information verification of the version program to be upgraded passes.

[0094] S606: When the version information verification of the program to be upgraded passes, obtain the event identifier of the running event in the historical version program of the target component.

[0095] S607: When the event identifier indicates that the running event is an interruptible event, the target component is controlled to re-run the program of the version to be upgraded.

[0096] S608: When the version information verification of the program to be upgraded fails, a request for re-obtaining the program to be upgraded is sent to the server, so that the server sends a new program to be upgraded to the target vehicle.

[0097] S609: If a heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

[0098] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0099] Based on the same inventive concept, the embodiment of the present application also provides a vehicle upgrade device for implementing the vehicle upgrade method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more vehicle upgrade device embodiments provided below can refer to the limitations on the vehicle upgrade method above, and will not be repeated here.

[0100] In one embodiment, Figure 7 As shown, a vehicle upgrading device is provided, comprising:

[0101] An execution module 10 is used to execute an operation of acquiring a heartbeat message sent by a target component during an upgrade process of a target component in a cockpit of a target vehicle; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0102] A restart module 20, configured to restart the program of the target component to be upgraded if no heartbeat message sent by the target component is received within a first preset time period;

[0103] The running module 30 is used to run the historical version program of the target component when the number of restarts of the upgraded version program of the target component exceeds a preset threshold within a second preset time period; wherein the second preset time period is greater than the first preset time period.

[0104] The above-mentioned vehicle upgrade device, during the upgrade process of the target component in the cockpit of the target vehicle, executes the operation of obtaining the heartbeat message sent by the target component; wherein the target component includes at least one of the central control, instrument and user interface engine; if the heartbeat message sent by the target component is not received within the first preset time period, the target component's version program to be upgraded is restarted; within the second preset time period, if the number of restarts of the target component's version program to be upgraded exceeds a preset threshold, the target component's historical version program is run; wherein the second preset time period is greater than the first preset time period. The above-mentioned scheme, in the case of a failure to upgrade the program to be upgraded, attempts to upgrade again, and in the case of a number of re-upgrades exceeding a preset threshold, runs the historical version program, thereby avoiding the problem of program instability caused by a failure to upgrade the program to be upgraded, thereby improving the user experience.

[0105] In one embodiment, the device further comprises:

[0106] A verification module, used for verifying the version information of the program to be upgraded after running the historical version program of the target component; wherein the version information includes the target version number and the target version content;

[0107] A control module, used for controlling the target component to re-run the program of the version to be upgraded when the version information of the program of the version to be upgraded passes the verification;

[0108] The sending module is used to send a request to the server to re-acquire the version of the program to be upgraded when the version information verification of the version of the program to be upgraded fails, so that the server sends a new version of the program to be upgraded to the target vehicle.

[0109] In one embodiment, the verification module is specifically used for:

[0110] The target version number is compared with the historical version number of the historical version program to obtain a first comparison result; the target verification value corresponding to the target version content is compared with the preset verification value to obtain a second comparison result; when the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target verification value is consistent with the preset verification value, it is determined that the version information verification of the version program to be upgraded has passed.

[0111] In one embodiment, the control module is specifically used to:

[0112] The event identifier of the running event in the historical version program of the target component is obtained; when the event identifier represents that the running event is an interruptible event, the target component is controlled to re-run the version program to be upgraded.

[0113] In one of the embodiments, the apparatus further comprises a determining module, configured to:

[0114] If the heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

[0115] In one of the embodiments, the historical version program of the target component is a pre-stored historical version program that the target component runs before upgrading.

[0116] Each module in the above vehicle upgrade device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the vehicle terminal in the form of hardware, or can be stored in the memory in the vehicle terminal in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0117] In one embodiment, a vehicle-mounted terminal is provided. The vehicle-mounted terminal may be a server, and its internal structure diagram may be as follows: Figure 8 As shown. The vehicle-mounted terminal includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the vehicle-mounted terminal is used to provide computing and control capabilities. The memory of the vehicle-mounted terminal includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the vehicle-mounted terminal is used to store version program data of the target component. The network interface of the vehicle-mounted terminal is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a vehicle upgrade method is implemented.

[0118] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of the present application, and does not constitute a limitation on the vehicle-mounted terminal to which the scheme of the present application is applied. The specific vehicle-mounted terminal may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0119] In one embodiment, a vehicle-mounted terminal is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0120] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0121] If the heartbeat message sent by the target component is not received within the first preset time, restart the program of the target component to be upgraded;

[0122] If the number of restarts of the to-be-upgraded version of the target component exceeds a preset threshold within a second preset time period, the historical version of the target component is run; wherein the second preset time period is greater than the first preset time period.

[0123] In one embodiment, after running the historical version program of the target component, the processor further implements the following steps when executing the computer program:

[0124] Verify the version information of the version program to be upgraded; wherein the version information includes the target version number and the target version content; if the version information of the version program to be upgraded passes the verification, control the target component to re-run the version program to be upgraded; if the version information of the version program to be upgraded fails the verification, send a request to the server to re-acquire the version program to be upgraded, so that the server sends a new version program to be upgraded to the target vehicle.

[0125] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0126] The target version number is compared with the historical version number of the historical version program to obtain a first comparison result; the target verification value corresponding to the target version content is compared with the preset verification value to obtain a second comparison result; when the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target verification value is consistent with the preset verification value, it is determined that the version information verification of the version program to be upgraded has passed.

[0127] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0128] The event identifier of the running event in the historical version program of the target component is obtained; when the event identifier represents that the running event is an interruptible event, the target component is controlled to re-run the version program to be upgraded.

[0129] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0130] If the heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

[0131] In one embodiment, the historical version program of the target component is a pre-stored historical version program that the target component runs before upgrading.

[0132] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0133] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0134] If the heartbeat message sent by the target component is not received within the first preset time, restart the program of the target component to be upgraded;

[0135] If the number of restarts of the to-be-upgraded version of the target component exceeds a preset threshold within a second preset time period, the historical version of the target component is run; wherein the second preset time period is greater than the first preset time period.

[0136] In one embodiment, after running the historical version program of the target component, the computer program further implements the following steps when executed by the processor:

[0137] Verify the version information of the version program to be upgraded; wherein the version information includes the target version number and the target version content; if the version information of the version program to be upgraded passes the verification, control the target component to re-run the version program to be upgraded; if the version information of the version program to be upgraded fails the verification, send a request to the server to re-acquire the version program to be upgraded, so that the server sends a new version program to be upgraded to the target vehicle.

[0138] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0139] The target version number is compared with the historical version number of the historical version program to obtain a first comparison result; the target verification value corresponding to the target version content is compared with the preset verification value to obtain a second comparison result; when the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target verification value is consistent with the preset verification value, it is determined that the version information verification of the version program to be upgraded has passed.

[0140] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0141] The event identifier of the running event in the historical version program of the target component is obtained; when the event identifier represents that the running event is an interruptible event, the target component is controlled to re-run the version program to be upgraded.

[0142] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0143] If the heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

[0144] In one embodiment, the historical version program of the target component is a pre-stored historical version program that the target component runs before upgrading.

[0145] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0146] During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine;

[0147] If the heartbeat message sent by the target component is not received within the first preset time, restart the program of the target component to be upgraded;

[0148] If the number of restarts of the to-be-upgraded version of the target component exceeds a preset threshold within a second preset time period, the historical version of the target component is run; wherein the second preset time period is greater than the first preset time period.

[0149] In one embodiment, after running the historical version program of the target component, the computer program further implements the following steps when executed by the processor:

[0150] Verify the version information of the version program to be upgraded; wherein the version information includes the target version number and the target version content; if the version information of the version program to be upgraded passes the verification, control the target component to re-run the version program to be upgraded; if the version information of the version program to be upgraded fails the verification, send a request to the server to re-acquire the version program to be upgraded, so that the server sends a new version program to be upgraded to the target vehicle.

[0151] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0152] The target version number is compared with the historical version number of the historical version program to obtain a first comparison result; the target verification value corresponding to the target version content is compared with the preset verification value to obtain a second comparison result; when the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target verification value is consistent with the preset verification value, it is determined that the version information verification of the version program to be upgraded has passed.

[0153] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0154] The event identifier of the running event in the historical version program of the target component is obtained; when the event identifier represents that the running event is an interruptible event, the target component is controlled to re-run the version program to be upgraded.

[0155] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0156] If the heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

[0157] In one embodiment, the historical version program of the target component is a pre-stored historical version program that the target component runs before upgrading.

[0158] 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, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0159] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0160] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0161] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A vehicle upgrading method, characterized in that: The method comprises: During the upgrade process of the target component in the cockpit of the target vehicle, an operation of acquiring a heartbeat message sent by the target component is performed; wherein the target component includes at least one of a central control, an instrument, and a user interface engine; If the heartbeat message sent by the target component is not received within the first preset time period, restarting the program of the to-be-upgraded version of the target component; If the number of restarts of the target component's to-be-upgraded version program exceeds a preset threshold within a second preset time period, the target component's historical version program is run; wherein the second preset time period is greater than the first preset time period.

2. The method according to claim 1, characterized in that: After running the historical version program of the target component, the method further includes: Verifying the version information of the program to be upgraded; wherein the version information includes the target version number and the target version content; When the version information of the program to be upgraded passes the verification, controlling the target component to re-run the program to be upgraded; When the version information verification of the version program to be upgraded fails, a request for re-obtaining the version program to be upgraded is sent to the server, so that the server sends a new version program to be upgraded to the target vehicle.

3. The method according to claim 2, characterized in that The verifying the version information of the program to be upgraded includes: Compare the target version number with the historical version number of the historical version program to obtain a first comparison result; Compare the target check value corresponding to the target version content with the preset check value to obtain a second comparison result; When the first comparison result is that the target version number is greater than the historical version number, and the second comparison result is that the target check value is consistent with the preset check value, it is determined that the version information verification of the version program to be upgraded has passed.

4. The method according to claim 2, characterized in that: Controlling the target component to re-run the program of the version to be upgraded includes: Obtaining an event identifier of a running event in a historical version program of the target component; In the case where the event identifier represents that the running event is an interruptible event, the target component is controlled to re-run the version of the program to be upgraded.

5. The method according to claim 1, characterized in that The method further comprises: If the heartbeat message sent by the target component is received within the first preset time period, it is determined that the upgraded version of the target component is successfully upgraded.

6. The method according to claim 1, characterized in that The historical version program of the target component is a pre-stored historical version program that the target component runs before upgrading.

7. A vehicle upgrading device, characterized in that: The device comprises: An execution module, used for executing an operation of acquiring a heartbeat message sent by a target component during an upgrade process of a target component in a cockpit of a target vehicle; wherein the target component includes at least one of a central control, an instrument, and a user interface engine; A restart module, used for restarting the program of the to-be-upgraded version of the target component if no heartbeat message sent by the target component is received within a first preset time period; The running module is used to run the historical version program of the target component when the number of restarts of the upgraded version program of the target component exceeds a preset threshold within a second preset time period; wherein the second preset time period is greater than the first preset time period.

8. A vehicle-mounted terminal, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images