Fault processing method, electronic equipment, storage medium and driving equipment
The fault information is obtained and processed through the fault management module, and the fault suppression information of the fault configuration file is used to solve the problems of low fault processing efficiency and high resource utilization in complex systems, achieving efficient fault information interaction and processing.
Patent Information
- Application Number
- CN202411119107.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2024-11-26
AI Technical Summary
The existing fault handling solutions are difficult to meet the fault handling requirements of complex systems, especially in the automotive industry. With the complexity of the system structure, the increase in the number of faults leads to high system resource utilization and large development workload, and it is difficult to adapt efficiently. Changes in trouble list.
The fault information sent by the service module is obtained through the fault management module, and the fault configuration file is used to obtain the fault suppression information corresponding to the fault identification code, and send it to the service module, so that it performs corresponding operations based on the fault suppression information to realize fault processing. This method can interact with multiple service modules through only one fault information and one fault suppression information, process a large amount of fault information, and reduce system resource consumption and development workload.
It improves the efficiency of fault information interaction and fault processing, reduces system resource usage and development workload, and can efficiently adapt to the ever-changing fault list to meet the fault processing needs of complex systems.
Smart Images

Figure CN119024810A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of fault handling, and in particular to a fault handling method, electronic equipment, storage medium and driving equipment. Background Art
[0002] At present, vehicle controllers are mainly composed of microcontroller units (MCUs). For faults inside the controller, the MCU can perform fault signal interaction and fault processing through the AUTOSAR protocol stack without the need to develop a dedicated fault processing application.
[0003] However, with the development of intelligence in the automotive industry, the vehicle system structure is becoming more and more complex. A controller may include multiple MCUs and multiple system-level chips SoCs. The original fault handling solutions are difficult to meet the fault handling requirements of complex systems.
[0004] Accordingly, the art needs a new technical solution for fault handling to solve the above problems. Summary of the invention
[0005] In order to overcome the above-mentioned defects, the present application is proposed to provide a fault handling method, electronic device, storage medium and driving device that solve or at least partially solve the technical problem that existing fault handling solutions are difficult to meet the fault handling requirements of complex systems.
[0006] In a first aspect, a fault handling method is provided, which is applied to a fault management module, and the method includes:
[0007] Acquire fault information sent by the service module; the fault information includes at least one fault identification code;
[0008] Acquire fault suppression information corresponding to the fault identification code; the fault suppression information includes the fault suppression identification code;
[0009] The fault suppression information is sent to the service module, so that the service module performs a corresponding operation based on the fault suppression information.
[0010] In a technical solution of the above fault handling method, the acquiring of the fault suppression information corresponding to the fault identification code includes:
[0011] Acquire a fault configuration file; the fault configuration file includes multiple fault information and fault suppression information corresponding to each fault information;
[0012] Based on the fault configuration file, acquiring the fault suppression identification code corresponding to the fault identification code;
[0013] Each of the fault identification codes corresponds to a unique fault, and each of the fault suppression identification codes corresponds to at least one fault.
[0014] In a technical solution of the above fault handling method, the fault information further includes a fault type and a fault name, and the fault suppression information further includes a fault suppression state and a fault suppression name; after acquiring the fault information sent by the service module, the method further includes:
[0015] Parsing the fault information to obtain the fault identification code, the fault type and the fault name;
[0016] Based on the fault configuration file, the fault suppression identification code, the fault suppression state and the fault suppression name corresponding to the fault identification code are acquired.
[0017] In a technical solution of the above fault handling method, sending the fault suppression information to the service module includes:
[0018] The fault suppression information is sent to a plurality of service modules, so that the service module that sends the fault information receives the fault suppression information and performs corresponding operations based on the fault suppression information.
[0019] In a technical solution of the above fault handling method, the fault configuration file also includes a fault diagnosis code corresponding to each fault identification code; the method further includes:
[0020] Acquire the fault diagnosis code corresponding to the fault identification code, and send the fault diagnosis code to a fault diagnosis module;
[0021] and / or,
[0022] The fault information and the fault suppression information are stored.
[0023] In a technical solution of the above fault handling method, the method further includes:
[0024] Get update fault configuration file;
[0025] The updated fault configuration file includes the added, deleted or modified multiple fault information and the fault suppression information corresponding to each fault information.
[0026] In a second aspect, a fault handling method is provided, which is applied to a service module, and the method includes:
[0027] In response to a failure of the service module, obtaining failure information; the failure information includes at least one failure identification code;
[0028] Sending the fault information to a fault management module, so that the fault management module obtains fault suppression information corresponding to the fault information and sends the fault suppression information; the fault suppression information includes a fault suppression identification code;
[0029] receiving the fault suppression information sent by the fault management module;
[0030] A corresponding operation is performed based on the fault suppression information.
[0031] In a technical solution of the above fault handling method, the fault suppression information further includes a fault suppression state; and performing corresponding operations based on the fault suppression information includes:
[0032] Parsing the fault suppression information to obtain the fault suppression identification code and the fault suppression status;
[0033] determining whether the fault suppression identification code corresponds to the fault;
[0034] If so, a corresponding operation is performed according to the fault suppression state.
[0035] In a technical solution of the above fault handling method, the fault suppression state includes suppression and non-suppression; and performing corresponding operations according to the fault suppression state includes:
[0036] When the fault suppression state is the suppression, performing a fault handling operation;
[0037] When the fault suppression state is the non-suppression state, no operation is performed;
[0038] The fault handling operation includes at least one of lowering the fault function level, prohibiting the operation of the fault function, and issuing a fault reminder.
[0039] In a third aspect, an electronic device is provided, which includes a processor and a memory, wherein the memory is suitable for storing multiple program codes, and the program codes are suitable for being loaded and run by the processor to execute the fault handling method described in any one of the technical solutions of the above-mentioned fault handling method applied to the fault management module or the business module.
[0040] In a fourth aspect, a computer-readable storage medium is provided, in which a plurality of program codes are stored, wherein the program codes are suitable for being loaded and run by a processor to execute the fault handling method described in any one of the technical solutions of the fault handling method applied to the fault management module or the business module.
[0041] In a fifth aspect, a driving device is provided, the driving device comprising a fault management module and a plurality of service modules, the fault management module and the plurality of service modules being communicatively connected;
[0042] The fault management module is configured to execute the fault handling method described in any one of the technical solutions of the fault handling method applied to the fault management module;
[0043] The multiple business modules are configured to execute the fault handling method described in any one of the technical solutions of the above-mentioned fault handling method applied to the business module.
[0044] Solution 1. A fault handling method, applied to a fault management module, characterized in that the method comprises:
[0045] Acquire fault information sent by the service module; the fault information includes at least one fault identification code;
[0046] Acquire fault suppression information corresponding to the fault identification code; the fault suppression information includes the fault suppression identification code;
[0047] The fault suppression information is sent to the service module, so that the service module performs a corresponding operation based on the fault suppression information.
[0048] Solution 2. The fault handling method according to Solution 1 is characterized in that the step of obtaining the fault suppression information corresponding to the fault identification code comprises:
[0049] Acquire a fault configuration file; the fault configuration file includes multiple fault information and fault suppression information corresponding to each fault information;
[0050] Based on the fault configuration file, acquiring the fault suppression identification code corresponding to the fault identification code;
[0051] Each of the fault identification codes corresponds to a unique fault, and each of the fault suppression identification codes corresponds to at least one fault.
[0052] Solution 3. The fault handling method according to Solution 2 is characterized in that the fault information further includes a fault type and a fault name, and the fault suppression information further includes a fault suppression state and a fault suppression name; after acquiring the fault information sent by the business module, the method further includes:
[0053] Parsing the fault information to obtain the fault identification code, the fault type and the fault name;
[0054] Based on the fault configuration file, the fault suppression identification code, the fault suppression state and the fault suppression name corresponding to the fault identification code are acquired.
[0055] Solution 4. The fault handling method according to Solution 1, characterized in that sending the fault suppression information to the service module comprises:
[0056] The fault suppression information is sent to a plurality of service modules, so that the service module that sends the fault information receives the fault suppression information and performs corresponding operations based on the fault suppression information.
[0057] Solution 5. The fault handling method according to Solution 2 is characterized in that the fault configuration file also includes a fault diagnosis code corresponding to each fault identification code; the method further includes:
[0058] Acquire the fault diagnosis code corresponding to the fault identification code, and send the fault diagnosis code to a fault diagnosis module;
[0059] and / or,
[0060] The fault information and the fault suppression information are stored.
[0061] Solution 6. The fault handling method according to Solution 2, characterized in that the method further comprises:
[0062] Get update fault configuration file;
[0063] The updated fault configuration file includes the added, deleted or modified multiple fault information and the fault suppression information corresponding to each fault information.
[0064] Solution 7. A fault handling method, applied to a service module, characterized in that the method comprises:
[0065] In response to a failure of the service module, obtaining failure information; the failure information includes at least one failure identification code;
[0066] Sending the fault information to a fault management module, so that the fault management module obtains fault suppression information corresponding to the fault information and sends the fault suppression information; the fault suppression information includes a fault suppression identification code;
[0067] receiving the fault suppression information sent by the fault management module;
[0068] A corresponding operation is performed based on the fault suppression information.
[0069] Solution 8. The fault handling method according to Solution 7 is characterized in that the fault suppression information also includes a fault suppression state; and the performing corresponding operations based on the fault suppression information includes:
[0070] Parsing the fault suppression information to obtain the fault suppression identification code and the fault suppression status;
[0071] determining whether the fault suppression identification code corresponds to the fault;
[0072] If so, a corresponding operation is performed according to the fault suppression state.
[0073] Solution 9. The fault handling method according to Solution 8 is characterized in that the fault suppression state includes suppression and non-suppression; and performing corresponding operations according to the fault suppression state includes:
[0074] When the fault suppression state is the suppression, performing a fault handling operation;
[0075] When the fault suppression state is the non-suppression state, no operation is performed;
[0076] The fault handling operation includes at least one of lowering the fault function level, prohibiting the operation of the fault function, and issuing a fault reminder.
[0077] Solution 10. An electronic device, comprising a processor and a memory, wherein the memory is suitable for storing multiple program codes, and wherein the program codes are suitable for being loaded and run by the processor to execute the fault handling method described in any one of Solutions 1 to 6 or 7 to 9.
[0078] Solution 11. A computer-readable storage medium storing a plurality of program codes, wherein the program codes are suitable for being loaded and run by a processor to execute the fault handling method described in any one of Solutions 1 to 6 or 7 to 9.
[0079] Solution 12. A driving device, characterized in that the driving device comprises a fault management module and a plurality of service modules, and the fault management module is communicatively connected with the plurality of service modules;
[0080] The fault management module is configured to execute the fault handling method described in any one of schemes 1 to 6;
[0081] The multiple business modules are configured to execute the fault handling method described in any one of Schemes 7 to 9.
[0082] The above one or more technical solutions of this application have at least one or more of the following Beneficial effects:
[0083] In the technical solution of the present application, the fault management module first obtains the fault information sent by the business module, the fault information includes at least one fault identification code, then obtains the fault suppression information corresponding to the fault identification code, the fault suppression information includes the fault suppression identification code, and finally sends the fault suppression information to the business module, so that the business module performs corresponding operations based on the fault suppression information. Through the above implementation, the fault management module can interact with multiple business modules only through one fault information and one fault suppression information, and process a large amount of fault information, which solves the problem of high system resource occupation and heavy development workload caused by the increase in the number of faults in complex systems, and improves the efficiency of fault information interaction and fault processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0084] The disclosure of the present application will become easier to understand with reference to the accompanying drawings. It is easy for those skilled in the art to understand that these drawings are only for illustrative purposes and are not intended to limit the scope of protection of the present application. Among them:
[0085] Figure 1 This is a flowchart of the main steps of a fault handling method according to an embodiment of the present application;
[0086] Figure 2 is a flowchart of main steps of a fault handling method according to another embodiment of the present application;
[0087] Figure 3 It is a main flow chart of a fault handling method according to an embodiment of the present application;
[0088] Figure 4 is a main flow chart of a fault handling method according to another embodiment of the present application;
[0089] Figure 5 It is a schematic diagram of the main structure of an electronic device according to an embodiment of the present application.
[0090] List of reference numerals:
[0091] 501: processor; 502: memory. DETAILED DESCRIPTION
[0092] Some embodiments of the present application are described below with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are only used to explain the technical principles of the present application and are not intended to limit the protection scope of the present application.
[0093] In the description of the present application, "module" and "processor" may include hardware, software or a combination of the two. A module may include hardware circuits, various suitable sensors, communication ports, memory, and may also include software parts, such as program code, or a combination of software and hardware. The processor may be a central processing unit, a microprocessor, an image processor, a digital signal processor or any other suitable processor. The processor has data and / or signal processing functions. The processor may be implemented in software, hardware or a combination of the two. Non-temporary computer-readable storage media include any suitable medium that can store program code, such as a disk, a hard disk, an optical disk, a flash memory, a read-only memory, a random access memory, etc. The term "A and / or B" means all possible combinations of A and B, such as only A, only B or A and B. The term "at least one A or B" or "at least one of A and B" has a similar meaning to "A and / or B" and may include only A, only B or A and B. The singular terms "one" and "the" may also include plural forms.
[0094] At present, in the field of vehicle failure, the main focus is on fault diagnosis methods and diagnostic equipment, fault cause investigation methods, and fault information coding, while less attention is paid to the transmission of fault information and fault handling methods within the controller. The main reason is that the vehicle controller structure is relatively simple and mainly consists of MCU. MCU can perform fault signal interaction and fault handling through the AUTOSAR protocol stack, without the need to develop a special fault handling application.
[0095] However, with the development of intelligent automobile industry, the vehicle system structure is becoming more and more complex. A controller may include multiple MCUs and multiple system-level chips SoC. The original fault handling solution is difficult to meet the fault handling requirements of complex systems and faces the following challenges:
[0096] 1. When the number of faults increases, how to reduce the system resource consumption occupied by fault handling. The number of traditional electronic controller units (ECUs) ranges from dozens to hundreds, but the number of vehicle controller faults exceeds 1,000.
[0097] 2. The fault list is constantly changing during the development process. How to efficiently adapt to the changing fault list and reduce software development and adaptation work.
[0098] 3. With the ever-changing upper-layer services, how can we efficiently adjust fault suppression and diagnostic trouble code (DTC) records without changing the software?
[0099] In order to solve the above problems, the present application provides a fault handling method, an electronic device, a storage medium and a driving device.
[0100] See attached Figure 1 , Figure 1 FIG. 1 is a flow chart of the main steps of a fault handling method according to an embodiment of the present application, which is applied to a fault management module. Figure 1 As shown, the fault handling method in the embodiment of the present application mainly includes the following steps S101 to S103.
[0101] Step S101: Obtaining fault information sent by the service module;
[0102] The fault information includes at least one fault identification code.
[0103] Step S102: Acquire fault suppression information corresponding to the fault identification code;
[0104] The fault suppression information includes a fault suppression identification code.
[0105] Step S103: Send the fault suppression information to the service module, so that the service module performs corresponding operations based on the fault suppression information.
[0106] Based on the method described in steps S101 to S103 above, the fault management module can interact with multiple business modules through only one fault message and one fault suppression message, and process a large amount of fault information, thereby solving the problem of high system resource usage and heavy development workload caused by the increase in the number of faults in complex systems, and improving the efficiency of fault information interaction and fault handling.
[0107] The above steps S101 to S103 are further explained below.
[0108] Currently, driving equipment may include multiple controllers, each of which integrates multiple MCUs, and each MCU contains at least one business module, which are software components that implement specific functions, such as engine management, brake control, steering assistance or vehicle stability control.
[0109] In the fault handling method provided in the present application, the fault management module of the driving device can interact with the above-mentioned multiple business modules for fault signals and handle faults.
[0110] Furthermore, in some implementations of the above step S101, the fault management module may receive fault information faults_message sent by multiple business modules, and the faults_message may transmit one or more fault signals.
[0111] Specifically, the fault contents in multiple business modules may be digitally encoded, each fault may be mapped to a fault identification code, and the fault signal may be transmitted through a generalized and unified data structure of faults_message.
[0112] faults_message may include the fault identification code faults_id, the fault name faults_name and the fault type trigger_type, etc.
[0113] Among them, faults_id is of digital type, which is mapped one by one to faults in multiple business modules; faults_name is of string type, which is used to describe specific faults, so that users or staff can quickly understand specific fault information; trigger_type is of enumeration type, which is used to describe the fault event type, such as fault trigger is fault_set, and fault clear is fault_clear.
[0114] Among them, the numeric type is a data type used to represent numerical values, including integers (such as integers and long integers) and floating-point numbers (such as single-precision floating-point numbers and double-precision floating-point numbers).
[0115] The string type is a data type used to represent text. It is usually composed of a series of characters. A string can contain letters, numbers, special symbols, and spaces. It is used to store and represent readable text information.
[0116] An enumeration type is a user-defined type that allows the definition of a set of named constants, each of which has an integer value. Enumerations make code more clear and easier to read, and help prevent errors because it restricts the range of values a variable can take.
[0117] Further, in some implementations, taking the proto file as an example, the data structure of faults_message is as follows:
[0118] 1message faultsMessage{
[0119] 2repeated faultInfo app_fault_info=1;
[0120] 3} 4
[0122] 5message faultInfo
[0123] 6{
[0124] 7optional uint32 fault_id = 1;
[0125] 8optional string fault_name=2; / / option
[0126] 9optional DTCTriggerEnum trigger_type=3;
[0127] 10enum DTCTriggerEnum
[0128] 11{
[0129] 12 none = 0;
[0130] 13 fault_set = 1;
[0131] 14 fault_clear=2;
[0132] 15}
[0133] 16}
[0134] The proto file is a syntax definition file of Protocol Buffers (Protobuf for short), which is used to describe the structure of data. In Protobuf, developers define data types and message formats by writing proto files.
[0135] in," f au l tIn f o " is a structure; " u i nt 32 " indicates a numeric type; " string " indicates string type; " DTCTr i ggerEnum " indicates an enumeration type, " DTCTr i ggerEnum "Defines three types of" tr i gger_type " constant, " none " indicates a null value, that is, no fault type, " f au l t_set " indicates a fault is triggered, " f au l t_c l ear "Indicates the fault is cleared;" op ti on "express" fault _name " is optional, that is, faults_name may or may not be included in faults_message.
[0136] It should be pointed out that the above composition and data structure of fault information are only schematic illustrations. In practical applications, those skilled in the art can make settings according to specific scenarios, and no limitation is made here.
[0137] Furthermore, when a fault occurs in a business module, faults_message can be filled in according to the specific fault and sent to the fault management module.
[0138] In the entire vehicle system, all business modules can send fault signals through the same faults_message, and the fault management module does not care about the sender of the faults_message.
[0139] The above is a further description of step S101 , and the following is a further description of step S102 .
[0140] In some implementations of the above step S102, after receiving the faults_message sent by the business module, the fault management module may parse the faults_message to obtain information such as faults_id, faults_name and trigger_type, and obtain fault suppression information fim_message corresponding to the faults_message.
[0141] Specifically, the fault suppression information of each fault may be digitally encoded, the fault suppression may be mapped to a fault suppression identification code, and the fault suppression signal may be transmitted through a fim_message of a generalized and unified data structure.
[0142] The fim message may include a fault suppression identification code fim_id / fim_bits, a fault suppression name fim_flag_name, and a fault suppression status fim_id_flag, etc.
[0143] Among them, fim_id is of digital type, one or more faults in the business module can be mapped to the same fim_id, fim_bits is also of digital type, each fim_id maps a bit position, so all fim_ids can be expressed by fim_bits. In practical applications, only fim_id or fim_bits can be selected to represent the fault suppression identification code; fim_id_flag is of Boolean type, which is used to describe whether fim_id is set. If it is set to true, the relevant business module needs to execute the fault handling strategy, otherwise it is ignored; fim_flag_name is of string type, which is used to describe specific fault suppression, so that users and staff can quickly understand the specific fault suppression information.
[0144] Among them, Boolean type is a basic data type, which contains only two possible values: true and false. fim_id_flag is used to describe whether fim_id is set, which can be determined according to trigger_type. If trigger_type is fault_set, fim_id is set to true, indicating that the relevant fault suppression logic or strategy has been triggered and needs to be processed accordingly; if trigger_type is fault_clear, fim_id is not set, indicating that the fault suppression logic or strategy is currently inactive and does not need to be processed.
[0145] Further, in some implementations, taking the proto file as an example, the data structure of fam_message is as follows:
[0146] 1message FIMMessage{
[0147] 2 repeated FIMInfo fim_info=1;
[0148] 3 repeated uint32 fim_bits=2;
[0149] 4optional uint32 max_fim_id=3; 5
[0151] 6optional uint64 publish_ptp_ts=536870907; / / publishptptimestamp, uint
[0152] 7optional string publisher_id=536870909; / / uuidofthepublisher
[0153] 8optional uint64 counter=536870910; / / messagecounter
[0154] 9optional uint64 publish_ts=536870911; / / publishtimestamp; unit:n
[0155] 10} 11
[0157] 12message FIMInfo
[0158] 13{
[0159] 14optional uint32 fim_id=1;
[0160] 15optional bool fim_id_flag=2;
[0161] 16optional string fim_flag_name=3; / / optional
[0162] 17}
[0163] in," FIMMessage " indicates the first message type. When the message contains " fi m_ bi ts ", you can set max_ fi m_ id ”, used to indicate “ fi m_ bi ts "The maximum length of "; Lines 6-9 indicate the PTP (Precision Time Protocol) timestamp, publisher ID, message counter and publishing timestamp of fam_message, which are all optional;" FIMInfo " indicates the second message type, " b oo l " indicates Boolean type, " op ti on "express" fi m_ fl ag_name " is optional, that is, the faults_message may include fim_flag_name or not.
[0164] It should be pointed out that the above composition and data structure of the fault suppression information are only schematic illustrations. In practical applications, those skilled in the art may make settings according to specific scenarios, and no limitation is made here.
[0165] Further, in some implementations of step S102, the fault suppression information corresponding to the fault identification code may be obtained through the following steps S1021 to S1022:
[0166] Step S1021: Obtain a fault configuration file;
[0167] The fault configuration file includes multiple fault information and fault suppression information corresponding to each fault information.
[0168] Specifically, the fault configuration file stores multiple fault information, including fault_id, fault_name and trigger_type, as well as fault suppression information corresponding to each fault information, including fim_id / fim_bits, fim_flag_name and fim_id_flag. It can also include fault description information description, dtc_id storing the fault diagnostic code DTC, fault start status enabled, etc.
[0169] In some implementations, taking a json file as an example, the data structure of the fault configuration file is as follows:
[0170] 1{
[0171] 2 "fault_info":[
[0172] 3 {
[0173] 4 "fault_id":1,
[0174] 5 "fault_name":"fault 1",
[0175] 6 "description":"this is a demo,id=1",
[0176] 7 "dtc_id":65518,
[0177] 8 "fim_id":1,
[0178] 9 "fim_flag_name":"control function1 and function2",
[0179] 10 "enabled":true
[0180] 11},
[0181] 12 {
[0182] 13 "fault_id":2,
[0183] 14 "fault_name":"fault 1",
[0184] 15 "description":"this is a demo,id=2",
[0185] 16 "dtc_id":65501,
[0186] 17 "fim_id":2,
[0187] 18 "fim_flag_name":"control function2",
[0188] 19 "enabled":true
[0189] 20} twenty one]
[0191] twenty two}
[0192] Json (JavaScript Object Notation) file is a lightweight data interaction format that uses a text format that is completely independent of the programming language to store and represent data.
[0193] In the fault configuration file, each fault_id corresponds to a unique fault, and each fam_id corresponds to at least one fault.
[0194] Furthermore, the fault management module may call the fault configuration file each time it is started to obtain relevant fault information.
[0195] The above is a further explanation of step S1021.
[0196] Step S1022: Based on the fault configuration file, a fault suppression identification code corresponding to the fault identification code is obtained.
[0197] Specifically, the fault management module can query the information such as fim_id / fim_bits, fim_flag_name and fim_id_flag corresponding to the fault_id in the faults_message according to the fault configuration file, and fill in the fim_message.
[0198] The above is a further description of step S102 , and the following is a further description of step S103 .
[0199] In some implementations of the above step S103, the fault management module may send the fim_message to multiple service modules, so that the service module that sends the fault information receives the fim_message and performs corresponding operations based on the fim_message.
[0200] Specifically, the fault management module may broadcast the fim_message so that all service modules receive the fim_message and perform corresponding operations according to the content of the fim_message.
[0201] The above is a further description of step S103.
[0202] In some implementations, after acquiring the fault information sent by the business module, the fault management module may also acquire a fault diagnosis code corresponding to the fault identification code, and send the fault diagnosis code to the fault diagnosis module.
[0203] Specifically, the fault management module can query the DTC corresponding to the fault_id in the faults_message in the fault configuration file, and send the DTC to the fault diagnosis module. After receiving the DTC, the fault diagnosis module records and stores it.
[0204] In some implementations, after the fault management module sends the fam_message to the business module, the fault information and the fault suppression information may be stored.
[0205] Specifically, the fault management module can record fault_id, faults_name, trigger_type in faults_message, fim_id / fim_bits, fim_flag_name and fim_id_flag in fam_message, as well as the time, description and enabled of the fault, and save them to disk as files to facilitate subsequent investigation of the problem.
[0206] Furthermore, in some implementations, the fault management module may obtain and update a fault configuration file.
[0207] Wherein, updating the fault configuration file includes adding, deleting or modifying a plurality of fault information and the fault suppression information corresponding to each fault information.
[0208] Specifically, the fault management module does not store any information and sends fam_message and DTC completely according to the fault configuration file. Therefore, when the fault list changes or the upper-level business changes and a certain fault needs to be added, deleted or adjusted, it only needs to update the fault configuration file to achieve efficient adaptation. There is no need to adjust the data structure and related code of faults_message and fam_message, which reduces software development and adaptation work and improves the efficiency of fault information interaction and fault handling.
[0209] The above is a description of the fault handling method applied to the fault management module.
[0210] Furthermore, the present application also provides a fault handling method applied to a business module.
[0211] See attached Figure 2 , Figure 2 FIG. 1 is a flow chart of the main steps of a fault handling method according to another embodiment of the present application, which is applied to a business module. Figure 2 As shown, it mainly includes the following steps S201 to S204.
[0212] Step S201: in response to a failure of a service module, obtaining failure information;
[0213] The fault information includes at least one fault identification code.
[0214] Specifically, when a certain service module fails, information such as fault_id, faults_name, and trigger_type corresponding to the specific fault can be obtained.
[0215] Step S202: sending the fault information to the fault management module, so that the fault management module obtains the fault suppression information corresponding to the fault information and sends the fault suppression information;
[0216] The fault suppression information includes a fault suppression identification code.
[0217] In some implementations, the business module may fill in the fault_message with information such as fault_id, faults_name, and trigger_type corresponding to a specific fault, and send the fault_messge to the fault management module.
[0218] Furthermore, after receiving the fault_message, the fault management module parses to obtain information such as fault_id, faults_name and trigger_type, obtains information such as fim_id / fim_bits, fim_flag_name and fim_id_flag corresponding to the fault_id according to the fault configuration file, fills it into fam_message, and broadcasts the fam_message.
[0219] Step S203: receiving fault suppression information sent by the fault management module;
[0220] Among them, each business software module only needs to receive the same fim_message.
[0221] Step S204: Execute corresponding operations based on the fault suppression information.
[0222] In some implementations, step S204 may include the following steps S2041 to S2043:
[0223] Step S2041: parse the fault suppression information to obtain a fault suppression identification code and a fault suppression status;
[0224] Specifically, after receiving the fim message, each service module can parse and obtain information such as fim_id / fim_bits, fim_flag_name and fim_id_flag.
[0225] Step S2042: determining whether the fault suppression identification code corresponds to the fault;
[0226] Since the fault management module broadcasts fam_message to all business modules, and fam_message may include suppression information of multiple faults, each business module needs to determine whether the fim_id / fim_bits in the fam_message corresponds to the fault of the business module after receiving the fam_message.
[0227] For example, the fim_id parsed from fam_message includes fim_id=1 and fim_id=2, and the fault functions corresponding to fim_id=1 are 1, 3, and 4, and the fault functions corresponding to fim_id=2 are 2, 5, and 6. At this time, the business module needs to determine whether the faulty function is the fault function 1, 3, and 4 corresponding to fim_id=1 or the fault function 2, 5, and 6 corresponding to fim_id=2.
[0228] Furthermore, if a service module does not fail, or the fim_id / fim_bits in the fam_message does not correspond to the failure of the service module, the fam_message is ignored.
[0229] If the fim_id / fim_bits in the fam_message corresponds to the fault of the service module, execute step S2043.
[0230] Step S2043: Execute corresponding operations according to the fault suppression status.
[0231] The fault suppression state includes suppression and non-suppression.
[0232] Specifically, the fim_id_flag in the fam_message may be obtained, and it may be determined whether the fim_id_flag is set to true. If so, it is in a suppressed state, otherwise, it is in a non-suppressed state.
[0233] In some implementations, when the fault suppression state is suppressed, a fault handling operation is performed.
[0234] That is, when fim_id_flag is set to true, the fault handling operation is performed.
[0235] The fault handling operation includes at least one of lowering the fault function level, prohibiting the operation of the fault function, and issuing a fault reminder.
[0236] The business module can reduce the level of the faulty function, prohibit the operation of the faulty function, or issue a fault reminder based on the specific function that has failed.
[0237] For example, when certain key functions fail, in order to ensure that the vehicle system can continue to operate, the faulty function level can be lowered, temporarily reducing the performance of these faulty functions or limiting some of their capabilities, allowing users to still use the basic functions of the business module while waiting for the problem to be resolved.
[0238] When certain faults may cause safety problems or seriously affect the operation of the vehicle system, the fault function can be prohibited to avoid danger.
[0239] The business module can also display reminder information to users through the HMI human-machine interaction interface, or issue voice reminders to inform users of existing problems and possible impacts, and guide users to take appropriate actions based on the prompts.
[0240] It should be pointed out that the above examples of fault handling operations are only illustrative. In practical applications, those skilled in the art can make settings according to specific needs, which are not limited here.
[0241] Further, in some implementations, when the fault suppression state is not suppressed, no operation is performed.
[0242] Specifically, if fim_id_flag is not set to true, it means that fault suppression is not performed. In this case, no operation needs to be performed.
[0243] The above is a description of the troubleshooting method applied to the business module.
[0244] For further information, see Appendix Figure 3 , Figure 3 It is a main flow chart of a fault handling method according to an embodiment of the present application.
[0245] like Figure 3 As shown, three control units are integrated inside the vehicle controller, namely control unit 1, control unit 2 and control unit 3. Among them, control unit 1 includes business module 1 and business module 2; control unit 2 includes business module 3 and business module 4, control unit 3 includes business module 5, and each business module communicates with the fault management module.
[0246] When business module 2 and business module 3 fail, business module 2 and business module 3 respectively obtain the fault_id, faults_name and trigger_type corresponding to the specific fault, fill them into the same faults_message, and send the faults_message to the fault management module;
[0247] After receiving the faults_message, the fault management module parses to obtain multiple fault_ids, faults_names, and trigger_types, and obtains the fim_id, fim_flag_name, and fim_id_flag corresponding to each fault_id according to the fault configuration file and fills them into fam_message, and finally broadcasts the fam_message;
[0248] Business modules 1-5 receive the same fim_message, parse it to obtain fim_ids, fim_flag_name and fim_id_flag, and perform corresponding operations.
[0249] For example, if business module 2 determines that fim_id corresponds to a fault in the business module, it will perform corresponding operations according to fim_id_flag; if business module 3 determines that fim_id does not correspond to a fault in the business module, it will ignore this fam_message; if business module 1, business module 4 and business module 5 do not have a fault, they will ignore this fam_message.
[0250] For further information, see Appendix Figure 4 , Figure 4 It is a main flow chart of a fault handling method according to another embodiment of the present application.
[0251] like Figure 4 As shown, the fault management module can also query the DTC corresponding to the fault_id and send the DTC to the fault diagnosis module.
[0252] Among them, the fault diagnosis module can be set in Figure 4 The control unit 3 shown may also be arranged in other control units or fault management modules, which is not limited here.
[0253] Through the above implementation, the fault management module can interact with multiple business modules only through one fault message and one fault suppression message, which reduces signal maintenance work and system resource consumption and improves the efficiency of fault information interaction and fault processing.
[0254] It should be pointed out that although the various steps in the above embodiments are described in a specific order, those skilled in the art can understand that in order to achieve the effect of the present application, different steps do not have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders. These changes are within the scope of protection of the present application.
[0255] It is understood by those skilled in the art that all or part of the processes in the method for implementing the above-mentioned embodiment of the present application can also be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may include: any entity or device, medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory, random access memory, electrical carrier signal, telecommunication signal and software distribution medium, etc. that can carry the computer program code.
[0256] Furthermore, the present application also provides an electronic device. Figure 5 , Figure 5 Schematic diagram of the main structure of an electronic device according to an embodiment of the present application. Figure 5As shown, the electronic device in the embodiment of the present application mainly includes a processor 501 and a memory 502. The memory 502 can be configured to store a program for executing the fault handling method of the above method embodiment, and the processor 501 can be configured to execute the program in the memory 502, which includes but is not limited to the program for executing the fault handling method of the above method embodiment. For ease of explanation, only the part related to the embodiment of the present application is shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present application.
[0257] In some possible implementations of the present application, the electronic device may include multiple processors 501 and multiple memories 502. The program for executing the fault handling method of the above method embodiment may be divided into multiple subprograms, and each subprogram may be loaded and run by the processor 501 to execute different steps of the fault handling method of the above method embodiment. Specifically, each subprogram may be stored in different memories 502, and each processor 501 may be configured to execute the program in one or more memories 502 to jointly implement the fault handling method of the above method embodiment, that is, each processor 501 executes different steps of the fault handling method of the above method embodiment, to jointly implement the fault handling method of the above method embodiment.
[0258] The above-mentioned multiple processors 501 may be processors deployed on the same device. For example, the above-mentioned electronic device may be a high-performance device composed of multiple processors, and the above-mentioned multiple processors 501 may be processors configured on the high-performance device. In addition, the above-mentioned multiple processors 501 may also be processors deployed on different devices. For example, the above-mentioned electronic device may be a server cluster, and the above-mentioned multiple processors 501 may be processors on different servers in the server cluster, or the above-mentioned computer device may be a driving device cluster, and the above-mentioned multiple processors 901 may be processors on different driving devices in the driving device cluster.
[0259] Furthermore, the present application also provides a driving device. In an embodiment of a driving device according to the present application, the driving device may include a fault management module and multiple service modules, and the fault management module and the multiple service modules are communicatively connected.
[0260] The fault management module is configured to execute the fault handling method of the method embodiment applied to the fault management module;
[0261] The multiple service modules are configured to execute the fault handling method of the above method embodiment applied to the service modules.
[0262] In an embodiment of a driving device according to the present application, the driving device may further include a fault diagnosis module.
[0263] Furthermore, the present application also provides a computer-readable storage medium. In a computer-readable storage medium embodiment according to the present application, the computer-readable storage medium may be configured to store a program for executing the fault handling method of the above-mentioned method embodiment, and the program may be loaded and run by the processor to implement the above-mentioned fault handling method. For ease of explanation, only the parts related to the embodiment of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present application. The computer-readable storage medium may be a memory device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiment of the present application is a non-temporary computer-readable storage medium.
[0264] It should be noted that the relevant user personal information that may be involved in the various embodiments of the present application is strictly in accordance with the requirements of laws and regulations, following the principles of legality, legitimacy and necessity, based on the reasonable purposes of business scenarios, to process the personal information that users actively provide during the use of products / services or generated due to the use of products / services, as well as the personal information obtained with the user's authorization.
[0265] The user personal information processed by this application will vary depending on the specific product / service scenario, and shall be based on the specific scenario in which the user uses the product / service, and may involve the user's account information, device information, driving information, vehicle information or other related information. This application will treat the user's personal information and its processing with a high degree of diligence.
[0266] This application attaches great importance to the security of user personal information and has taken reasonable and feasible security protection measures that meet industry standards to protect user information and prevent personal information from being accessed, disclosed, used, modified, damaged or lost without authorization.
[0267] So far, the technical solution of the present application has been described in conjunction with an embodiment shown in the accompanying drawings, but it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific embodiments. Without departing from the principles of the present application, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present application.
Claims
1. A fault handling method, applied to a fault management module, characterized in that: The method comprises: Acquire fault information sent by the service module; the fault information includes at least one fault identification code; Acquire fault suppression information corresponding to the fault identification code; the fault suppression information includes the fault suppression identification code; The fault suppression information is sent to the service module, so that the service module performs a corresponding operation based on the fault suppression information.
2. The fault handling method according to claim 1, characterized in that: The acquiring of the fault suppression information corresponding to the fault identification code comprises: Acquire a fault configuration file; the fault configuration file includes multiple fault information and fault suppression information corresponding to each fault information; Based on the fault configuration file, acquiring the fault suppression identification code corresponding to the fault identification code; Each of the fault identification codes corresponds to a unique fault, and each of the fault suppression identification codes corresponds to at least one fault.
3. The fault handling method according to claim 2, characterized in that: The fault information further includes a fault type and a fault name, and the fault suppression information further includes a fault suppression state and a fault suppression name; after acquiring the fault information sent by the service module, the method further includes: Parsing the fault information to obtain the fault identification code, the fault type and the fault name; Based on the fault configuration file, the fault suppression identification code, the fault suppression state and the fault suppression name corresponding to the fault identification code are acquired.
4. The fault handling method according to claim 1, characterized in that: The sending the fault suppression information to the service module comprises: The fault suppression information is sent to a plurality of service modules, so that the service module that sends the fault information receives the fault suppression information and performs corresponding operations based on the fault suppression information.
5. The fault handling method according to claim 2, characterized in that: The fault configuration file also includes a fault diagnosis code corresponding to each fault identification code; the method further includes: Acquire the fault diagnosis code corresponding to the fault identification code, and send the fault diagnosis code to a fault diagnosis module; and / or, The fault information and the fault suppression information are stored.
6. The fault handling method according to claim 2, characterized in that: The method further comprises: Get update fault configuration file; The updated fault configuration file includes the added, deleted or modified multiple fault information and the fault suppression information corresponding to each fault information.
7. A fault handling method, applied to a business module, characterized in that: The method comprises: In response to a failure of the service module, obtaining failure information; the failure information includes at least one failure identification code; Sending the fault information to a fault management module, so that the fault management module obtains fault suppression information corresponding to the fault information and sends the fault suppression information; the fault suppression information includes a fault suppression identification code; receiving the fault suppression information sent by the fault management module; A corresponding operation is performed based on the fault suppression information.
8. The fault handling method according to claim 7, characterized in that: The fault suppression information further includes a fault suppression state; and performing corresponding operations based on the fault suppression information includes: Parsing the fault suppression information to obtain the fault suppression identification code and the fault suppression status; determining whether the fault suppression identification code corresponds to the fault; If so, a corresponding operation is performed according to the fault suppression state.
9. The fault handling method according to claim 8, characterized in that: The fault suppression state includes suppression and non-suppression; and performing corresponding operations according to the fault suppression state includes: When the fault suppression state is the suppression, performing a fault handling operation; When the fault suppression state is the non-suppression state, no operation is performed; The fault handling operation includes at least one of lowering the fault function level, prohibiting the operation of the fault function, and issuing a fault reminder.
10. An electronic device comprising a processor and a memory, wherein the memory is suitable for storing a plurality of program codes, wherein: The program code is suitable for being loaded and run by the processor to execute the fault handling method according to any one of claims 1 to 6 or 7 to 9.
Citation Information
Cited By
Fault scene transaction method and device, and program product
CN119762075A
