Vehicle restarting method and device, vehicle, electronic equipment and readable storage medium

Abstract

The invention relates to a vehicle restarting method and device, a vehicle, electronic equipment and a readable storage medium. The method comprises the steps that software nodes corresponding to target hardware equipment needing to be restarted are closed firstly, the target hardware equipment comprises hardware equipment which fails in cold start, then power reset of the target hardware equipment is controlled, and after the power reset of the target hardware equipment succeeds, the software nodes corresponding to the target hardware equipment are started. According to the scheme provided by the invention, the hardware equipment can be automatically restarted when the cold start process of the hardware equipment cannot be completed, and after the software node of the hardware equipment is closed, the power supply of the hardware equipment is controlled to reset and the software node is started in sequence, so that the success rate of restarting the hardware equipment is improved.

Description

Technical Field

[0001] The present application relates to the technical field of hardware device restart, and in particular to a vehicle restart method, device, vehicle, electronic device, and readable storage medium. Background Art

[0002] After the vehicle is powered on, some hardware may occasionally fail to start, preventing the cold start process from completing. If a cold start fails, the vehicle will not be able to enter normal operation, affecting the use of the vehicle.

[0003] Therefore, how to achieve a quick restart of the vehicle without affecting the normal use of the vehicle has become a technical problem that needs to be solved urgently by those skilled in the art. Summary of the Invention

[0004] In order to solve or partially solve the problems existing in the related art, the present application provides a vehicle restart method, device, vehicle, electronic device and readable storage medium, which can realize the rapid restart of the vehicle and avoid affecting the normal use of the vehicle.

[0005] A first aspect of the present application provides a vehicle restart method, comprising: Shutting down the software node corresponding to the target hardware device; the target hardware device includes the hardware device that failed the cold start; Controlling a power reset of the target hardware device; After the target hardware device is successfully powered on, the software node corresponding to the target hardware is started.

[0006] Furthermore, in the vehicle restart method described above, the target hardware device includes a hardware device that actively requests restart in a running state; The method further comprises: When it is detected that the vehicle where the target hardware device is located is in manual driving mode, the target hardware device is restarted, and the vehicle is prohibited from turning on the automatic driving mode before the target hardware device completes the restart.

[0007] Furthermore, the vehicle restart method described above further includes: During the restart process of the target hardware device, fault recording is suspended.

[0008] Furthermore, in the vehicle restart method described above, the step of controlling the power reset of the target hardware device includes: Sending a power reset instruction; the power reset instruction is used to trigger a power supply device to re-supply power to the target hardware device; the power supply device includes a device that supplies power to the target hardware device; If the reset signal is not obtained within the first time period after sending the power reset instruction, the power reset instruction is repeatedly sent until the reset signal is obtained within the first time period; the reset signal is sent by the target hardware device after the power reset is successful.

[0009] Furthermore, in the vehicle restart method described above, starting the software node corresponding to the target hardware includes: Sending a software startup instruction; the software startup instruction is used to trigger a management program to start the software node; the management program includes a program for managing the working status of the software node; If the startup signal is not obtained within the second time period after the software startup instruction is sent, restart failure information of the target hardware device is generated; the startup signal is sent by the software node after the startup is successful.

[0010] Furthermore, in the vehicle restart method described above, different target hardware devices correspond to different restart fault types and restart channels; The method further includes: determining a target hardware device according to the detected restart fault type; The controlling the power reset of the target hardware device includes: controlling the power reset of the target hardware device according to a restart channel corresponding to the target hardware device.

[0011] A second aspect of the present application provides a vehicle restarting device, comprising: A software shutdown module, configured to shut down a software node corresponding to a target hardware device; the target hardware device includes a hardware device that has failed a cold start; A power reset module, used to control the power reset of the target hardware device; The software startup module is used to start the software node corresponding to the target hardware after the power of the target hardware device is successfully reset.

[0012] A third aspect of the present application provides an electronic device, including: processor; and The memory stores executable codes thereon, and when the executable codes are executed by the processor, the processor is caused to execute the method described above.

[0013] A fourth aspect of the present application provides a vehicle, comprising: Restart unit of hardware device; The restart unit of the hardware device is configured to execute the method described above.

[0014] A fifth aspect of the present application provides a computer-readable storage medium having executable code stored thereon. When the executable code is executed by a processor of an electronic device, the processor is caused to execute the method described above.

[0015] The technical solution provided by this application may have the following beneficial effects: The technical solution of the present application can first shut down the software node corresponding to the target hardware device that needs to be restarted, where the target hardware device includes a hardware device that has failed a cold start, then control the power reset of the target hardware device, and after the power reset of the target hardware device is successful, start the software node corresponding to the target hardware. This configuration automatically restarts the hardware device if the cold start process of the hardware device cannot be completed, and first shuts down the software node of the hardware device, then controls the power reset of the hardware device and starts the software node in sequence, thereby improving the success rate of restarting the hardware device.

[0016] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other objects, features and advantages of the present application will become more apparent by describing in more detail exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0018] Figure 1 1 is a flow chart of a vehicle restart method according to an embodiment of the present application; Figure 2 1 is another flow chart of a vehicle restart method according to an embodiment of the present application; Figure 3 1 is another flow chart of a vehicle restart method according to an embodiment of the present application; Figure 4 is a schematic structural diagram of a vehicle restart device shown in an embodiment of the present application; Figure 5 is a schematic structural diagram of an electronic device shown in an embodiment of the present application; Figure 6 It is a schematic structural diagram of a vehicle shown in an embodiment of the present application. DETAILED DESCRIPTION

[0019] The following describes embodiments of the present application in more detail with reference to the accompanying drawings. Although the accompanying drawings illustrate embodiments of the present application, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. Rather, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0020] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0021] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0022] In related technologies, a vehicle undergoes a cold boot after powering on. A cold boot refers to the process by which the vehicle's hardware devices transition from a powered-off state to normal operation. During a cold boot, some critical hardware devices may occasionally fail to boot, preventing the cold boot from completing and triggering a fault report. If a cold boot fails, the vehicle will be unable to return to normal operation, impacting its usability.

[0023] Currently, manual intervention is commonly used to resolve such issues. However, this approach requires the involvement of drivers or maintenance personnel, preventing fully automated recovery. Furthermore, lacking an intelligent recovery mechanism, it can take a long time to troubleshoot the issue, impacting normal vehicle operation. Therefore, how to quickly restart a hardware cold start failure without disrupting normal vehicle operation has become a pressing technical challenge for those skilled in the art.

[0024] To address the above-mentioned issues, embodiments of the present application provide a vehicle restart method, device, vehicle, electronic device, and readable storage medium, which can quickly restart when a hardware cold start fails, thereby avoiding affecting the normal use of the vehicle.

[0025] The technical solutions of the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0026] An embodiment of the present application provides a vehicle restart method, which can be executed by an electronic device. The electronic device can be any device with data and instruction processing capabilities, for example, it can be various types of user terminals such as a car computer, a laptop computer, a tablet computer, a desktop computer, a mobile device (for example, a mobile phone, a personal digital assistant, a dedicated messaging device), or a combination of any two or more of these electronic devices, or a server.

[0027] See also Figure 1 As shown, the method includes: S101: Shut down the software node corresponding to the target hardware device.

[0028] The target hardware device includes a hardware device that needs to be restarted. In some embodiments, the target hardware device is a hardware device that needs to be restarted due to a cold start failure, such as a domain controller, radar, or other hardware device that has a cold start failure, which is not limited in this embodiment.

[0029] A software node corresponding to a target hardware device is an independent software module that is applied to the target hardware device and can implement the functions of the target hardware device or manage its operation. For example, the software node of a radar device in a vehicle can implement functions such as data acquisition, signal processing, and target recognition.

[0030] It should be noted that the vehicle in this embodiment refers to a motor vehicle, which can be a new energy vehicle or a conventional energy vehicle, and this embodiment does not limit this.

[0031] In the embodiments of the present application, when restarting a target hardware device, the software node corresponding to the target hardware device must first be shut down. A command can be issued to a hypervisor (Agent) to shut down the software node corresponding to the target hardware device. It should be noted that the hypervisor refers to a task management process in the system that is responsible for receiving commands and executing software node management based on the received commands, for example, enabling or disabling the corresponding software node based on the received commands.

[0032] In a specific embodiment, if the radar device of the vehicle fails to start when the vehicle is cold started, the radar device is the target hardware device in this embodiment, and the software node corresponding to the radar device needs to be shut down.

[0033] S102: Control the power reset of the target hardware device.

[0034] Perform a hardware power reset on the target hardware device, that is, power off and then power on the target hardware device to try to restore the target hardware device to normal operation.

[0035] Specifically, a command may be issued to a power supply device, causing the power supply device to perform a power-off and power-on operation on the target hardware device. The power supply device includes a device that supplies power to the target hardware device, for example, the power supply device may be a power box of a vehicle.

[0036] After the target hardware device is successfully reset, that is, the power supply device performs a power-off and power-on operation on the target hardware device so that the target hardware device is successfully powered on and started, the target hardware device can send a reset signal.

[0037] If a reset signal fed back by the target hardware device is received within the first period of time after the command is sent to the power supply device, it indicates that the power supply of the target hardware device is reset successfully.

[0038] In some embodiments, if a reset signal is not received from the target hardware device within a first period of time after a command is issued to the power supply device, a command may be issued to the power supply device again, causing the power supply device to power off and then power on the target hardware device again. If a reset signal is still not received from the target hardware device after the command has been issued to the power supply device a set number of times, it indicates that the power reset of the target hardware device has failed. Attempts to control the target hardware device to reset its power may be discontinued, and a cold start fault work order may be directly reported. Operations and maintenance personnel may then perform vehicle repairs based on the cold start fault work order.

[0039] The above-mentioned first duration can be set according to actual conditions, for example, set to 10 milliseconds, and the number of times can also be set according to actual conditions, for example, set to 10 times, which is not limited in this embodiment.

[0040] In a specific embodiment, the first duration is 10 milliseconds, the number of times is set to 3, and the process of controlling the power reset of the target hardware device includes: After shutting down the software node corresponding to the target hardware device, a command is sent to the power supply device for the first time, causing the power supply device to perform a power-off and power-on operation on the target hardware device. If a reset signal is received from the target hardware device within 10 milliseconds after the command is sent to the power supply device, it indicates that the power reset of the target hardware device is successful.

[0041] If no reset signal is received from the target hardware device within 10 milliseconds after the command is sent to the power supply device, a command is sent to the power supply device for the second time, so that the power supply device performs the power-off and power-on operation on the target hardware device again. If a reset signal is received from the target hardware device within 10 milliseconds after the command is sent to the power supply device, it means that the power reset of the target hardware device is successful.

[0042] If the reset signal from the target hardware device is still not received within 10 milliseconds after the command is sent to the power supply device, a command is sent to the power supply device for the third time, so that the power supply device performs the power-off and power-on operation on the target hardware device again. If the reset signal from the target hardware device is received within 10 milliseconds after the command is sent to the power supply device, it means that the power reset of the target hardware device is successful.

[0043] If no reset signal is received from the target hardware device within 10 milliseconds after the command is sent to the power device, and the number of commands sent to the power device reaches the set number of times 3, it means that the power reset of the target hardware device has failed. You can stop trying to control the target hardware device to reset the power supply and directly report a cold start fault work order. The operation and maintenance personnel can then perform vehicle repairs based on the cold start fault work order.

[0044] S103: After the target hardware device is successfully powered on, the software node corresponding to the target hardware is started.

[0045] After the target hardware device is successfully powered on, the software node corresponding to the target hardware device may be reopened. Specifically, a command may be issued to the aforementioned management program to reopen the software node corresponding to the target hardware device.

[0046] After the software node corresponding to the target hardware device is successfully started, the software node sends a start signal.

[0047] In some embodiments, if a startup signal fed back by the software node is received within the second time period after the command is issued to the hypervisor, it indicates that the software node corresponding to the target hardware device is successfully started and the target hardware device is successfully restarted.

[0048] If no startup signal is received from the software node within the second period after the command is issued to the hypervisor, the command can be issued to the hypervisor again, causing the hypervisor to execute the operation to start the software node corresponding to the target hardware device again. If the startup signal is still not received from the software node after the command is issued to the hypervisor a set number of times, it means that the software node startup has failed. No attempt to control the software node startup can be made, and a cold start fault work order can be directly reported. Operations and maintenance personnel can then perform vehicle repairs based on the cold start fault work order.

[0049] The second duration mentioned above can be set according to actual conditions, for example, it can be set to 10 milliseconds, and the number of times can also be set according to actual conditions, for example, it can be set to 10 times, which is not limited in this embodiment.

[0050] In a specific embodiment, the second time duration is 10 milliseconds, the number of times is set to 3, and after the power of the target hardware device is successfully reset, the process of starting the software node corresponding to the target hardware includes: The first command is sent to the hypervisor, causing the hypervisor to execute the operation of starting the software node corresponding to the target hardware device. If a start signal is received from the software node within 10 milliseconds after the command is sent to the hypervisor, it means that the software node is successfully started and the target hardware device is successfully restarted.

[0051] If no startup signal is received from the software node within 10 milliseconds after the command is sent to the hypervisor, a command is sent to the hypervisor for the second time, so that the hypervisor executes the operation of starting the software node corresponding to the target hardware device again. If a startup signal is received from the software node within 10 milliseconds after the command is sent to the hypervisor, it means that the software node is started successfully and the target hardware device is restarted successfully.

[0052] If the startup signal from the software node is still not received within 10 milliseconds after the command is sent to the hypervisor, a command is sent to the hypervisor for the third time, so that the hypervisor executes the operation of starting the software node corresponding to the target hardware device again. If the startup signal from the software node is received within 10 milliseconds after the command is sent to the hypervisor, it means that the software node is started successfully and the target hardware device is restarted successfully.

[0053] If no startup signal is received from the software node within 10 milliseconds after the command is sent to the hypervisor, and the number of commands sent to the hypervisor reaches the set number of times, it means that the software node startup has failed and the target hardware device has failed to restart. You can stop trying to control the software node startup and directly report a cold start fault work order. The operation and maintenance personnel can then perform vehicle repairs based on the cold start fault work order.

[0054] In the above embodiment, the software node corresponding to the target hardware device that needs to be restarted can be first shut down, where the target hardware device includes a hardware device that has failed a cold start, and then the target hardware device is controlled to be powered on and reset. After the target hardware device is powered on and reset successfully, the software node corresponding to the target hardware device is started. This configuration automatically restarts the hardware device when the cold start process of the hardware device cannot be completed, and first shuts down the software node of the hardware device, and then sequentially controls the power reset of the hardware device and starts the software node. This can mimic the normal startup process of the target hardware device and effectively improve the success rate of restarting the target hardware device.

[0055] As an optional implementation, another embodiment of the present application discloses that the target hardware device in the above embodiment also includes a hardware device that actively requests a restart in a running state. The method in the above embodiment may further include the following steps: When it is detected that the vehicle where the target hardware device is located is in manual driving mode, the target hardware device is restarted, and the vehicle is prohibited from turning on the automatic driving mode before the target hardware device completes the restart.

[0056] The target hardware devices in the above embodiments also include hardware devices that actively request a restart while in operation. In some embodiments, when the vehicle is in a non-cold start state, that is, the vehicle system is already running, if the software node corresponding to a hardware device actively requests a hardware restart operation, then the hardware device is determined to be the target hardware device of this embodiment.

[0057] At this time, the vehicle is in running state. To ensure the safety of the vehicle, if it is detected that the vehicle is currently in automatic driving mode, it is necessary to wait until the vehicle switches to manual driving mode before restarting the target hardware device.

[0058] Specifically, when it is detected that the vehicle where the target hardware device is located is in manual driving mode, the target hardware device can be restarted according to the description of the above embodiment, that is, the software node corresponding to the target hardware device is turned off, and the power reset of the target hardware device is controlled. After the power reset of the target hardware device is successful, the software node corresponding to the target hardware is started.

[0059] The vehicle is prohibited from engaging in autonomous driving mode until the target hardware device has completed a reboot to ensure safe driving. Specifically, if the vehicle is in manual driving mode, the hardware reboot flag is set to True, and the vehicle's Function State Machine (FSM) is notified that autonomous driving conditions are not currently met. Once the corresponding software node successfully starts (i.e., the target hardware device has successfully rebooted), the hardware reboot flag is set to False, and the vehicle's FSM is notified that autonomous driving conditions are now met, allowing the vehicle to engage.

[0060] Such a setting can avoid restarting the hardware equipment during the vehicle's automatic driving process, thereby avoiding affecting the reliability of the vehicle's automatic driving and improving driving safety.

[0061] As an optional implementation, another embodiment of the present application discloses that the method of the above embodiment may further include the following steps: During the restart process of the target hardware device, fault logging is suspended.

[0062] Specifically, vehicle fault records can provide real-time basis for whether the vehicle can enter self-driving mode, and repairs and maintenance can also be carried out in the later stage according to the content of the vehicle fault record.

[0063] During the restart process of the target hardware device, the software node corresponding to the target hardware device needs to be turned off, and the software node corresponding to the target hardware device needs to be turned on after the power of the target hardware device is reset. During this process, since the software node corresponding to the target hardware device is turned off and on again, other software nodes that rely on the software node will be triggered to report faults related to the software node, and then the system will think that the software node is unstable, resulting in the vehicle being unable to enter automatic driving, or causing the fault light to light up and unnecessary repairs. However, if the software node has not failed, the restart of the software node will cause the system to think that the software node is unstable, which is an erroneous detection result. Therefore, in order to avoid this erroneous detection result, fault recording can be suspended during the restart process of the target hardware device. If the power reset of the target hardware device fails or the software node fails to start, the fault report can be performed.

[0064] Specifically, before executing the power reset operation of the target hardware device, the fault recording is suspended. For example, the fault management program (Fault Manager, FM) can be notified to suspend the fault recording. After the software node corresponding to the target hardware device is successfully started, that is, the target hardware device is successfully restarted, the FM is notified to restart the fault recording.

[0065] This setting can prevent the vehicle from mistakenly recording the fault of the software node, causing the vehicle to be unable to enter autonomous driving, or causing the fault light to light up and unnecessary repairs.

[0066] As an optional implementation, another embodiment of the present application discloses that the steps of the above embodiment control the power reset of the target hardware device, which may specifically include the following steps: Send a power reset command; if the reset signal is not obtained within the first time period after sending the power reset command, repeat sending the power reset command until the reset signal is obtained within the first time period; the reset signal is sent by the target hardware device after the power reset is successful.

[0067] A power reset instruction may be sent, specifically to a power supply device. As described in the above embodiment, the power supply device includes a device that supplies power to the target hardware device. The power reset instruction is used to trigger the power supply device to re-supply power to the target hardware device, i.e., to trigger the power supply device to power off and then power on the target hardware device.

[0068] As described in the above embodiment, if the target hardware device is successfully powered on and reset, the target hardware device will send a reset signal.

[0069] In this embodiment, after sending the power reset instruction, if a reset signal is obtained from the target hardware device within the first time period, it means that the power reset of the target hardware device is successful; after sending the power reset instruction, if no reset signal is obtained from the target hardware device within the first time period, the above-mentioned power reset instruction can be repeatedly sent at a set frequency until a reset signal is obtained within the first time period.

[0070] The above-mentioned first duration and set frequency can be set according to actual conditions and are not limited in this embodiment.

[0071] The target hardware device power reset failure may be caused by network anomalies or other system anomalies. This setting can solve the above problems by continuously retrying and control the target hardware device to successfully reset.

[0072] As an optional implementation, another embodiment of the present application discloses that the steps of the above embodiment to start the software node corresponding to the target hardware may specifically include the following steps: Send a software startup command; if the startup signal is not obtained within the second time period after sending the software startup command, a restart failure message of the target hardware device is generated; the startup signal is sent by the software node after the startup is successful.

[0073] A software startup instruction may be sent, specifically, a software startup instruction may be sent to a management program. As described in the above embodiment, the management program includes a program for managing the working status of the software node. The software startup instruction is used to trigger the management program to start the software node.

[0074] As described in the above embodiment, if the software node is successfully started, the software node will send a start signal.

[0075] In this embodiment, after sending the software startup instruction, if the startup signal fed back by the software node is obtained within the second time period, it means that the software node corresponding to the target hardware device is successfully started; after sending the software startup instruction, if the startup signal fed back by the software node is not obtained within the second time period, no retry is attempted, but the restart fault information of the target hardware device is directly generated to facilitate subsequent follow-up by the operation and maintenance personnel or vehicle repairs, etc.

[0076] It should be noted that when the hypervisor starts a software node, it will start the software node according to the set startup count. If the software node fails to start once, the hypervisor will try to start the software node again until the set startup count is reached. In other words, after sending a software startup instruction to the hypervisor once, the hypervisor will try to start the software node multiple times until the software node starts successfully or the number of attempts reaches the set startup count. The set startup count can be set according to actual circumstances, for example, to 10 times, and this embodiment is not limited to this.

[0077] The second duration mentioned above can also be set according to actual conditions, and is not limited in this embodiment.

[0078] In the above embodiment, the software node corresponding to the target hardware device can be started after the target hardware device is successfully started, thereby simulating the normal startup process of the target hardware device and effectively improving the restart success rate of the target hardware device.

[0079] As an optional implementation, another embodiment of the present application discloses that different target hardware devices in the above embodiment correspond to different restart fault types and restart channels. The method in the above embodiment also includes the following steps: determining the target hardware device according to the detected restart fault type; The steps of the above embodiment for controlling the power reset of the target hardware device may specifically include the following steps: controlling the power reset of the target hardware device according to the restart channel corresponding to the target hardware device.

[0080] The corresponding relationship between the restart fault type and the hardware device, as well as the restart channel of the hardware device, can be configured. In this embodiment, the restart channel refers to the smallest unit that can be controlled by the power supply device, and each hardware device corresponds to an independent restart channel.

[0081] After detecting the restart fault type, the target hardware device to be restarted can be determined based on the pre-configured mapping relationship. For example, if fault A is pre-configured to correspond to hardware device a, fault B to correspond to hardware device b, and fault C to correspond to hardware device c, then when the current restart fault type is detected as fault A, the target hardware device can be determined to be hardware device a.

[0082] Then, the power supply resets the target hardware device according to the pre-configured restart channel. For example, the power supply uses the α restart channel to power hardware device a, the β restart channel to power hardware device b, and the γ restart channel to power hardware device c. If the current restart fault type is detected as fault A and the target hardware device is hardware device a, the α restart channel can be selected to cause the power supply to reset hardware device a through the α restart channel.

[0083] In the above embodiment, the correspondence between the restart fault type and the hardware device, as well as the restart channel of the hardware device, is configured, so that a quick response can be made when a restart fault is detected, and the target hardware device and restart channel that need to be restarted are determined, thereby reducing the restart waiting time and improving the user experience.

[0084] In a specific embodiment, Figure 2 As shown, if the target hardware device fails to cold start, a command can be sent to the hypervisor to shut down the software node corresponding to the target hardware device.

[0085] Then, a power reset instruction is sent to the power supply device to detect whether a reset signal is received within the first time period. If a reset signal is not received within the first time period, the power reset instruction is repeatedly sent until a reset signal is received within the first time period.

[0086] Then, a software startup instruction is sent to the management program to start the corresponding software node, and the cold start timeout is started. The second cold start flag position is Ture, and it is detected whether the startup signal is received within the second time period. If the startup signal is received within the second time period, it means that the cold start is successful. If the startup signal is not received within the second time period, it means that the cold start has failed, and no restart is performed. A cold start work order is directly reported to generate restart failure information for the target hardware device to facilitate the operation and maintenance personnel to follow up on vehicle repairs, etc.

[0087] In a specific embodiment, Figure 3 As shown, if the target hardware device is a hardware device that actively requests a restart, it is possible to first detect whether the vehicle is in the automatic driving mode. If the vehicle is in the automatic driving mode, the detection is continued until it is detected that the vehicle exits the automatic driving mode and enters the manual driving mode.

[0088] A command can be sent to the hypervisor to shut down the software node corresponding to the target hardware device, set the hardware restart flag to True, notify the vehicle FSM that the autonomous driving conditions are not currently met, notify the FM to suspend fault recording, and set the FM cold start flag to False.

[0089] Then, a power reset instruction is sent to the power supply device to detect whether a reset signal is received within the first time period. If no reset signal is received, the power reset instruction is repeatedly sent until a reset signal is received within the first time period.

[0090] Then, a software startup instruction is sent to the hypervisor to start the corresponding software node. After the corresponding software node is successfully started, that is, the target hardware device is restarted successfully, the hardware restart flag is set to False, and the vehicle's FSM is notified. At this time, the autonomous driving conditions are met, the vehicle is allowed to start autonomous driving, the FM is notified to restart fault recording, and the FM cold start flag is set to True.

[0091] Corresponding to the aforementioned application function implementation method embodiment, the present application also provides a vehicle restart device, an electronic device, a vehicle, a computer-readable storage medium and corresponding embodiments.

[0092] Figure 4 Schematic diagram of the structure of a vehicle restart device shown in an embodiment of the present application.

[0093] See also Figure 4 , the vehicle restart device includes: The software shutdown module 100 is used to shut down the software node corresponding to the target hardware device; the target hardware device includes the hardware device that failed the cold start; A power reset module 110 is used to control the power reset of the target hardware device; The software startup module 120 is used to start the software node corresponding to the target hardware after the power of the target hardware device is successfully reset.

[0094] Furthermore, the target hardware device of the above embodiment includes a hardware device that actively requests restart in the running state. The vehicle restart device of the above embodiment also includes: The driving management module is used to restart the target hardware device when it is detected that the vehicle where the target hardware device is located is in manual driving mode, and prohibit the vehicle from turning on the automatic driving mode before the target hardware device completes the restart.

[0095] Furthermore, the vehicle restarting device of the above embodiment further includes: The record management module is used to suspend fault recording during the restart process of the target hardware device.

[0096] Furthermore, the power reset module 110 of the above embodiment is specifically configured to: Sending a power reset instruction; the power reset instruction is used to trigger the power supply device to re-supply power to the target hardware device; the power supply device includes a device that supplies power to the target hardware device; If the reset signal is not obtained within the first time period after sending the power reset instruction, the power reset instruction is sent repeatedly until the reset signal is obtained within the first time period; the reset signal is sent by the target hardware device after the power reset is successful.

[0097] Furthermore, the software startup module 120 of the above embodiment is specifically used to: Sending a software startup instruction; the software startup instruction is used to trigger the management program to start the software node; the management program includes a program for managing the working status of the software node; If the startup signal is not obtained within the second time period after the software startup instruction is sent, restart failure information of the target hardware device is generated; the startup signal is sent by the software node after the startup is successful.

[0098] Furthermore, different target hardware devices in the above embodiment correspond to different restart fault types and restart channels; the vehicle restart device in the above embodiment also includes: The device determination module is used to determine the target hardware device according to the detected restart fault type.

[0099] The power reset module 110 of the above embodiment is specifically used to: Control the power reset of the target hardware device according to the restart channel corresponding to the target hardware device.

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

[0101] Figure 5 It is a structural diagram of an electronic device shown in an embodiment of the present application.

[0102] See also Figure 5 , the electronic device includes a memory 200 and a processor 210.

[0103] The memory 200 stores executable codes. When the executable codes are processed by the processor 210 , the processor 210 can execute part or all of the above-mentioned methods.

[0104] Specifically, the electronic device may further include: a bus, a communication interface 220 , an input device 230 and an output device 240 .

[0105] The processor 210, the memory 200, the communication interface 220, the input device 230 and the output device 240 are interconnected via a bus. The processor 210 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0106] Memory 200 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage. ROM may store static data or instructions required by processor 210 or other computer modules. Permanent storage may be a readable and writable storage device. Permanent storage may be a non-volatile storage device that retains stored instructions and data even when the computer is powered off. In some embodiments, the permanent storage device utilizes a mass storage device (e.g., a magnetic or optical disk, flash memory). In other embodiments, the permanent storage device may be a removable storage device (e.g., a floppy disk, optical drive). System memory may be a readable and writable storage device or a volatile readable and writable storage device, such as dynamic random access memory (DRAM). System memory may store some or all instructions and data required by the processor during operation. Furthermore, memory 200 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (e.g., DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), as well as magnetic disks and / or optical disks. In some embodiments, the memory 200 may include a readable and / or writable removable storage device, such as a compact disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, mini SD card, Micro-SD card, etc.), a magnetic floppy disk, etc. Computer-readable storage media do not contain carrier waves and transient electronic signals transmitted wirelessly or wired.

[0107] The input device 230 may include a device for receiving data and information input by a user, such as a keyboard, a mouse, a camera, a scanner, a light pen, a voice input device, a touch screen, a pedometer, or a gravity sensor.

[0108] Output device 240 may include devices that allow information to be output to a user, such as a display screen, printer, speakers, etc.

[0109] The communication interface 220 may include any transceiver or similar device for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0110] The processor 210 processes the executable code stored in the memory 200 and calls other devices, so that the processor 210 can execute part or all of the methods described above.

[0111] Figure 6 It is a schematic structural diagram of a vehicle shown in an embodiment of the present application.

[0112] See also Figure 6The vehicle includes a restart unit 300 of a hardware device, and the restart unit 300 of the hardware device is configured to execute part or all of the methods described above.

[0113] The hardware device's restart unit 300 can be located in the vehicle's center console or any other location, such as the vehicle's engine compartment. The hardware device's restart unit 300 can be an electronic device embedded in the vehicle's electronic control unit (ECU), or a processing chip independent of the ECU. Alternatively, the hardware device's restart unit 300 can be one or more ECUs specifically designed to control the hardware device's restart.

[0114] The vehicle provided in this embodiment belongs to the same application concept as the method provided in the above embodiments of this application, can execute the method provided in any of the above embodiments of this application, and has the corresponding functional modules and beneficial effects for executing the above methods. For technical details that are not fully described in this embodiment, please refer to the specific processing content of the method provided in the above embodiments of this application, which will not be repeated here.

[0115] Furthermore, the method according to the present application may also be implemented as a computer program or computer program product, which includes computer program code instructions for executing some or all of the steps of the method described above. Alternatively, the computer program may be stored on a computer-readable storage medium or in the cloud; the computer device's processor reads the computer program from the computer-readable storage medium or the cloud.

[0116] The computer program product may be written in any combination of one or more programming languages ​​to implement the program code of the embodiments of the present application, including object-oriented programming languages ​​such as Java, C++, and conventional procedural programming languages ​​such as C or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0117] The computer program product may be implemented in hardware, software, or a combination thereof. In one embodiment, the computer program product is implemented as a computer storage medium. In another embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0118] Alternatively, the present application can also be implemented as a computer-readable storage medium (or non-transitory machine-readable storage medium or machine-readable storage medium) on which executable code (or computer program or computer instruction code) is stored. When the executable code (or computer program or computer instruction code) is executed by a processor of an electronic device (or server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.

[0119] Computer-readable storage media may take the form of any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may include, for example, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0120] The embodiments of the present application have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or improvements to the technology in the market, or to enable other persons skilled in the art to understand the embodiments disclosed herein.

Claims

1. A vehicle restart method, characterized in that: include: Shutting down the software node corresponding to the target hardware device; the target hardware device includes the hardware device that failed the cold start; Controlling a power reset of the target hardware device; After the target hardware device is successfully powered on, the software node corresponding to the target hardware is started.

2. The vehicle restart method according to claim 1, characterized in that: The target hardware device includes a hardware device that actively requests to restart in a running state; The method further comprises: When it is detected that the vehicle where the target hardware device is located is in manual driving mode, the target hardware device is restarted, and the vehicle is prohibited from turning on the automatic driving mode before the target hardware device completes the restart.

3. The vehicle restart method according to claim 2, characterized in that: Also includes: During the restart process of the target hardware device, fault recording is suspended.

4. The vehicle restart method according to claim 1, characterized in that: The controlling the power reset of the target hardware device includes: Sending a power reset instruction; the power reset instruction is used to trigger a power supply device to re-supply power to the target hardware device; the power supply device includes a device that supplies power to the target hardware device; If the reset signal is not obtained within the first time period after sending the power reset instruction, the power reset instruction is repeatedly sent until the reset signal is obtained within the first time period; the reset signal is sent by the target hardware device after the power reset is successful.

5. The vehicle restart method according to claim 1, characterized in that: The starting of the software node corresponding to the target hardware includes: Sending a software startup instruction; the software startup instruction is used to trigger a management program to start the software node; the management program includes a program for managing the working status of the software node; If the startup signal is not obtained within the second time period after the software startup instruction is sent, restart failure information of the target hardware device is generated; the startup signal is sent by the software node after the startup is successful.

6. The vehicle restart method according to claim 1, characterized in that: Different target hardware devices correspond to different restart failure types and restart channels; The method further includes: determining a target hardware device according to the detected restart fault type; The controlling the power reset of the target hardware device includes: controlling the power reset of the target hardware device according to a restart channel corresponding to the target hardware device.

7. A vehicle restarting device, characterized in that: include: A software shutdown module, configured to shut down a software node corresponding to a target hardware device; the target hardware device includes a hardware device that has failed a cold start; A power reset module, used to control the power reset of the target hardware device; The software startup module is used to start the software node corresponding to the target hardware after the power of the target hardware device is successfully reset.

8. An electronic device, characterized in that: include: processor; as well as A memory having executable codes stored thereon, which, when executed by the processor, causes the processor to execute the method according to any one of claims 1 to 6.

9. A vehicle, characterized in that: include: Restart unit of hardware device; The restart unit of the hardware device is configured to execute the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having executable codes stored thereon, wherein when the executable codes are executed by a processor of an electronic device, the processor is caused to execute the method according to any one of claims 1 to 6.

Images