Reset method, system and product of vehicle-mounted domain controller

Abstract

The embodiment of the invention provides a reset method, system and product of a vehicle-mounted domain controller. The method comprises the following steps: monitoring whether abnormal reset occurs or not; sending a reset flag bit to a control module in the domain controller according to the abnormal reset monitoring result; determining the abnormal reset duration from the start of the abnormal reset to the success of the abnormal reset; comparing the abnormal reset duration with a preset duration to obtain a comparison result; and under the condition that the comparison result is that the abnormal reset duration exceeds the preset duration, the control module is controlled to send a safety instruction to the corresponding execution controller for execution based on the reset flag bit. The invention aims to ensure the safety of the vehicle under the condition that the domain controller is abnormally reset.

Description

Technical Field

[0001] The present application relates to the technical field of automobile controllers, and in particular to a method, system and product for resetting an on-board domain controller. Background Art

[0002] When the vehicle is driving, due to hardware or software problems, the controller itself will trigger a reset, causing the controller to restart from initialization. For the vehicle domain controller, the current reset response strategy only focuses on the response during the reset process. In fact, the vehicle domain controller may also have corresponding security issues after a successful reset. However, there is currently no corresponding response strategy to ensure the safety of the vehicle after the abnormal reset of the vehicle domain controller is successful. Summary of the invention

[0003] In view of this, the embodiments of the present application provide a method, system and product for resetting a vehicle-mounted domain controller, aiming to ensure vehicle safety after the domain controller is abnormally reset successfully through a corresponding reset response strategy.

[0004] A first aspect of an embodiment of the present application provides a method for resetting a vehicle-mounted domain controller, the method comprising:

[0005] Monitor whether abnormal reset occurs;

[0006] According to the abnormal reset monitoring result, a reset flag is sent to the control module in the domain controller;

[0007] Determine the abnormal reset time from the start of abnormal reset to the success of abnormal reset;

[0008] Compare the abnormal reset time with the preset time to obtain a comparison result;

[0009] When the comparison result is that the abnormal reset duration exceeds the preset duration, the control module is controlled to send a safety instruction to a corresponding execution controller for execution based on the reset flag.

[0010] Optionally, the method further includes:

[0011] When the comparison result is that the abnormal reset duration does not exceed the preset duration, the control module is controlled to send a pre-reset instruction to a corresponding execution controller for execution within the first software running cycle based on the reset flag.

[0012] Optionally, before sending the reset flag to the control module in the domain controller according to the abnormal reset monitoring result, the method further includes:

[0013] When the monitoring result is that an abnormal reset occurs, the low voltage power supply to the execution controller hard line is maintained.

[0014] Optionally, the method further includes:

[0015] receiving in real time the key state information sent by the control module, wherein the key state information includes the key state before resetting;

[0016] The received key status information is stored in a non-volatile storage space.

[0017] Optionally, determine the pre-reset instructions, including:

[0018] Obtaining the critical state before the reset stored in the non-volatile storage space;

[0019] Based on the key state before resetting, a pre-resetting instruction corresponding to the key state before resetting is determined.

[0020] Optionally, the method further includes:

[0021] When the comparison result shows that the abnormal reset time duration does not exceed the preset time duration, the execution controller is controlled by the pre-reset instruction to maintain the state corresponding to the pre-reset instruction within the abnormal reset time duration.

[0022] Optionally, the method further includes:

[0023] When the comparison result shows that the abnormal reset duration exceeds the preset duration, the control of each execution controller is terminated at the target time, and the control of each execution controller is restored when the abnormal reset is successful. The target time is the time after the preset time has passed since the abnormal reset.

[0024] Optionally, the method further includes:

[0025] Between the target time and the time when the abnormality is successfully reset, each execution controller performs corresponding actions based on its own fault response strategy.

[0026] Optionally, the control module includes: a vehicle body control module and a vehicle power control module.

[0027] Optionally, key status information sent by the vehicle body control module includes: low voltage power supply status information, wiper operation status information, light status information, and hard line output status information;

[0028] The key status information sent by the vehicle power control module includes: vehicle drivability status information, high-voltage status information, gear status information, electric drive controller operating instructions, and battery controller operating instructions.

[0029] A second aspect of an embodiment of the present application provides a system for resetting a vehicle-mounted domain controller, the system comprising:

[0030] A reset identification module is used to monitor and determine whether an abnormal reset occurs, and send a reset flag to a control module in the domain controller according to the abnormal reset monitoring result;

[0031] A timeout processing module is used to determine the abnormal reset duration from the start of the abnormal reset to the success of the abnormal reset; and to compare the abnormal reset duration with a preset duration to obtain a comparison result; and to control the control module to send a safety instruction to the corresponding execution controller for execution based on the reset flag when the comparison result is that the abnormal reset duration exceeds the preset duration.

[0032] A third aspect of an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is executed by the processor, the steps in a method for resetting a vehicle domain controller as described in the first aspect of the present application are implemented.

[0033] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in the method for resetting a vehicle domain controller as described in the first aspect of the present application are implemented.

[0034] The method for resetting a vehicle domain controller provided by the present application has the following advantages:

[0035] A method for resetting a vehicle-mounted domain controller provided by an embodiment of the present application first monitors whether an abnormal reset occurs; according to the abnormal reset monitoring result, a reset flag is sent to a control module in the domain controller; the abnormal reset duration from the start of the abnormal reset to the success of the abnormal reset is determined; the abnormal reset duration is compared with the preset duration to obtain a comparison result; when the comparison result is that the abnormal reset duration exceeds the preset duration, the control module sends a safety instruction to the corresponding execution controller for execution based on the reset flag. Thus, the present application monitors whether the domain controller itself has an abnormal reset by the corresponding module in the domain controller, and when an abnormal reset is detected, an abnormal flag is sent to the control module inside the domain controller for sending instructions to each execution controller to inform the control module that the current domain controller is in an abnormal reset state and needs to execute the corresponding reset response strategy by itself. At this time, the corresponding module in the domain controller will monitor the time it takes to successfully reset (i.e., the abnormal reset duration). If the duration exceeds the preset duration, it is determined that the vehicle has a safety problem at this time. At this time, the safety instruction will be sent to the control module immediately after the abnormal reset is successful. The control module knows that it needs to execute the corresponding reset response strategy based on the received reset flag. At this time, after it receives the safety instruction, it will send the received safety instruction to the corresponding execution controller for execution to ensure that if it is determined that there is a safety problem with the vehicle, the vehicle will be immediately controlled to switch to a safe state after the abnormal reset is successful. For example, for all execution controllers that involve high-voltage power-on in the working process, a safety instruction to power off high voltage is sent to it. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] Figure 1 A flowchart of a method for resetting a vehicle-mounted domain controller is shown as an embodiment of the present application;

[0038] Figure 2 A connection relationship diagram of controllers in a method for resetting a vehicle-mounted domain controller according to an embodiment of the present application;

[0039] Figure 3 Another flow chart of a method for resetting a vehicle-mounted domain controller according to an embodiment of the present application;

[0040] Figure 4 A schematic diagram of a vehicle-mounted domain controller reset system is shown in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] refer to Figure 1 , Figure 1 The flowchart of a method for resetting a vehicle domain controller is shown in one embodiment of the present application. The method is applied to a vehicle domain controller, such as Figure 1 As shown, the method includes:

[0043] Step S1: monitor whether an abnormal reset occurs.

[0044] In this embodiment, in order to facilitate the understanding of the present application, the control architecture of the domain controller is first explained. The domain controller includes various control modules for controlling the execution controller, and each control module includes but is not limited to: a vehicle power control module and a vehicle body control module. The execution controller controlled by the vehicle power control module includes but is not limited to: a battery controller, an electric drive controller, a DC-to-DC transformer controller, a DC-to-AC transformer controller, etc.; the execution controller controlled by the vehicle body control module includes but is not limited to: a lighting execution controller, a wiper execution controller, a low-voltage power supply control actuator, etc. The domain controller sends instructions to each execution controller through each execution module inside itself to execute control actions. For example, the domain controller controls the vehicle body control module to send a wiper operation instruction to the wiper execution controller, and the wiper execution controller controls the wiper operation based on the received wiper operation instruction. Figure 2 As shown, the body function execution controller in the figure represents all execution controllers controlled by the vehicle body control module in the domain controller, and the power function execution controller in the figure represents all execution controllers controlled by the vehicle power control module in the domain controller.

[0045] In this embodiment, the present application sets a software-level reset identification module in the underlying software in the domain controller. The reset identification module will identify in real time whether a reset has occurred during the operation of the domain controller, and determine whether the reset is due to a normal reset from shutdown to startup, or an abnormal reset caused by software or hardware reasons.

[0046] Step S2: According to the abnormal reset monitoring result, a reset flag is sent to the control module in the domain controller.

[0047] In this embodiment, based on the abnormal reset monitoring result, when it is determined that the reset of the domain controller is an abnormal reset, the reset identification module sends a reset flag to the control module in the domain controller for controlling the execution controller to inform the control module that the current domain controller is in an abnormal reset state and needs to execute the corresponding reset response strategy, that is, the reset flag is used to inform the control module that the current domain controller has an abnormal reset. The reset response strategy at least includes: sending a safety instruction to each execution controller when receiving a safety instruction to control each execution controller to be in a safe state, so that the vehicle is in a safe state.

[0048] Step S3: Determine the abnormal reset time taken from the start of the abnormal reset to the success of the abnormal reset.

[0049] In this embodiment, the present application sets an application-level timeout processing module in the application software in the domain controller. The timeout processing module will be used to monitor whether the abnormal reset is successful, and to record the start time of the abnormal reset and the time when the abnormal reset is successful. If the reset is not successful, the corresponding time when the abnormal reset is successful cannot be recorded.

[0050] In this embodiment, when the timeout processing module detects that the abnormal reset is successful, the time length between the abnormal reset success time and the abnormal reset start time is determined based on the abnormal reset success time and the abnormal reset start time, and the time length is the abnormal reset time length.

[0051] Step S4: Compare the abnormal reset time with the preset time to obtain a comparison result.

[0052] In this embodiment, after obtaining the abnormal reset time length in step S3, the timeout processing module compares the abnormal reset time length with the preset time length to obtain a corresponding comparison result. The preset time length is the maximum time length that the execution controller can wait to receive instructions. If the domain controller still fails to abnormally reset successfully within the preset time length, the execution controller will not be able to receive the instruction issued by the domain controller after waiting for the maximum time length. At this time, it is determined that the vehicle has a safety problem. At this time, even if the domain controller is successfully reset at a certain time exceeding the preset time length, it will be determined that it has a safety problem.

[0053] Step S5: When the comparison result shows that the abnormal reset duration exceeds the preset duration, the control module is controlled to send a safety instruction to a corresponding execution controller for execution based on the reset flag.

[0054] In this embodiment, when the comparison result obtained by step S4 is that the abnormal reset duration exceeds the preset duration, that is, starting from the abnormal reset start time, the domain controller is reset successfully at a certain time after the preset duration, and then the timeout processing module sends a safety instruction to the control module. After receiving the safety instruction, the control module knows that it will send the safety instruction to the corresponding execution controller for execution based on the reset flag bit received before. At this time, the control module sends the received safety instruction to the corresponding execution controller for execution. Due to the differences in the working states of different execution controllers, such as some execution controllers will be in high voltage power-on when working normally, so here there is a corresponding safety instruction for each different execution controller. The control module in this application receives the safety instructions corresponding to each execution controller, and sends it to the corresponding execution controller for execution, so that the execution controller that executes the corresponding safety instruction is in a safe state. For example, for all execution controllers involved in high voltage power-on during the working process, a safety instruction for high voltage power-off is sent to it, due to the work of different execution controllers. Among them, the preset duration can be set according to the actual application scenario, and is not limited here, such as 600ms, 500ms, etc.

[0055] For example, the domain controller starts abnormal reset at time t1, with a preset duration of 500ms, and the domain controller is successfully reset 700ms from time t1. At this time, after the domain controller is successfully reset, it will immediately send each safety instruction through the control module to the execution controller corresponding to each safety instruction for execution, so as to control the vehicle to be in a safe state.

[0056] In this embodiment, for the scenario where the abnormal reset duration exceeds the preset duration, the execution controller has not received the instruction sent by the domain controller after waiting for the maximum duration, so each execution controller at this time will know that there is a problem with the domain controller. At this time, different execution controllers have their own corresponding fault response strategies, so some execution controllers may be restored to a safe state in this scenario, while some execution controllers may continue to maintain the current unsafe working state (such as maintaining its own high-voltage power-on state even though it has not received the instruction sent by the domain controller after waiting for the maximum duration). In order to control the vehicle in a safe state in a more efficient and low-cost manner in this scenario, this application no longer focuses on the fault response strategy of the execution controller itself, and in the case where the abnormal reset duration exceeds the preset duration, after the domain controller is successfully reset, a corresponding safety instruction will be sent to each of all execution controllers. For the execution controller that has switched to a safe state based on its own fault response strategy, it is allowed to maintain a safe state based on the received safety instruction, and for the execution controller that has not switched to a safe state based on its own fault response strategy, it is allowed to switch to a safe state based on the received safety instruction. In this way, the vehicle is controlled to be in a safe state more efficiently and at a lower cost.

[0057] A method for resetting a vehicle-mounted domain controller provided by an embodiment of the present application first monitors whether an abnormal reset occurs; according to the abnormal reset monitoring result, a reset flag is sent to a control module in the domain controller; the abnormal reset duration from the start of the abnormal reset to the success of the abnormal reset is determined; the abnormal reset duration is compared with the preset duration to obtain a comparison result; when the comparison result is that the abnormal reset duration exceeds the preset duration, the control module sends a safety instruction to the corresponding execution controller for execution based on the reset flag. Thus, the present application monitors whether the domain controller itself has an abnormal reset by the corresponding module in the domain controller, and when an abnormal reset is detected, an abnormal flag is sent to the control module inside the domain controller for sending instructions to each execution controller to inform the control module that the current domain controller is in an abnormal reset state and needs to execute the corresponding reset response strategy by itself. At this time, the corresponding module in the domain controller will monitor the time it takes to successfully reset (i.e., the abnormal reset duration). If the duration exceeds the preset duration, it is determined that the vehicle has a safety problem at this time. At this time, the safety instruction will be sent to the control module immediately after the abnormal reset is successful. The control module knows that it needs to execute the corresponding reset response strategy based on the received reset flag. At this time, after it receives the safety instruction, it will send the received safety instruction to the corresponding execution controller for execution to ensure that if it is determined that there is a safety problem with the vehicle, the vehicle will be immediately controlled to switch to a safe state after the abnormal reset is successful. For example, for all execution controllers that involve high-voltage power-on in the working process, a safety instruction to power off high voltage is sent to it.

[0058] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for resetting a vehicle-mounted domain controller. In the method for resetting the vehicle-mounted domain controller, the method further includes step S6:

[0059] Step S6: When the comparison result shows that the abnormal reset duration does not exceed the preset duration, the control module is controlled to send a pre-reset instruction to the corresponding execution controller for execution within the first software running cycle based on the reset flag.

[0060] In this embodiment, in order to avoid power loss in the vehicle after the domain controller successfully completes the abnormal reset within the preset time. The present application sets a memory module in the domain controller by combining software and hardware. The hardware part of the memory module is a non-destructive storage space. The memory module will record the instructions sent to each execution controller before the abnormal reset of the domain controller. When it is determined that the domain controller is reset successfully and the abnormal reset time spent does not exceed the preset time, in the first software operation cycle, the memory module sends the pre-reset instructions of each execution controller to the control module. The control module knows that it will send these pre-reset instructions to the corresponding execution controllers based on the reset flag bit received before, and the corresponding control module will send these pre-reset instructions to the corresponding execution controllers for execution. This method can avoid power loss in the vehicle because the domain controller will immediately send initial instructions to each execution controller after the normal reset of the normal switch is successful. Such a startup initial instruction is the instruction for the vehicle to start up and does not provide power to the vehicle. If the domain controller successfully completes the abnormal reset within the preset time, it will also send initial instructions to each execution controller, which will cause the vehicle to lose power. Therefore, after the application successfully completes the abnormal reset within the preset time, the pre-reset instructions of each execution controller are sent to the control module in the first software operation cycle. In this way, after the domain controller successfully completes the abnormal reset within the preset time, the pre-reset instructions are sent in the first software operation cycle instead of the initial instructions, which can avoid vehicle power loss.

[0061] In combination with the above embodiments, in one implementation, the embodiment of the present application further provides a method for resetting a vehicle-mounted domain controller. In the method for resetting a vehicle-mounted domain controller, before step S2, the method further includes: when the monitoring result is an abnormal reset, maintaining low-voltage power supply to the execution controller hard line.

[0062] In this embodiment, when it is determined that the reset of the domain controller is an abnormal reset, before the reset identification module sends a reset flag to the control module in the domain controller used to control the execution controller, the reset identification module will first maintain low-voltage power supply to the power supply hard line and wake-up hard line of the execution controller based on the high-side locking logic inside the domain controller. This is to prevent the various execution controllers from losing power without any control when the domain controller is reset.

[0063] In combination with the above embodiments, in one implementation, the embodiment of the present application also provides a method for resetting a vehicle-mounted domain controller. In the method for resetting the vehicle-mounted domain controller, the method also includes: receiving the key status information sent by the control module in real time, the key status information includes the key status before resetting; storing the received key status information in a non-destructive storage space; the key status information sent by the vehicle body control module includes: low-voltage power supply status information, wiper operation status information, light status information, hard-wire output status information; the key status information sent by the vehicle power control module includes: vehicle drivable status information, high-voltage status information, gear status information, electric drive controller operation instructions, and battery controller operation instructions.

[0064] In this embodiment, the memory module set in the domain controller of the present application will receive the key status information sent by the control module in real time. Since it is received in real time, the key status information will also record the key status of each execution controller before reset. After receiving the key status information, the memory module will immediately store the key status information in the corresponding non-destructive storage space.

[0065] In this embodiment, the key status information sent to the vehicle body control module includes, but is not limited to: low voltage power supply status information, wiper operation status information, light status information, hard line output status information, etc. The key status information sent to the vehicle power control module includes, but is not limited to: vehicle drivable status information, high voltage status information, gear status information, electric drive controller operation instructions, battery controller operation instructions, etc.

[0066] In combination with the above embodiments, in one implementation, the embodiment of the present application further provides a method for resetting a vehicle-mounted domain controller. In the method for resetting the vehicle-mounted domain controller, determining a pre-reset instruction includes: obtaining a pre-reset critical state stored in a non-volatile storage space; and determining a pre-reset instruction corresponding to the pre-reset critical state based on the pre-reset critical state.

[0067] In this embodiment, for the pre-reset instructions sent to the control module, the memory module obtains the key states of each execution controller before reset sent by the control module and stored in the non-volatile storage space, and then based on these pre-reset key states, the instructions corresponding to each key state can be determined, and the instructions are the pre-reset instructions. These pre-reset instructions are sent to the corresponding execution controllers for execution, so that the execution controllers can maintain the pre-reset state.

[0068] In combination with the above embodiments, in one implementation, the embodiment of the present application further provides a method for resetting a vehicle-mounted domain controller. In the method for resetting a vehicle-mounted domain controller, the method further includes: when the comparison result shows that the abnormal reset duration does not exceed the preset duration, controlling the execution controller with the pre-reset instruction to maintain the state corresponding to the pre-reset instruction within the abnormal reset duration.

[0069] In this embodiment, when the domain controller is abnormally reset successfully and the abnormal reset time taken for the successful abnormal reset does not exceed the preset time, each execution controller will no longer receive instructions sent by the domain controller during the period from the start of the abnormal reset of the domain controller to the success of the abnormal reset. At this time, each execution controller maintains the state corresponding to the pre-reset instruction based on the pre-reset instruction sent before the abnormal reset of the domain controller begins.

[0070] In combination with the above embodiments, in one implementation, the embodiment of the present application further provides a method for resetting a vehicle-mounted domain controller. In the method for resetting a vehicle-mounted domain controller, the method further includes: when the comparison result is that the abnormal reset duration exceeds the preset duration, ending the control of each execution controller at a target time, and resuming the control of each execution controller at the time of successful abnormal reset, the target time being the time after the preset duration has passed since the abnormal reset.

[0071] In this embodiment, when the domain controller is successfully reset due to an abnormality, and the abnormal reset time taken for the abnormal reset to succeed exceeds the preset time, the domain controller will end the control of each execution controller from the target time to the time before the reset is successful. At this time, it means that each execution controller has not received a new instruction sent by the domain controller after waiting for the maximum time. At this time, since the domain controller has not been successfully reset due to an abnormality, it will not send a new instruction, and each execution controller will perform corresponding actions based on its own fault response strategy. Among them, the target time is the time after the abnormal reset start time passes the preset time, for example, the abnormal reset start time is t1, and the preset time is 500ms, and the corresponding target time is t1+500ms. When the domain controller is successfully reset due to an abnormality, and the abnormal reset time taken for the abnormal reset to succeed exceeds the preset time, the domain controller will resume the control of each execution controller from the time of the abnormal reset success. At this time, it means that the domain controller will send a safety instruction to the control module in this scenario to control the vehicle to be in a safe state, that is, the process of the above step S4.

[0072] In combination with the above embodiments, in one implementation, the embodiment of the present application further provides a method for resetting a vehicle-mounted domain controller. In the method for resetting a vehicle-mounted domain controller, the method further includes: between the target time and the abnormal reset success time, each execution controller performs a corresponding action based on its own fault response strategy.

[0073] In this embodiment, from the target time to the time when the reset is successful, the domain controller will end the control of each execution controller, and each execution controller will perform corresponding actions based on its own response strategy. For example, some execution controllers may continue to maintain the state corresponding to the pre-reset instruction, while some execution controllers may end their work at the target time. As the intelligent driving controller is directly related to driving safety, the intelligent driving controller will actively exit the intelligent driving at the target time and prompt the driver to intervene. That is, if no new instructions are received from the domain controller within the preset time, the intelligent driving controller will actively exit the intelligent driving.

[0074] In this embodiment, if Figure 3 As shown, Figure 3Another flow chart of a method for resetting a vehicle-mounted domain controller provided by the present application is shown. First, it is identified whether the domain controller is reset. If so, the reset time is recorded, including the reset start time, the reset success time, the time taken for the reset to succeed, etc., and then the reset identification module determines whether the current reset is an abnormal reset caused by software or hardware. If not, the control process is not intervened, and the normal control process is directly executed. In the case of determining that it is an abnormal reset, the reset flag is output to each control module in the domain controller, so that each control module knows that the domain controller has an abnormal reset and needs to execute the corresponding reset response strategy. The memory module records in real time that the memory module will receive the key status information sent by the control module in real time, and based on these key status information, it can be determined that the domain controller sends instructions to each execution controller before the abnormal reset occurs. In the case of an abnormal reset of the domain controller, and the time taken for the successful reset does not exceed the preset time (that is, the time agreed with the execution controller in the figure), the memory module will send a pre-reset instruction to the control module within the first software operation cycle to control the control module to send the received pre-reset instruction to the corresponding execution controller for execution based on the received reset flag. In the event that an abnormal reset occurs to the domain controller and the time taken for a successful reset exceeds a preset time (i.e., the time agreed with the execution controller in the figure), if the reset is successful, the timeout processing module sends a safety instruction to each control module in the domain controller, allowing each control module to control its corresponding execution controller to switch to a safe state, thereby switching the entire vehicle to a safe state and then waiting for rescue, or if the reset is not successful within the preset time, also wait for rescue.

[0075] Based on the same inventive concept, an embodiment of the present application provides a reset system for a vehicle-mounted domain controller, such as Figure 4 As shown, the system 400 includes:

[0076] The reset identification module 401 is used to monitor and determine whether an abnormal reset occurs, and send a reset flag to a control module in the domain controller according to the abnormal reset monitoring result;

[0077] The timeout processing module 402 is used to determine the abnormal reset duration from the start of the abnormal reset to the success of the abnormal reset; and to compare the abnormal reset duration with the preset duration to obtain a comparison result; and to control the control module to send a safety instruction to the corresponding execution controller for execution based on the reset flag when the comparison result is that the abnormal reset duration exceeds the preset duration.

[0078] Optionally, the system 400 further includes:

[0079] The memory module is used to control the control module to send a pre-reset instruction to the corresponding execution controller for execution within the first software running cycle based on the reset flag when the comparison result shows that the abnormal reset duration does not exceed the preset duration.

[0080] Optionally, the reset identification module 401 is further configured to maintain low voltage power supply to the execution controller hard line when the monitoring result indicates that an abnormal reset has occurred.

[0081] Optionally, the memory module is further used to receive in real time the critical status information sent by the control module, the critical status information including the critical status before reset; and to store the received critical status information into a non-volatile storage space.

[0082] Optionally, the memory module is further used to obtain the critical state before reset stored in the non-volatile storage space; and to determine the pre-reset instruction corresponding to the critical state before reset based on the critical state before reset.

[0083] Optionally, the system 400 further includes: an execution controller, configured to control the execution controller to maintain a state corresponding to the pre-reset instruction within the abnormal reset duration by using the pre-reset instruction when the comparison result shows that the abnormal reset duration does not exceed the preset duration.

[0084] Optionally, the system 400 further includes:

[0085] The domain controller is used to end the control of each execution controller at a target time when the comparison result is that the abnormal reset duration exceeds the preset duration, and to resume the control of each execution controller when the abnormal reset is successful. The target time is the time after the preset duration has passed since the abnormal reset.

[0086] Optionally, the execution controller is further used to execute corresponding actions based on its own fault response strategy between the target time and the time when the abnormal reset is successful.

[0087] Optionally, the control module in the domain controller of the system 400 includes: a vehicle body control module and a vehicle power control module; the key status information sent by the vehicle body control module includes: low-voltage power supply status information, wiper operation status information, light status information, and hard-wire output status information; the key status information sent by the vehicle power control module includes: vehicle drivable status information, high-voltage status information, gear status information, electric drive controller operation instructions, and battery controller operation instructions.

[0088] Based on the same inventive concept, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and running on the processor. When the computer program is executed by the processor, the steps in the method for resetting a vehicle domain controller as described in the first aspect of the present application are implemented.

[0089] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in a method for resetting a vehicle domain controller as described in the first aspect of the present application are implemented.

[0090] As for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0091] It should be noted that, for the method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.

[0092] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0093] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application may adopt the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0094] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0095] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0096] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0097] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0098] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0099] The above is a detailed introduction to the resetting method, system and product of a vehicle-mounted domain controller provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technicians in this field, according to the ideas of the present application, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for resetting a vehicle-mounted domain controller, characterized in that: Applied to a domain controller, the method comprises: Monitor whether abnormal reset occurs; According to the abnormal reset monitoring result, a reset flag is sent to the control module in the domain controller; Determine the abnormal reset time from the start of abnormal reset to the success of abnormal reset; Compare the abnormal reset time with the preset time to obtain a comparison result; When the comparison result is that the abnormal reset duration exceeds the preset duration, the control module is controlled to send a safety instruction to a corresponding execution controller for execution based on the reset flag.

2. A method for resetting a vehicle domain controller according to claim 1, characterized in that: The method further comprises: When the comparison result is that the abnormal reset duration does not exceed the preset duration, the control module is controlled to send a pre-reset instruction to a corresponding execution controller for execution within the first software running cycle based on the reset flag.

3. The method for resetting a vehicle-mounted domain controller according to claim 1, characterized in that: Before sending the reset flag to the control module in the domain controller according to the abnormal reset monitoring result, the method further includes: When the monitoring result is that an abnormal reset occurs, the low voltage power supply to the execution controller hard line is maintained.

4. A method for resetting a vehicle-mounted domain controller according to claim 1, characterized in that: The method further comprises: receiving in real time the key state information sent by the control module, wherein the key state information includes the key state before resetting; The received key status information is stored in a non-volatile storage space.

5. A method for resetting a vehicle-mounted domain controller according to claim 4, characterized in that: Determine the pre-reset instructions, including: Obtaining the critical state before the reset stored in the non-volatile storage space; Based on the key state before resetting, a pre-resetting instruction corresponding to the key state before resetting is determined.

6. The method for resetting a vehicle-mounted domain controller according to claim 1, characterized in that: The method further comprises: When the comparison result shows that the abnormal reset time duration does not exceed the preset time duration, the execution controller is controlled by the pre-reset instruction to maintain the state corresponding to the pre-reset instruction within the abnormal reset time duration.

7. A method for resetting a vehicle-mounted domain controller according to claim 1, characterized in that: The method further comprises: When the comparison result shows that the abnormal reset duration exceeds the preset duration, the control of each execution controller is terminated at the target time, and the control of each execution controller is restored when the abnormal reset is successful. The target time is the time after the preset time has passed since the abnormal reset.

8. The method for resetting a vehicle-mounted domain controller according to claim 1, characterized in that: The method further comprises: Between the target time and the time when the abnormality is successfully reset, each execution controller performs corresponding actions based on its own fault response strategy.

9. A method for resetting a vehicle-mounted domain controller according to claim 1, characterized in that: The control module includes: a vehicle body control module and a vehicle power control module.

10. A method for resetting a vehicle-mounted domain controller according to claim 9, characterized in that: The key status information sent by the vehicle body control module includes: low-voltage power supply status information, wiper operation status information, light status information, and hard-line output status information; The key status information sent by the vehicle power control module includes: vehicle drivability status information, high-voltage status information, gear status information, electric drive controller operating instructions, and battery controller operating instructions.

11. A vehicle-mounted domain controller reset system, characterized in that: The system comprises: A reset identification module is used to monitor and determine whether an abnormal reset occurs, and send a reset flag to a control module in the domain controller according to the abnormal reset monitoring result; A timeout processing module is used to determine the abnormal reset duration from the start of the abnormal reset to the success of the abnormal reset; and to compare the abnormal reset duration with a preset duration to obtain a comparison result; and to control the control module to send a safety instruction to the corresponding execution controller for execution based on the reset flag when the comparison result is that the abnormal reset duration exceeds the preset duration.

12. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is executed by the processor, the steps in the method for resetting a vehicle domain controller according to any one of claims 1 to 10 are implemented.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the method for resetting a vehicle domain controller according to any one of claims 1 to 10 are implemented.

Images