Distributed integrated fault processing system and method, electronic equipment and storage medium
Through a distributed integrated fault processing system, the combination of calibration module, data input module, fault determination module and fault processing module is solved, and the problems of poor scalability and high maintenance costs in automotive software fault processing are achieved. More efficient fault identification and processing are achieved, reducing the system's dependence on central nodes.
Patent Information
- Application Number
- CN202411053700.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-02
- Publication Date
- 2024-11-19
AI Technical Summary
Traditional centralized architectures have problems in automotive software troubleshooting, poor scalability, high maintenance costs, and service interruption when the central node fails.
Adopting a distributed integrated fault processing system, the combination of calibration module, data input module, fault determination module and fault processing module can realize fault identification and processing, reducing the system's dependence on the central node, improving scalability and maintenance Convenience.
It improves the scalability and flexibility of the fault handling system, reduces the number of connections and changes of the model, enhances the flexibility and accuracy of fault handling, and reduces maintenance costs.
Smart Images

Figure CN118981198A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of distributed integrated architecture, and in particular to a distributed integrated fault handling system, method, electronic device, and computer-readable storage medium. Background Art
[0002] With the development of technology, distributed integration has become more and more mainstream for automotive software, so the architecture of fault software also needs to be adjusted accordingly. The previous fault software architecture required wire-to-wire connections between interfaces to transmit signals, and because the entire software was not divided into multiple independent software units (Software Component SWC), the entire Simulink model was updated together when the software was updated, and when the software failed, the entire Simulink model was paralyzed.
[0003] The existing traditional integrated architecture or centralized architecture relies on a central node or server to process all data and service requests. If this central node fails or shuts down, the entire system may be affected, resulting in service interruption or unavailability. It also has poor scalability and high maintenance costs. Summary of the invention
[0004] To solve the above technical problems, embodiments of the present application provide a distributed integrated fault handling system and method, an electronic device, and a computer-readable storage medium.
[0005] According to one aspect of an embodiment of the present application, a distributed integrated fault handling system is provided, characterized in that it includes: a calibration module, which is used to configure multiple different fault calibration parameters and data types corresponding to the calibration parameters; a data input module, which is used to receive vehicle operating parameters sent from a vehicle communication bus; a fault judgment module, which is used to receive the vehicle operating parameters sent by the data input module, and compare the vehicle operating parameters with the fault calibration parameters in the calibration module to determine the fault type and fault level based on the comparison result; a fault handling module, which is used to determine the corresponding fault handling strategy based on the fault type and the fault level.
[0006] According to one aspect of an embodiment of the present application, the calibration module is further used to: obtain actual fault parameters of the vehicle during operation, and correct the fault calibration parameters based on the actual fault parameters.
[0007] According to one aspect of an embodiment of the present application, after receiving the vehicle operating parameters sent by the data input module, the fault judgment module is also used to: judge the signal type corresponding to the vehicle operating parameters to obtain a judgment result; send the vehicle operating parameters to a corresponding service unit based on the judgment result, and compare the vehicle operating parameters with the fault calibration parameters in the calibration module based on the service unit to determine the fault type and fault level based on the comparison result.
[0008] According to one aspect of an embodiment of the present application, the fault judgment module is also used to: if a signal shielding request is received, parse the target signal corresponding to the signal shielding request; search for a fault calibration parameter matching the target signal from the calibration module, and shield the fault calibration parameter.
[0009] According to one aspect of an embodiment of the present application, the fault judgment module is also used to: if a signal delay detection request is received, then parse the target duration and target vehicle operating parameters corresponding to the signal delay detection request; if it is detected that the duration of the target vehicle operating parameters meets the target duration, then compare the operating parameters of the target vehicle with the fault calibration parameters in the calibration module to determine the fault type and fault level based on the comparison result.
[0010] According to one aspect of an embodiment of the present application, the system further includes: a fault output module, which is used to output the fault type and fault level to the corresponding functional layer, and send the fault handling measures and the identity corresponding to the fault to the vehicle communication bus.
[0011] According to one aspect of an embodiment of the present application, the system also includes: a storage module for pre-storing the association between the fault type, fault level and fault handling strategy; a configuration module for configuring at least one or more of the data type, signal name, size value, dimension and reference method corresponding to each module in the fault handling system.
[0012] According to one aspect of an embodiment of the present application, a fault handling method is provided, the method comprising: receiving operating parameters of a vehicle sent from a vehicle communication bus; comparing the operating parameters of the vehicle with fault calibration parameters to determine a fault type and a fault level based on the comparison result; and determining a corresponding fault handling strategy based on the fault type and the fault level.
[0013] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the road condition refresh method as described above.
[0014] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the distributed integrated fault handling system as described above.
[0015] According to one aspect of an embodiment of the present application, a computer program product is also provided, including a computer program, which implements the steps in the distributed integrated fault handling method as described above when executed by a processor.
[0016] In the technical solution provided in the embodiments of the present application, by splitting the vehicle's software architecture into a distributed calibration module, a data input module, a fault judgment module and a fault processing module, the fault processing system can be decoupled through a distributed system, thereby improving the scalability of the fault processing system and making the distributed software architecture more convenient to maintain. Fault identification and processing can be achieved through the joint use of each module in the distributed software architecture, and the fault processing architecture can be optimized to reduce the wiring and modification of the model, thereby improving the flexibility of the fault processing system.
[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0019] Figure 1 is a structural schematic diagram of a distributed integrated fault handling system shown in an exemplary embodiment of the present application;
[0020] Figure 2 is a flowchart of a fault handling method shown in an exemplary embodiment of the present application;
[0021] Figure 3 is a flowchart of a fault handling method shown in another exemplary embodiment of the present application;
[0022] Figure 4 is a flowchart of a fault handling method shown in another exemplary embodiment of the present application;
[0023] Figure 5is a structural schematic diagram of a distributed integrated fault handling system shown in another exemplary embodiment of the present application;
[0024] Figure 6 is a structural schematic diagram of a distributed integrated fault handling system shown in another exemplary embodiment of the present application;
[0025] Figure 7 is a flowchart of a fault handling method shown in another exemplary embodiment of the present application;
[0026] Figure 8 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION
[0027] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.
[0028] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0029] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0030] The term "multiple" as used in this application refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.
[0031] First of all, it should be noted that a distributed integration system is a complex system architecture, which involves multiple independent computer nodes connected and communicating with each other through the network to jointly complete tasks or provide services. The following is a detailed analysis of the distributed integration system: Definition: A distributed integration system refers to a system that distributes multiple independent computer nodes, hardware or software components in different locations of the network, and jointly implements a specific function or service through message passing, network communication and coordination mechanisms. Its characteristics include: Scalability: A distributed integration system can easily expand the processing capacity of the system by adding more nodes to meet the growing demand; Reliability: Through redundant design and fault-tolerant mechanism, the distributed integration system can maintain the continuity of the overall service when some nodes fail; Geographic distribution: The nodes in the system can be located in different geographical locations, connected to each other through the network, and realize remote collaboration; Heterogeneity: A distributed integration system can integrate different types of hardware and software components and support diverse technologies and platforms. Distributed integration systems usually adopt a service-oriented or microservice architecture to split the system into multiple independent services or components, each of which is responsible for a specific business function. These services or components communicate and collaborate through the network to complete tasks together.
[0032] Distributed integrated systems are widely used in various fields, including cloud computing and big data processing, search engines, social networks and instant messaging, e-commerce and financial transactions, games and online entertainment, the Internet of Things and smart homes, financial technology and blockchain, etc. These application scenarios usually require processing large-scale data sets and complex computing tasks, and distributed integrated systems can provide efficient, reliable and scalable solutions.
[0033] With the development of technology, distributed integration has become more and more mainstream for automotive software, so the architecture of fault software also needs to be adjusted accordingly. The previous fault software architecture required wire-to-wire connections between interfaces to transmit signals, and because the entire software was not divided into multiple independent software units (Software Component SWC), the entire Simulink model was updated together when the software was updated, and when the software failed, the entire Simulink model was paralyzed.
[0034] The existing traditional integrated architecture or centralized architecture relies on a central node or server to process all data and service requests. If this central node fails or shuts down, the entire system may be affected, resulting in service interruption or unavailability. It also has poor scalability and high maintenance costs.
[0035] The above-mentioned problems are generally applicable in common usage scenarios. To solve these problems, the embodiments of the present application respectively propose a distributed integrated fault handling system, a fault handling method, an electronic device, a computer-readable storage medium, and a computer program product, which will be described in detail below.
[0036] Figure 1 It is an optional architecture diagram of a distributed integrated fault handling system shown in an exemplary embodiment of the present application. In order to support a distributed integrated fault handling application, the architecture includes a calibration module 110, a data input module 120, a fault judgment module 130 and a fault handling module 140, which are described below respectively.
[0037] A calibration module 110, which is used to configure a plurality of different fault calibration parameters and data types corresponding to the calibration parameters;
[0038] like Figure 1 The calibration module 110 shown is used to configure a plurality of different fault calibration parameters and data types corresponding to the fault calibration parameters, that is, it can be used to store calibration parameters related to time delay. These parameters may be used to adjust the time response of the system to ensure that the system triggers a specific event or fault report at the correct time point, and to store calibration parameters related to signal enable. These parameters are used to control the activation conditions of the signal to ensure that the system responds only when specific conditions are met. In addition, the calibration module 110 defines the output port signals of all SWC models. This table is a central repository for signal definitions, which helps to ensure the consistency and traceability of all output signals.
[0039] The data input module 120 is used to receive vehicle operation parameters sent from the vehicle communication bus;
[0040] like Figure 1The data input module 120 shown is used to receive the fault level signal from the CAN bus and the power-on status signal of the vehicle, determine when to start monitoring the fault level signal according to the power-on status, analyze the received fault level signal, determine whether there is a fault that needs to be handled, and after confirming the fault, trigger the corresponding fault handling process, which may include recording the fault, issuing a warning, or activating a safety policy. Among them, the FDIN SWC (Software Component) may be included, which is a component specifically used to receive and process fault signals. The main responsibility of this SWC is to monitor and evaluate fault signals from different sources (such as other controllers on the CAN bus) and trigger the fault handling mechanism under appropriate conditions. The fault judgment module 130 is specifically used for the vehicle operating parameters sent by the data input module 120, and compares the vehicle operating parameters with the fault calibration parameters in the calibration module 110 to determine the fault type and fault level based on the comparison results;
[0041] like Figure 1 As shown, the fault determination module 130 receives signals from the input part and makes fault determinations based on the types and contents of these signals. Each SWC is responsible for processing a specific type of signal and decides whether to regard a certain signal as a fault based on preset rules and conditions. Exemplarily, the arbitration part first receives signals from the input part, which may include the fault level of the generator, the high-voltage state of the whole vehicle, etc. For the received signal, such as the fault level of the generator, the arbitration part will determine its level (such as level 1, level 2, level 3 or level 4). In addition, in addition to the fault level, the arbitration part will also check whether other prerequisites are met, such as whether the whole vehicle is in a high-voltage state.
[0042] Exemplarily, the fault determination module is the core component in the vehicle fault diagnosis system. It is responsible for receiving the vehicle operating parameters sent by the data input module and comparing these parameters with the fault calibration parameters preset in the calibration module in detail. Based on this comparison result, the fault determination module can accurately determine whether the vehicle has a fault, as well as the specific type and level of the fault. The fault determination module first receives the vehicle operating parameters from the data input module, which may include key indicators such as engine temperature, oil pressure, vehicle speed, battery voltage, etc. Then, the module compares these received parameters with the fault calibration parameters preset in the calibration module one by one. The calibration parameters usually define the normal range or threshold of each operating parameter. During the comparison process, if a vehicle operating parameter exceeds its corresponding normal range or threshold, the fault determination module will detect this abnormality and preliminarily determine that the vehicle has a fault. Once a fault is detected, the module will further determine the specific type and level of the fault according to the preset rules and algorithms. Fault types may include electrical faults, mechanical faults, sensor faults, etc., and the fault levels may be divided into different levels such as minor, moderate and severe. Finally, the fault judgment module outputs information such as the fault type, level and related vehicle operating parameters to other modules of the system, such as the fault handling module or the user interface module, for subsequent fault processing or display to the driver.
[0043] The fault handling module 140 is used to determine a corresponding fault handling strategy based on the fault type and fault level.
[0044] Specifically, based on the parsed fault information and vehicle strategy, the execution module determines the fault level. For example, in the case of a vehicle collision, the fault level may be set to level 15. Each fault is assigned a unique fault code to facilitate fault diagnosis and tracking. After determining the fault type and level, the execution module generates the corresponding fault code. Based on the rules defined in the vehicle strategy, the execution module determines the treatment measures to be taken. For example, in the case of a vehicle collision, the vehicle may be operated to lower high voltage to ensure safety. The execution module sends the determined fault level, fault code and treatment measures to other systems or components through the CAN bus. This information is critical to other parts of the vehicle (such as the dashboard, fault diagnosis system, etc.) because they need to display fault information, record fault logs or perform further fault processing based on this information.
[0045] Exemplarily, the fault handling module first receives fault information from the fault determination module, including the fault type, fault level, and related vehicle operating parameters. Then, the module performs a detailed analysis of the received fault information to determine the specific cause and scope of the fault. This step may involve querying the vehicle's historical data, identifying the fault mode, etc. Based on the fault type and fault level, the fault handling module determines the corresponding fault handling measures according to preset rules and strategies. These measures may include sending fault warnings to the driver, adjusting the vehicle's operating status, starting the backup system, shutting down the affected components, etc. Once the fault handling strategies are determined, the module will immediately execute these strategies to ensure the safety and normal operation of the vehicle. This may involve interaction with other vehicle systems, such as the engine control system, the braking system, etc. After executing the fault handling strategy, the fault handling module will continue to monitor the vehicle's operating status to evaluate the effect of the fault handling. If the fault is not resolved or a new fault occurs, the module will re-determine and handle the fault. Finally, the fault handling module will record the entire fault handling process, including fault information, handling strategies, execution results, etc., for subsequent analysis and optimization.
[0046] In this embodiment, by splitting the vehicle's software architecture into a distributed calibration module, a data input module, a fault judgment module and a fault processing module, the fault processing system can be decoupled through a distributed system, thereby improving the scalability of the fault processing system and making the distributed software architecture more convenient to maintain. Fault identification and processing can be achieved through the joint use of various modules in the distributed software architecture, and the fault processing architecture is optimized to reduce the wiring and modification of the model, thereby improving the flexibility of the fault processing system.
[0047] Further, based on the above embodiment, in one of the exemplary embodiments provided in the present application, the calibration module 110 is further used for:
[0048] The actual fault parameters of the vehicle during operation are obtained, and the fault calibration parameters are corrected based on the actual fault parameters.
[0049] Specifically, during the actual operation of the vehicle or the summary of the vehicle test process, the actual fault parameters of the vehicle are obtained, and the fault calibration parameters in the calibration module 110 are corrected based on the actual fault parameters, so as to improve the accuracy of the fault calibration parameters in the calibration module 110, and then determine that the system uses more accurate and reliable parameters in future fault judgments.
[0050] Exemplarily, when a vehicle fails, the system will record the actual operating parameters at the time of the failure, including but not limited to engine speed, oil temperature, vehicle speed, battery status, etc. These actual fault parameters may be obtained in real time from the vehicle communication bus through the data input module, or may be extracted from the vehicle storage system after the failure occurs. The actual fault parameters obtained are analyzed in depth to determine the specific conditions and patterns of the failure, which may involve statistical analysis of the parameters, trend prediction, or comparison with historical fault data. Based on the analysis results of the actual fault parameters, the existing fault calibration parameters are corrected, and the correction may include adjusting the normal range of the parameters, changing the threshold, or adding new fault judgment conditions. After correcting the fault calibration parameters, verification is required to ensure that the new parameter settings can more accurately determine the fault, which may involve testing on actual vehicles or using simulation data to verify the validity of the new parameters. Once the verification is passed, the corrected fault calibration parameters are updated to the calibration module, which will ensure that the system uses more accurate and reliable parameters in future fault judgments. Moreover, the whole process is a continuous optimization cycle. With the continuous accumulation and analysis of vehicle operation data, the fault calibration parameters will be continuously corrected and improved.
[0051] In this way, the vehicle fault diagnosis system can continuously adapt to the actual operating conditions of the vehicle and improve the accuracy and efficiency of fault determination, which will help reduce misjudgments and missed judgments and improve the overall performance and reliability of the vehicle.
[0052] Further, based on the above embodiments, please refer to Figure 2 In one of the exemplary embodiments provided in the present application, after receiving the vehicle operating parameters sent by the data input module, the fault determination module 130 is further configured to execute the following steps S210 and S220, which are described in detail as follows:
[0053] Step S210, determining the signal type corresponding to the vehicle operating parameter and obtaining a determination result;
[0054] Step S220, sending the vehicle operating parameters to the corresponding service unit based on the judgment result, and comparing the vehicle operating parameters with the fault calibration parameters in the calibration module based on the service unit to determine the fault type and fault level based on the comparison result.
[0055] Specifically, determining the signal type corresponding to the vehicle operating parameters involves classifying the operating parameters provided by the vehicle sensors or other data sources. For example, parameters such as temperature, speed, and pressure are identified as different types of signals. Based on the classification in the previous step, the system determines which signal type each parameter belongs to, such as analog signals, digital signals, etc. Once the signal type is determined, the system sends the parameters to a service unit that specializes in processing that type of signal. This helps ensure that the data is processed and analyzed correctly. The service unit compares the received vehicle operating parameters with the preset fault calibration parameters, where the fault calibration parameters are established based on historical data under normal and abnormal operating conditions. Through comparison, the system can identify any parameters that deviate from the normal range, thereby determining the type of fault (such as sensor failure, mechanical failure, etc.) and level (such as minor, severe, etc.).
[0056] In this embodiment, through an automated vehicle fault diagnosis process, it utilizes signal classification, data comparison, and fault calibration to identify and evaluate vehicle faults, which helps to improve the efficiency and accuracy of vehicle maintenance and reduce downtime caused by faults.
[0057] Further, based on the above embodiments, please refer to Figure 3 In one of the exemplary embodiments provided in the present application, the fault determination module 130 is further configured to execute the following steps S310 and S320, which are described in detail as follows:
[0058] Step S310, if a signal shielding request is received, parsing the target signal corresponding to the signal shielding request;
[0059] Step S320, searching the calibration module for fault calibration parameters that match the target signal, and shielding the fault calibration parameters.
[0060] Specifically, if a signal shielding request is received, where the signal shielding request may be for a fault in the fault calibration parameters, the received signal shielding request can be parsed to determine the target signal corresponding to the signal shielding request based on the parsing result, and then the fault calibration parameters matching the target signal can be searched from the calibration module 110, and the fault calibration parameters can be shielded to perform further fault comparison steps.
[0061] For example, if the requirement is not to judge a certain fault, it can be shielded in the calibration module, and the judged fault flag bit is output at the end. For example, if the signal is a power CAN fault flag bit output, once a matching fault calibration parameter is found, the system will perform a shielding operation. This may mean marking these parameters as invalid, deleting them, or preventing them from being used in subsequent diagnosis or processing.
[0062] In this embodiment, by adding fault diagnosis and signal processing links, it is intended to deal with certain signal problems or abnormal conditions by shielding specific fault calibration parameters. This mechanism can improve system stability, reduce false alarms or optimize performance.
[0063] Further, based on the above embodiments, please refer to Figure 4 In one of the exemplary embodiments provided in the present application, the fault determination module 130 is further used to execute step S410 and step S420, which are described in detail as follows:
[0064] Step S410, if a signal delay detection request is received, then analyzing the target duration and target vehicle operating parameters corresponding to the signal delay detection request;
[0065] Step S420, if it is detected that the duration of the target vehicle operating parameters meets the target duration, the target vehicle operating parameters are compared with the fault calibration parameters in the calibration module to determine the fault type and fault level based on the comparison result.
[0066] Specifically, the system first receives a signal delay detection request, which may be issued by the user, other system components, or an automatic monitoring program to detect the delay of a specific signal. The system parses this request to determine the target duration and the operating parameters of the target vehicle that need to be detected. The target duration may be a time period used to determine whether the signal has been delayed within this time period. The operating parameters of the target vehicle may be the vehicle's speed, acceleration, temperature, etc., which will be used for subsequent fault diagnosis. The system detects whether the operating parameters of the target vehicle continue to meet the target duration. This means that the system monitors these parameters and determines whether they maintain a certain state or value within a specified time period. If the operating parameters of the target vehicle continue to meet the target duration, the system compares these operating parameters with the fault calibration parameters in the calibration module. The fault calibration parameters may be a set of predefined parameter values or ranges used to represent different fault types and levels. By comparing the operating parameters and the fault calibration parameters, the system can determine whether a fault exists, as well as the type and level of the fault. This helps with subsequent diagnosis and repair work.
[0067] In this embodiment, by adding the signal delay detection and fault diagnosis link, it is intended to identify and diagnose potential faults by detecting the signal delay and comparing the vehicle operating parameters with the fault calibration parameters. This mechanism is of great significance for improving the reliability, safety and maintenance efficiency of the vehicle.
[0068] Further, based on the above embodiments, please refer to Figure 5In one of the exemplary embodiments provided in the present application, the above-mentioned distributed integrated fault handling system further includes:
[0069] The fault output module 150 is used to output the fault type and fault level to the corresponding functional layer, and send the fault handling measures and the identity corresponding to the fault to the vehicle communication bus.
[0070] Specifically, when a vehicle fails, the fault output module 150 first identifies the type and level of the fault, and then sends this information to the corresponding functional layer in the vehicle so that the functional layer can take corresponding measures. At the same time, the fault output module will also generate processing measures for the fault, and send this information and the identity of the fault to the vehicle's communication bus so that other systems or components can obtain and use this information.
[0071] For example, in the output part, the functional module here has only one data interface like the input. Its function is to give the fault flag determined in the arbitration module to other functional layer modules that need to be used (such as electrical, torque, energy, thermal management) and to transmit the processing measures, fault level and fault code of the execution module to CAN.
[0072] In this embodiment, by providing a fault output module, the fault information can be effectively transmitted to different systems or components of the vehicle, and they can be coordinated to take corresponding measures to deal with the fault.
[0073] Further, based on the above embodiments, please refer to Figure 6 In one of the exemplary embodiments provided in the present application, the above-mentioned distributed integrated fault handling system further includes:
[0074] The storage module 160 is used to pre-store the association relationship between the fault type, the fault level and the fault handling strategy.
[0075] Specifically, the main responsibility of the storage module 160 is to pre-store the relationship between fault types, fault levels and their corresponding fault handling strategies. This relationship is usually organized into a structured data form, such as a database table, a configuration file or a data structure in memory, for quick retrieval and reference. Among them, the fault type refers to various types of faults that may occur in the vehicle, such as hardware failure, software failure, network failure, etc. Each fault type has its own unique characteristics and manifestations. The fault level is used to assess the impact and urgency of the fault on the vehicle. Usually, the fault level is divided into different levels according to the severity of the fault, such as low, medium, high or level 1, level 2, level 3, etc. The fault handling strategy refers to the predefined handling measures or action plans for each fault type and level. These strategies may include automatic repair, notification of relevant personnel, switching to a backup system, logging, etc.
[0076] The configuration module 170 is used to configure at least one or more of the data type, signal name, size value, dimension and reference method corresponding to each module in the fault processing system.
[0077] Specifically, the configuration module 170 is used to set or adjust the parameters such as data type, signal name, size value, dimension and reference mode required by each module in the fault handling system. These configuration information are crucial to ensure that the modules in the system can correctly and efficiently exchange and process data.
[0078] Among them, the data type specifies the format and type of data transmitted between modules, such as integers, floating-point numbers, strings, arrays, etc. The signal name provides a unique identifier for the data or signal transmitted in the system to facilitate identification and processing. Size value: defines the specific size or range of the data or signal to ensure that the receiver can correctly parse and process it. Dimension: for multidimensional data, specify its dimension information, such as the number of rows and columns of a two-dimensional array. Reference method: describes how to reference or access data between modules, including direct memory access, message queues, shared memory, etc.
[0079] In this embodiment, by configuring the storage module, the corresponding processing strategy can be found based on the pre-stored association relationship, thereby accelerating the fault response and recovery time, and by providing flexible configuration options through the configuration module, the system can adapt to different application scenarios and needs. By adjusting the configuration parameters, the system performance can be optimized, the accuracy and efficiency of data processing can be improved, and the maintenance cost can be reduced.
[0080] Figure 7 7 is a simplified flowchart of fault handling in a distributed integrated system in an exemplary application scenario. In the application scenario shown in 7, the specific implementation process of the above fault handling method includes steps S710 to S730, which are described in detail as follows:
[0081] Step S710, receiving the vehicle operating parameters sent from the vehicle communication bus;
[0082] Step S720, comparing the operating parameters of the vehicle with the fault calibration parameters to determine the fault type and fault level based on the comparison result;
[0083] Step S730: determine a corresponding fault handling strategy based on the fault type and fault level.
[0084] Specifically, the various systems inside the vehicle (such as the engine, gearbox, brake system, airbag, etc.) exchange data and information through the communication bus. These buses transmit data according to a predetermined protocol and format, so that different systems can share the vehicle's operating status information. Among them, the vehicle's operating parameters include but are not limited to engine speed, vehicle speed, oil pressure, water temperature, battery voltage, brake pressure, tire pressure, etc. These parameters are important indicators for evaluating the health and performance of the vehicle. Then, a series of pre-set parameter thresholds or ranges are used to determine whether the various functions of the vehicle are working properly. These calibration parameters may be based on the vehicle manufacturer's specifications, industry standards or historical data statistical analysis. The comparison process includes comparing the vehicle operating parameters received in real time with the fault calibration parameters one by one, checking whether any parameters exceed or fall below the preset threshold range, and then quickly identifying potential fault points through comparison.
[0085] Then, for minor faults, it may only need to display a warning message on the vehicle dashboard to alert the driver; for general faults, the system may take measures such as limiting the operation of some vehicle functions and reducing vehicle performance, and prompt the driver to go to the repair station for inspection as soon as possible; for serious faults, the system may immediately cut off vehicle power, activate emergency braking and other safety measures to ensure the safety of passengers and vehicles, and strongly recommend the driver to stop immediately and seek professional repair services. In addition, depending on the specific situation, it may also include recording fault logs, sending fault information to the remote service center for remote diagnosis, or activating vehicle rescue services.
[0086] In this embodiment, by real-time monitoring and analysis of vehicle operating parameters, automatic detection and diagnosis of vehicle faults are achieved, and corresponding processing strategies are formulated according to the fault type and level, thereby improving the safety and reliability of the vehicle.
[0087] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by one or more processors, the electronic device is configured with the distributed integrated fault handling system provided in the above-mentioned embodiments.
[0088] Figure 8 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 8 The computer system 800 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0089] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 802 or the program loaded from the storage part 808 to the random access memory (RAM) 803, such as executing the method in the above embodiment. In the RAM 803, various programs and data required for system operation are also stored. The CPU 801, ROM 802 and RAM 803 are connected to each other through a bus 804. The input / output (I / O) interface 805 is also connected to the bus 804.
[0090] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed so that a computer program read therefrom is installed into the storage section 808 as needed.
[0091] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 809, and / or installed from a removable medium 811. When the computer program is executed by a central processing unit (CPU) 801, various functions defined in the system of the present application are executed.
[0092] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0093] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0094] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0095] Another aspect of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the fault handling method as described above is implemented. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.
[0096] Another aspect of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the road condition refreshing method provided in each of the above embodiments.
[0097] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.
Claims
1. A distributed integrated fault handling system, characterized in that: include: A calibration module, the calibration module is used to configure a plurality of different fault calibration parameters and data types corresponding to the calibration parameters; A data input module, used for receiving vehicle operation parameters sent from a vehicle communication bus; a fault determination module, configured to receive the vehicle operating parameters sent by the data input module, and compare the vehicle operating parameters with the fault calibration parameters in the calibration module, so as to determine the fault type and fault level based on the comparison result; The fault handling module is used to determine a corresponding fault handling strategy based on the fault type and the fault level.
2. The system according to claim 1, characterized in that The calibration module is also used for: The actual fault parameters of the vehicle during operation are obtained, and the fault calibration parameters are corrected based on the actual fault parameters.
3. The system according to claim 1, characterized in that After receiving the vehicle operating parameters sent by the data input module, the fault determination module is further used to: Determine the signal type corresponding to the vehicle operating parameter and obtain a determination result; The vehicle operating parameters are sent to a corresponding service unit based on the judgment result, and the vehicle operating parameters are compared with the fault calibration parameters in the calibration module based on the service unit to determine the fault type and fault level based on the comparison result.
4. The system according to claim 1, characterized in that The fault determination module is also used for: If a signal shielding request is received, parsing the target signal corresponding to the signal shielding request; A fault calibration parameter matching the target signal is searched from the calibration module, and the fault calibration parameter is shielded.
5. The system according to claim 1, wherein: The fault determination module is also used for: If a signal delay detection request is received, parsing the target duration and target vehicle operating parameters corresponding to the signal delay detection request; If it is detected that the duration of the target vehicle operating parameters meets the target duration, the target vehicle operating parameters are compared with the fault calibration parameters in the calibration module to determine the fault type and fault level based on the comparison result.
6. The system according to claim 1, wherein: The system further comprises: The fault output module is used to output the fault type and fault level to the corresponding functional layer, and send the fault handling measures and the identity corresponding to the fault to the vehicle communication bus.
7. The system according to claim 1, characterized in that The system further comprises: A storage module, used to pre-store the association relationship between the fault type, fault level and fault handling strategy; A configuration module is used to configure at least one or more of the data type, signal name, size value, dimension and reference method corresponding to each module in the fault handling system.
8. A fault handling method, characterized in that: include: receiving operating parameters of the vehicle sent from the vehicle communication bus; Comparing the operating parameters of the vehicle with the fault calibration parameters to determine the fault type and fault level based on the comparison result; A corresponding fault handling strategy is determined based on the fault type and the fault level.
9. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to be configured with a distributed integrated fault handling system as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the fault handling method according to any one of claim 8.
Citation Information
Cited By
Fault processing mode determination method and device, electronic equipment and storage medium
CN119872587A
