Vehicle-mounted system restarting method and device, vehicle-mounted system and storage medium

Abstract

The invention discloses a vehicle-mounted system restarting method and device, a vehicle-mounted system and a storage medium, and relates to the field of whole vehicle intelligence, the method is applied to a functional layer in the vehicle-mounted system of a vehicle, the vehicle-mounted system further comprises an interaction layer, a first software system and a second software system, and the method comprises the steps that under the condition that the interaction layer is coupled with the first software system, the interaction layer is connected with the first software system; if it is detected that the first software system operates abnormally, the interaction layer is coupled with the second software system; running the second software system to obtain a running result; and if the operation result of the second software system is that the second software system operates normally, decoupling the interaction layer from the first software system and restarting the first software system. According to the method, the interaction layer is decoupled and separated from the first software system and the second software system, partition restarting of the first software system and the second software system is achieved, a user side can achieve non-inductive system switching feeling, and experience deviation and function safety risks perceived by a user in the fault system switching and restarting process are reduced.

Description

Technical Field

[0001] The present application relates to the field of vehicle intelligent technology, and more specifically, to a vehicle system restart method, device, vehicle system and storage medium. Background Art

[0002] With the development of intelligent car connection technology, the functions that cars can achieve are becoming more and more complex, and more and more software is integrated into the vehicle system. For some electronic control units (ECU) in the vehicle system that integrate more complex software, software conflicts, process conflicts, process interruptions and other failure scenarios may occur during their operation, resulting in ECU function abnormalities and freezes, causing the vehicle system to have black screens, function freezes, screen flashes and other abnormalities, which brings great inconvenience to users.

[0003] Therefore, how to solve the problem of vehicle system failure during driving is an urgent problem to be solved. Summary of the invention

[0004] The present application proposes a vehicle system restart method, device, vehicle system and storage medium to improve the above-mentioned defects.

[0005] In a first aspect, an embodiment of the present application provides a method for restarting an in-vehicle system, which is applied to a functional layer in an in-vehicle system of a vehicle, wherein the in-vehicle system also includes an interaction layer, a first software system, and a second software system. The method includes: when the interaction layer is coupled with the first software system, if it is detected that the first software system is running abnormally, coupling the interaction layer with the second software system; running the second software system to obtain the running result of the second software system; if the running result of the second software system is that the second software system is running normally, decoupling the interaction layer from the first software system; and restarting the first software system.

[0006] In a second aspect, an embodiment of the present application further provides a vehicle-mounted system restart device, which is applied to a functional layer in a vehicle-mounted system, wherein the vehicle-mounted system also includes an interaction layer, a first software system, and a second software system, and the device includes: a coupling module, which is used to couple the interaction layer with the second software system if an abnormal operation of the first software system is detected when the interaction layer is coupled to the first software system; a monitoring module, which is used to run the second software system and obtain the operation result of the second software system; a decoupling module, which is used to decouple the interaction layer from the first software system if the operation result of the second software system is that the second software system is running normally; and a restart module, which is used to restart the first software system.

[0007] In the third aspect, an embodiment of the present application also provides a vehicle-mounted system, including a functional layer, an interaction layer, a first software system and a second software system, wherein the interaction layer is coupled to at least one of the first software system and the second software system, and the functional layer is independent of the interaction layer, the first software system and the second software system: wherein the functional layer is used to execute the method as described above.

[0008] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a program code executable by a processor, and when the program code is executed by the processor, the processor executes the above-mentioned method.

[0009] Therefore, the present application provides a vehicle system restart method, device, vehicle system and storage medium, the method is applied to the functional layer of the vehicle system, the vehicle system also includes an interaction layer, a first software system and a second software system, specifically, the method includes: when the interaction layer is coupled with the first software system, if it is detected that the first software system is running abnormally, the interaction layer is coupled with the second software system; the second software system is run to obtain the running result of the second software system; if the running result of the second software system is that the second software system is running normally, the interaction layer is decoupled from the first software system; and the first software system is restarted. In the embodiment of the present application, the interaction layer is decoupled from the first software system and the second software system. When the first software system fails, the interaction layer can be connected to the first software system and the second software system at the same time, and the coupling with the first software system is disconnected until it is confirmed that the second software system is running normally to achieve switching between the two systems, and the first software system is restarted to repair the fault. In the whole process, the user side can achieve a sense of system switching without feeling, reducing the user's perceived experience deviation and functional safety risk during the switching and restarting of the faulty system.

[0010] Other features and advantages of the embodiments of the present application will be described in the subsequent description, and partly become apparent from the description, or can be understood by practicing the embodiments of the present application. The purposes and other advantages of the embodiments of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0012] Figure 1 A schematic diagram of a vehicle hardware environment suitable for an embodiment of the present application is shown.

[0013] Figure 2 A flow chart of a vehicle system restart method proposed in an embodiment of the present application is shown.

[0014] Figure 3 A flow chart of another vehicle system restart method proposed in an embodiment of the present application is shown.

[0015] Figure 4 A flow chart of another vehicle system restarting method proposed in an embodiment of the present application is shown.

[0016] Figure 5 A structural block diagram of a vehicle-mounted system restarting device proposed in an embodiment of the present application is shown.

[0017] Figure 6 A structural block diagram of a vehicle-mounted system proposed in an embodiment of the present application is shown.

[0018] Figure 7 A structural block diagram of a computer-readable storage medium provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0019] In order to make those skilled in the art better understand the present application scheme, the technical scheme in the present application embodiment will be clearly and completely described below in conjunction with the drawings in the present application embodiment. Obviously, the described embodiment is only a part of the present application embodiment, rather than all the embodiments. The components of the present application embodiment usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the present application for protection, but merely represents the selected embodiment of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0020] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0021] At present, when a vehicle system fails, professional maintenance personnel can use professional diagnostic equipment to detect and repair it, or forcibly disconnect the battery to reset the vehicle, but this cannot solve the problem of users encountering failures during driving. There is also a common solution of pre-embedded factory reset and other restart functions in the vehicle system, but this method cannot repair most software failures like restarting the system, and still cannot completely solve the problem of system failure.

[0022] See also Figure 1 , Figure 1 A schematic diagram of a vehicle hardware environment applicable to an embodiment of the present application is shown, where the vehicle 100 includes an in-vehicle system 111. As an implementation method, the in-vehicle system 111 generally includes a hardware system and a software system, wherein the hardware system provides a data basis and execution capability for the software system, and the software system controls and optimizes the hardware system through algorithms and rules, and the intelligence and automation of the vehicle are realized through the mutual cooperation between the software system and the hardware system, which greatly improves the convenience, safety and comfort of driving.

[0023] Specifically, the vehicle-mounted system 111 may include a processor and a memory. Among them, the processor may be a microcontroller unit (MCU), and the microcontroller unit has a built-in memory, in which a program that can execute the content of the following embodiments is stored, and the processor can execute the program stored in the memory. Further, the processor is connected to the cloud, and data can be exchanged between the processor and the cloud, so that the acquired relevant data is uploaded to the cloud for further processing, and the processor can also receive information from the cloud to perform relevant operations. Among them, the processor may include one or more processing cores. The processor uses various interfaces and lines to connect various parts of the entire vehicle 100, and executes various functions and processes data of the vehicle 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory, and calling data stored in the memory. Optionally, the processor can be implemented in at least one hardware form of a network processor (Neural network Processing Unit, NPU), a digital signal processing (Digital Signal Processing, DSP), a field programmable gate array (Field-Programmable Gate Array, FPGA), and a programmable logic array (Programmable Logic Array, PLA). The processor can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a neural network processing unit (NPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; the NPU is responsible for processing multimedia data such as video and images; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor, but may be implemented separately through a communication chip.

[0024] Furthermore, the memory may include a random access memory (RAM), and may also include a read-only memory (RAM) and a double data rate synchronous dynamic random access memory (DDR). The memory may be used to store instructions, programs, codes, code sets or instruction sets. The memory may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a monitoring function, a restart function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data created by the vehicle 100 during use, etc.

[0025] See also Figure 2 , Figure 2 A flowchart of a vehicle system restart method proposed in an embodiment of the present application is shown. The method can be applied to Figure 1 In the functional layer of the vehicle-mounted system of the vehicle shown, the vehicle-mounted system also includes an interaction layer, a first software system and a second software system. Specifically, the method includes the following steps:

[0026] S110: When the interaction layer is coupled with the first software system, if it is detected that the first software system runs abnormally, coupling the interaction layer with the second software system.

[0027] As an implementation method, the interaction layer is used to manage the In-Vehicle Infotainment (IVI) interface, and is used to implement functions such as information display, entertainment, navigation and vehicle control, so as to realize information exchange and operation control between the user and the vehicle; the first software system and the second software system are used to receive signals sent by the user based on the interaction layer, to perform data management, file processing and other operations based on the signals, and to output the results to realize different functions. Furthermore, the first software system and the second software system can be exactly the same software system. As an implementation method, when designing the in-vehicle system, the functional experience that the user can perceive is placed in the interaction layer and designed as a separate interaction module. That is to say, the interaction layer has an independent thread, and is a thread that runs separately from the first software system or the second software system. Therefore, the interaction layer and the first software system or the second software system can be decoupled and separated. The interaction layer can be coupled to the first software system to implement the corresponding functions of the software based on the first software system, and can also be coupled to the second software system to implement the corresponding functions of the software based on the second software system. In this embodiment, when the vehicle is in the factory state, the interaction layer is coupled to the first software system to run the corresponding functions based on the first software system. The second software system serves as a backup system and is stored separately from the first software system in the in-vehicle system.

[0028] As an implementation method, the function layer can detect the operation status of the first software system. Exemplarily, the first software system includes a first system operation layer, a first communication layer and a first signal link layer. The first system operation layer is used to run software and execute functions, the first communication layer is used to receive user signals, and the first signal link layer is used to transmit signals. Further, the function layer can obtain the operation result of the first system operation layer through a variety of module programs such as a health management module and a watchdog program, and obtain the operation result of the first communication layer by relying on the state of the bus signal transceiver and through the communication module, and obtain the operation result of the first signal link layer through the signal processing module. Furthermore, if the operation result of the first system operation layer, the operation result of the first communication layer and the operation result of the first signal link layer are all normal, it is determined that the operation result of the first software system is normal; if any one of the operation result of the first system operation layer, the operation result of the first communication layer and the operation result of the first signal link layer is abnormal, it is determined that the operation result of the first software system is abnormal. Exemplarily, the functional layer may include a monitoring function module for monitoring the functional operation status of the software system. It has a health management function and can promptly detect abnormal conditions in the functional operation of the first software system by monitoring some key parameters and processes of the first software system.

[0029] In this embodiment, when the user uses the vehicle normally, the interaction layer is coupled with the first software system. If the operation of the first software system is monitored to be abnormal, the interaction layer is coupled with the second software system. Exemplarily, the functional layer may include a system switching function module. When the monitoring function module detects that the operation of the first software system is abnormal, a trigger instruction can be sent to the system switching function module, and the redundant information of the processor and memory in the vehicle system is used to provide the system switching function module with capabilities, so that the information interface between the interaction layer and the first software system and the second software system is divided into two channels in the system switching function module, so that the interaction layer can be coupled to the first software system and the second software system at the same time. In other words, when the interaction layer is running, the first software system and the second software system are also running at the same time, and both can provide corresponding processing results according to the signals sent back by the interaction layer.

[0030] S120: Run the second software system and obtain the running result of the second software system.

[0031] In this embodiment, after coupling the interaction layer and the second software system, according to the relevant description of step S110, the signal or instruction input by the user through the interaction layer can be processed by the first software system and the second software system at the same time and the result is output. Therefore, as an implementation method, during the operation of the second software system, the functional layer can detect the operation status of the second software system. Exemplarily, the second software system includes a second system operation layer, a second communication layer, and a second signal link layer. The second system operation layer is used to run software and execute functions, the second communication layer is used to receive user signals, and the second signal link layer is used to transmit signals. Furthermore, the functional layer can obtain the operation results of the second system operation layer through various module programs such as the health management module and the watchdog program, rely on the state of the bus signal transceiver and obtain the operation results of the second communication layer through the communication module, and obtain the operation results of the second signal link layer through the signal processing module. Furthermore, if the operation result of the second system operation layer, the operation result of the second communication layer, and the operation result of the second signal link layer are all normal, the operation result of the second software system is determined to be normal operation of the second software system; if any one of the operation result of the second system operation layer, the operation result of the second communication layer, and the operation result of the second signal link layer is abnormal operation, the operation result of the second software system is determined to be abnormal operation of the second software system. Furthermore, the operation status of the second software system can also be monitored and detected according to the monitoring function module in the function layer.

[0032] S130: If the operation result of the second software system is that the second software system operates normally, decoupling the interaction layer from the first software system.

[0033] As an implementation method, the monitoring function module of the functional layer can always monitor the operation of the second software system. For example, the operation of the second software system can be obtained once at a preset time interval, and the operation result can be signal arbitrated, and the result can be provided to the interaction layer. In this embodiment, if the functional layer detects that the operation result of the second software system is that the second software system is running normally, it means that the second software system can replace the first software system to support the operation of related functions of the vehicle-mounted system. Therefore, when the interaction layer is coupled to the first software system and the second software system at the same time, the interaction layer is decoupled from the first software system, that is, the switching between the first software system with functional failure and the second software system with intact functions is realized.

[0034] As an implementation method, after the monitoring function module confirms that the second software system is running normally, it can send a trigger instruction to the system switching function module to enable the system switching function module to disconnect the information interface between the interaction layer and the first software system to achieve decoupling of the interaction layer and the first software system.

[0035] It can be understood that when a fault is found in the first software system coupled to the interaction layer, the second software system is also coupled to the interaction layer. The second software system running in this way can also receive and output signals based on the interaction layer. In this way, when the user has an operation demand, it can always be ensured that at least one software system in the vehicle system remains in operation. The simultaneous docking processing of the two systems ensures the stability of the system switching transition.

[0036] S140: Restart the first software system.

[0037] In this embodiment, after the operation result of the second software system is that the second software system is running normally, the interaction layer is decoupled from the first software system, and the first software system is restarted, that is, all threads of the first software system are reset, and the operating system of the first software system is completely restarted, so as to reset the system and restore default parameters by restarting to solve the faults of the first software system such as software lock, crash, etc. As an implementation method, the function layer may also include a restart function module, which is used to restart the first software system or restart the second software system in some implementation methods.

[0038] As an implementation method, the method for restarting the first software system may be: obtaining the number of restarts of the first software system; if the number of restarts of the first software system is greater than or equal to the rated number of restarts, stopping the restart of the first software system; if the number of restarts of the first software system is less than the rated number of restarts, restarting the first software system. It is understandable that the vehicle-mounted system needs to provide additional computing power and storage space to maintain the coupling of the interaction layer with the first software system and the first software system at the same time. Under the premise of setting the rated number of restarts, if the number of restarts of the abnormally running first software system exceeds the rated number of restarts, the system switching and restarting operations are stopped to save system computing power.

[0039] In the process of switching conventional software systems, users will inevitably experience a sense of lag caused by system switching, and may even be unable to operate the vehicle system during the switching process, which may cause certain safety hazards during driving. In this embodiment, since the user will only interact with the interaction layer during use, and the interaction layer is decoupled from the first software system and the second software system, the interaction layer remains running during the entire system monitoring, system switching, and system restart process, and the interaction layer can at least execute commands based on any one of the first software system and the second software system, so that the user side can achieve a senseless system switching experience, reducing the user's perceived experience deviation and functional safety risks during the fault system switching and restart process.

[0040] Therefore, the embodiment of the present application proposes a method for restarting an in-vehicle system, which is applied to the functional layer of the in-vehicle system of the vehicle, and the in-vehicle system also includes an interaction layer, a first software system, and a second software system. Specifically, the method includes: when the interaction layer is coupled with the first software system, if it is detected that the first software system is running abnormally, coupling the interaction layer with the second software system; running the second software system to obtain the running result of the second software system; if the running result of the second software system is that the second software system is running normally, decoupling the interaction layer from the first software system; restarting the first software system. The embodiment of the present application decouples the interaction layer from the first software system and the second software system. When the first software system fails, the interaction layer can be connected to the first software system and the second software system at the same time, and the coupling with the first software system is disconnected until it is confirmed that the second software system is running normally to achieve switching between the two systems, and restart the first software system to repair the fault. In the whole process, the user side can achieve a senseless system switching experience, which reduces the user's perceived experience deviation and functional safety risks during the switching and restarting of the faulty system.

[0041] See also Figure 3 , Figure 3 A flowchart of another vehicle system restart method proposed in an embodiment of the present application is shown. The method can be applied to Figure 1 On the functional layer of the vehicle-mounted system of the vehicle shown, the vehicle-mounted system further includes an interaction layer, a first software system and a second software system. Specifically, the method includes the following steps:

[0042] S210: When the interaction layer is coupled with the first software system, if it is detected that the first software system runs abnormally, coupling the interaction layer with the second software system.

[0043] S220: Run the second software system and obtain the running result of the second software system.

[0044] S221: If the operation result of the second software system is that the second software system operates normally, decouple the interaction layer from the first software system, and restart the first software system.

[0045] Specifically, the specific implementation of steps S210 - S221 may refer to the specific implementation of steps S110 - S140 in the above embodiment, which will not be described in detail here.

[0046] S222: If the operating result of the second software system is that the second software system operates abnormally, decoupling the interaction layer from the second software system.

[0047] In this embodiment, if an abnormal operation of the second software system is detected when the interaction layer is coupled with both the first software system and the second software system, it means that the second software system is not sufficient to replace the first software system to support the normal operation of the vehicle system. At this time, you can choose to decouple the interaction layer and the second software system first, restart the second software system to restore the normal operation of the second software system, and then execute the original system switching and restarting steps.

[0048] It can be understood that when the interaction layer is coupled to the first software system and the second software system at the same time, the monitoring function module in the functional layer can monitor the processing results of the first software system and the second software system for the same user signal output, and feed back the correct processing result of the processing result of the first software system and the processing result of the second software system to the interaction layer for output. That is to say, when the interaction layer is coupled to the first software system and the second software system at the same time, both software systems are in operation. At this time, the processing result finally output by the vehicle-mounted system for user input can be based on the output of the first software system or the output of the second software system. This can ensure that the vehicle-mounted system outputs the best processing result.

[0049] S230: Restart the second software system.

[0050] In this embodiment, the functional layer can restart the second software system based on the restart function module to repair the abnormality of the second software system. As an implementation method, the method of restarting the second software system can be: obtaining the number of restarts of the second software system; if the number of restarts of the second software system is greater than or equal to the rated number of restarts, stop restarting the second software system; if the number of restarts of the second software system is less than the rated number of restarts, restart the second software system. It can be understood that the vehicle-mounted system maintains the simultaneous coupling of the interaction layer with the first software system and the second software system, and needs to provide additional computing power and storage space. Under the premise of setting the rated number of restarts, if the number of restarts of the abnormally running second software system exceeds the rated number of restarts, the system switching and restarting operations are stopped to save system computing power. Further, the rated number of restarts of the first software system and the rated number of restarts of the second software system can be different. For example, the first software system is the main software system of the vehicle. When designing, the safety and stability design of the first software system can be higher than that of the second software system. Therefore, its rated number of restarts can be greater than the rated number of restarts of the second software system as a backup system.

[0051] S240: Return to execute the step of coupling the interaction layer with the second software system and subsequent steps until the operation result of the second software system is that the second software system operates normally.

[0052] In this embodiment, if an abnormal operation of the second software system is detected, the interaction layer and the second software system are repeatedly decoupled, and the second software system is restarted within a rated restart number, and then recoupled, thereby ensuring the normal operation and stability of the switched backup system.

[0053] See also Figure 4 , Figure 4 A flowchart of another vehicle system restart method proposed in an embodiment of the present application is shown. The method can be applied to Figure 1 On the functional layer of the vehicle-mounted system of the vehicle shown, the vehicle-mounted system further includes an interaction layer, a first software system and a second software system. Specifically, the method includes the following steps:

[0054] S310: When the interaction layer is coupled with the first software system, if it is detected that the first software system runs abnormally, coupling the interaction layer with the second software system.

[0055] S320: Run the second software system and obtain the running result of the second software system.

[0056] S330: If the running result of the second software system is that the second software system runs normally, decouple the interaction layer from the first software system, and restart the first software system.

[0057] Specifically, the specific implementation of steps S310 - S330 may refer to the specific implementation of steps S110 - S140 in the above embodiment, which will not be described in detail here.

[0058] S340: While keeping the interaction layer coupled with the second software system, couple the interaction layer with the first software system after the current restart, run the first software system after the current restart, and obtain the running result of the first software system.

[0059] In this embodiment, after the system has been switched and the first software system has been restarted, the interaction layer is coupled with the first software system after the current restart, the first software system after the current restart is run and the operation result of the first software system is obtained to detect whether the first software system has resumed normal operation through the restart. Specifically, the specific implementation method of obtaining the operation result of the first software system can refer to the above embodiment. Further, if the operation result of the first software system is that the first software system runs normally, it means that the first software system has resumed normal operation, the interaction layer is decoupled from the first software system, and the operation of the first software system is stopped. If the operation result of the first software system is that the first software system runs abnormally, it means that the first software system has not resumed normal operation through the restart. At this time, the above steps can be executed again to restart the first software system, that is, the operation of decoupling the interaction layer from the first software system and restarting the first software system and subsequent operations are executed again until the operation result of the first software system is that the first software system runs normally.

[0060] S341: If the operation result of the first software system is that the first software system operates normally, when it is detected that the vehicle enters an ignition-off state, the interaction layer is decoupled from the second software system, and the interaction layer is coupled to the first software system.

[0061] In this embodiment, the operation result of the first software system is that the first software system runs normally, which means that the first software system has been restored to normal through the restart operation. Therefore, when the vehicle is turned off, the software system can be switched from the second software system back to the first software system, that is, the interaction layer is decoupled from the second software system, and the interaction layer is coupled with the first software system. It can be understood that since the user no longer has any operating requirements for the vehicle-mounted system at this time, it is possible to decouple first and then couple without considering the problem of switching lag.

[0062] As an implementation mode, after the vehicle-mounted system switches from the first software system to the second software system, if the second software system fails during driving, the method shown in any of the above embodiments can still be used to switch the second software system to the first software system. Furthermore, if the normal operation of the first software system is confirmed after the first software system is restarted, when the abnormal second software system is switched back to the first software system, the step of determining whether the first software system can operate normally can be omitted to improve the efficiency of system switching and restarting.

[0063] Therefore, the embodiment of the present application detects whether the restarted system can operate normally after executing the system switching and restarting operations, so as to ensure that after the vehicle is turned off or the currently used system fails again, it can be switched again directly based on normal operation, thereby improving the efficiency of restarting the vehicle system.

[0064] See also Figure 5 , Figure 5 The structure block diagram of a vehicle system restart device 500 proposed in an embodiment of the present application is shown. The device can be applied to Figure 1 On the functional layer of the vehicle-mounted system of the vehicle shown, the vehicle-mounted system 500 also includes an interaction layer, a first software system and a second software system. Specifically, the device includes:

[0065] The coupling module 501 is used to couple the interaction layer with the second software system if it is detected that the first software system runs abnormally when the interaction layer is coupled with the first software system.

[0066] The monitoring module 502 is used to run the second software system and obtain the running result of the second software system.

[0067] The decoupling module 503 is configured to decouple the interaction layer from the first software system if the operation result of the second software system is that the second software system is operating normally.

[0068] The restart module 504 is used to restart the first software system.

[0069] Optionally, the restart module 504 is further configured to restart the second software system.

[0070] Optionally, the decoupling module 503 is also used to decouple the interaction layer from the second software system if the operating result of the second software system is that the second software system operates abnormally, and after the second software system is restarted, return to execute the step of coupling the interaction layer with the second software system and subsequent steps until the operating result of the second software system is that the second software system operates normally.

[0071] Optionally, the restart module 504 is also used to obtain the number of restarts of the second software system; if the number of restarts of the second software system is greater than or equal to the rated number of restarts, stop restarting the second software system; if the number of restarts of the second software system is less than the rated number of restarts, restart the second software system.

[0072] Optionally, the vehicle-mounted system 500 also includes an operation judgment module, which is used to obtain the operation results of the second system operation layer, the operation results of the second communication layer, and the operation results of the second signal link layer; if the operation results of the second system operation layer, the operation results of the second communication layer, and the operation results of the second signal link layer are all normal, it is determined that the operation result of the second software system is that the second software system is running normally; if any one of the operation results of the second system operation layer, the operation results of the second communication layer, and the operation results of the second signal link layer is abnormal, it is determined that the operation result of the second software system is that the second software system is running abnormally.

[0073] Optionally, the operation judgment module is also used to obtain the operation result of the first system operation layer, the operation result of the first communication layer, and the operation result of the first signal link layer; if the operation result of the first system operation layer, the operation result of the first communication layer, and the operation result of the first signal link layer are all normal operation, it is determined that the operation result of the first software system is that the first software system is running normally; if any one of the operation result of the first system operation layer, the operation result of the first communication layer, and the operation result of the first signal link layer is abnormal operation, it is determined that the operation result of the first software system is that the first software system is running abnormally.

[0074] Optionally, the coupling module 501 is further used to couple the interaction layer with the first software system after the current restart while maintaining the coupling between the interaction layer and the second software system, run the first software system after the current restart and obtain the running result of the first software system.

[0075] Optionally, the decoupling module 503 is also used to decouple the interaction layer from the first software system and stop running the first software system if the running result of the first software system is that the first software system runs normally; if the running result of the first software system is that the first software system runs abnormally, decouple the interaction layer from the first software system again, restart the operation of the first software system and subsequent operations until the running result of the first software system is that the first software system runs normally.

[0076] Optionally, the decoupling module 503 is further configured to decouple the interaction layer from the second software system and couple the interaction layer to the first software system when it is detected that the vehicle enters an ignition-off state.

[0077] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0078] In several embodiments provided in the present application, the coupling between modules may be electrical, mechanical or other forms of coupling.

[0079] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

[0080] See also Figure 6 , which shows a structural block diagram of a vehicle-mounted system provided by an embodiment of the present application. Specifically, the vehicle-mounted system 600 includes a functional layer 610, an interactive layer 620, a first software system 630 and a second software system 640, wherein the interactive layer 620 is coupled with at least one of the first software system 630 and the second software system 640, and the functional layer 610 is set independently of the interactive layer 620, the first software system 630 and the second software system 640. Furthermore, the interactive layer is used to manage the vehicle-machine interaction interface, the first software system and the second software system are used to receive signals sent by users based on the interactive layer, so as to perform data management, file processing and other operations based on the signals, and output results to realize different functions, and the functional layer is used to execute the method of any of the above embodiments.

[0081] As an implementation method, the functional layer 610 may include a monitoring function module, a system switching function module and a restart function module, wherein the monitoring function module is used to monitor whether the first software system 630 and the second software system 640 can operate normally, the system switching function module is used to couple or decouple the interaction layer 610 with the first software system 630, and also to couple or decouple the interaction layer 610 with the second software system 640, and the restart function module is used to restart the first software system 630 or restart the second software system 640.

[0082] See also Figure 7 , which shows a structural block diagram of a computer-readable storage medium provided in an embodiment of the present application. The computer-readable medium 700 stores program codes, which can be called by a processor to execute the method described in the above method embodiment.

[0083] The computer readable storage medium 700 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium 700 includes a non-transitory computer-readable storage medium. The computer readable storage medium 700 has storage space for program code 710 that performs any method step in the above method. These program codes can be read from or written to one or more computer program products. The program code 710 can be compressed, for example, in an appropriate form.

[0084] As an implementation mode, the present application also provides a computer program product. The computer program product includes a computer program / instruction, and the computer program / instruction implements the steps of the above method when executed by a processor.

[0085] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A vehicle system restart method, characterized in that: A functional layer applied to an in-vehicle system of a vehicle, wherein the in-vehicle system further comprises an interaction layer, a first software system and a second software system, and the method comprises: In the case where the interaction layer is coupled with the first software system, if it is detected that the first software system runs abnormally, coupling the interaction layer with the second software system; Running the second software system and obtaining the running result of the second software system; If the operation result of the second software system is that the second software system operates normally, decoupling the interaction layer from the first software system; Restart the first software system.

2. The method according to claim 1, characterized in that After obtaining the running result of the second software system, the method further includes: If the operation result of the second software system is that the second software system operates abnormally, decoupling the interaction layer from the second software system; Restarting the second software system; Return to execute the step of coupling the interaction layer with the second software system and subsequent steps until the operation result of the second software system is that the second software system operates normally.

3. The method according to claim 2, characterized in that The restarting of the second software system includes: Obtaining the number of restarts of the second software system; If the number of restarts of the second software system is greater than or equal to the rated number of restarts, stop restarting the second software system; If the restart times of the second software system are less than the rated restart times, restart the second software system.

4. The method according to claim 1, characterized in that: The second software system includes a second system operation layer, a second communication layer, and a second signal link layer, and obtaining the operation result of the second software system includes: Obtaining the operation result of the second system operation layer, the operation result of the second communication layer, and the operation result of the second signal link layer; If the operation result of the second system operation layer, the operation result of the second communication layer and the operation result of the second signal link layer are all running normally, determining that the operation result of the second software system is that the second software system runs normally; If any one of the operation result of the second system operation layer, the operation result of the second communication layer and the operation result of the second signal link layer is an operation abnormality, it is determined that the operation result of the second software system is the second software system operation abnormality.

5. The method according to claim 1, characterized in that After restarting the first software system, the method further includes: While keeping the interaction layer coupled with the second software system, coupling the interaction layer with the first software system after the current restart, running the first software system after the current restart and obtaining the running result of the first software system; If the operation result of the first software system is that the first software system operates normally, decoupling the interaction layer from the first software system, and stopping the operation of the first software system; If the operating result of the first software system is that the first software system operates abnormally, the interaction layer is decoupled from the first software system again, and the operation of the first software system and subsequent operations are restarted until the operating result of the first software system is that the first software system operates normally.

6. The method according to claim 5, characterized in that After obtaining the running result of the first software system, the method further includes: If the operation result of the first software system is that the first software system operates normally, when it is detected that the vehicle enters an ignition-off state, the interaction layer is decoupled from the second software system, and the interaction layer is coupled to the first software system.

7. The method according to claim 5, characterized in that The first software system includes a first system operation layer, a first communication layer, and a first signal link layer, and obtaining the operation result of the first software system includes: Obtaining the operation result of the first system operation layer, the operation result of the first communication layer, and the operation result of the first signal link layer; If the operation result of the first system operation layer, the operation result of the first communication layer, and the operation result of the first signal link layer are all normal, determining that the operation result of the first software system is that the first software system is running normally; If any one of the operation result of the first system operation layer, the operation result of the first communication layer and the operation result of the first signal link layer is an operation abnormality, it is determined that the operation result of the first software system is the first software system operation abnormality.

8. A vehicle system restart device, characterized in that: A functional layer applied to an onboard system of a vehicle, the onboard system further comprising an interaction layer, a first software system and a second software system, the device comprising: a coupling module, configured to couple the interaction layer with the second software system if it is detected that the first software system is operating abnormally when the interaction layer is coupled with the first software system; A monitoring module, used for running the second software system and obtaining the running result of the second software system; a decoupling module, configured to decouple the interaction layer from the first software system if the operation result of the second software system is that the second software system is operating normally; A restart module is used to restart the first software system.

9. A vehicle-mounted system, characterized in that: The system comprises a functional layer, an interactive layer, a first software system and a second software system, wherein the interactive layer is coupled to at least one of the first software system and the second software system, and the functional layer is independent of the interactive layer, the first software system and the second software system: Wherein, the functional layer is used to perform the method as claimed in claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program code executable by a processor, and when the program code is executed by the processor, the processor executes the method according to any one of claims 1 to 7.

Images