Vehicle diagnostic parameter processing method

Abstract

The present invention relates to the fields of data processing and vehicle technology, and in particular to a method for processing diagnostic parameters of a vehicle, the method comprising: obtaining diagnostic parameters input into a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in the vehicle, and the target platform is one of the following: a diagnostic platform, a product system platform, or a vehicle model platform; performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include verification-passing parameters and verification-failure parameters; updating a cache area of ​​the target platform based on the verification-passing parameters, and comparing the differences between the cache area data and the platform database data to obtain difference data; and updating the platform database of the target platform based on the difference data. The present invention solves the technical problem in the related art of using Excel spreadsheets to manage diagnostic parameters, which leads to omissions and errors in data transmission.

Description

Technical Field

[0001] The embodiments of the present invention relate to the fields of data processing and vehicle technology, and in particular to a method for processing vehicle diagnostic parameters. Background Art

[0002] With the advancement of automotive electronics and intelligent systems, the management of on-board diagnostic parameters has become increasingly complex, especially with the prevalence of domain control architectures. Diagnostic parameters, including diagnostic trouble codes (DTCs), data identifiers (DIDs), and communication parameters, are critical to ensuring the proper operation of vehicle electronic systems and troubleshooting.

[0003] Currently, many OEMs use Excel spreadsheets or rudimentary online systems to manage diagnostic parameters. This can easily lead to information omissions and data errors during the data transfer process between products and models. This not only increases the burden of manual intervention but also reduces the efficiency of data updates, limiting the advancement of intelligent automotive diagnostic management. Summary of the Invention

[0004] An embodiment of the present invention provides a vehicle diagnostic parameter processing method, which aims to solve the technical problem in the related art of using Excel spreadsheets to manage diagnostic parameters, which leads to omissions and errors in data transmission.

[0005] According to one aspect of an embodiment of the present invention, a method for processing diagnostic parameters of a vehicle is provided, comprising: obtaining diagnostic parameters input into a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in the vehicle, and the target platform is one of the following: a diagnostic platform, a product system platform, and a vehicle model platform, the diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters, the product system platform is used to separately manage the diagnostic parameters corresponding to different products or systems, and the vehicle model platform is used to separately manage the diagnostic parameters corresponding to different vehicle models; performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, wherein the verification result includes parameters that passed the verification and parameters that failed the verification; updating a cache area of ​​the target platform based on the parameters that passed the verification, and comparing the difference between the cache area data and the platform database data to obtain difference data, wherein the cache area data is the data stored in the updated cache area, and the platform database data is the data stored in the platform database of the target platform; and updating the platform database of the target platform based on the difference data.

[0006] Based on the above technical solution as a whole, by verifying the input diagnostic parameters, the correctness and standardization of the input parameters are ensured, and format and logical errors in data transmission are reduced. At the same time, by storing the verified diagnostic parameters in the cache area, a temporary and secure data storage environment is provided, which facilitates data review and change management and avoids data loss during database updates. In addition, the cross-platform synchronization mechanism of the present invention ensures the consistency and accuracy of all relevant platform databases, greatly improves the reusability and sharing of data, and avoids the errors and inefficiencies caused by manual updates.

[0007] According to another aspect of an embodiment of the present invention, a vehicle diagnostic parameter processing device is also provided, including: an acquisition module for acquiring diagnostic parameters input into a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in a vehicle; a verification module for performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, wherein the verification result includes verification-passed parameters and verification-failed parameters; a comparison module for updating a cache area of ​​the target platform based on the verification-passed parameters, and comparing the difference between the cache area data and the platform database data to obtain difference data, wherein the cache area data is the data stored in the updated cache area, and the platform database data is the data stored in the platform database of the target platform; and an update module for updating the platform database of the target platform based on the difference data.

[0008] According to another aspect of an embodiment of the present invention, a vehicle diagnostic system is provided. The vehicle diagnostic system is configured to execute any one of the above vehicle diagnostic parameter processing methods.

[0009] According to another aspect of an embodiment of the present invention, a vehicle is provided, which is used to execute any one of the above-mentioned vehicle diagnostic parameter processing methods.

[0010] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute any of the above-mentioned vehicle diagnostic parameter processing methods when running on a computer or processor.

[0011] According to another aspect of an embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute any of the above vehicle diagnostic parameter processing methods.

[0012] In an embodiment of the present invention, diagnostic parameters are input to a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in a vehicle, and the target platform is one of the following: a diagnostic platform, a product system platform, or a vehicle model platform; the diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters; the product system platform is used to separately manage the diagnostic parameters corresponding to different products or systems; and the vehicle model platform is used to separately manage the diagnostic parameters corresponding to different vehicle models; data verification is performed on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include verification-passing parameters and verification-failed parameters; a cache of the target platform is updated based on the verification-passing parameters, and the difference between the cache data and the platform database data is compared to obtain difference data, wherein the cache data is the data stored in the updated cache, and the platform database data is the data stored in the platform database of the target platform; and the platform database of the target platform is updated based on the difference data. Thus, the purpose of building a standardized and intelligent diagnostic parameter management system is achieved, thereby achieving accurate data transmission and efficient change management, enhancing system stability and diagnostic reliability, and solving the technical problem of using Excel spreadsheets to manage diagnostic parameters in the related art, which leads to omissions and errors in data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a flow chart of a vehicle diagnostic parameter processing method provided by one embodiment of the present invention;

[0014] Figure 2 is a schematic structural diagram of a vehicle diagnostic system provided by one embodiment of the present invention;

[0015] Figure 3 This is a schematic diagram of the overall process of changing and publishing diagnostic parameters provided by an embodiment of the present invention;

[0016] Figure 4 This is a schematic diagram of a change impact analysis process according to an embodiment of the present invention;

[0017] Figure 5 is a structural diagram of a vehicle diagnostic parameter processing device provided by an embodiment of the present invention;

[0018] Figure 6 is a structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0019] In order to make the technical problems, technical solutions and beneficial effects solved by the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0020] In order to help those skilled in the art better understand the present technical solution, the following terminology is explained:

[0021] Diagnostic parameters are key data indicators used by automotive electronic control units (ECUs) and in-vehicle network systems to monitor, diagnose, and maintain vehicle health. Diagnostic parameters play a central role in vehicle fault detection, condition monitoring, and repair services, helping technicians quickly locate problems and take appropriate action. The comprehensiveness and accuracy of diagnostic parameters directly impact vehicle diagnostic efficiency and maintenance quality.

[0022] Diagnostic parameters include but are not limited to the following categories:

[0023] Diagnostic Trouble Code (DTC): Used to indicate potential vehicle faults. Each DTC has a specific meaning and can help identify the specific type of fault detected in the ECU.

[0024] Data Identifier (DID): used to identify and obtain specific data streams in the ECU, such as engine temperature, speed, oil pressure, etc.

[0025] Freeze Frame Data: When a DTC is triggered, the ECU will record and save various operating parameters of the vehicle at that time. This data is called freeze frame data. Freeze frame data helps to deeply analyze the specific circumstances when the fault occurs.

[0026] Communication parameters: Parameters related to in-vehicle network communication, such as the baud rate and signal transmission protocol of the Controller Area Network (CAN) bus, are crucial for network diagnosis and data exchange.

[0027] Diagnostic address: The unique address of the ECU in the network, used for the diagnostic tool to communicate with the specific ECU.

[0028] Security algorithms: Algorithms used to protect diagnostic data and communications from unauthorized access and modification.

[0029] Service response parameters: Parameters related to specific diagnostic services, such as read DTC, clear DTC, etc.

[0030] Checksum parameters: Parameters that ensure the integrity and correctness of data transmission, such as the cyclic redundancy check (CRC) checksum.

[0031] Excel: is a widely used spreadsheet software that provides users with powerful data management and analysis tools. It is widely used in finance, statistics, engineering, education and almost all fields that require data management and calculation.

[0032] Electronic Control Unit (ECU): It is one of the core components of the vehicle's electronic system and is widely used in various vehicle systems, such as the engine control system, braking system, steering system, body stability control system, entertainment information system and even advanced driver assistance system. It is mainly responsible for monitoring and analyzing various signals from vehicle sensors, and controlling the actions of actuators accordingly to achieve precise control of vehicle functions.

[0033] Diagnostic parameters are important indicators for troubleshooting and analyzing vehicle component faults. With the development of intelligent vehicles, in-vehicle systems are becoming increasingly intelligent. With the application of domain control architecture, the design of vehicle diagnostic parameters has become more complex and extensive, and the parameter management requirements have also become higher. It is necessary to introduce more intelligent management methods to improve the efficiency and quality of diagnostic parameter design.

[0034] Currently, major OEMs manage diagnostic parameters using Excel spreadsheets, with some also implementing system management. However, these only update model diagnostic parameters online. Both product and supplier management is platform-based, while OEM management and output are based on model. This creates difficulties in reusing and sharing diagnostic parameters, and makes it difficult to accurately identify the impact of parameter changes. This makes information omissions and data errors common during the data transfer process from product to model.

[0035] The embodiment of the present invention provides a method for processing vehicle diagnostic parameters. Figure 1 , including the following steps:

[0036] S10: Acquire diagnostic parameters input to a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in a vehicle. The target platform is one of the following: a diagnostic platform, a product system platform, or a vehicle model platform. The diagnostic platform is used to manage functional requirements of a vehicle diagnostic system and parameter attributes of diagnostic parameters. The product system platform is used to separately manage diagnostic parameters corresponding to different products or systems. The vehicle model platform is used to separately manage diagnostic parameters corresponding to different vehicle models.

[0037] In this embodiment of the present invention, diagnostic parameters are managed across three platforms. In addition to the conventional vehicle platform, a product system platform and a diagnostic platform are also newly added. In step S10 above, the target platform can be the diagnostic platform, the product system platform, or the vehicle platform, determined based on the type and source of the input diagnostic parameters.

[0038] Among them, the diagnostic platform is responsible for managing the functional requirements of the vehicle diagnostic system and the common parameter attributes of the diagnostic parameters, such as the diagnostic address, communication parameters, etc., that is, the diagnostic platform is responsible for managing the common requirements and attributes related to the entire vehicle.

[0039] The product system platform is used to manage the diagnostic parameters corresponding to different products or systems respectively. That is, the product system platform is responsible for managing specific diagnostic parameters for different products or systems, such as power systems, chassis systems, etc.

[0040] The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively, that is, the vehicle model platform is responsible for managing the diagnostic parameters related to a specific vehicle model, including diagnostic parameters of vehicle model-specific attributes.

[0041] Diagnostic parameters are used to monitor the health and fault conditions of electronic control systems in vehicles, such as diagnostic trouble codes (DTCs), data identifiers (DIDs), freeze frame data, etc.

[0042] Exemplarily, the diagnostic parameters input to the target platform can be edited online or imported in batches. For example, the system can receive diagnostic parameters input from a diagnostic engineer, system engineer, or product engineer, and determine the target platform based on the input platform.

[0043] In the present invention, by obtaining the diagnostic parameters input into the target platform, it is ensured that the input of the diagnostic parameters is an organized process. Engineers with different roles input the parameters into the correct platform according to their authority and responsibilities, avoiding data confusion and erroneous input, and improving the efficiency and accuracy of data management.

[0044] S12: performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include parameters that passed the verification and parameters that failed the verification;

[0045] In embodiments of the present invention, validation rules are predefined validation standards and specifications for each platform, used to ensure the correctness of data format, standardization, and relationships. For example, validation rules can be developed based on different platform requirements and On-Board Diagnostic System Object Database (ODX) specifications to verify data input. Different platforms may have different validation rules.

[0046] The verification result is the feedback result after data verification. That is, after the verification process is completed, the vehicle diagnostic system will generate a verification result. The verification result includes diagnostic parameters that passed the verification (parameters that passed the verification) and diagnostic parameters that failed the verification (parameters that failed the verification). That is, the verification result will clearly indicate which parameters passed the verification and which failed.

[0047] In this invention, the vehicle diagnostic system verifies input diagnostic parameters according to the target platform's validation rules to check whether the parameters meet preset standards. This rigorous data validation ensures the correctness and standardization of input parameters, reducing formatting and logical errors in data transmission. Furthermore, automated validation reduces the time and workload of manual checks, improves data processing efficiency, and allows engineers to focus more on innovation and problem solving rather than data error correction.

[0048] S14: updating the cache area of ​​the target platform based on the verification parameters, and comparing the differences between the cache area data and the platform database data to obtain difference data, wherein the cache area data is the data stored in the updated cache area, and the platform database data is the data stored in the platform database of the target platform;

[0049] In an embodiment of the present invention, the cache area of ​​the target platform is a temporary storage area for storing verified diagnostic parameters for further processing and confirmation. It is understandable that the verified diagnostic parameters have not yet been formally incorporated into the platform database, but can be viewed, edited and managed in the cache area before further review and processing. That is, the establishment of the cache area is mainly to provide a buffer zone so that the diagnostic parameters that are about to change can be preliminarily processed and reviewed before the platform database is officially updated. Exemplarily, different target platforms may correspond to different cache areas.

[0050] Each platform (such as the diagnostic platform, product system platform, and vehicle model platform) has its corresponding platform database, which is used to store the diagnostic parameter data and attribute information of the platform. The platform database contains all verified and reviewed diagnostic parameters. The platform database data is the diagnostic parameter data stored in the platform database corresponding to the target platform.

[0051] Difference data refers to the difference between the cache data and the platform database data. By comparing the cache data with the platform database data, the vehicle diagnostic system identifies differences between the two, including but not limited to the addition, modification, or deletion of diagnostic parameters. It is understood that this difference data forms the basis for subsequent change records, which guide the formal modification of diagnostic parameters.

[0052] In the present invention, the vehicle diagnostic system updates the verified diagnostic parameters to the cache area of ​​the target platform. By using the cache area, the data being modified can be effectively isolated from the official platform database, avoiding database damage or data inconsistency problems caused by uncertainties that may exist during the data change process.

[0053] At the same time, the vehicle diagnostic system compares the data in the cache with the existing diagnostic parameters in the platform database to identify any discrepancies, such as newly added, modified, or deleted parameters. This process of comparing discrepant data provides the ability to track the history of diagnostic parameter changes, allowing any diagnostic parameter modifications to be clearly recorded, enhancing the transparency and traceability of data management. As can be seen, the above steps ensure the accuracy and security of data changes while also facilitating subsequent change analysis and review.

[0054] S16: Update the platform database of the target platform based on the difference data.

[0055] In the present invention, the vehicle diagnostic system will also update the platform database of the target platform based on the difference data obtained above. That is, all modified, newly added or confirmed deleted diagnostic parameters will be reflected in the latest database version of the target platform.

[0056] This update of the target platform's database based on the difference data formally records the diagnostic parameters, ensuring that parameter changes are permanently stored for future query and application, while also helping to maintain data accuracy and system consistency. Furthermore, updating the platform database ensures that all stakeholders (such as diagnostic engineers and system engineers) have the latest diagnostic parameters, improving the efficiency of the entire team.

[0057] As can be seen, this invention achieves accurate output of vehicle diagnostic parameters and platform-based management of diagnostic parameters and products through data linkage between the diagnostic platform, product system platform, and vehicle platform. This helps improve the efficiency of diagnostic parameter design and enhance the quality of diagnostic data. In other words, this invention ensures high data accuracy and standardization, improves the efficiency and transparency of data processing, and ultimately enhances the stability and reliability of the entire vehicle diagnostic system.

[0058] Compared to traditional solutions, this invention verifies input diagnostic parameters, ensuring their accuracy and standardization, reducing formatting and logic errors in data transmission. Furthermore, by storing verified diagnostic parameters in a cache, this invention provides a temporary, secure data storage environment, facilitating data review and change management, and avoiding data loss during database updates.

[0059] In an embodiment of the present invention, diagnostic parameters are input to a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in a vehicle, and the target platform is one of the following: a diagnostic platform, a product system platform, or a vehicle model platform; the diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters; the product system platform is used to separately manage the diagnostic parameters corresponding to different products or systems; and the vehicle model platform is used to separately manage the diagnostic parameters corresponding to different vehicle models; data verification is performed on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include verification-passing parameters and verification-failed parameters; a cache of the target platform is updated based on the verification-passing parameters, and the difference between the cache data and the platform database data is compared to obtain difference data, wherein the cache data is the data stored in the updated cache, and the platform database data is the data stored in the platform database of the target platform; and the platform database of the target platform is updated based on the difference data. Thus, the purpose of building a standardized and intelligent diagnostic parameter management system is achieved, thereby achieving accurate data transmission and efficient change management, enhancing system stability and diagnostic reliability, and solving the technical problem of using Excel spreadsheets to manage diagnostic parameters in the related art, which leads to omissions and errors in data transmission.

[0060] Optionally, in step S16, updating the platform database of the target platform based on the difference data includes the following execution steps:

[0061] Step S161: In response to receiving a diagnostic parameter change request for a target platform, a change record is generated based on the difference data, and a change impact analysis is generated based on the data impact scope and the change operation type. The change record is used to record the modification, addition, or deletion of the diagnostic parameter. The data impact scope is used to indicate the impact scope of the diagnostic parameter change on different platforms and vehicle models. The change impact analysis is used to record the impact scope of the target platform's diagnostic parameter change on other platforms except the target platform.

[0062] S162: Update the platform database of the target platform based on the change record and change impact analysis.

[0063] In an embodiment of the present invention, the diagnostic parameter change application is a diagnostic parameter change request submitted by a demander (such as a diagnostic engineer, system engineer, or product engineer), which aims to modify, add, or delete one or more diagnostic parameters on the target platform.

[0064] The change log is used to record in detail every change of diagnostic parameters, including the time of change, operation type (modification, addition, deletion), specific differences in data before and after the change, etc., which are not restricted here to facilitate traceability and analysis.

[0065] The data impact range can reflect which platforms or models will be affected by a specific diagnostic parameter change, that is, the diagnostic parameters of which related platforms or models may need to be updated or adjusted accordingly due to this diagnostic parameter change, helping to determine which platforms and models need to be updated.

[0066] Change impact analysis is used to record in detail the impact of changes in the diagnostic parameters of the target platform on other platforms, including changes in the reference relationships of the diagnostic parameters.

[0067] Based on the change history and data impact range, the vehicle diagnostic system automatically analyzes and records the impact of diagnostic parameter changes on other platforms and models in the entire vehicle diagnostic system architecture, except for the target platform, including a list of parameters that may need to be updated, a list of models or ECUs, etc.

[0068] In the present invention, when the vehicle diagnostic system receives an application for a diagnostic parameter change for a target platform, it will generate a change record based on the aforementioned difference data and analyze the potential impact of this diagnostic parameter change on other platforms. The generation of change records provides a complete history of diagnostic parameter changes, facilitates future inquiries and audits, and ensures the transparency and traceability of data changes. Change impact analysis can inform in advance of the possible impact of changes on the entire vehicle diagnostic system, helping decision makers evaluate the necessity and impact of changes, and thus make more comprehensive approval decisions. By automatically analyzing the impact of changes, the vehicle diagnostic system can notify relevant platforms and models to make necessary updates, avoiding manual notifications and data synchronization, and saving a lot of time and human resources. At the same time, the generation process of change records and change impact analysis helps to maintain the consistency of diagnostic parameters for all platforms and models in the entire system architecture, and prevent system failures or diagnostic errors caused by parameter changes.

[0069] Based on the change record and the results of the change impact analysis, the vehicle diagnostic system automatically updates the platform database of the target platform. For example, based on the change record, the vehicle diagnostic system applies approved diagnostic parameter modifications, additions, or deletions to the platform database of the target platform. For example, if the change record indicates a modification to a specific DTC description, this modification will be implemented in the platform database. If the change impact analysis indicates that the change also affects other platforms or vehicle models, the vehicle diagnostic system automatically synchronizes the modifications described in the change record with the platform databases of those platforms, ensuring consistent and accurate diagnostic parameters for all relevant platforms.

[0070] In this invention, the vehicle diagnostic system updates the target platform's platform database based on change records and change impact analysis. This cross-platform synchronization ensures consistent diagnostic parameter data across all relevant platforms, preventing diagnostic errors or system failures caused by inconsistent data. Furthermore, the automated data update and cross-platform synchronization process significantly reduces the need for manual intervention, improves data update efficiency, and reduces error rates.

[0071] Thus, the present invention intelligently manages diagnostic parameter changes and verification processes through data linkage between the diagnostic platform, product system platform, and vehicle platform. This enables accurate output of vehicle diagnostic parameters and platform-based management of diagnostic parameters and products, helping to improve the efficiency of diagnostic parameter design and enhance diagnostic data quality. As can be seen, the present invention ensures high data accuracy and standardization, enhances the efficiency and transparency of data processing, and achieves seamless data synchronization across platforms and vehicle models, providing strong support for decision-making and ultimately enhancing the stability and reliability of the entire vehicle diagnostic system.

[0072] Compared to traditional solutions, this invention automatically identifies and analyzes the impact of parameter changes on other platforms and models, generating change records and impact analysis reports. This ensures transparency and traceability of changes and reduces missed updates to data across platforms. Furthermore, the invention's cross-platform synchronization mechanism enables intelligent, synchronized updates of changed parameters, ensuring consistency and accuracy across all relevant platform databases. This significantly improves data reusability and sharing, and avoids the errors and inefficiencies associated with manual updates.

[0073] Optionally, in step S10, obtaining the diagnostic parameters input to the target platform includes the following execution steps:

[0074] Step S101 , in response to the target platform being a diagnostic platform, obtaining diagnostic parameters to be imported into the diagnostic platform based on a predefined template or a product data exchange database, or obtaining diagnostic parameters to be input into the diagnostic platform based on an online editing application;

[0075] Step S102 , in response to the target platform being a product system platform, obtaining diagnostic parameters to be imported into the product system platform based on a predefined template or a product data exchange database, or obtaining diagnostic parameters to be input into the product system platform based on an online editing application;

[0076] Step S103 : in response to the target platform being a vehicle model platform, obtaining diagnostic parameters input to the vehicle model platform based on the online editing application.

[0077] In the embodiment of the present invention, the vehicle diagnostic system has three platforms, each of which has a demand entry, and diagnostic parameters can be input from different entries according to different needs.

[0078] The predefined template is usually an Excel spreadsheet or a file in a similar format, which is used to batch import diagnostic parameter data that conforms to a specific format, facilitating quick data input.

[0079] The Product Data Exchange (PDX) database is a standardized data format and database used in the field of vehicle technology to store and exchange information related to on-board diagnostic systems. It supports the import of database files related to vehicle diagnostics, provides a standardized data input method, and enhances data standardization and interoperability.

[0080] The online editing application allows users to edit and input diagnostic parameters directly on the vehicle diagnostic system interface. It is suitable for modifying or adding small amounts of data, and improves the flexibility and immediacy of input.

[0081] Specifically, when the target platform is a diagnostic platform, the vehicle diagnostic system provides two data input methods: batch import of data using predefined templates, or direct data entry through an online editing application. These two methods ensure that the diagnostic platform can efficiently and accurately receive and manage diagnostic parameters.

[0082] As can be seen, batch import, through predefined templates or PDX databases, accelerates the data entry process, reduces manual input errors and workload, and thus improves data entry efficiency. The online editing application provides the ability to modify and add data instantly, increasing the flexibility and responsiveness of data management and enabling flexible data management.

[0083] When the target platform is a product system platform, the vehicle diagnostic system also supports two data input methods: batch import of predefined templates and online editing application, ensuring that the product system platform can efficiently and accurately manage its specific diagnostic parameters.

[0084] It can be seen that the standardized input method improves the reusability of diagnostic parameters between similar products or systems, promoting data reuse. The diagnostic parameters of the product system platform can be imported in batches through templates or edited online, significantly improving the efficiency and accuracy of data management and enhancing management efficiency.

[0085] For vehicle platform, the vehicle diagnostic system only provides input for online editing applications, which is suitable for direct editing and management of vehicle-specific attributes, ensuring that the diagnostic parameters of the vehicle platform can flexibly adapt to the needs of different vehicle models.

[0086] As can be seen, the online editing application addresses vehicle-specific diagnostic requirements, ensuring that diagnostic parameters are precisely adapted to each vehicle model. Furthermore, direct online editing of vehicle-specific attributes accelerates the customization process of vehicle diagnostic parameters and improves the immediacy and flexibility of data management.

[0087] Optionally, in step S12, data verification is performed on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, which includes the following execution steps:

[0088] In step S121 , the target platform's verification engine is used to perform data verification on the diagnostic parameters based on the target platform's verification rules to obtain verification results, wherein the verification rules are used to verify the data format, data standardization, and data association relationship of the diagnostic parameters.

[0089] In an embodiment of the present invention, after performing data verification on diagnostic parameters based on the verification rules of the target platform and obtaining verification results, the target platform's verification engine can be used to perform data verification on the diagnostic parameters based on the verification rules of the target platform. It is understood that different platforms have corresponding verification engines, which can be understood as a software module responsible for executing data verification rules and checking the correctness of diagnostic parameters. The verification engine can be pre-built or customized to meet the verification requirements of different platforms.

[0090] Validation rules can be a set of well-defined rules used to verify that the data format, data standardization, and data relationships of diagnostic parameters meet standards and requirements. The design of validation rules should take into account industry standards such as the ODX specification and the logical relationships between diagnostic parameters.

[0091] Data format refers to the structure and presentation of diagnostic parameters, ensuring they can be correctly identified and processed by the vehicle diagnostic system. Data standardization typically refers to whether data conforms to specific industry standards or internal regulations, such as the ODX specification, ensuring data uniformity and accuracy. Data associations refer to the logical connections between diagnostic parameters and other parameters or vehicle diagnostic systems, ensuring correct data reference and interaction within the vehicle diagnostic system.

[0092] In this invention, the vehicle diagnostic system automatically verifies input diagnostic parameters using the target platform's validation engine according to predefined validation rules. This includes checking for correct data formatting, compliance with the ODX specification, and the logical relationships between parameters. The validation results clearly indicate whether the data passed validation, as well as the specific reasons for failure or the location of the error.

[0093] This automated verification process effectively prevents data format errors, non-compliant issues, and correlation errors, ensuring data quality. Furthermore, by verifying the standardization and correlation of diagnostic parameters, data issues that could lead to vehicle diagnostic system failures can be identified in advance, preventing them from occurring.

[0094] Optionally, the vehicle diagnostic parameter processing method further includes the following execution steps:

[0095] Step S122: Generate a verification report based on the verification failed parameters, wherein the verification report is used to list the verification failed parameters and the problems corresponding to the verification failed parameters.

[0096] In an embodiment of the present invention, after performing data verification on the diagnostic parameters and obtaining verification results, a verification report is generated based on the parameters that failed verification. The verification report is a document generated by the verification engine that lists all parameters that failed verification and their specific problem conditions. The verification report provides detailed error information, including parameter identification, error type, error location, etc. (not limited here), to facilitate users to quickly locate and resolve errors.

[0097] In this invention, after completing the data verification of diagnostic parameters, if any parameters fail verification, the verification engine will generate a verification report. This report lists all parameters that failed verification in detail and provides a description of the error for each parameter. Based on the information in the report, users or system administrators can quickly locate the problematic parameters and understand the nature of the problem (for example, data format errors, non-compliance with standards, or incorrect associations), and then take appropriate measures to correct them.

[0098] As a result, verification reports provide clear problem location and description, greatly improving error correction efficiency, avoiding blind modifications and repeated verification, and improving error location and correction efficiency. At the same time, by generating and providing feedback on verification reports in a timely manner, the impact of data errors on subsequent system operations can be avoided, preventing system failures before they occur.

[0099] Optionally, in step S162, updating the platform database of the target platform based on the change record and the change impact analysis includes the following execution steps:

[0100] Step S1621: Determine the target audit object based on the data impact scope and the change operation type, and use the target audit object to audit the diagnostic parameter change application;

[0101] Step S1622 : In response to the diagnostic parameter change application being approved, the platform database is updated based on the change record and the change impact analysis.

[0102] In this embodiment of the present invention, the target audit object is determined based on the data impact scope and the change operation type, and is a specific role or person who needs to approve the change application. For example, if the change affects the product system platform, the administrator of the product system platform will become the target audit object.

[0103] In this invention, when updating the target platform's platform database based on change records and change impact analysis, the vehicle diagnostic system first analyzes the impact scope and operation type of the diagnostic parameter changes. Based on this analysis, it identifies specific roles or individuals who need to participate in the review as target review subjects. These target review subjects then conduct a detailed review of the submitted change request to ensure its rationality, necessity, and safety. This involvement of the target review subjects ensures that every change is evaluated by professionals, preventing unauthorized changes and enhancing regulatory compliance.

[0104] Afterward, once the diagnostic parameter change request passes review by the target audit entity, the vehicle diagnostic system automatically updates the database of the corresponding platform based on the change record and the results of the change impact analysis. This means that the specific details of the change are applied to the database, ensuring that data on all relevant platforms remains consistent and up-to-date, improving data accuracy and timeliness.

[0105] Optionally, in step S1621, the target audit object is determined based on the data impact scope and the change operation type, including the following execution steps:

[0106] Step S16211: In response to the change operation type being a modification operation or a new addition operation, and the data impact range having an impact on the target platform, determining the target audit object to be the audit object corresponding to the target platform; or

[0107] Step S16212: In response to the change operation type being a delete operation, determining whether other platforms except the target platform are affected based on the data impact scope;

[0108] Step S16213: In response to the impact on the remaining platforms except the target platform, determining the target audit object as the audit object corresponding to the remaining platforms except the target platform;

[0109] Step S16214: In response to the fact that there is no impact on the remaining platforms except the target platform, the target audit object is determined to be the audit object corresponding to the target platform.

[0110] In this embodiment of the present invention, when determining the target review subject based on the data impact scope and change operation type, if the change operation involves modifying or adding diagnostic parameters and these changes directly impact the data of the target platform (which could be the diagnostic platform, product system platform, or vehicle platform), the vehicle diagnostic system will identify the target platform's administrator or designated reviewer as the target review subject. This means that the change request will require approval from the target platform's reviewer before it can be formally implemented.

[0111] If the change operation involves deleting diagnostic parameters, the vehicle diagnostic system will further analyze the scope of the data impact to determine whether other platforms, in addition to the original target platform, also reference or rely on this parameter, in order to prevent accidental deletion from causing irreversible impact on other platforms.

[0112] Furthermore, if the deletion operation affects platforms other than the target platform, the vehicle diagnostic system will include the administrators or auditors of these affected platforms in the target audit objects, thereby ensuring that cross-platform changes can be fully considered and agreed upon by all relevant parties, avoiding changes on one platform without the consent of other platforms causing a series of adverse consequences.

[0113] If the deletion operation is confirmed to have no impact on other platforms, the vehicle diagnostic system only requires the reviewers of the target platform to participate in the change application approval. In this case, the change approval is more direct, reducing unnecessary approval steps and speeding up the processing of the change application.

[0114] It can be seen that the vehicle diagnostic system can intelligently determine the target review objects based on different types of change operations and data impact scope, which not only ensures the proper review of changes, but also promotes cross-platform collaborative decision-making, while optimizing the approval process and improving the efficiency and security of the entire diagnostic parameter management system in change management.

[0115] Optionally, in step S1622, updating the platform database based on the change record and change impact analysis includes the following execution steps:

[0116] Step S16221: in response to the target platform being a diagnostic platform, updating the platform database of the diagnostic platform based on the change record and change impact analysis; or,

[0117] Step S16222: In response to the target platform being a product system platform, updating the platform database of the diagnostic platform based on the change record and change impact analysis, and updating the platform database of the vehicle platform and the target version data of the vehicle platform based on the change record and change impact analysis; or

[0118] Step S16223 : In response to the target platform being a vehicle model platform, the platform database of the vehicle model platform is updated based on the change record and change impact analysis.

[0119] In this embodiment of the present invention, when updating the platform database based on change records and change impact analysis, if the target platform is determined to be a diagnostic platform, the vehicle diagnostic system automatically updates the diagnostic platform database based on the change records and the results of the change impact analysis. This ensures that all modifications reflected in the change records are accurately reflected in the database, ensuring that the diagnostic platform data is up-to-date and accurate. This ensures that the diagnostic platform data is synchronized with the information in the change records in real time, improving the timeliness and effectiveness of the data.

[0120] If the target platform is a product system platform, the vehicle diagnostic system must not only update the product system platform database but also consider the impact of the change on the diagnostic platform and the vehicle platform, updating the databases of both platforms simultaneously. Furthermore, the target version data related to the change must be updated on the vehicle platform to ensure the accuracy and applicability of the vehicle diagnostic data. The target version data is the master version, which is the latest valid version of the diagnostic parameters stored on the vehicle platform.

[0121] This enables cross-platform data synchronization, ensuring data consistency across product system platforms, diagnostic platforms, and vehicle platform platforms, avoiding development delays or diagnostic failures caused by data asynchrony. It also optimizes version management, specifically focusing on updating target versions within vehicle platform models. This helps maintain version consistency across vehicle diagnostic parameters and simplifies version management.

[0122] If the target platform is a vehicle model, the vehicle diagnostic system will update only the vehicle model platform's database based on the change history and change impact analysis. This is typically performed when diagnostic parameters specific to the vehicle model platform are modified, ensuring that only vehicle model-specific data is updated without affecting data on other platforms. This reduces unnecessary computing resource consumption and improves the targetedness and efficiency of data updates by limiting updates to vehicle model platform data.

[0123] It can be seen that the vehicle diagnostic system of the present invention can accurately update the database according to the characteristics and requirements of different target platforms, which not only ensures the timeliness and accuracy of the data, but also maintains the consistency of cross-platform data and the applicability of vehicle model diagnostic parameters through change impact analysis and target version updates, greatly improving the stability and efficiency of the vehicle diagnostic system, while also optimizing the version management process and reducing data conflicts and maintenance costs.

[0124] Optionally, in step S16222, after updating the platform database of the vehicle model platform and the target version data of the vehicle model platform based on the change record and the change impact analysis, the following execution steps are further included:

[0125] Step S162221, copy the updated target version data to obtain the first copy version data;

[0126] Step S162222: Freeze the first copy version data to obtain the first frozen version data;

[0127] Step S162223: Export the first frozen version data and publish the first frozen version data.

[0128] In this embodiment of the present invention, after updating the platform database and target version data for the vehicle platform based on change records and change impact analysis, the vehicle diagnostic system also copies the latest target version data to generate a first copy of the version data. This copying process ensures the security of the original data and avoids data risks associated with direct modifications to the real-time database during subsequent operations. Thus, by copying rather than directly modifying the data, the integrity of the original data is ensured, facilitating data backup and recovery. Furthermore, the copy of the version data, forming a new version, facilitates tracking and management of change history, enabling subsequent version control and data backtracking.

[0129] The vehicle diagnostic system then freezes the first copy of the data, generating the first frozen version. This frozen version serves as the final reference version, and no further modifications are permitted. This first frozen version prevents pre-release data changes and ensures data accuracy at the time of release. Furthermore, serving as the standard version, the first frozen version facilitates distribution to various downstream systems or development teams, streamlining the data distribution process.

[0130] Finally, the vehicle diagnostic system exports and publishes the first frozen version of the data, i.e., the product system platform data. For example, the frozen first frozen version of the data can be converted into a format suitable for use by external systems or devices, such as Excel, PDF, or PDX, to facilitate data transfer and use. By exporting and converting the frozen first copy of the data into a compatible format, followed by a formal release, the release process pushes the data version to the various systems and teams that need to use these parameters, ensuring timely data availability.

[0131] Optionally, the vehicle diagnostic parameter processing method further includes the following execution steps:

[0132] Step S162224: in response to receiving the electronic control unit diagnostic parameter change application for the vehicle platform, reviewing the electronic control unit diagnostic parameter change application;

[0133] Step S162225: In response to the electronic control unit diagnostic parameter change application being approved, the first frozen version data is supplemented based on the electronic control unit variant and vehicle model to obtain supplemented version data, wherein the electronic control unit variant is a different electronic control unit version designed to address differences between different vehicle models;

[0134] Step S162226, copy the supplemented version data to obtain the second copied version data;

[0135] Step S162227, freezing the second copy version data to obtain the second frozen version data;

[0136] Step S162228: Export the second frozen version data and publish the second frozen version data.

[0137] In the embodiment of the present invention, the electronic control unit (ECU) diagnostic parameters refer to specific parameters used to diagnose and monitor the ECU status, such as fault codes, sensor data, etc.

[0138] It is understandable that depending on the model of the car, there will be multiple versions of the ECU, namely ECU variants. ECU variants are different electronic control unit versions designed to address the differences between different models. Each version may contain specific diagnostic parameters to suit the needs of different models.

[0139] After the first frozen version of data is released (i.e., after the product system platform data is released), when the vehicle diagnostic system receives a request to change diagnostic parameters for a specific ECU on a vehicle platform, a review process will be initiated. The corresponding administrator will evaluate the rationale of the change based on the scope of impact and technical specifications. This review prevents unauthorized changes and ensures that the changes comply with technical specifications and corporate policies.

[0140] After the electronic control unit diagnostic parameter change application is approved, the vehicle diagnostic system will supplement the first frozen version data, adding or modifying diagnostic parameters required by the ECU variant and specific vehicle model. This supplemented data becomes the supplemented version data, ready for the next stage. This supplemented version data thus takes into account the specific requirements of different ECU variants and vehicle models, improving the applicability of diagnostic parameters to specific vehicle models and thus enhancing vehicle applicability. Furthermore, by differentiating between ECU variants and vehicle models, it enables refined management of diagnostic parameters, better adapting to multi-vehicle development environments and achieving refined management.

[0141] The vehicle diagnostic system then copies the supplementary version data to form a second copy. To prevent direct modification of the first frozen version, the system preserves its original state and prevents subsequent operations from affecting it. The second copy is then frozen, prohibiting any modification and ensuring data stability and consistency before release.

[0142] Finally, the vehicle diagnostic system exports and publishes the second frozen version of the data, specifically the vehicle model ECU data, ensuring that all relevant personnel and systems have access to the latest diagnostic parameters for subsequent development and testing. This export ensures that data is distributed in a standard format, facilitating data exchange and understanding across different systems and teams.

[0143] Optionally, the vehicle diagnostic parameter processing method further includes the following execution steps:

[0144] Step S162229: Generate a vehicle model release document based on the task plan and the second frozen version data, wherein the vehicle model release document includes technical parameters, configuration information, system status, and diagnostic parameters of the target vehicle model at any development stage;

[0145] Step S162230: Release the vehicle model release document.

[0146] In the embodiments of the present invention, a mission plan refers to a schedule related to the vehicle development cycle, including tasks, deadlines, and key activities required to be completed at different development stages. The mission plan provides a timeframe and a list of goals for the entire vehicle development process.

[0147] The vehicle model release document is a comprehensive document that covers the key technical parameters, configuration information, system status and the latest diagnostic parameter information of a specific vehicle model at a certain development stage.

[0148] After the second frozen version data is released (i.e., after the vehicle model ECU data is released), the vehicle diagnostic system automatically generates a vehicle model release document based on a pre-defined task plan and the diagnostic parameter information in the second frozen version data. This vehicle model release document details the technical status of the target vehicle at any given stage of development, including all technical parameters, configuration settings, system status, and most importantly, diagnostic parameters, ensuring that vehicle development, testing, and maintenance teams have the most comprehensive and accurate information about the vehicle model.

[0149] As a result, the vehicle release document becomes the authoritative source of information for vehicle development and maintenance, ensuring that all team members work from the same data set, improving the efficiency and quality of team collaboration. Furthermore, the diagnostic parameter information contained in the vehicle release document provides clear guidance for vehicle testing and fault diagnosis, helping to quickly locate problems and improve diagnostic and maintenance efficiency.

[0150] Once the vehicle launch document is generated, the next step is to officially release it—that is, release the vehicle data. This release process typically involves digitally distributing the document to ensure that all relevant team members (such as R&D, testing, production, and after-sales service) have timely access to the complete document, as well as any updates to the electronic database, so that downstream systems can read and apply the latest diagnostic parameter information.

[0151] As a result, release documents ensure that information is quickly and accurately delivered to every team member who needs it, avoiding information silos and accelerating the dissemination and application of information. Furthermore, it ensures that all team members work based on the latest, unified information, eliminating duplication of work and communication barriers caused by inconsistent information and promoting efficient collaboration across teams. Furthermore, downstream teams no longer need to search or organize information independently; they can directly use the data in the vehicle model release document to work, improving overall work efficiency and productivity.

[0152] As can be seen, the present invention proposes a method and system for intelligently managing vehicle diagnostic parameters. By integrating data from the diagnostic platform, product system platform, and vehicle platform, the entire process of diagnostic parameter modification, verification, and review and release is intelligently managed online, generating standardized and reliable diagnostic data. This enables accurate output of vehicle diagnostic parameters and platform-based management of diagnostic parameters and products, helping to improve the efficiency of diagnostic parameter design and enhance the quality of diagnostic data.

[0153] The embodiment of the present invention also provides a vehicle diagnostic system, Figure 2 FIG. 1 is a schematic diagram of the structure of a vehicle diagnostic system provided by an embodiment of the present invention. Figure 2 As shown, the vehicle diagnostic system includes a diagnostic platform, a product system platform, and a vehicle model platform. The diagnostic platform, serving as a universal management platform for vehicle diagnostic parameters, is primarily used by diagnostic engineers. These engineers can enter vehicle-level diagnostic parameters, including but not limited to diagnostic addresses, communication parameters, DTCs, freeze frames, DIDs, and safety algorithms. The platform supports batch import (e.g., Excel and PDX databases) and online editing, ensuring comprehensive and real-time data updates.

[0154] The product system platform is used jointly by system engineers, product engineers, and diagnostic engineers to manage product- or system-specific diagnostic requirements. It also supports batch import and online editing, with a particular focus on product-specific diagnostic parameters such as fault settings and recovery conditions, safety levels, and other attributes. It also synchronizes vehicle applicability to ensure parameter consistency and applicability across different models.

[0155] ECU1 is a specific ECU instance managed within a product system platform. ECU1 may be responsible for controlling a specific vehicle function or system, such as engine control or brake system control. ECU Platform 1 and ECU Platform 2 can be understood as a set of ECUs with similar functionality but applicable to different vehicle models or technical standards. Each ECU platform has its own diagnostic parameter standards and definitions to meet the specific needs of different product lines.

[0156] The vehicle platform is used by diagnostic engineers or product engineers to input vehicle-specific diagnostic requirements. It supports online editing only to ensure the applicability of diagnostic parameters for each vehicle. The vehicle platform primarily handles vehicle diagnostic parameters with vehicle-specific attributes, such as default values, storage locations, and application scenarios, and ensures that parameter changes accurately impact the corresponding vehicle and ECU variant.

[0157] ECU1 is a specific ECU referenced in the vehicle platform. ECU Variant 1 and ECU Variant 2 are specific instances of an ECU used in different configurations or versions of the same vehicle model. Because a vehicle model may have multiple configurations, such as a base model, a luxury model, or models equipped with different technology packages, different configurations may require different ECU versions to meet specific functional requirements or performance specifications.

[0158] The vehicle diagnostic system also features a change management module, an approval management module, a user and role management module, a task management module, and a log management module. The change management module manages the entire process of diagnostic parameter creation, modification, and deletion, tracking the history of parameter changes. The approval management module controls the review process during diagnostic parameter changes, ensuring that only approved changes are formally implemented. The user and role management module defines the access rights and scope of operations for different users, ensuring data security and compliance. The task management module automatically triggers tasks, such as phase freezes and data releases, based on the vehicle development plan to ensure that projects proceed on schedule. The log management module maintains a log of all operations for auditing and problem tracing.

[0159] In summary, Figure 2 The vehicle diagnostic system architecture diagram clearly demonstrates how diagnostic parameter management methods and systems effectively coordinate different platforms and roles within an organization's intelligent connected vehicle development, ensuring efficient and accurate management and release of diagnostic parameters. Through data linkage, role interaction, and process control, this vehicle diagnostic system significantly improves the intelligence and efficiency of vehicle diagnostic parameter management.

[0160] It is understandable that Figure 2The vehicle diagnostic system shown can execute the vehicle diagnostic parameter processing method provided by the present invention. Please refer to the description of the aforementioned embodiment and will not be elaborated here.

[0161] Figure 3 FIG. 1 is a schematic diagram of the overall process of changing and publishing diagnostic parameters provided by an embodiment of the present invention. Figure 3 As shown in the figure, when a diagnostic parameter needs to be modified or added, the user initiates a request through the diagnostic parameter input step on the diagnostic platform, product system platform, or vehicle model platform. The system then proceeds to the input platform determination step and directs subsequent processes based on the platform for parameter input.

[0162] Automatic verification is a core component of the process. Regardless of the platform to which the diagnostic parameters are input, they are reviewed to determine whether they comply with the platform's corresponding verification rules. For example, data format, standardization (ODX standard), and relevance are verified to ensure that the parameters meet established standards. If the parameters pass verification, they are updated to the platform's corresponding cache. The cache data is then compared with the platform's database data to generate the difference data.

[0163] If a change request is received from a platform requester, the system generates a change record based on the difference data. It also analyzes the impact of the change on different platforms (diagnostic platform, product system platform, vehicle platform) and vehicle models, generating a change impact analysis. Based on this change impact analysis, the automatic review role assignment mechanism is activated, automatically pushing the change request to the administrators of the relevant platforms for necessary approval.

[0164] The approval process is monitored by determining which platforms have passed the review process. Once a platform's change request is approved, the data is updated and synchronized to the official database for that platform. This also triggers additional data releases for product system platforms and vehicle model platforms. Product system platform data releases generate exportable versions for software development. Vehicle ECU data releases target specific models and ECU variants to ensure software adaptability.

[0165] Finally, at the designated vehicle development stage, through the vehicle data release, the system, according to the instructions of the vehicle administrator, summarizes the latest diagnostic parameter versions of all ECUs, generates a vehicle PDX database and related documents, and sends them to the remote diagnosis and testing system, or makes them available to offline diagnostic equipment developers, thereby completing the entire change and release process and achieving the goal of improving the efficiency and quality of diagnostic parameter design.

[0166] Figure 4 FIG. 1 is a flow chart of a change impact analysis process according to an embodiment of the present invention. Figure 4As shown in the figure, upon receiving a change request, the system determines which platform the change request originated from. Different platforms represent different contexts and data networks, which directly influence the subsequent change impact analysis strategy. Once the source of the change is determined, the system will further identify the specific products or systems affected, as well as the types of parameters, to accurately analyze the nature and scope of the change.

[0167] Specifically, if it is determined that the change application comes from the diagnostic platform, the diagnostic parameter type of the changed parameter is queried, and the change operation type is determined to determine whether the change request is to add, modify, or delete a certain diagnostic parameter. If it is a new operation, the diagnostic platform adds a new diagnostic parameter under the corresponding category according to the parameter type, and records the initial version V1.0. The attribute content is updated according to the change record. If it is a modification operation, the diagnostic platform adds a new diagnostic parameter under the corresponding category according to the parameter type, and updates the diagnostic parameters based on the same key attributes according to the change record, and the versions are accumulated (if the current version of the diagnostic parameter with the same key attributes is V1.5, the newly created parameter version is V1.6). If it is a deletion operation, the diagnostic platform logically deletes all attribute contents of the corresponding diagnostic parameter, and the product system platform and vehicle model platform logically delete the parameters corresponding to the main version according to the reference relationship.

[0168] If the change request is determined to be from a vehicle model platform, the vehicle model platform only allows modification of vehicle model-specific attributes, which only affects the changed vehicle model platform. Query the changed vehicle model and ECU variant name and diagnostic parameter type, and update the modified content to the vehicle model platform database (vehicle model diagnostic parameters are updated to the corresponding vehicle model, and ECU diagnostic parameters are updated to the ECU under the vehicle model).

[0169] If the change request is determined to be from the product system platform, the name of the product / system initiating the change and the diagnostic parameter type are queried, and the data operation type is then determined. If it is a new operation, a new record is created on the product system platform, with the initial version V1.0 recorded. The diagnostic platform attribute content is checked to see if it is consistent with the diagnostic platform definition. If so, the diagnostic platform parameters are directly referenced. If not, they are updated synchronously to the diagnostic platform and referenced again after the diagnostic platform is updated. The referenced diagnostic platform parameter version is then recorded. The product system platform attributes and vehicle applicability attributes are then added to the product system platform database. Simultaneously, the diagnostic platform attributes, product system platform attributes, and version information are updated synchronously to the corresponding vehicle model and ECU variant based on vehicle applicability. The diagnostic platform is then updated based on the results uploaded by the product system platform. If data is uploaded, it is updated according to the diagnostic platform's method (which will not be elaborated on here). If no data is uploaded, the diagnostic platform updates the attributes of the subsystem and product platform to which it belongs based on the reference relationship.

[0170] If the operation involves modification, a new record is created on the product system platform, and the version is incremented (if the current version of a diagnostic parameter with the same key attributes is V1.5, the newly created parameter version is V1.6). The product system platform determines the modified parameter attribute. If it is a diagnostic platform attribute (i.e., platform attribute), it checks whether the modified diagnostic platform attribute content is consistent with the diagnostic platform definition. If so, the reference relationship is updated. If not, the attribute is updated synchronously to the diagnostic platform and referenced again after the diagnostic platform is updated. The referenced diagnostic platform parameter version is then recorded. If it is a product system platform attribute or vehicle applicability attribute (i.e., other attributes), it is updated to the product system platform database. Then, according to the reference relationship (vehicle applicability attribute), the diagnostic platform attribute, product system platform attribute, and version information are synchronously updated to the corresponding vehicle model and ECU variant on the vehicle platform. The diagnostic platform is then updated based on the results uploaded by the product system platform. If data is uploaded, it is updated according to the diagnostic platform's method (not detailed here). If no data is uploaded, the diagnostic platform updates the attributes of the corresponding subsystem and product platform according to the reference relationship.

[0171] If it is a modification operation, all attribute contents of the diagnostic parameters corresponding to the product system platform will be deleted. The diagnostic platform will delete the reference relationship between its subsystem and the product platform to which it belongs. The vehicle model platform will delete the parameters corresponding to the main version according to the reference relationship logic.

[0172] The vehicle diagnostic parameter processing method proposed by the present invention is generally described below.

[0173] Step 1: Diagnostic parameter input. The diagnostic parameters mentioned in this invention mainly include diagnostic address, communication parameters, DTC, freeze frame, DID, safety algorithm and other parameters involved in ECU diagnostic development.

[0174] The vehicle diagnostic system has three platforms, each with a requirements portal. Different requirements can be entered through different portals. The first is the diagnostic platform, where diagnostic engineers typically enter general vehicle-related requirements. This input supports pre-defined templates (Excel spreadsheets) and PDX database import, as well as online editing. The second is the product system platform, where system engineers, product engineers, and diagnostic engineers typically jointly enter system and product-related diagnostic requirements. This input supports pre-defined templates (Excel spreadsheets) and PDX database import, as well as online editing. The third is the vehicle model platform, which only supports diagnostic engineers or product engineers entering diagnostic requirements specific to vehicle models, and this input supports only online editing.

[0175] It is understandable that the data operation types supported by different entrances and input methods are not exactly the same. Among them, batch import of the diagnostic platform supports addition and modification, and online editing supports addition, modification and deletion; batch import and online editing of the product system platform both support addition, modification and deletion; online editing of the vehicle model platform supports modification.

[0176] For example, the diagnostic parameter attribute definitions stored in each platform system can be referred to in Tables 1 to 3 below.

[0177] Table 1 Diagnostic Platform: Import template contains diagnostic platform attributes

[0178]

[0179] Table 2 Product system platform: The import template includes three types of attributes: diagnostic platform attributes, product system platform attributes, and vehicle model applicability

[0180]

[0181] Table 3 Vehicle Platform

[0182]

[0183] It should be noted that for the data of the three platforms, the system will automatically generate two attributes: creator and creation time; the diagnostic platform attribute is required for all diagnostic parameters, and some parameters may not have product system platform attributes or vehicle-specific attributes (such as safety algorithms).

[0184] Step 2: Automatic Verification: The vehicle diagnostic system determines the platform for diagnostic parameter input and invokes the corresponding platform's verification engine to verify the input data (including additions, deletions, modifications, and references) according to predefined verification rules (rules can be configured with error levels and effectiveness). Verification is performed on data format, data standardization (ODX specifications), and data relationships to accurately locate erroneous data. For online data input, the system directly restricts the input data format according to the rules to ensure input data correctness. For batch imported data, if any data verification rule items are not met, the system generates a verification report.

[0185] Step 3: Change Analysis

[0186] 1) Generate change records

[0187] If the data verification passes, the vehicle diagnostic system will update the data to the cache area of ​​the corresponding platform (only visible and re-editable by roles with current data editing permissions). The vehicle diagnostic system will compare the data differences between the cache area and the corresponding platform database, and generate a diagnostic parameter change record when the party proposing the diagnostic requirement initiates a change application.

[0188] 2) Change impact analysis

[0189] For changes initiated on different platforms, the vehicle diagnostic system performs change impact analysis based on the data impact range and parameter change operation type.

[0190] a) Diagnostic Platform

[0191] Query the diagnostic parameter type of the changed parameter, and then determine the operation type of the data.

[0192] New: The diagnostic platform adds a new diagnostic parameter under the corresponding category according to the parameter type, and records the initial version V1.0. The content of each attribute is updated according to the change record.

[0193] Modification: The diagnostic platform adds a new diagnostic parameter under the corresponding category according to the parameter type. The diagnostic parameters with consistent key attributes are updated according to the change records, and the versions are accumulated (if the current version of the diagnostic parameter with consistent key attributes is V1.5, the new parameter version is V1.6).

[0194] Delete: The diagnostic platform logically deletes all attribute contents of the corresponding diagnostic parameters; the product system platform and vehicle model platform logically delete the parameters corresponding to the main version based on the reference relationship.

[0195] b) Product system platform

[0196] Query the product / system name and diagnostic parameter type that initiated the change, and then determine the data operation type.

[0197] New: A new record is added to the product system platform, and the initial version V1.0 is recorded. The diagnostic platform attribute content is checked to see if it is consistent with the diagnostic platform definition. If it is consistent, the diagnostic platform parameters are directly referenced. If not, they are updated synchronously to the diagnostic platform and referenced again after the diagnostic platform is updated. The referenced diagnostic platform parameter version is then recorded. The product system platform attributes and vehicle model applicability attribute content are added to the product system platform database. At the same time, the diagnostic platform attributes, product system platform attributes, and version information are synchronously updated to the corresponding vehicle model and ECU variant based on the vehicle model applicability. The diagnostic platform is updated based on the results uploaded by the product system platform. If there is data uploaded, it is updated according to the diagnostic platform method. If there is no data uploaded, the attributes of the subsystem and the product platform to which it belongs are updated according to the reference relationship.

[0198] Modification: A new record is added to the product system platform, and the version is accumulated (if the current version of the diagnostic parameter with the same key attributes is V1.5, the newly created parameter version is V1.6). The product system platform determines the modified parameter attribute. If it is a diagnostic platform attribute, it queries whether the modified diagnostic platform attribute content is consistent with the diagnostic platform definition. If it is consistent, the reference relationship is updated. If it is inconsistent, it is updated to the diagnostic platform synchronously, and referenced again after the diagnostic platform is updated, and then the referenced diagnostic platform parameter version is recorded. If it is a product system platform attribute and a vehicle model applicability attribute, it is updated to the product system platform database, and then the diagnostic platform attribute, product system platform attribute and version information are synchronously updated to the vehicle model and ECU variant corresponding to the vehicle model platform according to the reference relationship (vehicle model applicability attribute). The diagnostic platform is updated according to the upload results of the product system platform. If there is data uploaded, it is updated according to the method of the diagnostic platform. If there is no data uploaded, the attributes of the subsystem and the product platform to which it belongs are updated according to the reference relationship.

[0199] Delete: All attribute contents of the diagnostic parameters corresponding to the product system platform are deleted. The diagnostic platform deletes the reference relationship between its subsystem and the product platform to which it belongs. The vehicle model platform deletes the parameters corresponding to the main version according to the reference relationship logic.

[0200] c) Vehicle platform

[0201] The vehicle platform only allows modification of vehicle-specific attributes, which only affects the changed vehicle platform. Query the changed vehicle model and ECU variant name and diagnostic parameter type, and update the modified content to the vehicle platform database (vehicle diagnostic parameters are updated to the corresponding vehicle model, and ECU diagnostic parameters are updated to the ECU under the vehicle model).

[0202] 3) Automatic allocation of audit roles

[0203] When a change request is initiated, the vehicle diagnostic system automatically pushes the request to the corresponding data administrator for approval based on the scope of the data update. (For example, additions and modifications to the diagnostic platform require approval from the diagnostic platform administrator. Deletions require further verification of whether the corresponding diagnostic parameter is referenced by the product platform (subsystem or product) or vehicle platform (vehicle and ECU variant). If not, approval is sufficient for the corresponding diagnostic platform administrator. If so, the request must be pushed to the referencing data administrator for approval.) The change initiator can select a specific user for approval based on their role.

[0204] Step 4: Product system platform data release. After the diagnostic platform change application is approved, only the diagnostic platform database needs to be updated. After the product system platform change application is reviewed and approved, the changed data is updated to the diagnostic platform database and the vehicle platform master version (synchronized with the database). The product initiating the change will copy and freeze a diagnostic parameter release version based on the master version and record the version number V1.x (versions are automatically incremented). This version supports the export of diagnostic parameters in formats such as EXCEL, PDF, and PDX, and is released to the product for software platform development.

[0205] Step 5: Vehicle ECU Data Release. After the product system platform data is released, the vehicle platform must supplement and improve the vehicle-specific attributes of the ECU variant. Before the release of specific vehicle data, an ECU diagnostic parameter change request is initiated on the vehicle platform (at least once per stage, but multiple requests are allowed). After approval by the vehicle and ECU administrators, the vehicle platform copies and freezes the ECU variant diagnostic parameter release version based on the master version, recording the version number V1.x (versions are automatically incremented) and the release stage (PT0, PT1, etc.). This version also supports the export of diagnostic parameters to Excel, PDF, PDX, and other formats, releasing them to the product for vehicle software adaptation.

[0206] Step 6: Vehicle data release. In the corresponding vehicle project stage (PT0, PT2, etc.), the system's task management module initiates the stage freezing and release tasks of the vehicle data according to the project plan (the development plan of the corresponding vehicle model can be imported or configured). The vehicle model administrator initiates the project node release on the vehicle model platform. The system automatically queries the latest version of the diagnostic parameters of each ECU in the current stage (including the diagnostic address, communication parameters, DTC, freeze frame, DID, security algorithm, etc. of all ECUs in the vehicle) and summarizes and updates them to the vehicle model release document directory. It also automatically generates a vehicle PDX database, pushes the release files to the remote diagnostic system and diagnostic test system on demand, and supports exporting or downloading the corresponding files in the vehicle model release document directory and outputting them to offline diagnostic equipment development.

[0207] It can be seen that the present invention supports batch import and online editing to input diagnostic parameters, and verifies the data format, data standardization (ODX specification), and data association relationship of the input data according to the verification rules. Change records are automatically generated for diagnostic parameter changes initiated by different platforms. At the same time, the system performs change impact analysis based on the data impact range and parameter change operation type, and then automatically assigns review roles in the approval process based on the impact range. After the corresponding change application is reviewed and approved, the system will perform version updates and data releases on the product system platform and vehicle model ECU diagnostic data respectively. In the corresponding project stage, after receiving the stage freeze and release tasks for the vehicle model data, the vehicle model administrator initiates the project node release on the vehicle model platform, and the release file is pushed to the remote diagnostic system and diagnostic test system as needed or output to the offline diagnostic equipment development.

[0208] Thus, the present invention achieves platform-based management of diagnostic parameters and products through data linkage between the diagnostic platform, product system platform, and vehicle platform. Simultaneously, the impact of diagnostic parameter changes on the platform and vehicle model is analyzed, and the corresponding platforms and vehicle models are automatically updated and synchronized to ensure accurate output of platform and vehicle model diagnostic parameters. In other words, through platform-based management of diagnostic parameters and products, automatic verification of diagnostic data, and change impact analysis, the present invention achieves automatic updating of diagnostic data and synchronous publication of a standard database, significantly avoiding errors that may occur during diagnostic development and application data transmission, improving the efficiency of diagnostic parameter design and enhancing diagnostic data quality.

[0209] The embodiment of the present invention further provides a vehicle diagnostic parameter processing device 50, please refer to Figure 5 , including: an acquisition module 501, used to obtain diagnostic parameters input into the target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of the electronic control system in the vehicle, and the target platform is one of the following: a diagnostic platform, a product system platform, and a vehicle model platform. The diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters. The product system platform is used to separately manage the diagnostic parameters corresponding to different products or systems, and the vehicle model platform is used to separately manage the diagnostic parameters corresponding to different vehicle models; a verification module 502, used to perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, wherein the verification result includes verification-passed parameters and verification-failed parameters; a comparison module 503, used to update the cache area of ​​the target platform based on the verification-passed parameters, and compare the differences between the cache area data and the platform database data to obtain difference data, wherein the cache area data is the data stored in the updated cache area, and the platform database data is the data stored in the platform database of the target platform; an update module 504, used to update the platform database of the target platform based on the difference data.

[0210] Furthermore, the update module 504 is also used to generate a change record based on the difference data in response to receiving a diagnostic parameter change application for the target platform, and generate a change impact analysis based on the data impact range and the change operation type, wherein the change record is used to record the modification, addition or deletion operations on the diagnostic parameters, the data impact range is used to indicate the impact range of the diagnostic parameter change on different platforms and vehicle models, and the change impact analysis is used to record the impact range of the target platform's diagnostic parameters on other platforms except the target platform when the target platform's diagnostic parameters change; and the platform database of the target platform is updated based on the change record and the change impact analysis.

[0211] Furthermore, the acquisition module 501 is also used to, in response to the target platform being a diagnostic platform, acquire diagnostic parameters imported into the diagnostic platform based on a predefined template or a product data exchange database, or, acquire diagnostic parameters input into the diagnostic platform based on an online editing application; in response to the target platform being a product system platform, acquire diagnostic parameters imported into the product system platform based on a predefined template or a product data exchange database, or, acquire diagnostic parameters input into the product system platform based on an online editing application; in response to the target platform being a vehicle model platform, acquire diagnostic parameters input into the vehicle model platform based on an online editing application.

[0212] Furthermore, the verification module 502 is also used to use the verification engine of the target platform to perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification rules are used to verify the data format, data standardization, and data association relationship of the diagnostic parameters.

[0213] Furthermore, the device also includes: a processing module, which is used to generate a verification report based on the verification failed parameters, wherein the verification report is used to list the verification failed parameters and problem situations corresponding to the verification failed parameters.

[0214] Furthermore, the update module 504 is also used to determine the target audit object based on the data impact scope and the change operation type, and use the target audit object to audit the diagnostic parameter change application; in response to the diagnostic parameter change application being reviewed and approved, the platform database is updated based on the change record and change impact analysis.

[0215] Furthermore, the update module 504 is also used to determine that the target audit object is the audit object corresponding to the target platform in response to the change operation type being a modification operation or a new addition operation, and the data impact range has an impact on the target platform; or, in response to the change operation type being a deletion operation, determine whether it affects the remaining platforms other than the target platform based on the data impact range; in response to the presence of an impact on the remaining platforms other than the target platform, determine the target audit object as the audit object corresponding to the remaining platforms other than the target platform; in response to no impact on the remaining platforms other than the target platform, determine the target audit object as the audit object corresponding to the target platform.

[0216] Furthermore, the update module 504 is also used to update the platform database of the diagnostic platform based on the change record and change impact analysis in response to the target platform being a diagnostic platform; or, in response to the target platform being a product system platform, update the platform database of the diagnostic platform based on the change record and change impact analysis, and update the platform database of the vehicle model platform and the target version data of the vehicle model platform based on the change record and change impact analysis; or, in response to the target platform being a vehicle model platform, update the platform database of the vehicle model platform based on the change record and change impact analysis.

[0217] Furthermore, the device also includes: a first publishing module, configured to copy the updated target version data to obtain first copied version data; freeze the first copied version data to obtain first frozen version data; export the first frozen version data, and publish the first frozen version data.

[0218] Furthermore, the device also includes: a second publishing module, which is used to review the electronic control unit diagnostic parameter change application in response to receiving the electronic control unit diagnostic parameter change application for the vehicle model platform; in response to the electronic control unit diagnostic parameter change application being reviewed and approved, supplement the first frozen version data based on the electronic control unit variant and the vehicle model to obtain supplemented version data, wherein the electronic control unit variant is a different electronic control unit version designed for the differences between different vehicle models; copy the supplemented version data to obtain a second copied version data; freeze the second copied version data to obtain a second frozen version data; export the second frozen version data, and publish the second frozen version data.

[0219] Furthermore, the device also includes: a third release module, used to generate a vehicle model release document based on the task plan and the second frozen version data, wherein the vehicle model release document includes the technical parameters, configuration information, system status and diagnostic parameters of the target vehicle model at any development stage; and publish the vehicle model release document.

[0220] According to another aspect of an embodiment of the present invention, a vehicle is provided for executing any one of the above-mentioned vehicle diagnostic parameter processing methods.

[0221] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute any of the above-mentioned vehicle diagnostic parameter processing methods when running on a computer or processor.

[0222] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0223] Step S10: Acquire diagnostic parameters input to a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of the electronic control system in the vehicle. The target platform is one of the following: a diagnostic platform, a product system platform, or a vehicle model platform. The diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters. The product system platform is used to separately manage the diagnostic parameters corresponding to different products or systems. The vehicle model platform is used to separately manage the diagnostic parameters corresponding to different vehicle models.

[0224] Step S12: performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include parameters that passed the verification and parameters that failed the verification;

[0225] Step S14: updating the cache area of ​​the target platform based on the verification parameters, and comparing the differences between the cache area data and the platform database data to obtain difference data, wherein the cache area data is the data stored in the updated cache area, and the platform database data is the data stored in the platform database of the target platform;

[0226] Step S16: updating the platform database of the target platform based on the difference data.

[0227] Optionally, in this embodiment, the above-mentioned computer-readable storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0228] The embodiment of the present invention further provides an electronic device 60, please refer to Figure 6 , including a memory 601 and a processor 602, wherein the memory 601 is used to store computer programs; the processor 602 is used to execute the programs stored in the memory 601 to implement the vehicle diagnostic parameter processing method introduced in any embodiment of the present invention.

[0229] Optionally, in this embodiment, the processor in the electronic device may be configured to run a computer program to perform the following steps:

[0230] Step S10: Acquire diagnostic parameters input to a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of the electronic control system in the vehicle. The target platform is one of the following: a diagnostic platform, a product system platform, or a vehicle model platform. The diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters. The product system platform is used to separately manage the diagnostic parameters corresponding to different products or systems. The vehicle model platform is used to separately manage the diagnostic parameters corresponding to different vehicle models.

[0231] Step S12: performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include parameters that passed the verification and parameters that failed the verification;

[0232] Step S14: updating the cache area of ​​the target platform based on the verification parameters, and comparing the differences between the cache area data and the platform database data to obtain difference data, wherein the cache area data is the data stored in the updated cache area, and the platform database data is the data stored in the platform database of the target platform;

[0233] Step S16: updating the platform database of the target platform based on the difference data.

[0234] In the present invention, a plurality refers to two or more.

[0235] In the present invention, unless otherwise expressly defined, the terms "mounted," "connected," and "connected" should be understood broadly. For example, they may refer to fixed, detachable, or integral connections; mechanical or electrical connections; direct or indirect connections through an intermediary; and internal communication between two components. Those skilled in the art will understand the specific meanings of these terms in the present invention based on the specific circumstances.

[0236] The terms "first", "second", "third", "fourth", etc. (if any) in the present invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0237] The term "and / or" in this disclosure simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this disclosure generally indicates that the related objects are in an "or" relationship.

[0238] Unless otherwise specified, all steps of the present invention may be performed sequentially or randomly. For example, a statement that the method includes steps A and B indicates that the method may include steps A and B performed sequentially, or steps B and A performed sequentially. For example, a statement that the method may further include step C indicates that step C may be added to the method in any order. For example, the method may include steps A, B, and C, or steps A, C, and B, or steps C, A, and B, etc.

[0239] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for processing vehicle diagnostic parameters, characterized in that: include: Obtaining diagnostic parameters input to a target platform, wherein the diagnostic parameters are used to monitor the health status and fault conditions of an electronic control system in a vehicle, and the target platform is one of the following: a diagnostic platform, a product system platform, and a vehicle model platform; the diagnostic platform is used to manage functional requirements of a vehicle diagnostic system and parameter attributes of the diagnostic parameters; the product system platform is used to separately manage diagnostic parameters corresponding to different products or systems; and the vehicle model platform is used to separately manage diagnostic parameters corresponding to different vehicle models; Performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain verification results, wherein the verification results include parameters that passed the verification and parameters that failed the verification; updating a cache area of ​​the target platform through parameters based on the verification, and comparing differences between cache area data and platform database data to obtain difference data, wherein the cache area data is data stored in the updated cache area, and the platform database data is data stored in the platform database of the target platform; Updating the platform database of the target platform based on the difference data includes: in response to receiving a diagnostic parameter change application for the target platform, generating a change record based on the difference data, and generating a change impact analysis according to the data impact range and the change operation type, wherein the change record is used to record the modification, addition or deletion operations on the diagnostic parameters, the data impact range is used to represent the impact range of the diagnostic parameter change on different platforms and vehicle models, and the change impact analysis is used to record the impact range of the diagnostic parameter of the target platform on other platforms except the target platform when the diagnostic parameter changes; updating the platform database of the target platform based on the change record and the change impact analysis.

2. The vehicle diagnostic parameter processing method according to claim 1, characterized in that: The step of obtaining the diagnostic parameters input to the target platform includes: In response to the target platform being the diagnostic platform, acquiring the diagnostic parameters imported into the diagnostic platform based on a predefined template or a product data exchange database, or acquiring the diagnostic parameters input into the diagnostic platform based on an online editing application; In response to the target platform being the product system platform, acquiring the diagnostic parameters imported into the product system platform based on the predefined template or the product data exchange database, or acquiring the diagnostic parameters input into the product system platform based on the online editing application; In response to the target platform being the vehicle model platform, the diagnostic parameters input to the vehicle model platform are acquired based on the online editing application.

3. The vehicle diagnostic parameter processing method according to claim 1, characterized in that: The data verification of the diagnostic parameters based on the verification rules of the target platform to obtain the verification results includes: The verification engine of the target platform is used to perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain the verification results, wherein the verification rules are used to verify the data format, data standardization, and data association relationship of the diagnostic parameters.

4. The vehicle diagnostic parameter processing method according to claim 1, characterized in that: The method further comprises: A verification report is generated based on the verification failed parameters, wherein the verification report is used to list the verification failed parameters and problem situations corresponding to the verification failed parameters.

5. The vehicle diagnostic parameter processing method according to claim 1, characterized in that: The updating of the platform database of the target platform based on the change record and the change impact analysis includes: Determine a target audit object based on the data impact scope and the change operation type, and use the target audit object to audit the diagnostic parameter change application; In response to the diagnostic parameter change application being approved, the platform database is updated based on the change record and the change impact analysis.

6. The vehicle diagnostic parameter processing method according to claim 5, characterized in that: Determining the target audit object based on the data impact scope and the change operation type includes: In response to the change operation type being a modification operation or a new addition operation, and the data impact range having an impact on the target platform, determining that the target audit object is an audit object corresponding to the target platform; or In response to the change operation type being a delete operation, determining, based on the data impact scope, whether the remaining platforms except the target platform are affected; In response to the presence of an impact on the remaining platforms except the target platform, determining the target audit object to be the audit object corresponding to the remaining platforms except the target platform; In response to no impact on the remaining platforms except the target platform, the target audit object is determined to be the audit object corresponding to the target platform.

7. The vehicle diagnostic parameter processing method according to claim 5, characterized in that: Updating the platform database based on the change record and the change impact analysis includes: In response to the target platform being a diagnostic platform, updating a platform database of the diagnostic platform based on the change record and the change impact analysis; or, In response to the target platform being a product system platform, updating the platform database of the diagnostic platform based on the change record and the change impact analysis, and updating the platform database of the vehicle platform and the target version data of the vehicle platform based on the change record and the change impact analysis; or In response to the target platform being the vehicle model platform, a platform database of the vehicle model platform is updated based on the change record and the change impact analysis.

8. The vehicle diagnostic parameter processing method according to claim 7, characterized in that: After updating the platform database of the vehicle platform and the target version data of the vehicle platform based on the change record and the change impact analysis, the method further includes: Copying the updated target version data to obtain first copied version data; Freezing the first copy version data to obtain first frozen version data; The first frozen version data is exported and published.

9. The vehicle diagnostic parameter processing method according to claim 8, characterized in that: The method further comprises: In response to receiving an electronic control unit diagnostic parameter change application for the vehicle platform, reviewing the electronic control unit diagnostic parameter change application; In response to the electronic control unit diagnostic parameter change application being reviewed and approved, the first frozen version data is supplemented based on an electronic control unit variant and a vehicle model to obtain supplemented version data, wherein the electronic control unit variant is a different electronic control unit version designed to address differences between different vehicle models; copying the supplemented version data to obtain second copied version data; Freezing the second copy version data to obtain second frozen version data; The second frozen version data is exported and published.

10. The vehicle diagnostic parameter processing method according to claim 9, characterized in that: The method further comprises: generating a vehicle model release document based on the task plan and the second frozen version data, wherein the vehicle model release document includes technical parameters, configuration information, system status, and diagnostic parameters of the target vehicle model at any development stage; Publish the vehicle model release document.

Images