A domain controller failure data storage resource occupation optimization system, method, storage medium and computer program product with a diagnostic agent function

Abstract

The application provides a domain controller fault data storage resource occupation optimization system, method, storage medium and computer program product with a diagnostic agent function, and the system comprises a configuration storage module, a data analysis module, a data compression module, a data storage module, a data reading response module and a data clearing response module. Through the diagnostic agent function of the domain controller, a compression and decompression mode corresponding one-to-one between a reading data identifier and a storage data identifier is designed, so that the actual storage occupation space of the fault information can be effectively reduced. Meanwhile, in the evolution process from a distributed electronic and electrical architecture to an integrated electronic and electrical architecture, the change dependence on downstream controllers and diagnostic equipment is reduced, and the corresponding period and cost are reduced.

Description

Technical Field

[0001] This invention belongs to the field of automotive electronics technology, specifically relating to a domain controller fault data storage resource utilization optimization system, method, storage medium, and computer program product with diagnostic agent function. Background Technology

[0002] To quickly pinpoint the cause and timing of a fault, the development of automotive diagnostic systems involves the design of fault codes and freeze frames. Fault codes indicate the direct cause of the fault, while freeze frames contain vehicle-related status information for a specific period at the time of the fault, serving as crucial for further fault analysis. Design, development, production, and after-sales personnel can access this information using diagnostic equipment, facilitating fault location and reproduction.

[0003] In a distributed electronic and electrical architecture, each controller is responsible for handling its own associated faults. Diagnostic equipment obtains the necessary freeze frame information through different physical addresses and data identifiers (DIDs). The data content corresponding to the DID generally consists of three parts: vehicle-wide data, vehicle-specific data, and reserved data space. Figure 1 As shown. Meanwhile, diagnostic equipment is generally shared across multiple vehicle models. Dedicated status bits in the same frozen frame can be enabled via vehicle model identification codes, which to some extent reduces the development and maintenance costs of multi-vehicle model adaptation for diagnostic equipment.

[0004] With the trend of integration, electronic and electrical architectures are evolving towards functional and spatial domains, while also giving rise to domain controller diagnostic agent functions, such as... Figure 2 As shown, the domain controller is responsible for generating and storing fault data for downstream controllers. This places higher demands on the storage space of the domain controller's hardware resources. If the domain controller stores fault information as a single controller, the storage space utilization will be low, resulting in a significant waste of hardware resources. Therefore, there is an urgent need for a fault data storage method that makes efficient use of limited storage space to address this trend. Summary of the Invention

[0005] This invention proposes a system, method, storage medium, and computer program product for optimizing the storage resource usage of faulty domain controllers with diagnostic agent functionality.

[0006] A domain controller fault data storage resource utilization optimization system with diagnostic agent function, which achieves one of the objectives of this invention, includes: Configuration storage module: used to store the list of valid byte numbers corresponding to interactive fault data, the preset total length, and the mapping relationship between stored fault data, fault data identifiers and non-volatile memory addresses. The list of valid byte numbers is an ordered list recording the byte numbers corresponding to valid bytes in interactive fault data, and the preset total length is the fixed byte length of interactive fault data. The configuration storage module is located in the fixed address area of ​​the domain controller RAM. The list of valid byte numbers, the preset total length of interactive fault data, and the mapping relationship are all determined by the vehicle model fault diagnosis requirement specification and pre-stored in the configuration storage module. Data parsing module: When the domain controller acts as a diagnostic agent, it is used to capture the fault data of the downstream controller based on the fault status of the received downstream controller, and store it in the volatile memory of the domain controller in the format of interactive fault data set according to the vehicle model fault diagnosis requirement specification. Data compression module: used to call the list of valid byte numbers from the configuration storage module, extract the corresponding valid bytes from the interactive fault data in the volatile memory according to the byte numbers in the list, and then concatenate them in the order of the byte numbers to form stored fault data and store it in the volatile memory. Data storage module: used to store fault data stored in volatile memory into non-volatile memory space and update the mapping relationship.

[0007] Furthermore, it also includes a data read response module: when the domain controller acts as a diagnostic agent, based on the read command issued by the diagnostic device received by the domain controller, combined with the fault data identifier carried in the read command and the mapping relationship obtained from the configuration storage module, it reads the stored fault data corresponding to the fault data identifier from the non-volatile memory, and then calls the list of valid byte numbers and the preset total length from the configuration storage module to restore the stored fault data into the original interactive fault data and respond to the diagnostic device.

[0008] Interactive fault data refers to uncompressed fault data that can be directly identified by diagnostic equipment, including fault condition data and freeze frame data; stored fault data refers to fault data that has been extracted, compressed, and stored. The non-volatile storage space is the EEPROM storage medium of the domain controller, and the fault data identifier is the fault code or data identifier code defined in the vehicle model fault diagnosis requirement specification.

[0009] Furthermore, the method for splicing together stored fault data in the data compression module includes: Obtain a list of valid byte numbers from the configuration storage module and sort the byte numbers in the list in ascending order; According to the sorted byte numbers, extract the corresponding valid bytes one by one from the interactive fault data in volatile memory; The extracted valid bytes are concatenated sequentially according to the sorted byte number order to form continuous, unfilled stored fault data, which is then stored in volatile memory.

[0010] Furthermore, the decompression method for restoring stored fault data to original interactive fault data by the data reading response module includes: initializing an interactive fault data buffer with a length equal to the preset total length and filling all bytes with default values; determining the original byte position corresponding to each byte in the stored fault data according to the effective byte number list; and completely filling each byte of the stored fault data into the corresponding original byte position of the buffer to form the original interactive fault data.

[0011] Furthermore, the fault status of the downstream controller received by the data parsing module is the fault enable status information uploaded by the downstream controller based on the vehicle diagnostic protocol, and the fault data is the original fault data containing fault codes and fault condition parameters.

[0012] Furthermore, the triggering conditions for the data storage module to store the stored fault data into the non-volatile memory include: the vehicle state is a preset state; the preset state includes: the vehicle state is powered off or in sleep mode, and the setting conditions are specifically defined by each vehicle model and are not limited here; that is, the stored fault data is stored into the non-volatile memory before the vehicle is powered off or in sleep mode.

[0013] Furthermore, the method for storing stored fault data and saving mapping relationships in the data storage module includes: Read the stored fault data to be stored and the corresponding fault data identifier from the volatile memory; Allocate a free storage address in the non-volatile storage space, and write the storage-type fault data into the free storage address; Based on the fault data identifier, stored fault data, and the actual allocated free storage address, update the corresponding mapping relationship in the configuration storage module to achieve a one-to-one binding of the three.

[0014] Furthermore, before reading the stored fault data, the data read response module also includes a validity check of the fault data identifier, and the check method includes: Extract the fault data identifier from the read command, and call the mapping relationship from the configuration storage module; Verify that the fault data identifier exists in the mapping relationship and that the corresponding mapping entry is not marked as invalid; If the verification passes, the stored fault data reading operation continues; if the verification fails, feedback information indicating invalid fault data is generated and sent to the diagnostic device via the communication interaction module.

[0015] Furthermore, it also includes a data clearing response module for clearing faulty data. The methods for performing faulty data clearing include: The communication interaction module receives a clearing command from the diagnostic device carrying fault data identifiers and transmits it to the data clearing response module; The data clearing response module sends a fault status reset command to the downstream controller via the communication interaction module and receives the reset result from the downstream controller. If the reset is successful, the mapping entry corresponding to the fault data identifier in the configuration storage module is updated and marked as invalid; if the reset fails, the original mapping entry is retained. Based on the reset result, positive / negative response feedback information is generated and sent to the diagnostic device via the communication interaction module.

[0016] A method for optimizing the storage resource usage of fault data in a domain controller with diagnostic agent functionality, which achieves the second objective of this invention, includes: The system stores a list of valid byte numbers corresponding to interactive fault data, a preset total length, and a mapping relationship between stored fault data, fault data identifiers, and non-volatile memory addresses. The list of valid byte numbers is an ordered list that records the byte numbers corresponding to valid bytes in the interactive fault data, and the preset total length is the fixed byte length of the interactive fault data. When the domain controller acts as a diagnostic agent, it extracts the corresponding valid bytes from the interactive fault data in the volatile memory according to the byte numbers in the list of valid byte numbers, and then concatenates them in the order of the byte numbers to form stored fault data and stores it in the volatile memory. Stored fault data stored in volatile memory is transferred to non-volatile memory, and the correspondence between stored fault data, fault data identifier and non-volatile memory address in the mapping relationship is updated.

[0017] Furthermore, when the domain controller acts as a diagnostic agent, it receives a read command from the diagnostic device, reads the stored fault data corresponding to the fault data identifier from the non-volatile memory based on the fault data identifier and the mapping relationship carried in the read command, and then restores the stored fault data into the original interactive fault data according to the list of valid byte numbers and the preset total length, and feeds the original interactive fault data back to the diagnostic device.

[0018] A non-transitory computer-readable storage medium storing a computer program is provided to achieve the third objective of the present invention. The computer program, when executed by a processor, implements the steps of the method for optimizing the storage resource usage of fault data in a domain controller with diagnostic agent functionality.

[0019] A computer program product for achieving the fourth objective of the present invention includes a computer program / instruction that, when executed by a processor, implements the steps of the method for optimizing the storage resource usage of fault data in a domain controller with diagnostic agent functionality.

[0020] The beneficial effects of this invention include: This invention utilizes the diagnostic agent function of a domain controller to design a compression and decompression method that ensures a one-to-one correspondence between data identifiers used for reading and data identifiers used for storage, effectively reducing the actual storage space occupied by fault information. Simultaneously, in the evolution from distributed to integrated electrical and electronic architectures, it reduces reliance on changes to downstream controllers and diagnostic equipment, thereby shortening the corresponding cycle time and costs. Attached Figure Description

[0021] Figure 1 This is a diagram illustrating the data information contained in the frozen frame; Figure 2 This is a schematic diagram of communication between a distributed and domain control diagnostic system; Figure 3 This is a diagram illustrating the compression and decompression of the diagnostic agent. Figure 4 This is a diagram illustrating the conversion between data identifiers used for storage and data identifiers used for retrieval. Figure 5 This is a schematic diagram of the system described in this invention. Detailed Implementation

[0022] The following detailed embodiments are provided to explain the technical solutions of the present invention, so that those skilled in the art can understand the present invention. The scope of protection of the present invention is not limited to the following specific embodiments. Any modifications or improvements made by those skilled in the art that incorporate the technical solutions of the present invention but differ from the following detailed embodiments are also within the scope of protection of the present invention.

[0023] A method for optimizing the storage resource consumption of fault data in a domain controller with diagnostic agent functionality includes: The system stores a list of valid byte numbers corresponding to interactive fault data, a preset total length, and a mapping relationship between stored fault data, fault data identifiers, and non-volatile memory addresses. The list of valid byte numbers is an ordered list that records the byte numbers corresponding to valid bytes in the interactive fault data, and the preset total length is the fixed byte length of the interactive fault data. When the domain controller acts as a diagnostic agent, it extracts the corresponding valid bytes from the interactive fault data in the volatile memory according to the byte numbers in the list of valid byte numbers, and then concatenates them in the order of the byte numbers to form stored fault data and stores it in the volatile memory. Stored fault data stored in volatile memory is transferred to non-volatile memory, and the correspondence between stored fault data, fault data identifier and non-volatile memory address in the mapping relationship is updated. When the domain controller acts as a diagnostic agent, it receives a read command from the diagnostic device, reads the stored fault data corresponding to the fault data identifier from the non-volatile memory based on the fault data identifier and the mapping relationship carried in the read command, and then restores the stored fault data into the original interactive fault data according to the list of valid byte numbers and the preset total length, and feeds the original interactive fault data back to the diagnostic device.

[0024] The domain controller generates and stores fault information of downstream controllers through the diagnostic agent function, and at the same time replaces the downstream controllers in information interaction with diagnostic devices.

[0025] In one embodiment, the aforementioned diagnostic agent function specifically involves the domain controller collecting fault states and corresponding data information from downstream controllers via the communication bus. Upon receiving a fault enable status signal, it generates corresponding fault codes (DTCs) and freeze frame data, and stores them in the domain controller's non-volatile memory at an appropriate time. When the domain controller receives read and clear commands from external diagnostic devices, it executes the commands and responds according to information recognizable by the external diagnostic devices.

[0026] Specifically, the domain controller diagnostic agent function includes four processes: fault data generation, fault data storage, fault data read response, and fault data clearing response.

[0027] The domain controller diagnostic agent function needs to process data including the following two parts: first, the data identifier data actually stored in non-volatile storage space, referred to as stored fault data S, such as... Figure 3 The data shown in the two centrally located figures, such as the data corresponding to DID_a or DID_b, includes: secondly, data identifiers readable by diagnostic equipment, referred to as interactive fault data R, such as the data corresponding to DID_A or DID_B; the stored fault data corresponding to DID_a is derived from the compression of the interactive fault data corresponding to DID_A, and the stored fault data corresponding to DID_b is derived from the compression of the interactive fault data corresponding to DID_B. It can be seen that the number of stored fault data is the same as the number of interactive faults, but the byte length is smaller, resulting in lower space occupancy.

[0028] Specifically, a compression algorithm is used to extract the bytes containing the valid bits from the interactive fault data R and recombine them into the storage-type fault data S, thereby compressing the storage space requirement. Figure 4 As shown. Simultaneously, the total length of the interactive fault data and the mapping relationship of the bytes containing the effective bits are obtained before compression, serving as the algorithm input for restoring the stored fault data into interactive fault data.

[0029] In one embodiment, the method for implementing the compression algorithm to compress interactive fault data R into stored fault data S includes: Preset list of valid bits B = {(R m ,b k )}, where R m This represents the m-th byte of the fault data R, where m is the byte number and m∈[0,L-1], and L is the preset total length of the fault data R in bytes. k Represents byte R m The kth bit, k∈[0,7] and k=0 is the least significant bit and k=7 is the most significant bit. The list of valid bits B is determined by the vehicle fault diagnosis requirement specification and is used to identify the bit positions in the fault data that carry the key fault status and operating condition data. The specific contents of the preset total length L and the list of valid bits B are both stored in the preset configuration module of the domain controller. The preset configuration module is located in the fixed address area of ​​the domain controller RAM and the address range is defined by the domain controller hardware design manual. The interactive fault data R is fixed-length data that can be recognized by the diagnostic equipment, and its bytes are numbered sequentially from low to high address as R0, R1, ..., R L-1 The stored fault data S is the compressed target data to be stored, formed by concatenating valid bytes in sequence; the domain controller traverses all bytes R0~R0 of the interactive fault data R in ascending order of byte number. L-1 Perform a valid bit existence check on each byte, specifically for byte R. m Iterate through the bits b0~b7 in sequence. If any b... k The corresponding bit is the data storage bit for critical fault states or operating conditions specified in the vehicle fault diagnosis requirements specification (i.e., satisfying (R)). m ,b k If )∈B), then determine that the byte R m The byte is identified as a valid byte, and its byte number m is stored in the valid byte list E in traversal order; Extract the corresponding valid bytes from the interactive fault data R in the order of the valid byte list E, without modifying any bits within the valid bytes. Simultaneously, concatenate the extracted valid bytes in the same extraction order to form the stored fault data S=[ , ,…, ], where e0, e1, ..., e n-1 The byte number is in the list of valid bytes E, where n is the number of valid bytes and n ≤ L; the concatenated stored fault data S is continuous byte data without any extra padding bytes, and its total storage space length is n bytes, where n is the number of valid bytes in the list of valid bytes E and n < L. The domain controller directly stores the stored fault data into its RAM temporary storage area, and writes it into the domain controller's non-volatile storage space when the vehicle is powered off or in sleep mode.

[0030] For example, the preset total length of interactive fault data is set to L=8 bytes, and the bytes are numbered from low to high address as R0, R1, R2, R3, R4, R5, R6, R7. The list of valid bits determined by the vehicle model fault diagnosis requirement specification is B={(R1,b3),(R1,b5),(R3,b1),(R5,b0),(R5,b2),(R5,b4)}, meaning that only bytes R1, R3, and R5 contain valid bits. The specific values ​​of each byte in the original interactive fault data are: R0=0x00, R1=0x28, R2=0x00, R3=0x0 2. R4=0x00, R5=0x15, R6=0x00, R7=0x00; The domain controller traverses each byte in the order of R0 to R7, determines R1, R3, and R5 as valid bytes, and generates a list of valid bytes E=[1,3,5]; then, in the order of E, it completely extracts the byte data corresponding to R1, R3, and R5 from the interactive fault data to form the stored fault data R={S0=0x28, S1=0x02, S2=0x15}, with a total length of 3 bytes (n=3<L=8), and stores it in the domain controller RAM temporary storage area for subsequent writing to the non-volatile storage space.

[0031] In one embodiment, the fault data generation process refers to the downstream controller transmitting the fault status to the domain controller via the communication bus. The fault status includes at least three types: disabled (no fault), confirming (fault suspected, confirmation conditions not met), and enabled (fault confirmed). The domain controller's diagnostic agent module monitors the fault status of the downstream controller in real time. When the domain controller detects the rising edge of the fault enable status issued by the downstream controller (the triggering condition is defined by the vehicle model fault diagnosis strategy; for example, a fault duration ≥ 500ms is considered a rising edge of the enable status), it triggers fault information processing. It captures the operating condition data and fault status information at the fault trigger moment, writes them into the corresponding fields of the interactive fault data according to the format requirements of reading DID data, and stores them in the temporary buffer of the domain controller's RAM. Simultaneously, it calls the compression algorithm, based on the list B of valid bits corresponding to the fault, extracts the bytes containing the valid bits from the interactive fault data, reassembles them in a preset order to generate stored fault data, and stores it in the temporary storage area of ​​the domain controller's RAM. The address of the temporary storage area is independently distinguished from the address of the temporary buffer area, achieving data compression.

[0032] The fault data storage process refers to storing stored fault data in non-volatile storage space when the vehicle is powered off or in sleep mode. The domain controller's power management module monitors the vehicle's power status in real time. When a power-off or sleep signal is detected, the storage process is triggered. The domain controller writes the stored fault data from the RAM temporary storage area to the non-volatile storage space. The storage address is defined by the partitioning plan of the non-volatile storage space. Each stored fault data corresponds to a unique storage address, and the address mapping relationship is stored in the domain controller's address mapping table, thus completing the persistent storage of fault data.

[0033] In one embodiment, the fault data reading process refers to the diagnostic device sending a fault information reading command to the target controller through a diagnostic interface, and the domain controller needing to respond based on the interactive fault data. Specifically, the domain controller retrieves the stored fault data corresponding one-to-one with the interactive fault data from non-volatile memory space through an address mapping table and stores it in the instruction cache of the domain controller's RAM. It then uses a decompression algorithm to write the decompressed information into the interactive fault data and responds in a manner recognizable by the diagnostic device.

[0034] The fault data clearing process refers to the diagnostic device sending a fault information clearing command to the target controller through the diagnostic interface. The domain controller needs to send a fault state reset command to the downstream controller. If the fault state information fed back by the downstream controller changes from the enabled state to the disabled state, that is, the domain controller recognizes the falling edge of the enabled state, then it will respond positively as required by the diagnostic device and clear the corresponding stored fault data. Otherwise, it will respond negatively.

[0035] A positive response is a confirmation message sent by the domain controller to the diagnostic equipment after successfully executing the read or clear command issued by the diagnostic equipment. The format conforms to the ISO 14229 automotive diagnostic standard and includes a "command executed successfully" flag and corresponding fault data (for read commands) or a "data reset" flag (for clear commands), ensuring the diagnostic equipment can recognize the execution result. A negative response is an abnormal message sent by the domain controller to the diagnostic equipment when it fails to execute the read or clear command issued by the diagnostic equipment. The format also conforms to the ISO 14229 automotive diagnostic standard and includes a "command not executed" flag and a specific reason code (such as "fault not cleared," "data not found," "format error," etc.), providing the diagnostic equipment with a basis for troubleshooting.

[0036] This invention also provides a domain controller fault data storage resource utilization optimization system with diagnostic agent function, comprising: Configure storage module: used to store the list of valid byte numbers corresponding to interactive fault data, the preset total length, and the mapping relationship between stored fault data, fault data identifier and non-volatile memory address. The list of valid byte numbers is an ordered list that records the byte numbers corresponding to the valid bytes in the interactive fault data. The preset total length is the fixed byte length of the interactive fault data. Data parsing module: When the domain controller acts as a diagnostic agent, it captures the fault data of the downstream controller based on the received fault status of the downstream controller and stores it in the domain controller's volatile memory according to the set interactive fault data format. Data compression module: used to call the list of valid byte numbers from the configuration storage module, extract the corresponding valid bytes from the interactive fault data in the volatile memory according to the byte numbers in the list, and then concatenate them in the order of the byte numbers to form stored fault data and store it in the volatile memory. Data storage module: used to store fault data stored in volatile memory into non-volatile memory and update the mapping relationship.

[0037] In one embodiment, a data read response module is further included: when the domain controller acts as a diagnostic agent, based on the read command issued by the diagnostic device received by the domain controller, combined with the fault data identifier carried in the read command and the mapping relationship obtained from the configuration storage module, reads the stored fault data corresponding to the fault data identifier from the non-volatile memory, and then calls the list of valid byte numbers and the preset total length from the configuration storage module to restore the stored fault data into the original interactive fault data and respond to the diagnostic device.

[0038] In one embodiment, the method for splicing together stored fault data in the data compression module includes: Obtain a list of valid byte numbers from the configuration storage module and sort the byte numbers in the list in ascending order; According to the sorted byte numbers, extract the corresponding valid bytes one by one from the interactive fault data in volatile memory; The extracted valid bytes are concatenated sequentially according to the sorted byte number order to form continuous, unfilled stored fault data, which is then stored in volatile memory.

[0039] In one embodiment, the decompression method of the data reading response module to restore stored fault data to original interactive fault data includes: initializing an interactive fault data buffer with a length of the preset total length and filling all bytes with default values, determining the original byte position corresponding to each byte in the stored fault data according to the effective byte number list, and completely filling each byte of the stored fault data into the corresponding original byte position of the buffer to form the original interactive fault data.

[0040] In one embodiment, the triggering condition for the data storage module to store fault data into the non-volatile memory includes: the vehicle is in a power-off or sleep state.

[0041] In one embodiment, the method for storing stored fault data and saving mapping relationships in the data storage module includes: Read the stored fault data to be stored and the corresponding fault data identifier from the volatile memory; Allocate a free storage address in the non-volatile storage space, and write the storage-type fault data into the free storage address; Based on the fault data identifier, stored fault data, and the actual allocated free storage address, update the corresponding mapping relationship in the configuration storage module.

[0042] In one embodiment, before reading the stored fault data, the data read response module further includes a validity check of the fault data identifier, and the check method includes: Extract the fault data identifier from the read command, and call the mapping relationship from the configuration storage module; Verify that the fault data identifier exists in the mapping relationship and that the corresponding mapping entry is not marked as invalid; If the verification passes, the stored fault data reading operation continues; if the verification fails, feedback information indicating invalid fault data is generated and sent to the diagnostic device via the communication interaction module.

[0043] In one embodiment, a data clearing response module is further included, used to clear fault data, and the method for performing fault data clearing includes: The communication interaction module receives a clearing command from the diagnostic device carrying fault data identifiers and transmits it to the data clearing response module; The data clearing response module sends a fault status reset command to the downstream controller via the communication interaction module and receives the reset result from the downstream controller. If the reset is successful, the mapping entry corresponding to the fault data identifier in the configuration storage module is updated and marked as invalid; if the reset fails, the original mapping entry is retained. Based on the reset result, positive / negative response feedback information is generated and sent to the diagnostic device via the communication interaction module.

[0044] This invention also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the various steps of the method described in this invention.

[0045] This invention also provides a non-transitory computer-readable storage medium storing a computer program. The computer program includes program instructions that, when executed by a processor, implement the various steps of the method described in this invention, which will not be elaborated further here.

[0046] The computer-readable storage medium can be the data transmission apparatus or the internal storage unit of a computer device provided in any of the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium can also be the external storage device of the computer device, such as the plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc. equipped on the computer device.

[0047] Furthermore, the computer-readable storage medium may include both internal storage units and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium may also be used to temporarily store data that is to be output or has already been output.

[0048] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0049] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0050] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0051] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0052] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

Claims

1. A domain controller fault data storage resource utilization optimization system with diagnostic agent function, characterized in that, include: Configure storage module: used to store the list of valid byte numbers corresponding to interactive fault data, the preset total length, and the mapping relationship between stored fault data, fault data identifier and non-volatile memory address. The list of valid byte numbers is an ordered list that records the byte numbers corresponding to the valid bytes in the interactive fault data. The preset total length is the fixed byte length of the interactive fault data. Data parsing module: When the domain controller acts as a diagnostic agent, it is used to capture the fault data of the downstream controller based on the received fault status of the downstream controller, and store it in the domain controller's volatile memory according to the set interactive fault data format. Data compression module: used to call the list of valid byte numbers from the configuration storage module, extract the corresponding valid bytes from the interactive fault data in the volatile memory according to the byte numbers in the list, and then concatenate them in the order of the byte numbers to form stored fault data and store it in the volatile memory. Data storage module: used to store fault data stored in volatile memory into non-volatile memory and update the mapping relationship.

2. The domain controller fault data storage resource utilization optimization system with diagnostic agent function as described in claim 1, characterized in that, The method for splicing together stored fault data in the data compression module includes: Obtain a list of valid byte numbers from the configuration storage module and sort the byte numbers in the list in ascending order; According to the sorted byte numbers, extract the corresponding valid bytes one by one from the interactive fault data in volatile memory; The extracted valid bytes are concatenated sequentially according to the sorted byte number order to form continuous, unfilled stored fault data, which is then stored in volatile memory.

3. The domain controller fault data storage resource utilization optimization system with diagnostic agent function as described in claim 1, characterized in that, It also includes a data read response module: when the domain controller acts as a diagnostic agent, based on the read command issued by the diagnostic device received by the domain controller, combined with the fault data identifier carried in the read command and the mapping relationship obtained from the configuration storage module, it reads the stored fault data corresponding to the fault data identifier from the non-volatile memory, and then calls the list of valid byte numbers and the preset total length from the configuration storage module to restore the stored fault data into the original interactive fault data and respond to the diagnostic device.

4. The domain controller fault data storage resource utilization optimization system with diagnostic agent function as described in claim 3, characterized in that, The decompression method of the data reading response module to restore the stored fault data to the original interactive fault data includes: initializing an interactive fault data buffer with a length of the preset total length and filling all bytes with default values, determining the original byte position corresponding to each byte in the stored fault data according to the effective byte number list, and completely filling each byte of the stored fault data into the corresponding original byte position of the buffer to form the original interactive fault data.

5. The domain controller fault data storage resource utilization optimization system with diagnostic agent function as described in claim 1, characterized in that, The triggering conditions for the data storage module to store fault data into the non-volatile memory include: the vehicle status is a preset state.

6. The domain controller fault data storage resource utilization optimization system with diagnostic agent function as described in claim 1, characterized in that, The method for storing stored fault data and saving mapping relationships in the data storage module includes: Read the stored fault data to be stored and the corresponding fault data identifier from the volatile memory; Allocate a free storage address in the non-volatile storage space, and write the storage-type fault data into the free storage address; Based on the fault data identifier, stored fault data, and the actual allocated free storage address, update the corresponding mapping relationship in the configuration storage module.

7. The domain controller fault data storage resource utilization optimization system with diagnostic agent function as described in claim 1 or 6, characterized in that, It also includes a data clearing response module for clearing faulty data. The methods for performing faulty data clearing include: The communication interaction module receives a clearing command from the diagnostic device carrying fault data identifiers and transmits it to the data clearing response module; The data clearing response module sends a fault status reset command to the downstream controller via the communication interaction module and receives the reset result from the downstream controller. If the reset is successful, the mapping entry corresponding to the fault data identifier in the configuration storage module is updated and marked as invalid; if the reset fails, the original mapping entry is retained. Based on the reset result, positive / negative response feedback information is generated and sent to the diagnostic device via the communication interaction module.

8. A method for optimizing the storage resource consumption of fault data in a domain controller with diagnostic agent functionality as described in claim 1, characterized in that, include: The system stores a list of valid byte numbers corresponding to interactive fault data, a preset total length, and a mapping relationship between stored fault data, fault data identifiers, and non-volatile memory addresses. The list of valid byte numbers is an ordered list that records the byte numbers corresponding to valid bytes in the interactive fault data, and the preset total length is the fixed byte length of the interactive fault data. When the domain controller acts as a diagnostic agent, it extracts the corresponding valid bytes from the interactive fault data in the volatile memory according to the byte numbers in the list of valid byte numbers, and then concatenates them in the order of the byte numbers to form stored fault data and stores it in the volatile memory. Stored fault data stored in volatile memory is transferred to non-volatile memory, and the correspondence between stored fault data, fault data identifier and non-volatile memory address in the mapping relationship is updated.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the domain controller fault data storage resource occupancy optimization method with diagnostic agent function as described in claim 8.

10. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the domain controller fault data storage resource occupancy optimization method with diagnostic agent function as described in claim 8.

Images