Remote upgrading method and device, computer equipment and storage medium

Abstract

The invention relates to a remote upgrading method and device, computer equipment and a storage medium. The method comprises the steps that after a remote upgrading failure event for a target controller in a target vehicle is detected, a remote upgrading log of the remote upgrading failure event is acquired; wherein the remote upgrade log comprises source information of a target upgrade package file used for upgrading the target controller, current transmission state information and a transmitted upgrade package file; determining a failure reason label according to the transmitted upgrade package file and the current transmission state information; wherein the failure reason label is software package abnormity, security access abnormity or external upgrade interruption; and upgrading the target controller again according to the failure reason label and the remote upgrading log. By adopting the method, the remote upgrading efficiency of the vehicle can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a remote upgrade method, apparatus, computer equipment and storage medium. Background Art

[0002] Remote upgrade technology is a very popular Internet of Vehicles technology. This technology has a wide range of applications. It can realize remote upgrades of vehicle controllers through vehicle-cloud interaction, reduce the frequency of offline upgrades at service stations, and save time and labor costs.

[0003] The active upgrade strategies of vehicle remote upgrade technology all require the vehicle to remain stationary and require the cooperation of the user for a short period of time. However, due to some emergencies in market vehicles or the user's accidental touch causing the vehicle to ignite or power off, the remote upgrade fails. However, when the remote upgrade fails, the operation and maintenance personnel generally analyze the cause of the failure based on the vehicle-side operation log and then determine the solution. This method is not only time-consuming and labor-intensive, but also requires high skills from the operation and maintenance personnel. When the operation and maintenance personnel have average skills, they may not even be able to determine the cause of the failure, and thus cannot solve the problem of remote upgrade failure, reducing the efficiency of remote upgrades. Summary of the invention

[0004] Based on this, it is necessary to provide a remote upgrade method, device, computer equipment and storage medium that can improve the efficiency of remote upgrading of vehicles in response to the above technical problems.

[0005] In a first aspect, the present application provides a remote upgrade method, comprising:

[0006] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller, current transmission status information, and transmitted upgrade package files;

[0007] Determine a failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0008] The target controller is upgraded again according to the failure reason tag and the remote upgrade log.

[0009] In one embodiment, determining the failure reason tag according to the transmitted upgrade package file and the current transmission status information includes:

[0010] Decompressing the transmitted upgrade package file to obtain a decompressed upgrade package file;

[0011] Verify the signature of the decompressed upgrade package file to obtain a verification result;

[0012] The failure reason label is determined according to the signature verification result.

[0013] In one embodiment, determining the failure reason tag according to the signature verification result includes:

[0014] If the signature verification result is a signature verification failure, determining the failure reason label as a software package abnormality;

[0015] If the signature verification result is successful, a security access request is sent to the target controller based on the diagnostic protocol, and the failure reason label of the remote upgrade event is determined according to the feedback of the target controller to the security access request within a preset time.

[0016] In one embodiment, determining the failure reason tag of the remote upgrade event according to the feedback of the target controller to the security access request within a preset time includes:

[0017] If no feedback information from the target controller regarding the security access request is received within a preset time, determining that the failure cause label of the remote upgrade event is a security access exception;

[0018] If feedback information from the target controller in response to the security access request is received within a preset time and a flash interrupt instruction is detected, the failure cause label of the remote upgrade event is determined to be an external upgrade interrupt.

[0019] In one embodiment, re-upgrading the target controller according to the failure reason tag and the remote upgrade log includes:

[0020] If the failure reason tag is software package abnormality, sending an upgrade package re-making request to the target terminal that generates the target upgrade package file according to the source information, so that the target terminal re-generates the target upgrade package file according to the upgrade package re-making request; wherein the upgrade package re-making request carries the identification information of the target controller;

[0021] Receiving the regenerated target upgrade package file sent by the target terminal;

[0022] The regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0023] In one embodiment, re-upgrading the target controller according to the failure reason tag and the remote upgrade log includes:

[0024] If the failure reason tag is security access exception, upgrading the remote upgrade terminal;

[0025] After the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller, so that the target controller is upgraded according to the transmitted upgrade package file.

[0026] In one embodiment, re-upgrading the target controller according to the failure reason tag and the remote upgrade log includes:

[0027] If the failure tag is an external upgrade interrupt, the target upgrade package file is retransmitted according to the transmitted upgrade package file, so that the target controller is re-upgraded according to the target upgrade package file after the transmission is completed.

[0028] In a second aspect, the present application also provides a remote upgrade device, comprising:

[0029] A log acquisition module, used for acquiring a remote upgrade log of a remote upgrade failure event after detecting a remote upgrade failure event for a target controller in a target vehicle; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller, current transmission status information, and transmitted upgrade package files;

[0030] A label determination module, used to determine a failure reason label according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason label is a software package exception, a security access exception, or an external upgrade interruption;

[0031] The remote upgrade module is used to re-upgrade the target controller according to the failure reason label and the remote upgrade log.

[0032] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0033] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller, current transmission status information, and transmitted upgrade package files;

[0034] Determine a failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0035] The target controller is upgraded again according to the failure reason tag and the remote upgrade log.

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

[0037] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller, current transmission status information, and transmitted upgrade package files;

[0038] Determine a failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0039] The target controller is upgraded again according to the failure reason tag and the remote upgrade log.

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

[0041] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller, current transmission status information, and transmitted upgrade package files;

[0042] Determine a failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0043] The target controller is upgraded again according to the failure reason tag and the remote upgrade log.

[0044] The above remote upgrade method, apparatus, computer equipment and storage medium, after detecting a remote upgrade failure event for a target controller in a target vehicle, obtains the remote upgrade failure event, including the source information of the target upgrade package file used to upgrade the target controller and the remote upgrade log of the transmitted upgrade package file; further, determines the failure reason label based on the transmitted upgrade package file; wherein the failure reason label is a software package exception, a security access exception or an external upgrade interruption; and re-upgrades the target controller based on the failure reason label and the remote upgrade log. The above scheme, after detecting an actual remote failure event, accurately determines the failure reason label that caused the remote upgrade failure event based on the remote upgrade log of the remote upgrade failure event; further, can accurately complete the process of re-upgrading the target controller based on the failure reason label and the remote upgrade log, thereby improving the efficiency and accuracy of the remote upgrade process. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 An application environment diagram of a remote upgrade method in an embodiment;

[0047] Figure 2 A flowchart of a remote upgrade method in one embodiment;

[0048] Figure 3 A schematic diagram of a process for determining a failure reason label in one embodiment;

[0049] Figure 4 A schematic diagram of a process for determining a failure reason label in another embodiment;

[0050] Figure 5 A schematic diagram of a process for determining a failure reason label in another embodiment;

[0051] Figure 6 A schematic diagram of a process of re-upgrading a target controller in one embodiment;

[0052] Figure 7 A schematic diagram of a process of re-upgrading a target controller in one embodiment;

[0053] Figure 8 A flowchart of a remote upgrade method in another embodiment;

[0054] Fig. 9 is a structural block diagram of a remote upgrade device in an embodiment;

[0055] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0056] 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.

[0057] The remote upgrade method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the remote upgrade platform 103 is a platform for remotely upgrading the vehicle, for example, it can be an application installed in a mobile terminal. The remote upgrade terminal 101 is a terminal installed in the target vehicle for communicating with the remote upgrade platform; the target controller 102 is the controller that needs to be upgraded in the target vehicle. Optionally, after detecting a remote upgrade failure event for the target controller 102 in the target vehicle, the remote upgrade terminal 101 obtains a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes the source information of the target upgrade package file used to upgrade the target controller and the transmitted upgrade package file; according to the transmitted upgrade package file, determine the failure reason label; wherein the failure reason label is a software package exception, a security access exception or an external upgrade interruption; according to the failure reason label and the remote upgrade log, re-upgrade the target controller.

[0058] In one embodiment, Figure 2 As shown, a remote upgrade method is provided, which is applied to Figure 1 Taking the remote upgrade terminal 101 in the target vehicle as an example, the following steps are specifically included:

[0059] S201, after detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event.

[0060] The target vehicle can be any vehicle equipped with a remote upgrade terminal; the target controller is the controller that needs to be upgraded; and the remote upgrade failure event is a failure event caused by an error in the upgrade process of the target controller. The remote upgrade log includes the source information of the target upgrade package file used to upgrade the target controller, the current transmission status information, and the transmitted upgrade package file.

[0061] Optionally, the owner of the target vehicle can upgrade the target controller through the remote upgrade platform. Furthermore, the remote upgrade platform will obtain the target upgrade package file for upgrading the target controller from the remote upgrade platform to the remote upgrade terminal in the target vehicle, and send the target upgrade package file to the target controller to complete the upgrade of the target controller.

[0062] Optionally, if the target controller is abnormally interrupted during the upgrade process, a remote upgrade failure indication will be sent to the remote upgrade terminal. At this time, the remote upgrade terminal can detect the remote upgrade event; further, a remote upgrade log of the remote upgrade failure event cached during the remote upgrade process is obtained.

[0063] S202: Determine a failure reason tag according to the transmitted upgrade package file.

[0064] The failure reason label is software package exception, security access exception or external upgrade interruption.

[0065] Optionally, the target upgrade package file may be resumably transferred based on the transferred upgrade package file, and during the resuming process, the cause of the remote upgrade failure event may be detected based on actual conditions, and a failure cause label may be determined based on the failure cause.

[0066] S203: Re-upgrade the target controller according to the failure reason tag and the remote upgrade log.

[0067] Optionally, different re-upgrade strategies may be formulated in advance for different failure reason tags, and based on the failure reason tag and the re-upgrade strategy corresponding to the failure reason tag, the target controller may be re-upgraded according to the remote upgrade log.

[0068] In the above remote upgrade method, after detecting a remote upgrade failure event for a target controller in a target vehicle, the remote upgrade failure event is obtained, including source information of the target upgrade package file used to upgrade the target controller and a remote upgrade log of the transmitted upgrade package file; further, the failure reason tag is determined based on the transmitted upgrade package file; wherein the failure reason tag is a software package exception, a security access exception, or an external upgrade interruption; and the target controller is re-upgraded based on the failure reason tag and the remote upgrade log. In the above scheme, after detecting an actual remote failure event, the failure reason tag that caused the remote upgrade failure event is accurately determined based on the remote upgrade log of the remote upgrade failure event; further, the process of re-upgrading the target controller can be accurately completed based on the failure reason tag and the remote upgrade log, thereby improving the efficiency and accuracy of the remote upgrade process.

[0069] In one embodiment, Figure 3As shown, a method for determining a failure reason label is provided, which specifically includes the following steps:

[0070] S301, decompress the transmitted upgrade package file to obtain a decompressed upgrade package file.

[0071] Optionally, the transferred upgrade package file may be decompressed by using a decompression tool to obtain the decompressed upgrade package file.

[0072] S302, verify the signature of the decompressed upgrade package file to obtain a signature verification result.

[0073] The signature verification result may be a success or a failure.

[0074] Optionally, the decompressed upgrade package can be verified by a signature verification tool to verify the integrity of the decompressed upgrade package file, that is, to verify the integrity of the transmitted upgrade package file. Specifically, if the transmitted upgrade package file is verified to be complete, the verification result may be a successful verification; correspondingly, if the transmitted upgrade package is missing or packaged incorrectly, the verification result may be a failed verification.

[0075] S303: Determine the failure reason tag according to the signature verification result.

[0076] Optionally, if the signature verification result is a signature verification failure, the failure cause can be directly determined to be an abnormal software package. If the verification result is a verification success, it means that the transmitted upgrade package file is normal; at this time, the failure cause label can be determined in combination with the remote upgrade log and the actual situation.

[0077] In this embodiment, by decompressing the transmitted upgrade package file and obtaining the signature verification result based on the compressed upgrade package file, it is equivalent to considering whether there is an abnormality in the transmitted upgrade package file; further, the accuracy of the determined failure reason label is guaranteed based on the signature verification result.

[0078] Optionally, based on the above embodiment, in one embodiment, as Figure 4 As shown, a method for determining a failure reason label is provided, which specifically includes the following steps:

[0079] S401: If the signature verification result is a signature verification failure, determine that the failure reason tag is a software package abnormality.

[0080] Optionally, if the signature verification result is a signature verification failure, it means that there is an abnormality in the transmitted upgrade package file, that is, the remote upgrade failure event is caused by the abnormality of the transmitted upgrade package file. Therefore, it can be determined that the failure reason label is a software package abnormality.

[0081] S401, if the signature verification result is successful, a security access request is sent to the target controller based on the diagnostic protocol, and a failure reason tag of the remote upgrade event is determined according to the feedback of the target controller to the security access request within a preset time.

[0082] The security access request is a request for requesting the target controller to establish a security access channel. The feedback status represents whether the target controller responds to the security access request.

[0083] Optionally, if the signature verification result is successful, it means that the transmitted upgrade package file is normal, so it is necessary to continue to determine the cause of the remote upgrade failure. At this time, a security access request can be sent to the target controller based on the diagnostic protocol. Further, the failure cause label of the remote upgrade event can be determined based on the feedback of the target controller to the security access request within a preset time.

[0084] For example, if the target controller does not receive feedback information on the security access request within the preset time, it can be determined that there is a problem with the security access between the target controller and the target controller. At this time, the failure reason tag can be determined as a security access exception. Correspondingly, if the target controller receives feedback information on the security access request within the preset time, it means that the security access between the target controller and the target controller is normal. At this time, it is necessary to continue to combine the remote upgrade log and the actual situation to determine the failure reason tag.

[0085] The embodiment of the present application combines the signature verification result and introduces a diagnostic protocol to send a security access request to the target controller when the signature verification result is successful. This is equivalent to considering whether there is an abnormality in the security access between the remote upgrade terminal and the target controller, and further ensures the accuracy and comprehensiveness of the determined failure cause label.

[0086] Optionally, based on the above embodiment, in one embodiment, as Figure 5 As shown, a method for determining a failure reason label is provided, which specifically includes the following steps:

[0087] S501: If no feedback information of the target controller in response to the security access request is received within a preset time, the failure reason label of the remote upgrade event is determined to be a security access exception.

[0088] Optionally, if no feedback information is received from the target controller regarding the security access request within a preset time, it can be determined that there is a problem with the security access to the target controller. In this case, the failure cause label can be determined as a security access exception.

[0089] S502: If feedback information of the target controller in response to the security access request is received within a preset time and a flash interrupt instruction is detected, it is determined that the failure cause label of the remote upgrade event is an external upgrade interrupt.

[0090] The flash interrupt instruction is a command sent by the target controller after an abnormal termination during the flash process.

[0091] Optionally, if feedback information of the target controller for the security access request is received within a preset time, it means that the security access with the target controller is normal. At this time, secure communication with the target controller can be carried out normally. Furthermore, after the security access verification is passed, in the transmission and verification stage, if a flash terminal instruction that interrupts the flash is detected according to the remote upgrade log, it can be determined that the failure cause label of the remote upgrade event is an external upgrade interrupt.

[0092] The embodiment of the present application ensures the accuracy and comprehensiveness of the determined failure cause label by fully considering the security access situation and the abnormal interruption situation caused by external interference, and combining the feedback of the target controller to the security access request and the flash interruption instruction.

[0093] Optionally, in one embodiment, Figure 6 As shown, a method for re-upgrading a target controller when the failure reason label is a software package abnormality is provided, which specifically includes the following steps:

[0094] S601, if the failure reason tag is software package abnormality, sending an upgrade package re-making request to a target terminal that generates a target upgrade package file according to source information, so that the target terminal re-generates the target upgrade package file according to the upgrade package re-making request.

[0095] The upgrade package re-production request is a request for instructing the target terminal to re-generate the target upgrade package file; the upgrade package re-production request carries the identification information of the target controller.

[0096] Optionally, if the failure reason label is software package exception, it means that there is an exception in the target upgrade package file obtained by the remote upgrade terminal itself. Therefore, the target terminal for generating the target upgrade package can be determined based on the source information of the target upgrade package file, which may be a remote upgrade platform; further, an upgrade package remake request is sent to the target terminal that generates the target upgrade package file, so that the target terminal regenerates the target upgrade package file according to the upgrade package remake request, and sends the regenerated target upgrade package file to the remote upgrade terminal.

[0097] S602: Receive the regenerated target upgrade package file sent by the target terminal.

[0098] S603: Send the regenerated target upgrade package file to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0099] Optionally, after receiving the regenerated target upgrade package file sent by the target terminal, the regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0100] In the embodiment of the present application, when the failure reason is labeled as software package exception, the regenerated target upgrade package file is re-obtained from the target terminal according to the source information, thereby ensuring the integrity and accuracy of the regenerated target upgrade package file; further, ensuring that the target controller upgrade process can be completed smoothly.

[0101] Optionally, in one embodiment, Figure 7 As shown, a method for re-upgrading a target controller when the failure reason label is a security access exception is provided, which specifically includes the following steps:

[0102] S701: If the failure reason tag is security access exception, the remote upgrade terminal is upgraded.

[0103] Optionally, if the failure reason label is security access exception, it means that the version of the remote upgrade terminal is too low. In this case, the software package file for upgrading the remote upgrade terminal can be obtained from the remote upgrade platform, and the remote upgrade terminal can be upgraded according to the obtained software package file to ensure that the remote upgrade terminal reaches the latest version.

[0104] S702: After the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller, so that the target controller is upgraded according to the transmitted upgrade package file.

[0105] Optionally, after the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is re-sent to the target controller, so that the target controller is upgraded according to the transmitted upgrade package file.

[0106] In the embodiment of the present application, by upgrading the Yancheng upgrade terminal when the failure reason label is a security access exception, the remote upgrade terminal can ensure that the target controller successfully completes the upgrade process under the latest version.

[0107] Optionally, if the failure tag is an external upgrade interruption, the target upgrade package file is resumed based on the transmitted upgrade package file, so that the target controller is re-upgraded based on the target upgrade package file that has been transmitted. Specifically, if the failure tag is an external upgrade interruption, it means that the remote upgrade failure event is caused by external interference, such as the target vehicle igniting or powering off due to some sudden conditions or the user accidentally touching it. At this time, it is only necessary to resume the target upgrade package file based on the transmitted upgrade package file, so that the target controller is re-upgraded based on the target upgrade package file that has been transmitted. It can be understood that in the case where the failure tag is an external upgrade interruption, the target upgrade package file is resumed, which avoids the retransmission of the entire target upgrade package file and reduces event waste.

[0108] Figure 8 FIG. 1 is a flow chart of a remote upgrade method in another embodiment. Based on the above embodiment, this embodiment provides an optional example of a remote upgrade method. Figure 8 The specific implementation process is as follows:

[0109] S801, after detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event.

[0110] The remote upgrade log includes source information of a target upgrade package file used to upgrade the target controller and the transmitted upgrade package file.

[0111] S802, decompress the transmitted upgrade package file in the remote upgrade log to obtain a decompressed upgrade package file.

[0112] S803, verify the signature of the decompressed upgrade package file to obtain a signature verification result.

[0113] S804, determine whether the signature verification result is successful; if so, determine the failure reason tag is software package abnormality, and execute S808; if not, execute S805.

[0114] S805: Send a security access request to the target controller based on the diagnostic protocol.

[0115] S806, determine whether feedback information of the target controller for the security access request is received within a preset time; if so, determine that the failure reason tag is a security access exception, and execute S811; if not, execute S807.

[0116] S807, if a flash interrupt instruction is detected, the failure reason label is determined to be an external upgrade interrupt, and S813 is executed.

[0117] S808, sending an upgrade package re-making request to the target terminal that generates the target upgrade package file according to the source information in the remote upgrade log, so that the target terminal re-generates the target upgrade package file according to the upgrade package re-making request.

[0118] The upgrade package re-making request carries the identification information of the target controller.

[0119] S809: Receive the regenerated target upgrade package file sent by the target terminal.

[0120] S810: Send the regenerated target upgrade package file to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0121] S811, upgrading the remote upgrade terminal.

[0122] S812, after the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller, so that the target controller is upgraded according to the transmitted upgrade package file.

[0123] S813, according to the transmitted upgrade package file, the target upgrade package file is retransmitted from the breakpoint, so that the target controller is re-upgraded according to the target upgrade package file after the transmission is completed.

[0124] The specific process of the above S801-S813 can be found in the description of the above method embodiment. The implementation principle and technical effect are similar and will not be repeated here.

[0125] 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 does not have a strict order restriction, 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 to be 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.

[0126] Based on the same inventive concept, the embodiment of the present application also provides a remote upgrade device for implementing the remote 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 remote upgrade device embodiments provided below can refer to the limitations of the remote upgrade method above, and will not be repeated here.

[0127] In an exemplary embodiment, Fig. 9 As shown, a remote upgrade device 900 is provided, including: a log acquisition module 910, a tag determination module 920 and a remote upgrade module 930, wherein:

[0128] The log acquisition module 910 is used to obtain the remote upgrade log of the remote upgrade failure event after detecting the remote upgrade failure event for the target controller in the target vehicle; wherein the remote upgrade log includes the source information of the target upgrade package file used to upgrade the target controller, the current transmission status information and the transmitted upgrade package file.

[0129] The label determination module 920 is used to determine the failure reason label according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason label is software package abnormality, security access abnormality or external upgrade interruption.

[0130] The remote upgrade module 930 is used to re-upgrade the target controller according to the failure reason tag and the remote upgrade log.

[0131] The above-mentioned remote upgrade device. After detecting a remote upgrade failure event for a target controller in a target vehicle, the remote upgrade failure event is obtained, including source information of the target upgrade package file used to upgrade the target controller and a remote upgrade log of the transmitted upgrade package file; further, the failure reason label is determined based on the transmitted upgrade package file; wherein the failure reason label is a software package exception, a security access exception, or an external upgrade interruption; and the target controller is re-upgraded based on the failure reason label and the remote upgrade log. The above-mentioned scheme, after detecting an actual remote failure event, accurately determines the failure reason label that caused the remote upgrade failure event based on the remote upgrade log of the remote upgrade failure event; further, the process of re-upgrading the target controller can be accurately completed based on the failure reason label and the remote upgrade log, thereby improving the efficiency and accuracy of the remote upgrade process.

[0132] In one embodiment, the tag determination module 920 includes:

[0133] The file decompression unit is used to decompress the transmitted upgrade package file to obtain a decompressed upgrade package file.

[0134] The result determination unit is used to verify the signature of the decompressed upgrade package file to obtain the signature verification result.

[0135] The label determination unit is used to determine the failure reason label according to the signature verification result.

[0136] In one embodiment, the tag determination unit includes:

[0137] The first determining subunit is configured to determine the failure cause label as software package abnormality if the signature verification result is signature verification failure.

[0138] The second determination subunit is used to send a security access request to the target controller based on the diagnostic protocol if the signature verification result is successful, and determine the failure reason tag according to the feedback of the target controller to the security access request within a preset time.

[0139] In one embodiment, the second determining subunit is specifically used for:

[0140] If no feedback information is received from the target controller regarding the security access request within the preset time, the failure cause label of the remote upgrade event is determined to be a security access exception; if feedback information is received from the target controller regarding the security access request within the preset time and a flash interrupt instruction is detected, the failure cause label is determined to be an external upgrade interrupt.

[0141] In one embodiment, the remote upgrade module 930 is specifically used to:

[0142] If the failure reason label is software package exception, then based on the source information, an upgrade package remake request is sent to the target terminal that generates the target upgrade package file, so that the target terminal regenerates the target upgrade package file according to the upgrade package remake request; wherein the upgrade package remake request carries the identification information of the target controller; the regenerated target upgrade package file sent by the target terminal is received; and the regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0143] In one embodiment, the remote upgrade module 930 is further configured to:

[0144] If the failure reason label is a security access exception, the remote upgrade terminal is upgraded; after the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller so that the target controller is upgraded according to the transmitted upgrade package file.

[0145] In one embodiment, the remote upgrade module 930 is further configured to:

[0146] If the failure tag is external upgrade interruption, the target upgrade package file is retransmitted according to the transmitted upgrade package file, so that the target controller is re-upgraded according to the target upgrade package file whose transmission has been completed.

[0147] Each module in the above remote 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 a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0148] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.10 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device 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 input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a remote upgrade method is implemented.

[0149] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0150] In one embodiment, a computer device 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:

[0151] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file used to upgrade the target controller, current transmission status information, and transmitted upgrade package files;

[0152] Determine the failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0153] Re-upgrade the target controller based on the failure reason tag and remote upgrade log.

[0154] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the transmitted upgrade package file and the current transmission status information, the processor further implements the following steps:

[0155] The transmitted upgrade package file is decompressed to obtain a decompressed upgrade package file; the decompressed upgrade package file is signature-verified to obtain a signature verification result; and a failure reason label is determined according to the signature verification result.

[0156] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the signature verification result, the processor further implements the following steps:

[0157] If the signature verification result is a signature verification failure, the failure reason tag is determined to be a software package abnormality; if the signature verification result is a signature verification success, a security access request is sent to the target controller based on the diagnostic protocol, and the failure reason tag is determined based on the feedback of the target controller to the security access request within a preset time.

[0158] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the feedback of the target controller to the security access request within a preset time, the processor further implements the following steps:

[0159] If no feedback information is received from the target controller regarding the security access request within the preset time, the failure cause label of the remote upgrade event is determined to be a security access exception; if feedback information is received from the target controller regarding the security access request within the preset time and a flash interrupt instruction is detected, the failure cause label is determined to be an external upgrade interrupt.

[0160] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0161] If the failure reason label is software package exception, then based on the source information, an upgrade package remake request is sent to the target terminal that generates the target upgrade package file, so that the target terminal regenerates the target upgrade package file according to the upgrade package remake request; wherein the upgrade package remake request carries the identification information of the target controller; the regenerated target upgrade package file sent by the target terminal is received; and the regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0162] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0163] If the failure reason label is a security access exception, the remote upgrade terminal is upgraded; after the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller so that the target controller is upgraded according to the transmitted upgrade package file.

[0164] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0165] If the failure tag is external upgrade interruption, the target upgrade package file is retransmitted according to the transmitted upgrade package file, so that the target controller is re-upgraded according to the target upgrade package file whose transmission has been completed.

[0166] 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:

[0167] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file used to upgrade the target controller, current transmission status information, and transmitted upgrade package files;

[0168] Determine the failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0169] Re-upgrade the target controller based on the failure reason tag and remote upgrade log.

[0170] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the transmitted upgrade package file and the current transmission status information, the processor further implements the following steps:

[0171] The transmitted upgrade package file is decompressed to obtain a decompressed upgrade package file; the decompressed upgrade package file is signature-verified to obtain a signature verification result; and a failure reason label is determined according to the signature verification result.

[0172] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the signature verification result, the processor further implements the following steps:

[0173] If the signature verification result is a signature verification failure, the failure reason tag is determined to be a software package abnormality; if the signature verification result is a signature verification success, a security access request is sent to the target controller based on the diagnostic protocol, and the failure reason tag is determined based on the feedback of the target controller to the security access request within a preset time.

[0174] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the feedback of the target controller to the security access request within a preset time, the processor further implements the following steps:

[0175] If no feedback information is received from the target controller regarding the security access request within the preset time, the failure cause label of the remote upgrade event is determined to be a security access exception; if feedback information is received from the target controller regarding the security access request within the preset time and a flash interrupt instruction is detected, the failure cause label is determined to be an external upgrade interrupt.

[0176] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0177] If the failure reason label is software package exception, then based on the source information, an upgrade package remake request is sent to the target terminal that generates the target upgrade package file, so that the target terminal regenerates the target upgrade package file according to the upgrade package remake request; wherein the upgrade package remake request carries the identification information of the target controller; the regenerated target upgrade package file sent by the target terminal is received; and the regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0178] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0179] If the failure reason label is a security access exception, the remote upgrade terminal is upgraded; after the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller so that the target controller is upgraded according to the transmitted upgrade package file.

[0180] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0181] If the failure tag is external upgrade interruption, the target upgrade package file is retransmitted according to the transmitted upgrade package file, so that the target controller is re-upgraded according to the target upgrade package file whose transmission has been completed.

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

[0183] After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file used to upgrade the target controller, current transmission status information, and transmitted upgrade package files;

[0184] Determine the failure reason tag according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption;

[0185] Re-upgrade the target controller based on the failure reason tag and remote upgrade log.

[0186] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the transmitted upgrade package file and the current transmission status information, the processor further implements the following steps:

[0187] The transmitted upgrade package file is decompressed to obtain a decompressed upgrade package file; the decompressed upgrade package file is signature-verified to obtain a signature verification result; and a failure reason label is determined according to the signature verification result.

[0188] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the signature verification result, the processor further implements the following steps:

[0189] If the signature verification result is a signature verification failure, the failure reason tag is determined to be a software package abnormality; if the signature verification result is a signature verification success, a security access request is sent to the target controller based on the diagnostic protocol, and the failure reason tag is determined based on the feedback of the target controller to the security access request within a preset time.

[0190] In one embodiment, when the processor executes the computer program to determine the failure reason tag according to the feedback of the target controller to the security access request within a preset time, the processor further implements the following steps:

[0191] If no feedback information is received from the target controller regarding the security access request within the preset time, the failure cause label of the remote upgrade event is determined to be a security access exception; if feedback information is received from the target controller regarding the security access request within the preset time and a flash interrupt instruction is detected, the failure cause label is determined to be an external upgrade interrupt.

[0192] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0193] If the failure reason label is software package exception, then based on the source information, an upgrade package remake request is sent to the target terminal that generates the target upgrade package file, so that the target terminal regenerates the target upgrade package file according to the upgrade package remake request; wherein the upgrade package remake request carries the identification information of the target controller; the regenerated target upgrade package file sent by the target terminal is received; and the regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

[0194] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0195] If the failure reason label is a security access exception, the remote upgrade terminal is upgraded; after the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller so that the target controller is upgraded according to the transmitted upgrade package file.

[0196] In one embodiment, when the processor executes the computer program to re-upgrade the target controller according to the failure reason tag and the remote upgrade log, the processor also implements the following steps:

[0197] If the failure tag is external upgrade interruption, the target upgrade package file is retransmitted according to the transmitted upgrade package file, so that the target controller is re-upgraded according to the target upgrade package file whose transmission has been completed.

[0198] It should be noted that the data involved in this application (including but not limited to data used for analysis, storage, display, etc.) are all information and data fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0199] 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.

[0200] 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.

[0201] 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 remote upgrade method, characterized in that: A remote upgrade terminal applied to a target vehicle, the method comprising: After detecting a remote upgrade failure event for a target controller in a target vehicle, obtaining a remote upgrade log of the remote upgrade failure event; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller and a transmitted upgrade package file; Determine a failure reason tag according to the transmitted upgrade package file; wherein the failure reason tag is software package abnormality, security access abnormality or external upgrade interruption; The target controller is upgraded again according to the failure reason tag and the remote upgrade log.

2. The method according to claim 1, characterized in that The step of determining the failure reason tag according to the transmitted upgrade package file includes: Decompressing the transmitted upgrade package file to obtain a decompressed upgrade package file; Verify the signature of the decompressed upgrade package file to obtain a verification result; The failure reason label is determined according to the signature verification result.

3. The method according to claim 2, characterized in that Determining the failure reason tag according to the signature verification result includes: If the signature verification result is a signature verification failure, determining the failure reason label as a software package abnormality; If the signature verification result is successful, a security access request is sent to the target controller based on a diagnostic protocol, and the failure reason tag is determined according to the feedback of the target controller to the security access request within a preset time.

4. The method according to claim 3, characterized in that The determining the failure reason tag according to the feedback of the target controller to the security access request within a preset time includes: If no feedback information from the target controller regarding the security access request is received within a preset time, determining that the failure cause label of the remote upgrade event is a security access exception; If feedback information from the target controller in response to the security access request is received within a preset time and a flash interrupt instruction is detected, it is determined that the failure cause tag is an external upgrade interrupt.

5. The method according to claim 1, characterized in that The re-upgrading the target controller according to the failure reason tag and the remote upgrade log includes: If the failure reason tag is software package abnormality, sending an upgrade package re-making request to the target terminal that generates the target upgrade package file according to the source information, so that the target terminal re-generates the target upgrade package file according to the upgrade package re-making request; wherein the upgrade package re-making request carries the identification information of the target controller; Receiving the regenerated target upgrade package file sent by the target terminal; The regenerated target upgrade package file is sent to the target controller, so that the target controller is upgraded according to the regenerated target upgrade package file.

6. The method according to claim 1, characterized in that The re-upgrading the target controller according to the failure reason tag and the remote upgrade log includes: If the failure reason tag is security access exception, upgrading the remote upgrade terminal; After the upgrade is completed, a software upgrade task carrying the transmitted upgrade package file is sent to the target controller, so that the target controller is upgraded according to the transmitted upgrade package file.

7. The method according to claim 1, characterized in that The re-upgrading the target controller according to the failure reason tag and the remote upgrade log includes: If the failure tag is an external upgrade interrupt, the target upgrade package file is retransmitted according to the transmitted upgrade package file, so that the target controller is re-upgraded according to the target upgrade package file after the transmission is completed.

8. A remote upgrade device, characterized in that: The device comprises: A log acquisition module, used for acquiring a remote upgrade log of a remote upgrade failure event after detecting a remote upgrade failure event for a target controller in a target vehicle; wherein the remote upgrade log includes source information of a target upgrade package file for upgrading the target controller, current transmission status information, and transmitted upgrade package files; A label determination module, used to determine a failure reason label according to the transmitted upgrade package file and the current transmission status information; wherein the failure reason label is a software package exception, a security access exception, or an external upgrade interruption; The remote upgrade module is used to re-upgrade the target controller according to the failure reason label and the remote upgrade log.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. 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 7 are implemented.

Images