Fault recovery method and system, driving equipment and storage medium

By identifying faulty peripheral components through a power supply fault detection unit and formulating fault recovery strategies, and by adopting soft reset or hard reset procedures, the problem of difficulty in identifying fault types in traditional fault recovery is solved, thus achieving stable operation and safety of the driving equipment.

CN121626174APending Publication Date: 2026-03-10NIO TECH ANHUI CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202511811908.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-03
Publication Date
2026-03-10

AI Technical Summary

Technical Problem

In traditional fault recovery processes, it is difficult to identify the fault type when detecting faults in peripheral components of the driving equipment, which may lead to a global reset and a brief system shutdown, affecting driving safety and stability.

Method used

The power supply fault detection unit identifies faulty peripheral components, obtains operating status information using device identification, formulates fault recovery strategies, performs fault recovery using soft reset or hard reset procedures, and performs initialization configuration and testing.

Benefits of technology

It enables precise recovery of faulty peripheral components, avoids system restarts, reduces data loss, and improves the availability and stability of driving equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121626174A_ABST
    Figure CN121626174A_ABST
Patent Text Reader

Abstract

The invention provides a fault recovery method and system, driving equipment and a storage medium, and belongs to the technical field of driving equipment.The method comprises the steps that in the running process of the driving equipment, an equipment identifier of a target peripheral component with a fault in multiple peripheral components of the driving equipment is determined; obtaining working state information of the target peripheral component according to the equipment identifier, wherein the working state information is used for reflecting whether the power supply state of the target peripheral component is normal when the fault occurs; determining a fault recovery strategy of the target peripheral component according to the working state information; and controlling the target peripheral component to perform fault recovery according to the fault recovery strategy. In this way, fault recovery is only carried out on the peripheral component with the fault, operation of other peripheral components is not affected, normal operation of the system can be guaranteed while the error state can be cleared away in time, unnecessary system restarting is avoided, data loss is prevented, the influence of the fault on operation of the driving equipment is reduced, and the driving efficiency is improved. And the availability and the stability of the system are improved.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of driving equipment, and particularly relates to a fault recovery method and system, a driving equipment and a storage medium. BACKGROUND

[0002] An electronic control unit (ECU) is a core control component of a driving equipment, responsible for coordinating and managing the operation of numerous peripheral components of the driving equipment. For example, engine control, chassis system control, cockpit entertainment control, etc. Among them, the control of components such as sensors, actuators, display screens, audio devices, etc. in each system. With the continuous enrichment of the functions of the driving equipment and the improvement of the intelligent level, the number and types of ECUs and the peripherals they control continue to increase, resulting in increasing system complexity.

[0003] In actual operation, the peripheral components of the driving equipment are prone to failure due to electrical interference, temperature changes, vibration, component aging, software vulnerabilities and other factors. Therefore, in order to ensure the normal operation of the driving equipment and prevent driving safety problems caused by the failure of peripheral components, fault detection of the driving equipment is required, and timely recovery of the fault is required. SUMMARY

[0004] The purpose of the present application is to provide a fault recovery method, system, driving equipment and storage medium, aiming to solve the problem of driving safety in the traditional fault recovery process.

[0005] The first aspect of the embodiment of the present application provides a fault recovery method, which comprises: During the operation of the driving equipment, the device identifier of a target peripheral component that has failed among a plurality of peripheral components of the driving equipment is determined; According to the device identifier, the working state information of the target peripheral component is obtained, and the working state information is used to reflect whether the power supply state of the target peripheral component is normal when the target peripheral component fails; According to the working state information, a fault recovery strategy of the target peripheral component is determined; The target peripheral component is controlled to perform fault recovery according to the fault recovery strategy.

[0006] In some embodiments, the fault recovery strategy includes performing a soft reset process and a hard reset process; The target peripheral component is controlled to perform fault recovery according to the fault recovery strategy, comprising: if the working state information indicates that the power supply state is normal when the target peripheral component fails, a soft reset instruction is sent to the target peripheral component, the soft reset instruction instructing the peripheral component to start the soft reset process; if the working state information indicates that the power supply state is abnormal when the peripheral component fails, a hard reset instruction is sent to the power supply control unit, the hard reset instruction at least including the device identifier of the target peripheral component, the hard reset instruction instructing the power supply control unit to start the hard reset process for the target peripheral component.

[0007] In some embodiments, after controlling the target peripheral component to perform fault recovery according to the fault recovery strategy, the method further comprises: performing initialization configuration on the target peripheral component after fault recovery according to configuration information of the target peripheral component.

[0008] In some embodiments, after performing initialization configuration on the target peripheral component after fault recovery according to the configuration information of the target peripheral component, the method further comprises: testing the target peripheral component after initialization is completed to obtain a test result, the test result being used to reflect whether the target peripheral component has recovered to a normal working state; if the test result indicates that the target peripheral component has not recovered to the normal working state, a hard reset instruction is sent to the power supply control unit, the hard reset instruction at least including the device identifier of the target peripheral component, the hard reset instruction instructing the power supply control unit to start the hard reset process for the target peripheral component.

[0009] In some embodiments, if the fault recovery strategy is to perform the hard reset process, and if the test result indicates that the target peripheral component has not recovered to the normal working state, the method further comprises: determining a continuous number of times of performing the hard reset process for the target peripheral component in the current fault recovery process; when the continuous number of times reaches a preset number of times, generating a fault report of the peripheral component, the fault report at least including: a time when the fault of the peripheral component occurs, a fault type of the fault, a device identifier of the peripheral component, a fault recovery strategy taken for the peripheral component, and a fault recovery result.

[0010] In some embodiments, the determining of the device identifier of the target peripheral component that fails among the plurality of peripheral components of the driving device comprises: obtaining a fault signal from the power supply control unit, the fault signal at least including at least one of the device identifiers, the fault signal being used to indicate that the target peripheral component corresponding to the device identifier fails.

[0011] A second aspect of the embodiments of the present application provides a fault recovery system, comprising: a power supply control unit, a power supply fault detection unit, and one or more drive management units, any of the drive management units being used to connect to one peripheral component of a driving device; The power supply control unit is configured to control the power supply module to supply power to the peripheral component at a target working parameter; The power supply fault detection unit is configured to acquire a power supply parameter of each of the peripheral components, and in the case that the power supply parameter of any of the peripheral components indicates that the peripheral component has a fault, send a fault signal to the drive management unit, the fault signal comprising at least one device identifier, the fault signal being used to indicate that the target peripheral component corresponding to the device identifier has a fault; The drive management unit is configured to execute the method according to any one of the first aspect.

[0012] In some embodiments, if the working state information indicates that the power supply state is normal when the target peripheral component has a fault, the drive management unit is configured to send a soft reset instruction to the target peripheral component having a fault according to the device identifier; The target peripheral component is configured to execute a soft reset process in response to the soft reset instruction.

[0013] In some embodiments, if the working state information indicates that the power supply is abnormal when the peripheral component has a fault, the power supply control unit is configured to acquire a hard reset instruction from the drive management unit, the hard reset instruction comprising at least the device identifier of the target peripheral component having a fault; in response to the hard reset instruction, based on the device identifier carried by the hard reset instruction, control the power supply module to stop supplying power to the target peripheral component and control the power supply module to continue supplying power to the target peripheral component after a preset time length.

[0014] In some embodiments, the fault recovery system further comprises one or more power supply switches, any of the power supply switches being connected in series between the power supply module and the peripheral component; The power supply control unit is configured to, in response to the hard reset instruction, control the power supply switch of the target peripheral component to be turned off based on the device identifier carried by the hard reset instruction. When the time length of stopping power supply reaches the preset time length, the power supply switch of the target peripheral component is re-controlled to be turned on.

[0015] A third aspect of the embodiments of the present application provides a driving device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the fault recovery method as described above.

[0016] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the fault recovery method described above.

[0017] A fifth aspect of this application provides a computer program product that, when run on an electronic device, causes the electronic device to perform the fault recovery method described above.

[0018] The beneficial effects of the embodiments of the present invention compared with the prior art are as follows: In this embodiment, the faulty peripheral component is identified by its device identifier. Then, the operating status information of the faulty peripheral component is determined, and a fault recovery strategy is formulated based on this information. The fault recovery strategy is then applied to the peripheral component to restore its functionality. This approach allows for different fault recovery strategies for different faults. Since this application focuses on restoring faults to the faulty peripheral component, it does not affect the operation of other peripheral components. It can promptly clear erroneous states while ensuring the normal operation of the system, avoiding unnecessary system restarts, preventing data loss, reducing the impact of faults on the operation of the driving equipment, and improving the availability and stability of the system. Attached Figure Description

[0019] Figure 1 A schematic diagram of the system architecture of a fault recovery system provided in an exemplary embodiment is shown; Figure 2 A schematic diagram of the system architecture of a fault recovery system provided in an exemplary embodiment is shown; Figure 3 A schematic diagram of the system architecture of a fault recovery system connected to two peripheral components is shown in an exemplary embodiment. Figure 4 A flowchart illustrating a fault recovery method provided in an exemplary embodiment is shown. Figure 5 A flowchart illustrating a fault recovery method provided in an exemplary embodiment is shown. Figure 6 A flowchart illustrating a fault recovery method provided in an exemplary embodiment is shown. Figure 7 This is a schematic diagram of the structure of the driving device provided in an embodiment of the present invention. Detailed Implementation

[0020] To make the technical problems, technical solutions, and beneficial effects to be solved by this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this application.

[0021] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0022] The electronic control unit (ECU) is the core control component of a driving system, responsible for coordinating and managing the operation of numerous peripheral components. For example, this ECU may reside within different control units such as the engine control unit, chassis system control unit, and cockpit entertainment control unit. Correspondingly, different ECUs can coordinate and manage various peripheral components. For instance, the electronic control power supply can coordinate and manage peripheral components such as sensors, actuators, displays, and audio equipment. As the functions of driving systems become increasingly sophisticated and their level of intelligence improves, the number and types of ECUs and the peripherals they control continue to increase, leading to ever-increasing system complexity.

[0023] In actual operation, the peripheral components of the driving equipment are prone to failure due to various factors such as electrical interference, temperature changes, vibration, component aging, and software vulnerabilities. Therefore, in order to ensure the normal operation of the driving equipment and prevent the driving safety of the driving equipment from being affected by the failure of peripheral components, it is necessary to perform fault detection on the driving equipment and restore the detected faults in a timely manner to ensure the normal operation of the driving equipment.

[0024] In some embodiments, a simple power supply fault detection circuit is used to detect whether the electronic control unit (ECU) and its controlled peripheral components are powered normally, thereby determining whether the multiple peripheral components controlled by the ECU are operating normally. This fault detection method can only detect whether the system composed of the ECU and its controlled peripheral components is currently operating normally, but it is difficult to identify the type of fault or determine which peripheral component has failed. Therefore, when a fault is detected in a peripheral component and fault recovery is required, a global reset is often used, that is, the system composed of the ECU and its controlled peripheral components is reset. This will cause a short-term shutdown of the entire system, thereby interrupting ongoing critical operations, such as real-time engine control and monitoring of driving equipment safety systems. It may also cause data loss, system instability, and other problems, seriously affecting the normal operation and safety performance of the driving equipment and impacting the user experience.

[0025] To meet the safety, reliability, and comfort requirements of the driving equipment industry, and to optimize user experience, this application provides a fault recovery method, a fault recovery system, a driving equipment, and a storage medium. The following description, in conjunction with specific embodiments, illustrates this application.

[0026] Please see Figure 1 This illustrates the system architecture of a fault recovery system provided by an exemplary embodiment. See also Figure 1 The fault recovery system includes a power supply control unit 10 and one or more drive management units 30.

[0027] In some embodiments, see Figure 2 The power supply control unit 10 may include a power supply fault detection unit 20.

[0028] As an example, this fault recovery system can be applied to driving equipment. Driving equipment may include multiple peripheral components. These peripheral components may include sensors, actuators, displays, audio equipment, and other similar devices.

[0029] In one possible embodiment of this application, each of the plurality of peripheral components can correspond to a drive management unit 30. That is, any drive management unit 30 is used to connect to a peripheral component of the driving device. For example, such as Figure 3 As shown, the driving device includes peripheral component A and peripheral component B, and the fault recovery system may include drive management unit A and drive management unit B. Drive management unit A is connected to peripheral component A and is used to manage peripheral component A. Drive management unit B is connected to peripheral component B and is used to manage peripheral component B.

[0030] Taking an audio device as an example, the driver management unit 30 connected to the audio device is used to control the audio device's startup, soft reset, hard reset, initialization, and audio playback.

[0031] In another possible embodiment of this application, multiple peripheral components may also be managed by the same drive management unit 30, and this embodiment of the application does not limit this.

[0032] like Figure 3 As shown, the fault recovery system in this embodiment may further include: a power supply unit, which is used to supply power to one or more peripheral components. As an example, a power supply unit may include multiple power supply modules. Each power supply module may be connected to at least one peripheral device. The power supply module is used to supply power to the connected peripheral device.

[0033] In one possible embodiment of this application, two or more peripheral components may be connected to the same power supply module. That is, one power supply module can supply power to two or more peripheral components. Key peripheral components can be powered individually, meaning each key peripheral component corresponds to a separate power supply module. Specifically, peripheral components can be categorized according to their importance to obtain key and non-key peripheral components. Multiple non-key peripheral components can correspond to one power supply unit, so that even if that power supply unit stops supplying power, it will not affect the operation of the driving device. Each key peripheral component can correspond to one power supply unit, so that even if that power supply unit stops supplying power, only that key peripheral component will be unable to operate due to power failure, without affecting the operation of other peripheral components.

[0034] In one possible embodiment of this application, different power supply modules are used to power different peripheral components. That is, any peripheral component can have a power supply module, which is used to power that peripheral component.

[0035] For example, one or more power supply modules can be connected to the power supply control unit 10. The power supply control unit 10 is used to set the target operating parameters for each power supply module, so that each power supply module supplies power to its connected peripheral components according to the set target operating parameters. The target operating parameters for different power supply modules can be the same or different. For example, the target operating parameters can be the power supply current and / or power supply voltage of the peripheral components during operation.

[0036] In other embodiments, the peripheral component is powered by its corresponding power supply module. Accordingly, the power supply control unit 10 and the power supply fault detection unit 20 are connected to the peripheral component through its respective power supply module. For example, please continue to see... Figure 3The power supply module is connected to the corresponding peripheral components, and the power supply module is also connected to the power supply control unit 10 and the power supply fault detection unit 20.

[0037] In some embodiments, the power supply control unit 10 is a programmable power management chip selected based on theoretical power supply parameters such as the power requirements, voltage levels, and startup priorities of the peripheral components connected to it. For example, the power supply control unit 10 is a TPS54331 series chip. In the embodiments of this application, the chip's output voltage, current limits, and other operating parameters can be precisely set using external high-precision resistors, capacitors, and other electronic components, thereby ensuring that the power supply control unit 10 can provide a stable and adaptable power supply to different peripheral components.

[0038] The output of the power supply control unit 10 is connected to the peripheral components via a power supply switch. In some embodiments, the power supply switch can be in the form of a switch array, with each power supply switch in the array connected to a peripheral component. The switch array can be controlled to be turned on or off by a programmable logic device, thereby controlling the power-on sequence of the peripheral components. The electronic switches and the programmable logic device in the switch array can be selected as needed; in this embodiment, the types of electronic switches and programmable logic devices are not specifically limited. For example, the switch array can be an array of MOSFET transistors. The programmable logic controller can be a Complex Programmable Logic Device (CPLD) or a Field-Programmable Gate Array (FPGA), etc.

[0039] The power supply control unit 10 is also connected to a power supply to provide power to peripheral components. In this embodiment, electrolytic capacitors and ceramic capacitors are arranged at the power input and output terminals to form a high-efficiency filtering and voltage regulation circuit, thereby effectively eliminating noise and interference in the power supply, ensuring its stability and purity, and creating favorable conditions for the smooth startup and stable operation of peripheral components. Simultaneously, a sensitive voltage and current feedback circuit is constructed and connected to the feedback pin of the power management unit to achieve real-time and accurate monitoring and dynamic adjustment of the power supply output status, ensuring that the power supply is always in optimal operating condition.

[0040] During the startup process of the driving device, the power supply control unit 10 initiates the initialization process, sequentially controlling the power supply modules connected to each peripheral component to supply power to the peripheral components according to the preset power-on sequence. In some embodiments, the power supply control unit 10 adopts a preset power management strategy, controlling the power supply module to gradually increase the output power supply voltage, thereby ensuring that each peripheral component can start up in a stable and safe power environment, avoiding damage to the peripheral components caused by instantaneous large current. For example, for some precision sensors with high requirements for power supply stability, the power supply control unit 10 will first control the power supply module to pre-charge the peripheral component with a lower voltage. After the internal circuit of the sensor stabilizes, the power supply module will then control the power supply module to gradually increase the sensor's power supply voltage to the normal operating voltage, thereby ensuring that the sensor can start up normally and operate stably.

[0041] The power supply fault detection unit 20 is used to acquire the power supply parameters of each peripheral component, and to send a fault signal to the drive management unit 30 corresponding to any peripheral component when the power supply parameters of any peripheral component indicate that the peripheral component has failed. The fault signal includes at least one device identifier, which is used to indicate that the peripheral component corresponding to the device identifier has failed. The device identifier can be the device identifier of any peripheral component that has failed.

[0042] For example, the power supply fault detection unit 20 is used to detect power supply parameters such as voltage and current of different peripheral components, so as to determine whether the peripheral component has failed based on the power supply parameters.

[0043] In some embodiments, the power supply fault detection unit 20 may include sensors such as voltage sensors and current sensors for detecting power supply parameters. The power supply fault detection unit 20 may use voltage sensors and current sensors selected according to the power supply parameter characteristics of the peripheral components to ensure that the range and accuracy of the sensors accurately match the power supply detection requirements of the peripheral components. For example, the voltage sensor may be a high-precision voltage sensor such as the LT6106 series, and the current sensor may be a current sensor such as the ASC712 series.

[0044] In this embodiment, voltage and current sensors can be installed on the power supply circuit of each peripheral component, thereby collecting the power supply voltage and current of the peripheral component in real time and accurately, and monitoring the changes in power supply voltage and current.

[0045] It should be noted that the power supply voltage or current parameters collected by the voltage or current sensor are in the form of analog signals. For ease of processing, an analog-to-digital converter (ADC) can be used to convert the analog power supply parameters into digital signals for subsequent processing. The ADC can be any type of ADC as needed; for example, it can be a high-performance ADC chip such as the ADS1256. However, this embodiment does not impose a specific limitation on this.

[0046] To ensure the accuracy of the acquired signals, the power supply parameters in analog form can be preprocessed before analog-to-digital conversion. For example, operational amplifiers can be used to amplify and filter the power supply parameters in analog form to enhance signal strength and stability, and remove interference components from the signal.

[0047] The power supply fault detection unit 20 also includes a microcontroller with a built-in fault diagnosis algorithm. Accordingly, the signal representing the power supply parameters after analog-to-digital conversion is transmitted to the microcontroller. The built-in fault diagnosis algorithm analyzes and compares these power supply parameters to identify various power supply fault conditions. When a power supply fault is detected in any peripheral component based on the power supply parameters, the power supply fault detection unit 20 generates a fault signal and transmits it to the drive management unit 30.

[0048] The microcontroller can be any microcontroller that supports fault diagnosis algorithms; in this embodiment, the type of microcontroller is not specifically limited. For example, the microcontroller can be an Aurix 367 series microcontroller. Furthermore, the microcontroller can communicate with the drive management unit 30 via a communication interface, and correspondingly, the microcontroller sends fault signals to the drive management unit 30 through this communication interface. This communication interface can be a Controller Area Network (CAN) interface or a Serial Peripheral Interface (SPI), etc.

[0049] In some embodiments, the power supply fault detection unit 20 periodically samples and analyzes the power supply parameters of each peripheral component at fixed time intervals. This time interval can be set as needed, and in this embodiment, it is not specifically limited. For example, the time interval can be 10 milliseconds, 15 milliseconds, 20 milliseconds, 5 seconds, 10 seconds, 30 seconds, or 1 minute.

[0050] The power supply fault detection unit 20 compares the power supply parameters of the peripheral component with preset parameter thresholds to determine whether the peripheral component has malfunctioned. For example, when the power supply voltage in the power supply parameters is lower than the lowest voltage in the parameter thresholds corresponding to the peripheral component, it is determined that the power supply parameters of the peripheral component do not meet the preset parameter thresholds.

[0051] It should be noted that in practical applications, when the power supply fault detection unit 20 detects that the power supply parameters of the peripheral component do not meet the preset parameter threshold, it generates a fault signal and sends the fault signal to the drive management unit 30. The preset parameter threshold can be a voltage threshold or a current threshold. Accordingly, the power supply fault detection unit 20 can determine whether the peripheral component meets the parameter threshold by comparing the power supply parameters of the peripheral component with the parameter threshold. For example, when the power supply parameter is the supply voltage, it can be set to determine that the power supply parameter does not meet the preset parameter threshold when the supply voltage is greater than the parameter threshold. The parameter threshold can be set as needed; in this embodiment, the parameter threshold is not specifically limited.

[0052] In this way, when the power supply parameters of the peripheral component are found to be inconsistent with the preset parameter threshold, a fault signal is sent to the drive management unit 30. This allows the drive management unit 30 to perform further fault detection on the peripheral component in a timely manner based on the fault signal. When a fault occurs in the peripheral component, it can be detected in time and measures can be taken to ensure the stable power supply and normal operation of the peripheral component.

[0053] In other embodiments, when the power supply fault detection unit 20 detects that the power supply parameters of a peripheral component do not meet a preset parameter threshold, it generates a fault signal and counts the number of consecutive fault signals. When the number of consecutive fault signals for the same peripheral component reaches a first preset number, it sends a fault signal to the drive management unit 30. This first preset number can be set as needed; in this embodiment, it is not specifically limited. In this implementation, recording the number of consecutive fault signal occurrences and sending the fault signal to the drive management unit 30 only when the number of consecutive fault signal occurrences reaches the first preset number prevents false alarms and jitter in the fault signal. Simultaneously, when a peripheral component malfunctions, it can be detected promptly and appropriate measures can be taken, ensuring stable power supply and normal operation of the peripheral component.

[0054] The power supply fault detection unit 20 and the drive management unit 30 can communicate via CAN or SPI bus. Accordingly, the power supply fault detection unit 20 can send the fault signal to the drive management unit 30 via CAN or SPI.

[0055] The power supply fault detection unit 20 starts its detection process synchronously when the power supply control unit 10 begins supplying power to the peripheral components, thus enabling it to detect any abnormalities in the power supply to each peripheral component during the startup phase. If problems such as excessively high or low voltage or excessive current are detected during the startup phase, the power supply fault detection unit 20 will immediately generate a fault signal and send it to the drive management unit 30, so that the drive management unit 30 can take appropriate measures in a timely manner to ensure that the system startup process proceeds smoothly.

[0056] For ease of description, in this embodiment, peripheral components whose power supply parameters do not meet a preset parameter threshold are identified as target peripheral components. The drive management unit 30 is used to receive a fault signal sent by the power supply fault detection unit 20, and obtain the working status information of the target peripheral component based on the device identifier carried by the fault signal. The working status information is used to reflect whether the power supply status of the target peripheral component is normal when a fault occurs. The drive management unit 30 is used to determine the fault recovery strategy of the target peripheral component based on the working status information.

[0057] The fault recovery strategy can be configured as needed. In this embodiment, the fault recovery strategy includes soft reset and hard reset.

[0058] Soft reset and hard reset refer to two methods for restoring a device to normal operation. Specifically, a soft reset refers to a reset method that restores peripheral components to their normal working state through software instructions. A hard reset refers to a reset method that restores peripheral components to their normal working state through physical means (such as pressing a reset button) or by powering off and restarting.

[0059] The drive management unit 30 is a processor with processing capabilities. In some embodiments, the core control component of the drive management unit 30 can be a driving device-level microprocessor, for example, the core control component of the drive management unit 30 can be an Aurix 367. Additionally, external memory can be expanded for the drive management unit 30 according to the actual data storage and computation requirements of the system, for storing system program code, configuration data of peripheral components, critical data generated during fault diagnosis, and critical data generated during fault recovery, etc. This expanded external memory can be any memory with storage capabilities; in this embodiment, the type of memory is not specifically limited. For example, the memory can be Synchronous Dynamic Random-Access Memory (SDRAM) or Non-volatile Memory (NOR Flash), etc.

[0060] The microprocessor's circuit board includes a reset circuit capable of both manual and power-on reset. This ensures that the system can be promptly reset and restored to normal operation should any abnormalities occur during startup and operation. The reset circuit can be any circuit with a reset function; however, the specific structure of the reset circuit is not specifically limited in this embodiment. For example, the reset circuit could be implemented using a MAX811 chip.

[0061] The drive management unit 30 includes peripheral interface circuitry, which comprises multiple Universal Asynchronous Receiver / Transmitter (UART), Inter-Integrated Circuit (I2C), and Controller Area Network (CAN) interfaces. Through these different peripheral interfaces, it can communicate with various peripheral components, enabling accurate data transmission and timely command issuance.

[0062] In some embodiments, in order to realize the control and real-time status monitoring of peripheral components, the drive management unit 30 is provided with a general-purpose input / output (GPIO) interface circuit. The GPIO interface circuit is connected to the control pin and register read pin of the peripheral component to realize the control and real-time status monitoring of each peripheral, timely obtain the working status information of the peripheral component and the feedback data of the executed command, and provide a comprehensive and accurate basis for fault diagnosis and recovery operation.

[0063] In other embodiments, the drive management unit 30 further includes a clock circuit to ensure stable operation of the microprocessor and precise timing control of various tasks. This clock circuit can be any circuit with timing functionality; in this embodiment, the circuit structure of the clock circuit is not specifically limited. For example, the clock circuit can be a circuit that provides a clock signal via a crystal oscillator.

[0064] The drive management unit 30 is used for tasks such as communication with peripheral components, fault detection and diagnosis, and coordination and execution of fault recovery operations. When a fault signal is received from the power supply fault detection unit 20, the unit identifies the target peripheral component whose power supply parameters do not meet the preset parameter thresholds based on the fault signal. Then, it reads the operating status information of the target peripheral component and determines whether the target peripheral component is operating normally based on this information. This operating status information consists of parameters indicating the operating status of the target peripheral component. For example, the operating status information may include parameters such as the register status of the target peripheral component and the control pin level of the peripheral component.

[0065] In some embodiments, if the operating status information indicates that the power supply status is normal when the target peripheral component malfunctions, the drive management unit 30 is used to send a soft reset command to the target peripheral component based on the device identifier; the peripheral component is used to execute a soft reset procedure in response to the soft reset command. If the operating status information indicates that the power supply status is abnormal when the target peripheral component malfunctions, the drive management unit 30 is used to send a hard reset command to the power supply control unit 10, the hard reset command including at least the device identifier of the target peripheral component, the hard reset command instructing the power supply control unit to initiate the hard reset procedure for the target peripheral component; correspondingly, the power supply control unit 10 is used to execute a hard reset procedure for the peripheral component based on the device identifier carried by the hard reset command in response to the hard reset command.

[0066] For the soft reset process, the drive management unit 30 sends a soft reset command to the target peripheral device based on the device identifier of the target peripheral device. Correspondingly, the target peripheral device invokes a soft reset command based on the soft reset command, thereby clearing the operating state and temporary data of the target peripheral device to restore it to normal operation. For the hard reset process, the drive management unit 30 can control the power supply module to stop supplying power to the target peripheral device through the power supply control unit 10, thus achieving a hard reset. Accordingly, the fault recovery system also includes one or more power switches, any one of which is connected in series between the power supply module and the peripheral device. The power supply control unit 10, in response to the hard reset command, controls the power supply switch of the target peripheral device to disconnect based on the device identifier carried in the hard reset command. After the power supply is stopped for a preset duration, the power supply switch of the target peripheral device is reconnected.

[0067] The preset duration can be set as needed, but in this embodiment, no specific limitation is made to the preset duration. For example, the preset duration can be 200 milliseconds, 500 milliseconds, 550 milliseconds, 600 milliseconds, 1 second, 5 seconds, or 10 seconds, etc.

[0068] In this way, different fault recovery methods are used for different fault types, and different fault recovery strategies are used for different types and severity of peripheral faults. This can clear the error state in a timely manner, ensure the normal operation of the system, avoid unnecessary system restarts, prevent data loss, reduce the impact of faults on the operation of driving equipment, and improve the availability and stability of the system.

[0069] In some embodiments, the process by which the drive management unit 30 determines whether the peripheral device is operating normally based on its operating status information includes: the drive management unit 30 sending control commands to the peripheral device according to a preset communication protocol, and receiving operating status information and data from the peripheral device; and determining whether the peripheral device is operating normally by performing in-depth analysis and comprehensive analysis of the operating status information and data from the peripheral device. For example, the operating status information is compared with the operating status information under a preset normal operating condition; if the difference between the operating status information and the operating status information under the preset normal operating condition is greater than a preset difference value, then the peripheral device is determined to be operating abnormally.

[0070] In some embodiments, the drive management unit 30 also periodically reads the register status information of peripheral components and monitors the changes in the control pin level in real time. Based on the register status and control pin level, it determines the internal working status and operation of the peripheral components so as to detect any potential fault signs in a timely manner, thereby taking effective measures to deal with the fault at the first moment, ensuring the stable operation of the peripheral components and the overall reliability of the system.

[0071] In some embodiments, the fault signal also includes the power supply parameters of the target peripheral component. The drive management unit 30 can also determine the fault type and cause of the target peripheral component by combining the operating status of the target peripheral component and the power supply parameters in the fault signal sent by the power supply fault detection unit 20. Specifically, the drive management unit 30 can detect the operating status information and data of the peripheral component. When the drive management unit 30 determines that the peripheral component has signs of fault based on the operating status information and data of the peripheral component, the drive management unit 30 reads the operating status information of the peripheral component and obtains the power supply parameters of the peripheral component from the power supply fault detection unit 20. Based on the operating status information and power supply parameters of the peripheral component, the drive management unit 30 determines the cause and type of the fault so that the drive management unit 30 can take corresponding fault recovery measures based on the cause and type of the fault.

[0072] For example, when peripheral component A experiences a power supply failure, the driver management unit 30 of peripheral component A will detect the working status information and data generated during operation of peripheral component A. Based on the working status information and data, it will determine that peripheral component A has communication abnormalities or data errors. At this time, the driver management unit 30 will initiate an efficient fault diagnosis process. On the one hand, it will quickly read the register status of peripheral component A and monitor the changes in the control pin level to obtain the working status information of peripheral component A, including the initialization completion status of peripheral component A, the current working mode, whether there is an error flag, and the type and code of the error. On the other hand, it will simultaneously read the power supply parameters of peripheral component A reported by the power supply fault detection unit 20, and determine the cause and type of fault of peripheral component A based on the power supply parameters and working status information.

[0073] For different causes and types of faults, the drive management unit 30 will adopt different fault recovery methods. For example, if a peripheral component fails but is found to be powered normally, a soft reset fault recovery method will be used for that peripheral component. That is, if the working status information indicates that the peripheral component is operating normally, the drive management unit 30 will generate a soft reset command and send the soft reset command to the peripheral component; the peripheral component will then control the peripheral component to perform a soft reset based on the soft reset command.

[0074] If a peripheral component malfunctions, and an abnormal power supply is detected, a hard reset fault recovery method is used. Specifically, the drive management unit 30 generates a hard reset command if the operating status information indicates an abnormal operation of the peripheral component. This hard reset command carries the device identifier of the peripheral component and is sent to the power supply control unit 10. The power supply control unit 10 receives the hard reset command and, based on this command, sends a power-off command to the power supply module of the peripheral component corresponding to the device identifier. After receiving the hard reset command, the power supply control unit 10 cuts off the power supply to the peripheral component by controlling the corresponding relay or MOSFET switch, ensuring a complete power-off of the peripheral component. Power is then restored to the peripheral component after a preset time.

[0075] It should be noted that the driver management unit 30 begins running during system startup. Accordingly, the driver management unit 30 can determine the fault recovery process based on the impact of faults occurring during startup on the startup process. When the fault is a power supply failure in a peripheral component that has a minor impact on the startup of critical system functions, the driver management unit 30 can temporarily record the fault information and wait for the system to start up before conducting detailed troubleshooting and handling. When the fault is a power supply failure in a critical peripheral component, the driver management unit 30 can immediately attempt some preliminary repair operations, such as quickly checking for loose power connection lines or poor contact, and taking appropriate corrective measures in a timely manner. Simultaneously, during system startup, the driver management unit 30 will perform a comprehensive and systematic initialization configuration of the peripheral communication interfaces to ensure that communication connections with peripherals can be established quickly and stably after system startup, enabling accurate data transmission and timely command issuance, thus fully preparing for the normal operation of the system.

[0076] When the peripheral component control system is running, the main program coordinates the work between various units. The following describes the operation process of the main program in the peripheral component control system.

[0077] During the initialization phase, the main program initializes and configures the power supply control unit, power supply fault detection unit, and drive management unit 30 in the system. This initialization configuration enables each unit to operate normally based on its corresponding working parameters. For example, the initialization configuration sets parameters such as output voltage, current limits, and power-on sequence for the power supply control unit 10 to ensure a stable and orderly power supply. Similarly, the initialization configuration sets parameters for the fault detection algorithm of the power supply fault detection unit 20, such as fault threshold and sampling frequency, enabling it to accurately and promptly detect power supply faults.

[0078] During the initialization phase of the driving equipment, the Real-Time Operating System (RTOS) is started so that the system can create driver tasks and fault recovery tasks for each peripheral component in the RTOS environment, and allocate system resources such as memory space and processor time slices to each task in a reasonable manner to ensure that each task can run independently and stably.

[0079] It should be noted that in this embodiment of the application, after performing a soft reset or hard reset on the peripheral component, the peripheral component will have its usage data cleared and will be restored to its factory state. Therefore, it is necessary to re-initialize the peripheral component after the reset. That is, the driving device initializes and configures the target peripheral component after fault recovery according to the configuration information of the target peripheral component.

[0080] After recovering from the faulty peripheral component, the drive management unit 30 can also test the peripheral component to ensure that it can operate normally after recovery. Accordingly, the drive management unit 30 is also used to test the target peripheral component after initialization and obtain test results. These test results reflect whether the target peripheral component has returned to normal operation. If the test results indicate that the target peripheral component has not returned to normal operation, a hard reset command is sent to the power supply control unit. This hard reset command includes at least the device identifier of the target peripheral component and instructs the power supply control unit to initiate the hard reset process for the target peripheral component.

[0081] If the fault recovery strategy involves a soft reset, for target peripheral components that fail to return to normal operation after fault recovery, the drive management unit 30 checks whether a power supply failure has occurred in the target peripheral component. If the cause of the power supply failure is a power supply fault, the step of sending a hard reset command to the power supply control unit is executed. If the target peripheral component does not have a power supply failure, it can continue to be reset using a soft reset. Furthermore, if the target peripheral component fails the test after multiple consecutive soft resets, the step of sending a hard reset command to the power supply control unit is executed again.

[0082] If the fault recovery strategy is to execute a hard reset procedure, and if the test result indicates that the peripheral component has not returned to normal operation, the drive management unit 30 determines the number of consecutive times the hard reset procedure is executed on the target peripheral component during this fault recovery process; when the number of consecutive times reaches a second preset number, a fault report of the peripheral component is generated, which includes at least: the time when the peripheral component experienced the fault, the fault type, the device identifier of the peripheral component, the fault recovery strategy adopted for the peripheral component, and the fault recovery result.

[0083] In this embodiment, the faulty peripheral component is identified by its device identifier. Then, the operating status information of the faulty peripheral component is determined, and a fault recovery strategy is formulated based on this information. The fault recovery strategy is then applied to the peripheral component to restore its functionality. This approach allows for different fault recovery strategies for different faults. Since this application focuses on restoring faults to the faulty peripheral component, it does not affect the operation of other peripheral components. It can promptly clear erroneous states while ensuring the normal operation of the system, avoiding unnecessary system restarts, preventing data loss, reducing the impact of faults on the operation of the driving equipment, and improving the availability and stability of the system.

[0084] Furthermore, throughout the entire fault detection and recovery process, each peripheral component—whether it's the power supply fault detection unit, the drive management unit, or the power supply control unit—operates and processes independently and precisely. The fault detection and recovery process for each peripheral component is completely isolated from other peripheral components, ensuring no interference and forming an efficient and reliable fault decoupling and independent processing mechanism. This complete decoupling and independence prevents the propagation and spread of faults in a single peripheral component within the system. It avoids the collapse or malfunction of the entire peripheral component control system due to a single peripheral component failure, ensuring that other peripheral components can continue to operate normally while a fault in one peripheral component is being addressed. This allows the driving equipment to maintain stable operation of its basic functions even when a single peripheral component fails, thereby improving vehicle safety and user experience.

[0085] After initialization, the driving system enters the main loop phase. During this phase, the main program coordinates the operation and communication between various tasks, monitoring the overall system status in real-time and comprehensively. This monitoring includes checking the working status of various peripherals, power supply, and communication link status. It also promptly handles global system events, such as communication interactions with other ECUs within the driving system and managing system hibernation and wake-up. Throughout the main loop, the RTOS's task scheduling mechanism is fully utilized to ensure each task executes within its predetermined timeframe based on priority and time slice requirements. This guarantees the real-time performance, stability, and reliability of the entire system, providing the software foundation for the stable operation of the peripheral component control system and its corresponding peripheral components.

[0086] The fault recovery process in the main loop phase is described below with reference to specific embodiments. See [link to documentation]. Figure 4 The document illustrates a flowchart of a fault recovery method provided by an exemplary embodiment. As an example and not a limitation, this embodiment is described using a driving device as the execution subject, specifically a driving device equipped with the aforementioned fault recovery system.

[0087] S401, During the operation of the driving equipment, the driving equipment identifies the device identifier of the target peripheral component that has malfunctioned among the multiple peripheral components of the driving equipment.

[0088] The operation of the driving device refers to the process from its startup to its shutdown, including but not limited to driving and parking. In some embodiments, the driving device determines whether a peripheral component has malfunctioned by checking its power supply parameters. Accordingly, if the power supply parameters of any peripheral component of the driving device do not meet a preset parameter threshold, the driving device determines that peripheral component is the target peripheral component that has malfunctioned. Accordingly, the driving device acquires the device identifier of the target peripheral component.

[0089] The power supply parameters represent the relevant parameters actually generated during the operation of peripheral components. For example, these parameters include the voltage and current of the peripheral components. The driving equipment can periodically sample and analyze the power supply parameters of each peripheral component at fixed time intervals through a fault detection unit. This time interval can be set as needed, and in this embodiment, it is not specifically limited. For example, the time interval can be 10 milliseconds, 15 milliseconds, 20 milliseconds, 5 seconds, 10 seconds, 30 seconds, or 1 minute.

[0090] The driving system compares the power supply parameters of peripheral components with preset parameter thresholds to determine whether the peripheral component is malfunctioning. For example, if the power supply voltage in the power supply parameters is lower than the lowest voltage in the corresponding parameter thresholds for the peripheral component, it is determined that the power supply parameters of the peripheral component do not meet the preset parameter thresholds.

[0091] The threshold parameter can be a parameter calibrated based on the normal operation of the peripheral component. Different peripheral components may have the same or different threshold parameters; this embodiment does not impose specific limitations on this.

[0092] When the driving device collects power supply parameters from peripheral components, it simultaneously records the device identifier of the peripheral component that generated those parameters. If any power supply parameter is detected to be inconsistent with a preset threshold, the device identifier corresponding to that parameter is determined. This device identifier is a unique identifier for the device. For example, the device identifier could be the device code of the peripheral component.

[0093] S402, the driving equipment obtains the working status information of the target peripheral component based on the device identifier. The working status information is used to reflect whether the power supply status of the target peripheral component is normal when a fault occurs.

[0094] Based on the device identifier, the driving device identifies the target peripheral component corresponding to the device identifier and then reads the operating status information of the target peripheral component. This operating status information may include parameters such as the register status of the target peripheral component and the control pin level of the peripheral component.

[0095] S403, the driving equipment determines the fault recovery strategy for the target peripheral component based on the operating status information.

[0096] The driving equipment analyzes the operating status information based on a preset fault analysis algorithm and selects different fault recovery strategies based on the analysis results.

[0097] The fault recovery strategy can be configured as needed. In this embodiment, the fault recovery strategy includes soft reset and hard reset. Soft reset and hard reset refer to two methods for restoring the system to normal operation in a device. Soft reset refers to a reset method that restores peripheral components to normal operation through software instructions. Hard reset refers to a reset method that restores peripheral components to normal operation through physical means (such as pressing a reset button) or power-off restart.

[0098] S404, the driving equipment controls the target peripheral components to perform fault recovery according to the fault recovery strategy.

[0099] In this embodiment, the driving device can determine whether the power supply status of peripheral components is normal through operating status information. If the power supply status of the peripheral component is normal, a soft reset is initiated for the peripheral component; if the power supply status of the peripheral component is abnormal, a hard reset is initiated for the peripheral component. That is, if the operating status information indicates that the power supply status is normal when the target peripheral component malfunctions, the driving device sends a soft reset command to the target peripheral component, which instructs the peripheral component to initiate the soft reset process; if the operating status information indicates that the power supply status is abnormal when the peripheral component malfunctions, the driving device sends a hard reset command to the power supply control unit. The hard reset command includes at least the device identifier of the target peripheral component, and the hard reset command instructs the power supply control unit to initiate the hard reset process for the target peripheral component.

[0100] Among them, controlling the peripheral component to perform a soft reset means controlling the internal state of the peripheral component's chip to restore it to the factory state and clearing the chip's current operating state and temporary data.

[0101] Controlling the peripheral device to perform a hard reset means stopping the power supply to the peripheral device, that is, controlling the power supply control unit to cut off the power supply to the peripheral device, and then re-energizing the peripheral device after a period of time.

[0102] In this embodiment, the faulty peripheral component is identified by its device identifier. Then, the operating status information of the faulty peripheral component is determined, and a fault recovery strategy is formulated based on this information. The fault recovery strategy is then applied to the peripheral component to restore its functionality. This approach allows for different fault recovery strategies for different faults. Since this application focuses on restoring faults to the faulty peripheral component, it does not affect the operation of other peripheral components. It can promptly clear erroneous states while ensuring the normal operation of the system, avoiding unnecessary system restarts, preventing data loss, reducing the impact of faults on the operation of the driving equipment, and improving the availability and stability of the system.

[0103] It should be noted that after the driving equipment performs fault recovery on peripheral components based on the above fault recovery procedure, it cannot guarantee that the peripheral components will return to normal operation. Therefore, it is necessary to test the peripheral components after fault recovery to ensure that they can resume normal operation. See also Figure 5 The document illustrates a flowchart of a fault recovery method provided by an exemplary embodiment. As an example and not a limitation, this embodiment is described using a driving device as the executing entity, which is a driving device equipped with the aforementioned peripheral component control system.

[0104] S501, During the operation of the driving equipment, the driving equipment determines the device identifier of the target peripheral component that has failed among the multiple peripheral components of the driving equipment.

[0105] This step is based on the same principle as step S401, and will not be repeated here.

[0106] S502, the driving equipment obtains the working status information of the target peripheral component based on the device identifier. The working status information is used to reflect whether the power supply status of the target peripheral component is normal when a fault occurs.

[0107] This step is based on the same principle as step S402, and will not be repeated here.

[0108] S503, the driving equipment determines the fault recovery strategy for the target peripheral component based on the operating status information.

[0109] This step is based on the same principle as step S403, and will not be repeated here.

[0110] S504, the driving equipment controls the target peripheral components to perform fault recovery according to the fault recovery strategy.

[0111] This step is based on the same principle as step S404, and will not be repeated here.

[0112] S505, the driving equipment initializes the target peripheral component after fault recovery based on the configuration information of the target peripheral component.

[0113] In the embodiments of this application, after performing a soft reset or hard reset on a peripheral component, the peripheral component will have its usage data cleared and will be restored to its factory state. Therefore, it is necessary to re-initialize the peripheral component after the reset, that is, to reset the parameters of the peripheral component.

[0114] After recovering from a fault in a peripheral component, the driving system re-initializes the component based on its configuration information. This includes resetting key configurations such as the component's operating parameters, communication baud rate, interrupt vector, and initial register values. Following initialization, a test command can be used to test the peripheral component, ensuring it can restart and resume normal operation. It's important to note that the initialization process follows a preset order and steps to avoid errors in the initialization sequence or improper parameter settings that could cause peripheral components to malfunction.

[0115] S506, the driving equipment tests the target peripheral component after initialization and obtains the test result, which reflects whether the target peripheral component has returned to normal working state.

[0116] In some embodiments, the driving device can test the peripheral component using a preset test command. Accordingly, this step can be implemented using the following steps S5061-S5063, including: S5061, The driving equipment acquires a preset test command.

[0117] This test command is used to test whether the peripheral component has returned to normal operation. This test command is a pre-written test command used to test the operating status of the peripheral component. Different peripheral components may use the same or different test commands. In this step, the driving device can retrieve the stored test command for the peripheral component based on its device identifier.

[0118] S5062, the driving equipment uses this test command to test the target peripheral components after initialization.

[0119] The driving equipment executes the test command based on the target peripheral component after fault recovery. If it receives feedback data from the test command and the feedback data meets the test result requirements, it determines that the target peripheral component has passed the test; otherwise, it determines that the target peripheral component has failed the test. For example, the test command can be a communication command. After the target peripheral component executes the test command, if it receives feedback based on the communication command, it determines that the target peripheral component has passed the test.

[0120] See Figure 6 After completing fault recovery and initialization, the target peripheral component is tested. If the target peripheral component passes the test command, the reset process ends. If the peripheral component fails the test command, step S507 is executed to start the hard reset operation.

[0121] It should be noted that when the fault recovery strategy is to execute a soft reset procedure, the driving equipment can directly execute step S507 to initiate a hard reset operation when the target peripheral component fails the test; or, for the target peripheral component that has not returned to normal working state after fault recovery, the driving equipment detects whether the target peripheral component has a power supply failure. If the reason for the power supply failure of the target peripheral component is a power supply failure, then step S507 is executed to initiate a hard reset operation.

[0122] The driving device can also determine the number of consecutive soft reset procedures performed on the target peripheral component during the current fault recovery process when the target peripheral component fails the test. Step S507 is only executed when this number reaches a second preset number. Before reaching the second preset number, the soft reset and test procedures can be repeated. The second preset number can be set as needed; in this embodiment, it is not specifically limited. For example, the second preset number can be 5, 10, or 15 times.

[0123] In this implementation, after the peripheral component is initialized, it is retested to ensure that the peripheral component can resume normal operation after fault recovery, and to prevent the driving equipment from malfunctioning due to the peripheral component still not operating normally after fault recovery.

[0124] S507, if the test result indicates that the target peripheral component has not returned to normal working state, the driving device sends a hard reset command to the power supply control unit. The hard reset command includes at least the device identifier of the target peripheral component, and the hard reset command instructs the power supply control unit to start the hard reset process for the target peripheral component.

[0125] The process of hard resetting the target peripheral device is the same as the process of hard resetting the target peripheral device in step S404, and will not be described again here.

[0126] S508, the driving equipment initializes the target peripheral component after fault recovery based on the configuration information of the target peripheral component.

[0127] This step is based on the same principle as step S505, and will not be repeated here.

[0128] S509, the driving equipment tests the target peripheral component after initialization and obtains the test result, which reflects whether the target peripheral component has returned to normal working state.

[0129] This step is based on the same principle as step S506, and will not be repeated here.

[0130] S510, if the test result indicates that the target peripheral component has not returned to normal operation, the driving equipment determines the number of consecutive times the hard reset procedure is executed on the target peripheral component during this fault recovery process.

[0131] If the test result indicates that the target peripheral component has not returned to normal operation, the driving device continues to execute step S507, repeats the hard reset procedure, and records the number of consecutive times the target peripheral component executes the hard reset procedure.

[0132] S511, when the number of consecutive occurrences reaches a preset number, a fault report for the peripheral component is generated. The fault report includes at least: the time when the peripheral component malfunctioned, the type of the malfunction, the device identifier of the peripheral component, the fault recovery strategy adopted for the peripheral component, and the fault recovery result.

[0133] When a peripheral component fails a test, the driving device records the number of times it fails the test. When the number of consecutive failed tests reaches a third preset number, the driving device generates a fault report for that peripheral component. When the peripheral component passes the test before reaching the third preset number, the driving device resets the current count to zero. The third preset number can be the same as or different from the second preset number, and it can be set as needed. In this embodiment, the third preset number is not specifically limited.

[0134] This fault report records relevant information about the fault, such as the time of occurrence, fault type, device identifier of the affected peripheral component, fault recovery measures taken, and fault recovery results. After generating the fault report, the driving equipment can upload it to its fault diagnosis system. This system then provides feedback to the user, enabling timely repair or replacement of the peripheral components to ensure the reliability and stability of the driving equipment.

[0135] Additionally, it should be noted that during the aforementioned fault recovery process, when the fault recovery is successful, i.e., when the peripheral components are running normally through the test command, the driving equipment can also generate a fault report so that users can review the operation of the driving equipment later.

[0136] In this embodiment, the faulty peripheral component is identified by its device identifier. Then, the operating status information of the faulty peripheral component is determined, and a fault recovery strategy is formulated based on this information. The fault recovery strategy is then applied to the peripheral component to restore its functionality. This approach allows for different fault recovery strategies for different faults. Since this application focuses on restoring faults to the faulty peripheral component, it does not affect the operation of other peripheral components. It can promptly clear erroneous states while ensuring the normal operation of the system, avoiding unnecessary system restarts, preventing data loss, reducing the impact of faults on the operation of the driving equipment, and improving the availability and stability of the system.

[0137] Furthermore, after initialization, the peripheral components are retested to ensure they can resume normal operation after fault recovery, preventing operational malfunctions caused by peripheral components failing to function properly after fault recovery. If the test fails repeatedly after repeated resets, the driving equipment generates a fault report, which can be uploaded to the driving equipment's fault diagnosis system. This system then relays the fault report to the user for timely repair or replacement of the peripheral components, ensuring the reliability and stability of the driving equipment.

[0138] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0139] Figure 7 This is a schematic diagram of a driving device provided in an exemplary embodiment of this application. Figure 7 As shown, the driving device 7 of this embodiment includes: a processor 70, a memory 71, and a computer program 72 stored in the memory 71 and executable on the processor 70, such as a fault recovery program. When the processor 70 executes the computer program 72, it implements the steps in the various fault recovery method embodiments described above, for example... Figure 4 The steps S401 to S404 are shown. Alternatively, when the processor 70 executes the computer program 72, it implements the functions of each unit in the above-described device embodiments, for example... Figure 1 The functions of units 101 to 103 are shown.

[0140] For example, the computer program 72 may be divided into one or more units, which are stored in the memory 71 and executed by the processor 70 to complete the present application. The one or more units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program 72 in the driving device 7.

[0141] The driving device 7 can be any driving device controller with control functions. The driving device 7 may include, but is not limited to, a processor 70 and a memory 71. Those skilled in the art will understand that... Figure 7 This is merely an example of driving device 7 and does not constitute a limitation on driving device 7. It may include more or fewer components than shown, or combine certain components, or different components. For example, driving device 7 may also include input / output devices, network access devices, buses, etc.

[0142] The processor 70 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0143] The memory 71 can be an internal storage unit of the driving device 7, such as a hard drive or memory of the driving device 7. The memory 71 can also be an external storage device of the driving device 7, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the driving device 7. Furthermore, the memory 71 can include both internal and external storage units of the driving device 7. The memory 71 is used to store the computer program and other programs and data required by the terminal device. The memory 71 can also be used to temporarily store data that has been output or will be output.

[0144] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0145] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0146] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0147] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0148] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0149] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0150] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0151] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the above method embodiments.

[0152] This application also provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the various method embodiments above.

[0153] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method of failure recovery, characterized by, The method comprises: In the process of driving the device, determining the device identifier of a target peripheral component that fails in a plurality of peripheral components of the driving device; According to the device identifier, obtaining working state information of the target peripheral component, the working state information reflecting whether the power supply state of the target peripheral component is normal when the target peripheral component fails; According to the working state information, determining a failure recovery strategy of the target peripheral component; According to the failure recovery strategy, controlling the target peripheral component to perform failure recovery.

2. The method of claim 1, wherein, The failure recovery strategy comprises executing a soft reset process and a hard reset process; According to the failure recovery strategy, controlling the target peripheral component to perform failure recovery, comprising: If the working state information indicates that the power supply state is normal when the target peripheral component fails, a soft reset instruction is sent to the target peripheral component, the soft reset instruction instructing the peripheral component to start the soft reset process; If the working state information indicates that the power supply state is abnormal when the peripheral component fails, a hard reset instruction is sent to a power supply control unit, the hard reset instruction comprising at least the device identifier of the target peripheral component, the hard reset instruction instructing the power supply control unit to start the hard reset process on the target peripheral component.

3. The method of claim 1 or 2, wherein, After controlling the target peripheral component to perform failure recovery according to the failure recovery strategy, the method further comprises: According to the configuration information of the target peripheral component, initializing and configuring the target peripheral component after failure recovery.

4. The method of claim 3, wherein, After initializing and configuring the target peripheral component after failure recovery according to the configuration information of the target peripheral component, the method further comprises: Testing the target peripheral component after initialization, obtaining a test result, the test result reflecting whether the target peripheral component has recovered to a normal working state; If the test result indicates that the target peripheral component has not recovered to a normal working state, a hard reset instruction is sent to a power supply control unit, the hard reset instruction comprising at least the device identifier of the target peripheral component, the hard reset instruction instructing the power supply control unit to start the hard reset process on the target peripheral component.

5. The method of claim 4, wherein, If the failure recovery strategy is to execute a hard reset process, and if the test result indicates that the target peripheral component has not recovered to a normal working state, the method further comprises: Determining the number of consecutive times of executing the hard reset process on the target peripheral component in the current failure recovery process; When the number of consecutive times reaches a preset number, generating a failure report of the peripheral component, the failure report comprising at least: the time when the peripheral component fails, the failure type of the failure, the device identifier of the peripheral component, the failure recovery strategy adopted for the peripheral component, and the failure recovery result.

6. The method of claim 1, wherein, The method further comprises: Obtaining a failure signal from a power supply control unit, the failure signal comprising at least one device identifier, the failure signal indicating that the target peripheral component corresponding to the device identifier fails.

7. A fault recovery system, characterized by, The fault recovery system comprises a power supply control unit, a power supply fault detection unit and one or more drive management units, any of the drive management units being used to connect a peripheral component of a driving device; The power supply control unit is used to control the power supply module to supply power to the peripheral component with a target working parameter; The power supply fault detection unit is used to acquire a power supply parameter of each peripheral component, and send a fault signal to the drive management unit in the case that the power supply parameter of any peripheral component indicates that the peripheral component has a fault, the fault signal comprising at least one device identifier, the fault signal being used to indicate that the target peripheral component corresponding to the device identifier has a fault; The drive management unit is used to execute the method according to any one of claims 1-6.

8. The failover system of claim 7, wherein, If the working state information indicates that the power supply state is normal when the target peripheral component has a fault, the drive management unit is used to send a soft reset instruction to the target peripheral component having a fault according to the device identifier; The target peripheral component is used to execute a soft reset process in response to the soft reset instruction.

9. The failover system of claim 7, wherein, If the working state information indicates that the power supply is abnormal when the peripheral component has a fault, the power supply control unit is used to acquire a hard reset instruction from the drive management unit, the hard reset instruction comprising at least the device identifier of the target peripheral component having a fault; In response to the hard reset instruction, the power supply module is controlled to stop supplying power to the target peripheral component and then to continue supplying power to the target peripheral component after a preset time length based on the device identifier carried by the hard reset instruction.

10. The failover system of claim 9, wherein, The fault recovery system further comprises one or more power supply switches, any of the power supply switches being connected in series between the power supply module and the peripheral component; The power supply control unit is used to control the power supply switch of the target peripheral component to be turned off based on the device identifier carried by the hard reset instruction in response to the hard reset instruction; When the time length of stopping power supply reaches the preset time length, the power supply switch of the target peripheral component is re-controlled to be turned on.

11. A driving apparatus characterized by comprising: A computer program product comprises a memory, a processor and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the fault recovery method according to any one of claims 1-6.

12. A computer-readable storage medium, characterized in that, The computer program product comprises a memory, a processor and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the fault recovery method according to any one of claims 1-6.

13. A computer program product, characterised in that, The computer program product comprises a memory, a processor and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the fault recovery method according to any one of claims 1-6.

Citation Information

Patent Citations

  • Abnormity handling method and device for embedded multimedia card (eMMC) chip

    CN104391755A

  • Fault recovery method and device, electronic equipment, storage medium and vehicle

    CN117148824A

  • Communication method based on sensor system and electronic equipment

    CN118354228A

  • Fault diagnosis method, device and equipment, vehicle and medium

    CN118938872A

  • A self-evaluation and booting system for a vehicle and a method thereof

    WO2025203042A1