Software fault recovery method, electronic equipment and computer readable storage medium

Abstract

The invention discloses a software fault recovery method, electronic equipment and a computer readable storage medium, and the method comprises the steps: responding to the obtained software fault information of a vehicle, and determining a target fault recovery strategy from preset fault recovery strategies according to the software fault information; determining a target vehicle from a preset vehicle database according to a fault software version in the software fault information, wherein the current software version of the target vehicle is the fault software version; and sending the target fault recovery strategy to the target vehicle, so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy. Therefore, the software fault can be timely and quickly solved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a software fault recovery method, an electronic device and a computer-readable storage medium. Background Art

[0002] As a means of transportation with complex functions, the software of a vehicle is also huge in size. During the operation of the vehicle, some unforeseen problems will inevitably occur in the software. At present, software upgrades are usually used to recover from software problems. However, since software upgrades require a certain R&D cycle, the released car software will only be upgraded in batches at a specific time to solve software problems. This method means that software problems will always exist before the software is upgraded, which seriously affects the user experience and may even affect the safety of users. Summary of the invention

[0003] The main technical problem solved by the present application is to provide a software fault recovery method, an electronic device and a computer-readable storage medium, which can solve software problems in a timely manner.

[0004] To solve the above technical problems, a technical solution adopted in the present application is: a software fault recovery method is provided, and the software fault recovery method is applied to a software fault recovery platform. The software fault recovery method includes: in response to obtaining software fault information of a vehicle, determining a target fault recovery strategy from preset fault recovery strategies according to the software fault information; determining a target vehicle from a preset vehicle database according to the faulty software version in the software fault information, the current software version of the target vehicle being the faulty software version; and sending the target fault recovery strategy to the target vehicle so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy.

[0005] In some embodiments, the step of determining a target fault recovery strategy from preset fault recovery strategies based on the software fault information includes: counting the total number of vehicles that have obtained the same software fault information; in response to the total number of vehicles being greater than a preset threshold, determining the target fault recovery strategy from preset fault recovery strategies based on the software fault information.

[0006] In some embodiments, the step of determining a target fault recovery strategy from preset fault recovery strategies based on the software fault information includes: obtaining a fault type of the software fault information; in response to the fault type belonging to a software development fault, determining the target fault recovery strategy from preset fault recovery strategies based on the software fault information.

[0007] To solve the above technical problems, another technical solution adopted in the present application is: a software fault recovery method is provided, and the software fault recovery method is applied to a vehicle. The software fault recovery method includes: receiving a target fault recovery strategy sent by a software fault recovery platform, and the target fault recovery strategy is the software fault recovery platform's response to obtaining software fault information of the vehicle, and determining the target fault recovery strategy from preset fault recovery strategies according to the software fault information; determining a target vehicle from a preset vehicle database according to the fault software version in the software fault information, and the current software version of the target vehicle is the fault software version; sending the target fault recovery strategy to the target vehicle; and performing software fault recovery processing according to the target fault recovery strategy.

[0008] In some embodiments, before the step of receiving the target fault recovery strategy sent by the software fault recovery platform, the method also includes: setting a perception information acquisition interface and a fault recovery operation execution interface, the perception information acquisition interface is used to obtain the perception information of the software, and the fault recovery operation execution interface is used to execute the software fault recovery operation.

[0009] In some embodiments, the step of performing software fault recovery processing according to the target fault recovery policy includes: obtaining the policy type of the target fault recovery policy; determining the fault recovery rules of the software according to the policy type, and performing software fault recovery processing on the software according to the fault recovery rules.

[0010] In some embodiments, the policy type includes a prevention type, and the steps of determining the fault recovery rules of the software according to the policy type and performing software fault recovery processing on the software according to the fault recovery rules include: in response to the policy type of the target fault recovery policy including a prevention type, obtaining a fault prevention operation of the software; and executing the fault prevention operation on the software.

[0011] In some embodiments, the policy type includes a repair type, and the steps of determining the fault recovery rule of the software according to the policy type, and performing software fault recovery processing on the software according to the fault recovery rule, include: in response to the policy type of the target fault recovery policy including the repair type, acquiring perception information of the software; in response to the perception information of the software characterizing that the software has a fault in the target fault recovery policy, determining a corresponding fault repair operation from the target fault recovery policy; and performing the corresponding fault repair operation on the software.

[0012] To solve the above technical problems, another technical solution adopted in the present application is: to provide an electronic device, including a memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to execute the above software fault recovery method.

[0013] In order to solve the above technical problems, another technical solution adopted by the present application is: providing a computer-readable storage medium including program data stored therein, wherein the program data is used to implement the above software fault recovery method when executed by a processor.

[0014] Compared with the above scheme, which only sends the upgraded software version uniformly when the software is upgraded to solve the software fault, resulting in the software fault not being solved in time, affecting the user experience, the present application provides a software fault recovery method, which includes: in response to the acquisition of the vehicle's software fault information, determining the target fault recovery strategy from the preset fault recovery strategy according to the software fault information; determining the target vehicle from the preset vehicle database according to the faulty software version in the software fault information, and the current software version of the target vehicle is the faulty software version; sending the target fault recovery strategy to the target vehicle, so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy. As a result, the software fault recovery platform can uniformly send the target fault recovery strategy to the target vehicle using the faulty software version in a timely manner when a software fault is found, and perform preventive repair processing of the software fault for the target vehicle, without waiting for the release of the upgraded software version, and quickly perform fault recovery. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0016] Figure 1 It is a flowchart of an exemplary embodiment of a software fault recovery method shown in the present application;

[0017] Figure 2 yes Figure 1 A flowchart of an exemplary embodiment of step S110 in the software fault recovery method is shown;

[0018] Figure 3 is a flowchart of another exemplary embodiment of a software fault recovery method shown in the present application;

[0019] Figure 4 It is a structural diagram of an exemplary embodiment of a software fault recovery system shown in the present application;

[0020] Figure 5 It is a specific flow chart of an exemplary embodiment of a software fault recovery method shown in the present application;

[0021] Figure 6 It is a structural schematic diagram of an embodiment of an electronic device provided by the present application;

[0022] Figure 7 It is a structural schematic diagram of an embodiment of a computer-readable storage medium provided by the present application. DETAILED DESCRIPTION

[0023] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It will be appreciated that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only some but not all structures related to the present application are shown in the drawings. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the art without making creative work are within the scope of protection of the present application.

[0024] First of all, it should be noted that under the general trend of automobile intelligence, software-defined cars have become an industry consensus. The software scale of smart cars is huge, including power systems, braking systems, autonomous driving, etc. In software development, it is inevitable that some unpredictable software problems will be introduced. The common solution is through software upgrades, but since software upgrades are comprehensive upgrades of the entire software, a certain research and development cycle is required. However, before the upgraded version of the software is released, software problems will always exist on the user side, seriously affecting the user experience and even affecting the user's safety.

[0025] Based on this, this application proposes a software fault recovery method, electronic device and computer-readable storage medium, which can solve software problems in a timely manner. Figure 1 , Figure 1 It is a flowchart of an exemplary embodiment of a software fault recovery method shown in the present application.

[0026] The execution subject of the software fault recovery method may be a terminal device or a server or other processing device, wherein the terminal device may be a user equipment (UE), a computer, a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. The execution subject of the software fault recovery method may also be a software fault recovery system, and the software fault recovery system includes a software fault recovery platform and a vehicle, and the software fault recovery platform and the vehicle are in communication connection. In some possible implementations, the software fault recovery method may be implemented by a processor calling a computer-readable instruction stored in a memory.

[0027] Specifically, the software fault recovery method of this embodiment includes the following steps:

[0028] S110: In response to obtaining the software fault information of the vehicle, determining a target fault recovery strategy from preset fault recovery strategies according to the software fault information.

[0029] The vehicle has software that improves the vehicle's intelligence. During the operation of the vehicle, if a vehicle failure occurs, the user can send a fault recovery instruction to the software fault recovery platform.

[0030] Software fault information refers to the fault information of the software in the vehicle, not the fault information of the hardware. The software fault information includes the name of the faulty software, the faulty software version, and the software fault characteristic information. For example, when the R&D personnel receive the fault recovery instruction sent by the vehicle, they pull the software fault information from the vehicle through the software fault recovery platform or directly collect the software fault information of the vehicle on the vehicle, such as logs, diagnostic information, and vehicle version, and then analyze the software version, fault characteristics, etc. of the vehicle. Specifically, when the user applies for after-sales service, he only needs to describe the fault characteristic information and vehicle information, and the software fault recovery platform can determine the software fault information therein according to the fault characteristic information and vehicle information. This can simplify the user's after-sales process and improve the automation level of fault recovery. As an example, the user provides vehicle information including the vehicle brand, vehicle model, and the software version of each software used by the vehicle, and provides fault characteristic information including that the vehicle cannot achieve Bluetooth connection. At this time, the software fault recovery platform can determine the faulty software version as the software version of the infotainment system provided by the user through the above information, and the fault characteristic information is that the Bluetooth connection of the infotainment system is damaged.

[0031] The preset fault recovery strategy can be a fault recovery strategy determined by the R&D personnel based on the software fault information, and the determined fault recovery strategy is added to the software fault recovery platform. In some embodiments, the software fault recovery platform can save the fault recovery strategy of the solved historical software fault information to obtain the preset fault recovery strategy. In other embodiments, the software fault recovery platform can also predetermine the software fault information that may occur and the corresponding preset fault recovery strategy. If software fault information other than the predetermined software fault information occurs, the R&D personnel can analyze the cause of the software fault information and formulate a corresponding fault recovery strategy; the formulated fault recovery strategy is added to the software fault recovery platform.

[0032] The target fault recovery strategy can be a fault recovery strategy corresponding to the software fault information selected from the preset fault recovery strategies. Of course, if the fault recovery strategy corresponding to the current software fault information does not exist in the preset fault recovery strategies, the R&D personnel can also analyze the cause of the software fault information, and determine the corresponding fault recovery strategy according to the cause, and determine the corresponding fault recovery strategy as the target fault recovery strategy.

[0033] S120: Determine a target vehicle from a preset vehicle database according to the faulty software version in the software fault information, wherein the current software version of the target vehicle is the faulty software version.

[0034] The faulty software version belongs to the basic information of the software, and the development process of the same version of software is basically the same. For example, the faulty software version can be obtained from the software fault information. When the software fault recovery platform receives the fault recovery instruction sent by the vehicle, it is found that the software has a fault, and the fault is caused by a software development problem rather than improper use by the user, which means that all software of the faulty software version have the problem.

[0035] The preset vehicle database may be a pre-established database including vehicle information. The vehicle information includes the software version of each software used by each vehicle. Exemplarily, the software fault recovery platform may uniformly receive the vehicle information of each vehicle and store the vehicle information of each vehicle in the preset vehicle database. At the same time, the software fault recovery platform may also update the preset vehicle database in real time.

[0036] The current software version of the target vehicle is the faulty software version. The current software version refers to the software version currently used by the target vehicle. After the faulty software version is determined, the preset vehicle database is traversed to determine the vehicle using the faulty software version and determine it as the target vehicle.

[0037] S130: Sending the target fault recovery strategy to the target vehicle, so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy.

[0038] The software fault recovery platform can be a cloud platform that can communicate with each vehicle. After determining the target fault recovery strategy, the software fault recovery platform uniformly sends the target fault recovery strategy to the target vehicle so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy.

[0039] It can be seen that the software fault recovery method of the embodiment of the present application responds to the software fault information of the vehicle, determines the target fault recovery strategy from the preset fault recovery strategy according to the software fault information; determines the target vehicle from the preset vehicle database according to the faulty software version in the software fault information, and the current software version of the target vehicle is the faulty software version; sends the target fault recovery strategy to the target vehicle, so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy. Therefore, the software fault recovery platform can promptly and uniformly send the target fault recovery strategy to the target vehicle using the faulty software version when a software fault is discovered, and perform preventive repair processing of the software fault for the target vehicle without waiting for the release of the upgraded software version.

[0040] Based on the above embodiments, the embodiments of the present application adopt Figure 2 The flowchart details how to determine the target fault recovery strategy to be issued. Figure 2 , Figure 2 yes Figure 1 The flowchart of an exemplary embodiment of step S110 in the software fault recovery method is shown. Specifically, the process of step S110 determining the target fault recovery strategy from the preset fault recovery strategy according to the software fault information may include the following steps:

[0041] S210: Count the total number of vehicles that have obtained the same software fault information.

[0042] The total number of vehicles may be the number of times the software fault information of each vehicle has been obtained by the software fault recovery platform. For example, the software fault recovery platform may establish a vehicle quantity table for each software fault information, and after receiving the software fault information sent by the vehicle, update the vehicle quantity table for the corresponding software fault information.

[0043] S220: In response to the total number of vehicles being greater than a preset threshold, determining a target fault recovery strategy from preset fault recovery strategies according to the software fault information.

[0044] If the total number of vehicles with a certain software fault information is greater than the preset threshold, that is, the number of times the vehicle sends the software fault information to the software fault recovery platform is greater than the preset threshold, the target fault recovery strategy is determined from the preset fault recovery strategy based on the software fault information. It should be noted that if the total number of vehicles with software fault information of the current vehicle does not exceed the preset threshold, a temporary fault recovery strategy is generated based on the software fault information to solve the software fault of the current vehicle. Among them, the target fault recovery strategy and the temporary fault recovery strategy may be different. The target fault recovery strategy is for all target vehicles using the faulty software version, while the temporary fault recovery strategy is only for vehicles with current software faults; the target fault recovery strategy may include prevention strategies and perception strategies. The prevention strategy refers to the prevention of software faults that have not yet occurred, the perception strategy refers to the monitoring of the working status of the software, and the temporary fault recovery strategy is mainly for repairing software faults that have occurred.

[0045] Only when the total number of vehicles with the same software fault information exceeds the preset number of times, the target fault recovery strategy will be determined from the preset fault recovery strategy and sent to the target vehicle, reducing the consumption of excessive resources due to occasional faults or faults caused by improper user use. However, it should be noted that if the fault severity of the software fault information is greater than the preset severity, the target fault recovery strategy needs to be sent to vehicles of the relevant version when the total number of vehicles is less than or equal to the preset number of times, or even if it only occurs once, to prevent it from happening again.

[0046] In other embodiments, the software fault recovery platform may also obtain the fault type of the software fault information; in response to the fault type belonging to a software development fault, a target fault recovery strategy is determined from preset fault recovery strategies according to the software fault information.

[0047] Among them, the fault types include software development faults and user improper use faults. Software development faults refer to software faults caused by problems with the software itself, and user improper use faults refer to software faults caused by unreasonable use of the software by users without problems with the software itself. Only when the fault type belongs to software development faults, the software fault recovery platform will determine the target fault recovery strategy from the preset fault recovery strategy, and send the target fault recovery strategy to the target vehicle using the faulty software version to solve the potential software faults in the target vehicle. When the fault type belongs to improper user use faults, the software fault recovery platform can provide a temporary fault recovery strategy to solve the software faults of the current vehicle. Therefore, when a software development fault is discovered, all target vehicles are uniformly resolved through the target fault recovery strategy, which can not only solve the software problems in the target vehicles in a timely manner, but also reduce the user's perception of software problems and improve the user experience.

[0048] In other embodiments, the conditions for determining a target fault recovery strategy from preset fault recovery strategies can also be determined in combination with the above-mentioned method, and the software fault recovery platform counts the total number of vehicles that have the same software fault information occurring in each vehicle; if the total number of vehicles is greater than a preset threshold, the fault type of the software fault information is obtained; if the fault type belongs to a software development fault, the target fault recovery strategy is determined from the preset fault recovery strategies based on the software fault information; the target fault recovery strategy is sent to the target vehicle using the faulty software version to resolve the software problem in the target vehicle.

[0049] Based on the above embodiments, the present application also provides a software fault recovery method, which is applied to a vehicle. For details, please refer to Figure 3 , specifically, the following steps are included:

[0050] S310: Receive a target fault recovery strategy sent by the software fault recovery platform.

[0051] The target fault recovery strategy is that the software fault recovery platform responds to the software fault information of the vehicle, determines the target fault recovery strategy from the preset fault recovery strategy according to the software fault information; determines the target vehicle from the preset vehicle database according to the faulty software version in the software fault information, and the current software version of the target vehicle is the faulty software version; and sends the target fault recovery strategy to the target vehicle.

[0052] After the software fault recovery platform sends the target fault recovery strategy to the vehicle, a corresponding receiving pop-up window may pop up on the vehicle side, and the user may choose whether to receive the target fault recovery strategy.

[0053] For example, the structure of the software fault recovery system can be found in Figure 4,The software fault recovery system includes a software fault recovery platform and a vehicle. The software fault recovery platform sends a target fault recovery strategy to the vehicle. The vehicle includes a fault recovery module, a perception module, a fault recovery operation execution module and a business function module. The fault recovery module is used to receive the target fault recovery strategy sent by the software fault recovery platform. The fault recovery module connects to the perception module and the fault recovery operation execution module to obtain relevant fault feature information when the fault occurs, and judges whether the fault occurs according to the strategy, and executes relevant fault recovery operations; the perception module is used to obtain software information, such as diagnostic system, log system and health management, etc. Through the pre-embedded perception information acquisition interface, the fault recovery module can subscribe to the perception information dynamically on demand according to the strategy, such as subscribing to specific faults of the diagnostic system, detecting characteristic log fields from log data, and subscribing to the health status of the business function module; the fault recovery operation execution module is used to execute relevant fault recovery operations, which may include startup management submodules, configuration submodules and remote call interfaces, etc. For example, the business function module can be started and stopped by the startup management submodule, the business module can be restarted, the relevant configuration of the submodule in the business function module can be modified by the configuration submodule, and the submodule in the business function module can be reset and switched through the remote call interface. Interface calls such as state switching and other fault recovery operations are implemented; the business function module is a functional module in the software, and a software failure is actually a failure of a functional module in the software.

[0054] In order to improve the comprehensiveness of software fault recovery, a perception information acquisition interface and a fault recovery operation execution interface can also be set in the software development stage. The perception information acquisition interface is used to obtain the perception information of the software, and the fault recovery operation execution interface is used to execute the software fault recovery operation. Compared with the current situation where only routine problems can be diagnosed and recovered, unexpected problems can only be solved or prevented by restarting, and the user side can clearly perceive the software fault, which affects the user experience and security. The embodiment of the present application is embedded in the software development stage through the interface. When a problem occurs in the software, the fault information can be perceived in time through the perception information acquisition interface, and the corresponding fault recovery operation can be executed through the fault recovery operation execution interface to quickly resolve the fault.

[0055] S320: Perform software fault recovery processing according to the target fault recovery strategy.

[0056] After receiving the target fault recovery strategy, the vehicle performs software fault recovery processing on the corresponding software according to the target fault recovery strategy. Specifically, the vehicle obtains the strategy type of the target fault recovery strategy; determines the fault recovery rule of the software according to the strategy type, and performs software fault recovery processing on the software according to the fault recovery rule.

[0057] Among them, the strategy types include prevention type, repair type and prompt type. The prevention type can be to modify certain configurations to prevent faults from occurring; the repair type can be to perform recovery operations to solve the faults that have occurred; the prompt type can be to remind the user of the fault to achieve the purpose of warning. When the vehicle receives the target fault recovery strategy of different strategy types, it will perform software fault recovery processing according to different fault recovery rules.

[0058] As an example, in response to the policy type of the target fault recovery policy including the prevention type, the fault prevention operation of the software is obtained; the fault prevention operation is performed on the software. The target fault recovery policy may include one or more sub-policies. After the vehicle receives the target fault recovery policy, the target fault recovery policy is analyzed and processed to obtain the policy type of each sub-policy in the target fault recovery policy; if each sub-policy in the target fault recovery policy includes a prevention type sub-policy, the prevention type is to prevent software failure, so the fault prevention operation can be directly performed. For example, the software configuration can be directly modified to prevent the software from failing.

[0059] As another example, in response to the policy type of the target fault recovery policy including a repair type, perception information of the software is obtained; in response to the perception information of the software characterizing that the software has a fault in the target fault recovery policy, a corresponding fault repair operation is determined from the target fault recovery policy; and the corresponding fault repair operation is performed on the software.

[0060] Specifically, if the sub-policy of the target fault recovery strategy includes a sub-policy of the repair type, then the relevant perception information acquisition interface is opened according to the sub-policy to obtain the perception information of the software, for example, it can be the operation log of a business function module in the subscription software; if the perception information of the software indicates that the software has a fault of the corresponding sub-policy in the target fault recovery strategy, then the fault repair operation corresponding to the fault is determined from the corresponding sub-policy and the corresponding fault repair operation is performed. For example, the characteristic field in the operation log can be detected in real time; the characteristic field is matched with the fault characteristic field in the sub-policy to obtain a matching result; if the matching result indicates that the match is successful, it means that the corresponding business function module in the software has a fault in the sub-policy; the business function module is repaired according to the corresponding fault repair operation in the sub-policy to obtain the business function module after the fault is repaired. Therefore, after the fault in the software is perceived, the fault repair can be quickly performed through the target fault recovery strategy, and the recovery request can be quickly responded to. The user side does not feel the fault strongly, which can improve the user experience.

[0061] In order to elaborate on the software fault recovery method of the present application, Figure 5 The flowchart shown further illustrates it, and the details are as follows:

[0062] First, in the software development stage, the software fault recovery platform will pre-embed interfaces in the vehicle, such as the fault recovery module in the vehicle, including the perception information acquisition interface and the fault recovery operation execution interface (general emergency plan execution interface), etc. The specific module type and parameters are specified when the interface is executed according to the policy; then the software is released to the market for operation. If the software fault recovery platform receives the fault recovery instruction sent by the vehicle, the R&D personnel obtain the software fault information from the vehicle through the software fault recovery platform and formulate the corresponding target fault recovery strategy. The target fault recovery strategy includes prevention-type sub-strategies, repair-type sub-strategies and prompt-type sub-strategies. Each sub-strategy needs to include the type of operation to be performed, such as start and stop, configuration modification, remote interface call, etc., the business function module corresponding to the fault recovery and the corresponding parameters; the prompt-type sub-strategy and the repair-type sub-strategy should include the perception step information, such as the appearance of a specific field in a certain type of log, the receipt of a specific fault code from the diagnostic system, or a series of information combinations, etc.

[0063] After the software fault recovery platform formulates the target fault recovery strategy, it is uniformly sent to the target vehicle of the faulty software version, and the fault recovery module in the vehicle loads and saves the strategy configuration; if there is a prevention-type sub-strategy in the target fault recovery strategy, the fault recovery module directly executes the relevant fault prevention operations, such as modifying a certain configuration; if there is no prevention-type sub-strategy, it detects whether there is a recovery-type sub-strategy. If so, it opens the relevant perception information acquisition interface, which can be to subscribe to relevant logs and monitor the characteristic fields in the logs in real time, or to subscribe to relevant diagnostic faults, etc. Multiple actions can be performed simultaneously; if a fault is detected in the perception information, and the fault belongs to the fault in the target fault recovery strategy, the target sub-strategy is determined from the target fault recovery strategy, and the corresponding fault repair operation is performed, such as starting a module, modifying a configuration, calling the module interface, or performing multiple operations as needed.

[0064] In summary, the software fault recovery method of the embodiment of the present application can prevent and recover related faults more flexibly and timely after an unforeseen problem occurs in the automotive software through the pre-embedding of the perception and prevention / recovery interface, and with flexible and variable strategies, without having to wait until the next software upgrade. This reduces the probability of software problems occurring in the market, quickly responds to market problems, reduces users' perception of problems, and thus improves customer experience and ensures user safety.

[0065] In order to implement the software fault recovery method of the above embodiment, the present application proposes another electronic device, which is specifically referred to as Figure 6 , Figure 6 It is a structural schematic diagram of an embodiment of an electronic device provided by the present application.

[0066] The electronic device 600 includes a memory 610 and a processor 620 , wherein the memory 610 and the processor 620 are coupled.

[0067] The memory 610 is used to store program data, and the processor 620 is used to execute the program data to implement the software fault recovery method of the above embodiment.

[0068] In this embodiment, the processor 620 may also be referred to as a CPU (Central Processing Unit). The processor 620 is an integrated circuit chip having the ability to process signals. The processor 620 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. A general-purpose processor may be a microprocessor or the processor 620 may also be any conventional processor, etc.

[0069] The present application also provides a computer-readable storage medium, such as Figure 7 As shown, the computer-readable storage medium 700 is used to store program data 710. When the program data 710 is executed by the processor, it is used to implement the software fault recovery method in the method embodiment of the present application.

[0070] The method involved in the embodiment of the software fault recovery method of the present application, when implemented in the form of a software functional unit and sold or used as an independent product, can be stored in a device, such as a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a disk or an optical disk.

[0071] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A software fault recovery method, characterized in that: The software fault recovery method is applied to a software fault recovery platform, and the software fault recovery method includes: In response to obtaining software fault information of the vehicle, determining a target fault recovery strategy from preset fault recovery strategies according to the software fault information; Determine a target vehicle from a preset vehicle database according to the faulty software version in the software fault information, wherein the current software version of the target vehicle is the faulty software version; The target fault recovery strategy is sent to the target vehicle, so that the target vehicle performs software fault recovery processing based on the target fault recovery strategy.

2. The software fault recovery method according to claim 1, characterized in that: The step of determining a target fault recovery strategy from preset fault recovery strategies according to the software fault information comprises: Count the total number of vehicles that have obtained the same software fault information; In response to the total number of vehicles being greater than a preset threshold, the target fault recovery strategy is determined from preset fault recovery strategies according to the software fault information.

3. The software fault recovery method according to claim 1, characterized in that: The step of determining a target fault recovery strategy from preset fault recovery strategies according to software fault information includes: Obtaining the fault type of the software fault information; In response to the fault type belonging to a software development fault, the target fault recovery strategy is determined from preset fault recovery strategies according to the software fault information.

4. A software fault recovery method, characterized in that: The software fault recovery method is applied to a vehicle, and the software fault recovery method comprises: Receive a target fault recovery strategy sent by a software fault recovery platform, wherein the target fault recovery strategy is determined by the software fault recovery platform in response to software fault information of the vehicle obtained, from preset fault recovery strategies according to the software fault information; determine a target vehicle from a preset vehicle database according to the fault software version in the software fault information, the current software version of the target vehicle being the fault software version; and send the target fault recovery strategy to the target vehicle; Software fault recovery processing is performed according to the target fault recovery strategy.

5. The software fault recovery method according to claim 4, characterized in that: Before the step of receiving the target fault recovery strategy sent by the software fault recovery platform, the method further includes: A perception information acquisition interface and a fault recovery operation execution interface are set, wherein the perception information acquisition interface is used to acquire the perception information of the software, and the fault recovery operation execution interface is used to execute the fault recovery operation of the software.

6. The software fault recovery method according to claim 4, characterized in that: The step of performing software fault recovery processing according to the target fault recovery strategy includes: Obtaining the policy type of the target fault recovery policy; A fault recovery rule of the software is determined according to the policy type, and software fault recovery processing is performed on the software according to the fault recovery rule.

7. The software fault recovery method according to claim 6, characterized in that: The strategy type includes a prevention type, and the step of determining a fault recovery rule of the software according to the strategy type and performing software fault recovery processing on the software according to the fault recovery rule includes: In response to the policy type of the target fault recovery policy including a prevention type, acquiring a fault prevention operation of the software; The fault prevention operation is performed on the software.

8. The software fault recovery method according to claim 6, characterized in that: The strategy type includes a repair type, and the step of determining a fault recovery rule of the software according to the strategy type and performing software fault recovery processing on the software according to the fault recovery rule includes: In response to the policy type of the target fault recovery policy including a repair type, acquiring perception information of the software; In response to the perception information of the software indicating that the software has a fault in the target fault recovery strategy, determining a corresponding fault repair operation from the target fault recovery strategy; A corresponding fault repair operation is performed on the software.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to execute the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: include: Program data is stored, and when the program data is executed by a processor, it is used to implement the method according to any one of claims 1 to 8.

Images