Method for processing diagnostic parameters of vehicle

Abstract

The invention relates to the technical field of data processing and vehicles, in particular to a vehicle diagnosis parameter processing method which comprises the steps that diagnosis parameters input to a target platform are obtained, and the diagnosis parameters are used for monitoring the health state and the fault condition of an electronic control system in a vehicle; the target platform is one of a diagnosis platform, a product system platform and a vehicle model platform; data verification is carried out on the diagnosis parameters based on a verification rule of the target platform to obtain a verification result, and the verification result comprises parameters passing verification and parameters not passing verification; updating a cache region of the target platform based on the verification passing parameter, and comparing differences between cache region data and platform database data to obtain difference data; and updating a platform database of the target platform based on the difference data. According to the method and the device, the technical problem that omission and errors are easy to occur in the data transmission process due to the fact that the diagnosis parameters are managed by adopting an Excel table in the related technology is solved.

Description

Technical Field

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

[0002] With the development of automotive electronics and intelligence, the management of in-vehicle diagnostic parameters has become increasingly complex, especially in the context of the popularization of domain control architectures. Diagnostic parameters, including Diagnostic Trouble Codes (DTCs), Data Identifiers (DIDs), communication parameters, etc., are crucial for ensuring the normal operation of vehicle electronic systems and troubleshooting.

[0003] Currently, many vehicle manufacturers use Excel spreadsheets or preliminary online systems to manage diagnostic parameters, and information omission and data errors are likely to occur during the data transfer process from products to models. This not only increases the burden of manual intervention but also reduces the efficiency of data update, restricting the intelligent progress of vehicle diagnostic management. Summary of the Invention

[0004] The embodiments of the present invention provide a method for processing diagnostic parameters of a vehicle, aiming to solve the technical problem in the related art that using Excel spreadsheets to manage diagnostic parameters easily causes omissions and errors in data transfer.

[0005] According to one aspect of the embodiments of the present invention, a method for processing diagnostic parameters of a vehicle is provided, including: obtaining diagnostic parameters input to a target platform, where 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 manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively; performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes verified parameters and unverified parameters; updating the buffer area of the target platform based on the verified parameters, and comparing the difference between the buffer area data and the platform database data of the target platform to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform; updating the platform database of the target platform based on the difference data.

[0006] Based on the overall above technical solution, 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 buffer area, a temporary and secure data storage environment is provided, facilitating data review and change management, and avoiding data loss during the database update process. Moreover, the cross-platform synchronization mechanism of the present invention ensures the consistency and accuracy of all relevant platform databases, greatly improving the data reusability and sharing, and avoiding errors and low efficiency caused by manual updates.

[0007] According to another aspect of the embodiments of the present invention, there is also provided a diagnostic parameter processing device for a vehicle, including: an acquisition module, configured to acquire diagnostic parameters input to a target platform, where the diagnostic parameters are used to monitor the health status and fault conditions of the electronic control system in the vehicle; a verification module, configured to perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes verified parameters and unverified parameters; a comparison module, configured to update the buffer area of the target platform based on the verified parameters and compare the difference between the buffer area data and the platform database data of the platform to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform; an update module, configured to update the platform database of the target platform based on the difference data.

[0008] According to another aspect of the embodiments of the present invention, there is also provided a vehicle diagnostic system, and the vehicle diagnostic system is used to execute the vehicle diagnostic parameter processing method in any one of the above.

[0009] According to another aspect of the embodiments of the present invention, there is also provided a vehicle, and the vehicle is used to execute the vehicle diagnostic parameter processing method in any one of the above.

[0010] According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, and a computer program is stored in the computer-readable storage medium, where the computer program is configured to execute the vehicle diagnostic parameter processing method in any one of the above when running on a computer or a processor.

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

[0012] In an embodiment of the present invention, by obtaining diagnostic parameters input to a target platform, where 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 the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters. The product system platform is used to manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively. Data verification is performed on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes verified parameters and unverified parameters. The buffer area of the target platform is updated based on the verified parameters, and the difference between the buffer area data and the platform database data is compared to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform. The platform database of the target platform is updated based on the difference data. Thus, the purpose of constructing a standardized and intelligent diagnostic parameter management system is achieved, thereby realizing accurate data transmission and efficient change management, enhancing the technical effects of system stability and diagnostic reliability, and further solving the technical problem in the related art that using an Excel spreadsheet to manage diagnostic parameters easily causes omissions and errors in data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a flowchart of a method for processing diagnostic parameters of a vehicle provided by an embodiment of the present invention; Figure 2 is a schematic structural diagram of a vehicle diagnostic system provided by an embodiment of the present invention; Figure 3 is a schematic diagram of the overall process of diagnostic parameter change and release provided by an embodiment of the present invention; Figure 4 is a schematic diagram of a change impact analysis process provided by an embodiment of the present invention; Figure 5 is a structural diagram of a device for processing diagnostic parameters of a vehicle provided by an embodiment of the present invention; Figure 6 is a structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0014] In order to make the technical problems, technical solutions, and beneficial effects solved by the present invention clearer, the present invention will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0015] To enable those skilled in the art to better understand the technical solution of the present application, the following term explanations are given: Diagnostic Parameters: These are key data indicators used in automotive electronic control units (ECUs) and in-vehicle network systems to monitor, diagnose, and maintain the health status of vehicles. Diagnostic parameters play a core role in automotive fault detection, status monitoring, and maintenance services, helping technicians quickly locate problems and take appropriate measures. The comprehensiveness and accuracy of diagnostic parameters directly affect the diagnostic efficiency and maintenance quality of vehicles.

[0016] Diagnostic parameters include, but are not limited to, the following categories: Diagnostic Trouble Code (DTC): Used to indicate potential vehicle faults. Each DTC has a specific meaning and can help identify specific fault types detected in the ECU.

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

[0018] Freeze Frame Data: When a DTC is triggered, the ECU records and saves various operating parameters of the vehicle at that time. These data are called freeze frame data, which helps in-depth analysis of the specific situation when the fault occurs.

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

[0020] Diagnostic address: The unique address of the ECU in the network, used for communication between diagnostic tools and a specific ECU.

[0021] Security algorithms: Algorithms used to protect the security of diagnostic data and communication, preventing unauthorized access and modification.

[0022] Service response parameters: Parameters related to specific diagnostic services, including operations such as reading DTCs and clearing DTCs.

[0023] Checksum parameters: Parameters to ensure the integrity and correctness of data transmission, such as Cyclic Redundancy Check (CRC) check codes.

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

[0025] Electronic Control Unit (ECU): One of the core components in a vehicle's electronic system, widely used in various vehicle systems such as engine control systems, braking systems, steering systems, vehicle stability control systems, infotainment systems, and even advanced driver assistance systems. 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.

[0026] Diagnostic parameters are important indicators for troubleshooting and analyzing faults in vehicle components. With the intelligent development of automobiles, in-vehicle systems are becoming more intelligent, and with the application of domain control architectures, the design of vehicle diagnostic parameters is more complex and extensive, and the requirements for parameter management are also higher. More intelligent management methods need to be introduced to improve the design efficiency and quality of diagnostic parameters.

[0027] Currently, some major vehicle manufacturers manage diagnostic parameters through Excel spreadsheets, and some have also implemented system management. However, they only put the diagnostic parameters of each vehicle model on the online system for updating. But both products and suppliers are managed according to the product's platformization, and vehicle manufacturers manage and output according to vehicle models. There will be difficulties in reusing and sharing diagnostic parameters, and it is impossible to accurately identify the scope of influence of parameter changes. During the data transfer process from products to vehicle models, information omission and data errors are likely to occur.

[0028] An embodiment of the present invention provides a method for processing diagnostic parameters of a vehicle. Please refer to Figure 1 , including the following steps: S10: Obtain the diagnostic parameters input to the target platform. Among them, 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: diagnostic platform, product system platform, vehicle model platform. The diagnostic platform is used to manage the functional requirements of the vehicle diagnostic system and the parameter attributes of diagnostic parameters. The product system platform is used to manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively; In an embodiment of the present invention, the diagnostic parameters are divided into three platforms for management. In addition to the conventional vehicle model platform, a product system platform and a diagnostic platform are newly added. In the above step S10, the target platform can be a diagnostic platform, a product system platform, or a vehicle model platform, which is determined according to the type and source of the input diagnostic parameters.

[0029] Among them, the diagnosis platform is responsible for managing the functional requirements of the vehicle diagnosis system and the general parameter attributes of diagnostic parameters, such as diagnostic addresses, communication parameters, etc. That is, the diagnosis platform is responsible for managing the general requirements and attributes related to the whole vehicle.

[0030] 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 the power system, chassis system, etc.

[0031] 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 specific vehicle models, including the diagnostic parameters of vehicle model-specific attributes.

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

[0033] Exemplarily, the diagnostic parameters input to the target platform can be performed by online editing or in a batch import manner. For example, the system can receive diagnostic parameters input by diagnostic engineers, system engineers, or product engineers, and determine the target platform according to the input platform.

[0034] In the present invention, by obtaining the diagnostic parameters input to the target platform, it is ensured that the input of diagnostic parameters is an organized process. Engineers of different roles input the parameters to the correct platform according to their permissions and responsibilities, avoiding data chaos and incorrect input, and improving the efficiency and accuracy of data management.

[0035] S12: Perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result. Among them, the verification result includes the parameters that pass the verification and the parameters that fail the verification; In the embodiments of the present invention, the verification rules are the verification standards and specifications predefined for each platform, which are used to ensure the correctness of the data format, normativity, and association relationship. Exemplarily, the verification rules can be formulated according to different platform requirements and the On-Board Diagnostic System Object Database (ODX) specifications for data input verification, and the verification rules corresponding to different platforms may be different.

[0036] The verification result is the feedback result after data verification. That is, after the verification process is completed, the vehicle diagnosis system will generate a verification result. The verification result includes the diagnostic parameters that pass the verification (parameters that pass the verification) and the diagnostic parameters that fail the verification (parameters that fail the verification), that is, the verification result will clearly indicate which parameters pass the verification and which do not.

[0037] In the present invention, the vehicle diagnostic system validates the input diagnostic parameters according to the validation rules of the target platform to check whether the parameters meet the preset standards. Through strict data validation, the correctness and standardization of the input parameters are ensured, and format and logical errors in data transmission are reduced. At the same time, automated validation reduces the time and workload of manual checking, improves the efficiency of data processing, and enables engineers to focus more on innovation and problem-solving rather than data error correction.

[0038] S14: Update the buffer of the target platform based on the validated parameters, and compare the differences between the buffer data and the platform database data of the target platform to obtain the difference data, where the buffer data is the data stored in the updated buffer, and the platform database data is the diagnostic parameter data stored in the platform database of the target platform; In the embodiment of the present invention, the buffer of the target platform is a temporary storage area for storing the validated diagnostic parameters for further processing and confirmation. It can be understood that the validated diagnostic parameters have not been officially incorporated into the platform database yet, but can be viewed, edited, and managed in the buffer before further review and processing. That is, the establishment of the buffer is mainly to provide a buffer zone so that the upcoming changed diagnostic parameters can be preliminarily processed and reviewed before officially updating the platform database. Exemplarily, different target platforms may correspond to different buffers.

[0039] Each platform (such as a diagnostic platform, a product system platform, a vehicle model platform) has its corresponding platform database for storing the diagnostic parameter data and attribute information of the platform. The platform database contains all the validated and reviewed diagnostic parameters, and the platform database data is the diagnostic parameter data stored in the platform database corresponding to the target platform.

[0040] The difference data is the difference data between the buffer data and the platform database data. By comparing the buffer data and the platform database data, the vehicle diagnostic system identifies the differences between the two, including but not limited to the addition, modification, or deletion of diagnostic parameters. It can be understood that the difference data forms the basis for subsequent change records and is used to guide the official change of diagnostic parameters.

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

[0042] Meanwhile, the vehicle diagnostic system also compares the data in the buffer with the existing diagnostic parameters in the platform database to identify the differences, such as newly added, modified, or deleted parameters. The comparison process of the differential data provides the ability to track the change history of diagnostic parameters, enabling any modification of diagnostic parameters to be clearly recorded, enhancing the transparency and traceability of data management. It can be seen that the above steps ensure the accuracy and security of data changes, while also facilitating subsequent change analysis and auditing.

[0043] S16: Update the platform database of the target platform based on the differential data.

[0044] In the present invention, the vehicle diagnostic system also updates the platform database of the target platform according to the differential 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.

[0045] Thus, updating the platform database of the target platform based on the differential data realizes the formal recording of diagnostic parameters, ensures that parameter changes are permanently saved, facilitates future query and application, and at the same time helps to maintain the accuracy of data and the consistency of the system. Moreover, the update of the platform database ensures that all relevant parties (such as diagnostic engineers, system engineers, etc.) have the latest diagnostic parameters, improving the work efficiency of the entire team.

[0046] It can be seen that the present invention realizes the accurate output of vehicle diagnostic parameters and the platform management of diagnostic parameters and products through the data linkage of the diagnostic platform, product system platform, and vehicle model platform, which helps to improve the efficiency of diagnostic parameter design and the quality of diagnostic data. That is, the present invention ensures the high precision and standardization of data, improves the efficiency and transparency of data processing, and ultimately enhances the stability and reliability of the entire vehicle diagnostic system.

[0047] Compared with the traditional solution, the present invention ensures the correctness and standardization of input parameters by validating the input diagnostic parameters, reducing format and logical errors in data transmission. At the same time, the present invention provides a temporary and secure data storage environment by storing the validated diagnostic parameters in the buffer, facilitating data review and change management, and avoiding data loss during the database update process.

[0048] In an embodiment of the present invention, by obtaining diagnostic parameters input to a target platform, where 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 model platform. The diagnostic platform is used to manage the functional requirements of a vehicle diagnostic system and the parameter attributes of diagnostic parameters. The product system platform is used to manage diagnostic parameters corresponding to different products or systems respectively. The model platform is used to manage diagnostic parameters corresponding to different vehicle models respectively. Data verification is performed on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes verified parameters and unverified parameters. The buffer area of the target platform is updated based on the verified parameters, and the difference between the buffer area data and the platform database data is compared to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform. The platform database of the target platform is updated based on the difference data. Thus, the purpose of constructing a standardized and intelligent diagnostic parameter management system is achieved, thereby realizing accurate data transmission and efficient change management, enhancing the technical effects of system stability and diagnostic reliability, and further solving the technical problem in the related art that using an Excel table to manage diagnostic parameters easily causes omissions and errors in data transmission.

[0049] Optionally, in step S16, updating the platform database of the target platform based on the difference data includes the following execution steps: Step S161, 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 scope and change operation type, where the change record is used to record operations such as modification, addition, or deletion of diagnostic parameters, the data impact scope is used to represent the impact scope of diagnostic parameter changes on different platforms and vehicle models, and the change impact analysis is used to record the impact scope on other platforms except the target platform when the diagnostic parameters of the target platform change; S162: Update the platform database of the target platform based on the change record and the change impact analysis.

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

[0051] The change record is used to detail each change detail of the diagnostic parameters, including the change time, operation type (modification, addition, deletion), and the specific differences in data before and after the change, etc., which are not limited here for easy traceability and analysis.

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

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

[0054] Based on the change records and data impact scope, the vehicle diagnostic system will automatically analyze and record the impact of diagnostic parameter changes on other platforms and vehicle models in the entire vehicle diagnostic system architecture except the target platform, including the list of parameters that may need to be updated, the list of vehicle models or ECUs, etc.

[0055] In the present invention, when the vehicle diagnostic system receives a diagnostic parameter change application for the target platform, it will generate a change record based on the aforementioned differential data and analyze the potential impact of this diagnostic parameter change on other platforms. The generation of the change record provides a complete history of the diagnostic parameter change, facilitating future queries and audits, ensuring the transparency and traceability of data changes. Change impact analysis can pre-inform the possible impact of the change on the entire vehicle diagnostic system, helping decision-makers evaluate the necessity and impact degree of the change, and thus making a more comprehensive approval decision. By automatically analyzing the change impact, the vehicle diagnostic system can notify relevant platforms and vehicle models for necessary updates, avoiding manual notification and data synchronization, saving a large amount of time and human resources. At the same time, the generation process of the change record and change impact analysis helps to maintain the consistency of diagnostic parameters for all platforms and vehicle models in the entire system architecture, preventing system failures or diagnostic errors caused by parameter changes.

[0056] After that, according to the results of the change record and change impact analysis, the vehicle diagnostic system will automatically update the platform database of the target platform. Exemplarily, based on the change record, the vehicle diagnostic system will apply the approved diagnostic parameter modification, addition, or deletion operations to the platform database of the target platform. For example, if the change record shows that the description of a certain DTC needs to be modified, then this modification will be implemented in the platform database. If the change impact analysis indicates that this change will also affect other platforms or vehicle models, the vehicle diagnostic system will automatically synchronize the modifications described in the change record to the platform databases of these platforms to ensure that the diagnostic parameters of all relevant platforms are consistent and accurate.

[0057] In the present invention, the vehicle diagnostic system updates the platform database of the target platform based on the change record and change impact analysis. Through cross-platform synchronization, it ensures that the diagnostic parameter data of all relevant platforms is consistent, avoiding diagnostic errors or system failures caused by inconsistent data. At the same time, the automated data update and cross-platform synchronization process significantly reduces the need for manual intervention, improves the efficiency of data update, and reduces the error rate.

[0058] Thus, through the data linkage of the diagnostic platform, product system platform, and vehicle model platform, the present invention intelligently manages processes such as the change and verification of diagnostic parameters, realizes the accurate output of vehicle model diagnostic parameters and the platform management of diagnostic parameters and products, which helps to improve the efficiency of diagnostic parameter design and enhance the quality of diagnostic data. It can be seen that the present invention ensures the high precision and standardization of data, improves the efficiency and transparency of data processing, realizes seamless data synchronization across platforms and vehicle models, provides strong support for decision-making, and ultimately enhances the stability and reliability of the entire vehicle diagnostic system.

[0059] Compared with the traditional solution, the present invention automatically identifies and analyzes the impact of parameter changes on other platforms and vehicle models, generates change records and impact analysis reports, ensures the transparency and traceability of changes, and reduces the omission of data updates for each platform. In addition, the cross-platform synchronization mechanism of the present invention realizes the intelligent synchronous update of changed parameters, ensures the consistency and accuracy of all relevant platform databases, greatly improves the reusability and sharing of data, and avoids errors and inefficiencies caused by manual updates.

[0060] Optionally, in step S10, obtaining the diagnostic parameters input to the target platform includes the following execution steps: Step S101, in response to the target platform being the diagnostic platform, obtaining the diagnostic parameters imported into the diagnostic platform based on a predefined template or a product data exchange database, or obtaining the diagnostic parameters input to the diagnostic platform based on an online editing application; Step S102, in response to the target platform being the product system platform, obtaining the diagnostic parameters imported into the product system platform based on a predefined template or a product data exchange database, or obtaining the diagnostic parameters input to the product system platform based on an online editing application; Step S103, in response to the target platform being the vehicle model platform, obtaining the diagnostic parameters input to the vehicle model platform based on an online editing application.

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

[0062] Predefined templates are usually Excel sheets or files in a similar format, which are used to batch import diagnostic parameter data that conforms to a specific format, facilitating rapid data entry.

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

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

[0065] Specifically, when the target platform is determined to be the diagnostic platform, the vehicle diagnostic system provides two data input methods: batch importing data through a predefined template, or directly inputting data through the online editing application. These two methods ensure that the diagnostic platform can efficiently and accurately receive and manage diagnostic parameters.

[0066] It can be seen that batch importing through a predefined template or the PDX database accelerates the data input process, reduces manual input errors and workload, thereby improving data input efficiency. The online editing application provides the ability to instantaneously modify and add data, enhancing the flexibility and response speed of data management, and achieving flexible data management.

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

[0068] It can be seen that through standardized input methods, the reusability of diagnostic parameters among the same type of products or systems is improved, promoting data reuse. The diagnostic parameters of the product system platform are batch imported or online edited through templates, significantly enhancing the efficiency and accuracy of data management and improving management efficiency.

[0069] For the vehicle model platform, the vehicle diagnostic system only provides the input method of the online editing application, which is suitable for directly editing and managing the unique attributes of the vehicle model, ensuring that the diagnostic parameters of the vehicle model platform can flexibly adapt to different vehicle model requirements.

[0070] It can be seen that the online editing application caters to the unique diagnostic requirements of vehicle models, ensuring that diagnostic parameters can accurately adapt to each vehicle model. Moreover, directly online editing the unique attributes of vehicle models accelerates the customization process of vehicle model diagnostic parameters, improving the immediacy and flexibility of data management.

[0071] 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, including the following execution steps: Step S121, 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 a verification result, where the verification rules are used to verify the data format, data standardization, and data association relationship of the diagnostic parameters.

[0072] In the embodiment of the present invention, when performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, the verification engine of the target platform can be used to perform data verification on the diagnostic parameters based on the verification rules of the target platform. It can be understood that different platforms have corresponding verification engines, and the verification engine 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.

[0073] The verification rules can be a set of well-defined rule sets used to verify whether the data format, data standardization, and data association relationship of the diagnostic parameters meet the standards and requirements. The design of the verification rules should take into account industry standards such as the ODX specification and the logical association between diagnostic parameters.

[0074] The data format refers to the structure and representation form of the diagnostic parameters, ensuring that the data can be correctly recognized and processed by the vehicle diagnostic system. Data standardization usually refers to whether the data conforms to specific industry standards or internal regulations, such as the ODX specification, to ensure the unity and correctness of the data. The data association relationship refers to the logical connection between the diagnostic parameters and other parameters or the vehicle diagnostic system, ensuring the correct reference and interaction of the data in the vehicle diagnostic system.

[0075] In the present invention, the vehicle diagnostic system uses the verification engine of the target platform to automatically verify the input diagnostic parameters according to the pre-defined verification rules. This includes checking whether the data format is correct, whether the data conforms to the ODX specification, and whether the logical relationship between the parameters is reasonable. The verification result will clearly indicate whether the data passes the verification and the specific reasons or error locations for those that do not pass the verification.

[0076] Thus, through the automatic verification process, data format errors, standardization problems, and association errors can be effectively prevented, ensuring data quality. At the same time, by verifying the standardization and association of diagnostic parameters, data problems that may cause vehicle diagnostic system failures can be identified in advance, thereby preventing failures from occurring.

[0077] Optionally, the diagnostic parameter processing method of the vehicle further includes the following execution steps: Step S122: Generate a verification report based on the parameters that fail the verification. The verification report is used to list the parameters that fail the verification and the corresponding problem situations of the parameters that fail the verification.

[0078] In an embodiment of the present invention, after performing data verification on diagnostic parameters and obtaining the verification result, for the parameters that fail the verification, a verification report will also be generated based on the parameters that fail the verification. The verification report is a document generated by the verification engine, listing all the parameters that fail the verification and their specific problem situations. The verification report provides detailed error information, including parameter identification, error type, error location, etc., which is not limited here, so as to facilitate users to quickly locate and solve errors.

[0079] In the present invention, after completing the data verification of diagnostic parameters, if there are parameters that fail the verification, the verification engine will generate a verification report. This report details all the parameters that fail the verification and provides a description of the error situation for each parameter. Users or system administrators can quickly locate the problem parameters based on the information in the report and understand the nature of the problem (e.g., data format error, non - compliance with norms, or error in association relationship), so as to take corresponding measures for correction.

[0080] Thus, the verification report provides clear problem location and description, greatly improving the efficiency of error correction, avoiding blind modification and repeated verification, and improving the efficiency of error location and correction. At the same time, by generating and feeding back the verification report in a timely manner, the impact of data errors on subsequent system operations can be avoided, and system failures can be prevented before they occur.

[0081] Optionally, in step S162, update the platform database of the target platform based on the change record and change impact analysis, including the following execution steps: Step S1621: Determine the target review object based on the data impact scope and change operation type, and use the target review object to review the diagnostic parameter change application; Step S1622: In response to the approval of the diagnostic parameter change application, update the platform database based on the change record and change impact analysis.

[0082] In an embodiment of the present invention, the target review object is determined according to the data impact scope and 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, then the administrator of the product system platform will become the target review object.

[0083] In the present invention, when updating the platform database of the target platform based on the change record and change impact analysis, the vehicle diagnostic system first analyzes the impact scope and operation type of the diagnostic parameter change, and based on this, determines specific roles or personnel who need to participate in the review as the target review objects. Subsequently, these target review objects will conduct a detailed review of the submitted change application to ensure the rationality, necessity, and safety of the change. It can be seen that the participation of the target review objects ensures that each change has been evaluated by professionals, avoids unauthorized changes, and enhances compliance.

[0084] After that, when the diagnostic parameter change application passes the review of the target review objects, the vehicle diagnostic system will automatically update the database of the corresponding platform according to the results of the change record and change impact analysis. That is, the specific details of the change will be applied to the database to ensure that the data on all relevant platforms remains consistent and up-to-date, improving the accuracy and timeliness of the data.

[0085] Optionally, in step S1621, determining the target review objects based on the data impact scope and change operation type includes the following execution steps: Step S16211, in response to the change operation type being a modification operation or an addition operation, and the data impact scope having an impact on the target platform, determining the target review objects as the review objects corresponding to the target platform; or, Step S16212, in response to the change operation type being a deletion operation, determining based on the data impact scope whether it affects platforms other than the target platform; Step S16213, in response to having an impact on platforms other than the target platform, determining the target review objects as the review objects corresponding to platforms other than the target platform; Step S16214, in response to not having an impact on platforms other than the target platform, determining the target review objects as the review objects corresponding to the target platform.

[0086] In the embodiment of the present invention, when determining the target review objects based on the data impact scope and change operation type, if the change operation is to modify or add diagnostic parameters, and these change operations have a direct impact on the data of the target platform (which may be a diagnostic platform, a product system platform, or a vehicle model platform), then the vehicle diagnostic system will determine the administrator or designated reviewer of the target platform as the target review objects. That is, the change application will need to be approved by the review personnel of the target platform before it can be officially implemented.

[0087] If the change operation involves deleting diagnostic parameters, then the vehicle diagnostic system will further analyze the data impact scope to determine whether, in addition to the original target platform, there are other platforms that also reference or depend on this parameter, thereby preventing irreversible impacts on other platforms caused by accidental deletion.

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

[0089] If it is confirmed that the deletion operation will not affect other platforms, then the vehicle diagnostic system only needs the reviewers of the target platform to participate in the approval of the change application. In this case, the approval of the change is more direct, reducing unnecessary approval links and accelerating the processing speed of the change application.

[0090] It can be seen that the vehicle diagnostic system can intelligently determine the target review objects according to different types of change operations and the scope of data impact, ensuring both the proper review of changes and promoting cross-platform collaborative decision-making. At the same time, it optimizes the approval process and improves the efficiency and security of the entire diagnostic parameter management system in terms of change management.

[0091] Optionally, in step S1622, updating the platform database based on the change record and change impact analysis includes the following execution steps: Step S16221, in response to the target platform being the diagnostic platform, updating the platform database of the diagnostic platform based on the change record and change impact analysis; or, Step S16222, in response to the target platform being the 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 model platform and the target version data of the vehicle model platform based on the change record and change impact analysis; or, Step S16223, in response to the target platform being the vehicle model platform, updating the platform database of the vehicle model platform based on the change record and change impact analysis.

[0092] In the embodiment of the present invention, when updating the platform database based on the change record and change impact analysis, if the target platform is determined to be the diagnostic platform, the vehicle diagnostic system will automatically update the database of the diagnostic platform according to the results of the change record and change impact analysis. That is, all the modified contents reflected in the change record will be accurately reflected in the database, ensuring that the data of the diagnostic platform is in the latest and correct state. Thus, it ensures the real-time synchronization of the data of the diagnostic platform with the information in the change record, improving the timeliness and effectiveness of the data.

[0093] If the target platform is the product system platform, then the vehicle diagnostic system not only needs to update the database of the product system platform, but also needs to consider the impact of the changes on the diagnostic platform and the vehicle model platform, and synchronously update the databases of these two platforms. In addition, it is also necessary to update the target version data related to the changes in the vehicle model platform to ensure the accuracy and applicability of the vehicle model diagnostic data. Among them, the target version data is the main version, that is, the latest valid version of the diagnostic parameters stored in the vehicle model platform.

[0094] Thus, cross-platform data synchronization is achieved, ensuring data consistency among the product system platform, the diagnostic platform, and the vehicle model platform, and avoiding development delays or diagnostic failures caused by data asynchronization. At the same time, version management optimization is realized, with special attention paid to the update of the target version in the vehicle model platform, which helps to maintain the version consistency of the vehicle model diagnostic parameters and simplifies the complexity of version management.

[0095] If the target platform is determined to be the vehicle model platform, then the vehicle diagnostic system will only update the database of the vehicle model platform based on the change record and change impact analysis. This is usually executed when the diagnostic parameters unique to the vehicle model platform change, ensuring that only vehicle model-related data is updated without affecting the data of other platforms. Thus, only the data of the vehicle model platform is updated, reducing unnecessary consumption of computing resources and improving the pertinence and efficiency of data update.

[0096] 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, ensuring the timeliness and accuracy of the data. At the same time, through change impact analysis and target version update, it maintains the cross-platform data consistency and the applicability of vehicle model diagnostic parameters, greatly improving the stability and efficiency of the vehicle diagnostic system. It also optimizes the version management process, reducing data conflicts and maintenance costs.

[0097] Optionally, 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 change impact analysis in step S16222, the following execution steps are further included: Step S162221, copy the updated target version data to obtain the first copied version data; Step S162222, freeze the first copied version data to obtain the first frozen version data; Step S162223, export the first frozen version data and publish the first frozen version data.

[0098] In the embodiments of the present invention, 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 change impact analysis, the vehicle diagnostic system will also copy the latest target version data to generate the first copied version data. This copying process ensures the security of the original data and avoids data risks caused by direct modification of the real-time database in subsequent operations. Thus, by copying instead of direct modification, the integrity of the original data is ensured, facilitating data backup and fault recovery. At the same time, the copied version data forms a new version, facilitating the tracking and management of the change history and providing the possibility for subsequent version control and data traceability.

[0099] After that, the vehicle diagnostic system freezes the first copied version data to generate the first frozen version data. It can be understood that the frozen data is used as the final reference version, and no further modification is allowed to the frozen data. Thus, the first frozen data version avoids data changes before release and ensures the accuracy of the data at the time of release. At the same time, the first frozen version data, as the standard version, is convenient for distribution to different downstream systems or development teams, simplifying the data distribution process.

[0100] Finally, the vehicle diagnostic system exports the first frozen version data and publishes the first frozen version data, that is, the product system platform data is published. Exemplarily, the frozen first frozen version data can be converted into a format suitable for use by external systems or devices, such as EXCEL, PDF, PDX, etc., facilitating data transfer and use. By exporting and converting the frozen first copied version data into a compatible format and then officially publishing it, the publishing process pushes the data version to each system and team that needs to use these parameters, ensuring the timely availability of the data.

[0101] Optionally, the diagnostic parameter processing method of the vehicle further includes the following execution steps: Step S162224, in response to receiving an electronic control unit diagnostic parameter change application for the vehicle model platform, review the electronic control unit diagnostic parameter change application; Step S162225, in response to the approval of the electronic control unit diagnostic parameter change application, supplement the first frozen version data based on the electronic control unit variant and the vehicle model to obtain the supplementary version data, where the electronic control unit variant is different electronic control unit versions designed for the differences between different vehicle models; Step S162226, copy the supplementary version data to obtain the second copied version data; Step S162227, freeze the second copied version data to obtain the second frozen version data; Step S162228, export the second frozen version data and publish the second frozen version data.

[0102] In the embodiments of the present invention, the diagnostic parameters of the Electronic Control Unit (ECU) refer to specific parameters used to diagnose and monitor the status of the ECU, such as fault codes, sensor data, etc.

[0103] It can be understood that, according to different vehicle models, there are multiple versions of the ECU, that is, ECU variants. The ECU variants are different versions of the electronic control unit designed for the differences between different vehicle models. Each version may contain specific diagnostic parameters to meet the requirements of different vehicle models.

[0104] After the release of the first frozen version of the data (i.e., after the release of the product system platform data), when the vehicle diagnostic system receives a diagnostic parameter change application for a specific ECU of a vehicle model platform, it will initiate an approval process. The corresponding administrator will evaluate the rationality of the change based on the scope of the impact and technical specifications of the change. Thus, unauthorized changes can be prevented through approval, ensuring that the changes comply with technical specifications and corporate policies.

[0105] After that, after the approval of the electronic control unit diagnostic parameter change application, the vehicle diagnostic system will supplement the first frozen version of the data, adding or modifying the diagnostic parameters required for the ECU variant and specific vehicle models. The supplemented data forms the supplemented version of the data, which is ready to enter the next stage. Thus, the supplemented version of the data takes into account the special requirements of different ECU variants and vehicle models, improving the applicability of the diagnostic parameters to specific vehicle models, thereby enhancing the vehicle model applicability. And by distinguishing the ECU variants and vehicle models, refined management of the diagnostic parameters is achieved, better adapting to the development environment of multiple vehicle models and realizing refined management.

[0106] Next, the vehicle diagnostic system copies the supplemented version of the data to form the second copied version of the data, in order to avoid directly modifying the first frozen version of the data and keeping its original state unaffected by subsequent operations. Then, the second copied version of the data is frozen to prohibit any modification, ensuring the stability and consistency before release.

[0107] Finally, the vehicle diagnostic system will export and release the second frozen version of the data, that is, the vehicle model ECU data release, ensuring that all relevant personnel and systems can obtain the latest diagnostic parameter data for subsequent development and testing work. Thus, the export operation ensures that the data is distributed in a standard format, facilitating data exchange and understanding between different systems and teams.

[0108] Optionally, the diagnostic parameter processing method of the vehicle further includes the following execution steps: Step S162229: Generate a vehicle model release document based on the task plan and the second frozen version data. 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. Step S162230: Release the vehicle model release document.

[0109] In the embodiments of the present invention, the task plan refers to the planned arrangements related to the vehicle development cycle, including the tasks, deadlines, and key activities to be completed at different development stages. The task plan provides a time frame and a list of goals for the entire vehicle development process.

[0110] 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.

[0111] 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 according to the preset task plan and in combination with the diagnostic parameter information in the second frozen version data. This vehicle model release document will detail the technical status of the target vehicle model at any given development stage, including all technical parameters, configuration settings, system status, and most importantly, the diagnostic parameters, so as to facilitate the vehicle development, testing, and maintenance teams to obtain the most comprehensive and accurate vehicle model information currently.

[0112] Thus, the vehicle model release document becomes an authoritative information source in vehicle development and maintenance, ensuring that all team members work based on the same dataset, improving the efficiency and quality of team collaboration. At the same time, the diagnostic parameter information included in the vehicle model release document provides clear guidance for vehicle testing and fault diagnosis, helping to quickly locate the problem and improve the efficiency of diagnosis and maintenance.

[0113] Once the vehicle model release document is generated, the next step is to officially release it, that is, to release the vehicle model data. The release process usually involves the digital distribution of the document to ensure that all relevant team members (such as R & D, testing, production, after-sales service, etc. departments) can obtain the complete document in a timely manner, as well as possible updates to the electronic database to enable downstream systems to read and apply these latest diagnostic parameter information.

[0114] Thus, the released document ensures that information can be quickly and accurately conveyed to every team member who needs it, avoiding the information silo phenomenon, accelerating the dissemination and application of information, and thus accelerating the information transmission. Moreover, it ensures that all team members work based on the latest and unified information, eliminating duplicate work and communication barriers caused by inconsistent information, and promoting efficient collaboration among teams. At the same time, downstream teams do not need to search or organize information by themselves and can directly use the data in the vehicle type release document for work, improving the overall work efficiency and productivity.

[0115] It can be seen that the present invention proposes a method and system for intelligently managing vehicle diagnostic parameters. Through the data linkage of the diagnostic platform, product system platform, and vehicle type platform, the entire process of change, verification, review, and release of diagnostic parameters is intelligently managed online, forming standard and reliable diagnostic data. Realizing the accurate output of vehicle type diagnostic parameters and the platform management of diagnostic parameters and products helps improve the efficiency of diagnostic parameter design and enhance the quality of diagnostic data.

[0116] An embodiment of the present invention also provides a vehicle diagnostic system. Figure 2 It is a schematic structural diagram of the vehicle diagnostic system provided by an embodiment of the present invention. As Figure 2 shown, the vehicle diagnostic system includes a diagnostic platform, a product system platform, and a vehicle type platform. Among them, the diagnostic platform serves as a general management platform for vehicle-level diagnostic parameters and is mainly used by diagnostic engineers. Diagnostic engineers can input vehicle-level diagnostic parameters on this platform, including but not limited to diagnostic addresses, communication parameters, DTCs, freeze frames, DIDs, and security algorithms, etc. The platform supports batch import (such as Excel, PDX database) and online editing to ensure the comprehensiveness and real-time update of data.

[0117] The product system platform is jointly used by system engineers, product engineers, and diagnostic engineers. The product system platform is used to manage diagnostic requirements specific to products or systems. The product system platform also supports batch import and online editing, and particularly focuses on diagnostic parameters for productization management, such as attributes like fault setting and recovery conditions, security levels, etc., and can synchronize vehicle type applicability to ensure the consistency and applicability of parameters among different vehicle types.

[0118] Among them, ECU1 can be a specific ECU instance managed in the product system platform. ECU1 may be responsible for controlling a specific function or system of the vehicle, such as engine control, brake system control, etc. ECU platform 1 and ECU platform 2 can be understood as a set of ECUs with similar functions but applicable to different vehicle types or technical standards. Each ECU platform has its own diagnostic parameter standards and definitions to meet the specific requirements of different product lines.

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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.

[0123] It is understandable that Figure 2 The 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.

[0124] 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.

[0125] Automatic verification is one of the cores of the process. No matter which platform the diagnostic parameters are input to, the input parameters will be reviewed to determine whether they comply with the inspection rules corresponding to that platform. For example, data format, standardization (ODX standard), and relevance verification are performed to ensure that the parameters meet the established standards. If the parameters pass the verification, the verified parameters will be updated to the cache area corresponding to that platform. At the same time, the differences between the cache area data and the platform database data of that platform are compared to obtain the difference data.

[0126] If a change request initiated by the requester of the corresponding platform is received, the system generates a change record based on the difference data. At the same time, it analyzes the scope of the impact of the change on different platforms (diagnostic platform, product system platform, vehicle model platform) and vehicle models, and generates a change impact analysis. Based on the change impact analysis, the automatic review role allocation mechanism is activated, and the change request is automatically pushed to the administrators of the relevant platforms to obtain the necessary approvals.

[0127] The approval process is monitored by determining which platform passes the review link. Once the change request of a certain platform is approved, the data will be updated and synchronized to the formal database of that platform. At the same time, for the product system platform and the vehicle model platform, additional data publishing operations will also be triggered. The product system platform data publishing generates an exportable version for software development, and the vehicle model ECU data publishing targets specific vehicle models and ECU variants to ensure software adaptation adjustments.

[0128] Finally, at the specified vehicle model development stage, through vehicle model data publishing, the system summarizes the latest diagnostic parameter versions of all ECUs according to the instructions of the vehicle model administrator, generates the vehicle PDX database and related documents, and sends them to the remote diagnosis and test system, or makes them available for offline diagnostic equipment developers to obtain, thus completing the entire change and publishing process, and achieving the goal of improving the design efficiency and quality of diagnostic parameters.

[0129] Figure 4 It is a schematic diagram of the change impact analysis process provided by an embodiment of the present invention. As Figure 4 shown, if a change request is received, the system will determine which platform the change request comes from. Different platforms mean different contexts and data association networks, which directly affect the subsequent change impact analysis strategy. Once the change source is identified, the system will specifically identify the products or systems specifically involved in the change, as well as the types of parameters, in order to accurately analyze the nature and scope of the change.

[0130] Specifically, if it is determined that the change application comes from the diagnostic platform, the diagnostic parameter type of the change parameter is queried, and the change operation type is judged to determine whether the change request is to add, modify, or delete a certain diagnostic parameter. If it is an addition 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, and updates each attribute content 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 with consistent key attributes according to the change record, and accumulates the version (if the current version of the diagnostic parameter with consistent key attributes is V1.5, the version of the newly created parameter 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 the vehicle model platform logically delete the corresponding parameters of the main version according to the reference relationship.

[0131] If it is determined that the change application comes from the 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, ECU variant name, and diagnostic parameter type, and update the modification content to the vehicle model platform database (update the vehicle model diagnostic parameters to the corresponding vehicle model, and update the ECU diagnostic parameters to the ECU under the vehicle model).

[0132] If it is determined that the change application comes from the product system platform, query the product / system name that initiates the change and the diagnostic parameter type, and then judge the operation type of the data. If it is an addition operation, the product system platform adds a new record and records the initial version V1.0. Query whether the attribute content of the diagnostic platform is consistent with the diagnostic platform definition. If it is consistent, directly reference the diagnostic platform parameters. If it is inconsistent, synchronously update it to the diagnostic platform, and then reference it after the diagnostic platform is updated. Then record the version of the referenced diagnostic platform parameters. After that, the product system platform attributes and vehicle model applicability attribute contents are added to the product system platform database, and at the same time, the diagnostic platform attributes, product system platform attributes, and version information are synchronously updated to the corresponding vehicle models and ECU variants according to the vehicle model applicability. After that, the diagnostic platform is updated according to the upload result of the product system platform. If there is data upload, it is updated according to the method of the diagnostic platform (not elaborated here too much). If there is no data upload, the diagnostic platform updates the attributes of the subordinate subsystem and the subordinate product platform according to the reference relationship.

[0133] In the case of a modification operation, a new record is added to the product system platform, and the version is incremented (if the current version of the diagnostic parameter with the same key attributes is version V1.5, the newly created parameter version is V1.6). The product system platform determines the modified parameter attributes. If they are diagnostic platform attributes (i.e., platform attributes), it queries whether the content of the modified diagnostic platform attributes is consistent with the diagnostic platform definition. If it is consistent, the reference relationship is updated; if not, it is synchronously updated to the diagnostic platform, and after the diagnostic platform is updated, it is referenced, and then the version of the diagnostic platform parameter reference is recorded. If they are product system platform attributes and vehicle type applicability attributes (i.e., other attributes), they are updated to the product system platform database, and then the diagnostic platform attributes, product system platform attributes, and version information are synchronously updated to the corresponding vehicle type and ECU variant of the vehicle type platform according to the reference relationship (vehicle type applicability attributes). After that, the diagnostic platform is updated according to the upload result of the product system platform. If there is data upload, it is updated according to the method of the diagnostic platform (not elaborated here). If there is no data upload, the diagnostic platform updates the attributes of the subordinate subsystem and the subordinate product platform according to the reference relationship.

[0134] In the case of a modification operation, for all attribute contents of the diagnostic parameters corresponding to the product system platform, the diagnostic platform deletes the reference relationships of the subordinate subsystem and the subordinate product platform, and the vehicle type platform logically deletes the corresponding parameters of the main version according to the reference relationship.

[0135] The following provides an overall description of the diagnostic parameter processing method for the vehicle proposed by the present invention.

[0136] Step 1: Diagnostic parameter input. The diagnostic parameters mentioned in the present invention mainly include parameters involved in ECU diagnostic development such as diagnostic addresses, communication parameters, DTCs, freeze frames, DIDs, and security algorithms.

[0137] The vehicle diagnostic system has three platforms, and each platform has a requirement entry. For different requirements, they can be input from different entries. One is the diagnostic platform, usually diagnostic engineers input general requirements related to the whole vehicle. The input methods support importing according to a predefined template (Excel sheet) and the PDX database, as well as online editing. The second is the product system platform, usually system engineers, product engineers, and diagnostic engineers jointly input diagnostic requirements related to the system and the product. The input methods support importing according to a predefined template (Excel sheet) and the PDX database, as well as online editing. The third is the vehicle type platform, which only supports diagnostic engineers or product engineers to input diagnostic requirements for vehicle type specific attributes, and the input method only supports online editing.

[0138] It can be understood that the data operation types supported by different entries and different input methods are not exactly the same. Among them, batch import on the diagnostic platform supports addition and modification, and online editing supports addition, modification, and deletion; both batch import and online editing on the product system platform support addition, modification, and deletion; online editing on the vehicle type platform supports modification.

[0139] Exemplarily, the definition of diagnostic parameter attributes stored in each platform system can refer to Tables 1 to 3 below.

[0140] Table 1 Diagnostic Platform: The import template contains diagnostic platform attributes

[0141] Table 2 Product System Platform: The import template contains three types of attributes: diagnostic platform attributes, product system platform attributes, and vehicle model applicability

[0142] Table 3 Vehicle Model Platform

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

[0144] Step 2: Automatic Verification. The vehicle diagnostic system determines the platform to which the diagnostic parameter is input, and calls the corresponding platform verification engine to verify the input data (including addition, deletion, modification, reference, etc.) according to the pre-defined verification rules (the rules can configure the error level and whether it takes effect) for data format, data standardization (ODX standard), and data association relationship, and accurately locate the incorrect data. For online input data, the system directly restricts the input data format according to the rules to ensure the correctness of the input data. For batch imported data, if the data verification does not meet the rule items, the system generates a verification report.

[0145] Step 3: Change Analysis 1) Generate a change record If the data verification passes, the vehicle diagnostic system updates the data to the cache area of the corresponding platform (visible and editable only by the role with the current data editing permission). The vehicle diagnostic system will compare the data difference between the cache area and the corresponding platform database, and generate a diagnostic parameter change record when the change application is initiated by the diagnostic requirement requester.

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

[0147] a) Diagnostic platform Query the diagnostic parameter type of the changed parameter, and then determine the data operation type.

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

[0149] Modify: The diagnostic platform adds a new diagnostic parameter under the corresponding category according to the parameter type. For diagnostic parameters with the same key attributes, update according to the change record and increment the version (if the current version of the diagnostic parameter with the same key attributes is V1.5, the version of the newly created parameter is V1.6).

[0150] Delete: The diagnostic platform logically deletes all attribute content of the corresponding diagnostic parameter; the product system platform and the vehicle model platform logically delete the corresponding parameters of the main version according to the reference relationship.

[0151] b) Product system platform Query the name of the product / system where the change is initiated and the diagnostic parameter type, and then judge the operation type of the data.

[0152] New: The product system platform adds a new record and records the initial version V1.0. Query whether the attribute content of the diagnostic platform is consistent with the diagnostic platform definition. If it is consistent, directly reference the diagnostic platform parameter. If it is not consistent, synchronously update it to the diagnostic platform, and then reference it after the diagnostic platform is updated. Then record the version of the referenced diagnostic platform parameter. The product system platform attributes and vehicle model applicability attribute content are added to the product system platform database, and at the same time, according to the vehicle model applicability, synchronously update the diagnostic platform attributes, product system platform attributes, and version information to the corresponding vehicle models and ECU variants. The diagnostic platform is updated according to the upload result of the product system platform. If there is data upload, update it according to the method of the diagnostic platform. If there is no data upload, update the attributes of the subordinate subsystem and the subordinate product platform according to the reference relationship.

[0153] Modify: The product system platform adds a new record and increments the version (if the current version of the diagnostic parameter with the same key attributes is V1.5, the version of the newly created parameter is V1.6). The product system platform judges the modified parameter attributes. If they are diagnostic platform attributes, query whether the modified diagnostic platform attribute content is consistent with the diagnostic platform definition. If it is consistent, update the reference relationship. If it is not consistent, synchronously update it to the diagnostic platform, and then reference it after the diagnostic platform is updated. Then record the version of the referenced diagnostic platform parameter. If they are product system platform attributes and vehicle model applicability attributes, update them to the product system platform database, and then synchronously update the diagnostic platform attributes, product system platform attributes, and version information to the corresponding vehicle models and ECU variants of the vehicle model platform according to the reference relationship (vehicle model applicability attributes). The diagnostic platform is updated according to the upload result of the product system platform. If there is data upload, update it according to the method of the diagnostic platform. If there is no data upload, update the attributes of the subordinate subsystem and the subordinate product platform according to the reference relationship.

[0154] Deletion: Delete all the attribute content of the diagnostic parameters corresponding to the product system platform. The diagnostic platform deletes the reference relationships with its subordinate subsystems and product platforms. The vehicle model platform deletes the parameters corresponding to the main version according to the reference relationship logic.

[0155] c) 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, ECU variant names, and diagnostic parameter types. The modified content can be updated to the vehicle model platform database (the vehicle model diagnostic parameters are updated to the corresponding vehicle model, and the ECU diagnostic parameters are updated to the ECU under the vehicle model).

[0156] 3) Automatic assignment of review roles When initiating a change request, the vehicle diagnostic system updates the affected scope based on the above data and adaptively pushes it to the corresponding data administrator for approval during the approval process. (For example: For new additions and modifications in the diagnostic platform, only the diagnostic platform administrator needs to approve. In the case of deletion, the system needs to further determine whether the corresponding diagnostic parameter is referenced by the product platform (subsystem or product) and the vehicle model platform (vehicle model and ECU variant). If not referenced, the corresponding diagnostic platform administrator can approve. If referenced, it needs to be pushed to the data administrator of the referencing party for approval). The change initiator can select specific users for approval according to the corresponding roles.

[0157] Step 4: Release of product system platform data. After the change request of the diagnostic platform is approved, only the diagnostic platform database needs to be updated. After the change request of the product system platform passes the review, the changed data is updated to the diagnostic platform database and the main version of the vehicle model platform (synchronized with the database update). The product that initiates the change will copy and freeze a diagnostic parameter release version based on the main version and record the version number V1.x (the version is 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.

[0158] Step 5: Release of vehicle model ECU data. After the release of the product system platform data, it is necessary to supplement and improve the vehicle model-specific attributes of the ECU variant on the vehicle model platform. Before the release of specific vehicle model data, initiate an ECU diagnostic parameter change request on the vehicle model platform (at least once per stage, multiple times are allowed). After the vehicle model and ECU administrators approve, the vehicle model platform copies and freezes the ECU variant diagnostic parameter release version based on the main version and records the version number V1.x (the version is automatically incremented) and the release stage (PT0, PT1, etc.). This version also supports the export of diagnostic parameters in formats such as EXCEL, PDF, and PDX, and is released to the product for vehicle model software adaptability adjustment.

[0159] Step 6: Vehicle model data release. In the corresponding vehicle model project phases (such as PT0, PT2, etc.), the task management module of the system initiates tasks for stage freezing and release of vehicle model 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 release of project nodes on the vehicle model platform. The system automatically queries the latest versions of the diagnostic parameters of each ECU in the current stage (including diagnostic addresses, communication parameters, DTCs, freeze frames, DIDs, security algorithms, etc. of all ECUs in the vehicle) and summarizes and updates them under the vehicle model release document directory, and automatically generates a vehicle PDX database. The release files are pushed to the remote diagnostic system and the diagnostic test system as required, and support exporting or downloading the corresponding files under the vehicle model release document directory for output to offline diagnostic device development.

[0160] It can be seen that the present invention inputs diagnostic parameters by supporting batch import and online editing, and verifies the data format, data standardization (ODX standard), and data association relationship of the input data according to the verification rules. An alteration record is automatically generated for the alteration of diagnostic parameters initiated on different platforms. At the same time, the system performs an alteration impact analysis according to the data impact scope and the type of parameter alteration operation, and then automatically assigns review roles in the approval process according to the impact scope. After the corresponding alteration application passes the review, the system updates the versions and releases the data of the product system platform and the vehicle model ECU diagnostic data respectively. In the corresponding project phase, after receiving the tasks of stage freezing and release of vehicle model data, the vehicle model administrator initiates the release of project nodes on the vehicle model platform, and the release files are pushed to the remote diagnostic system and the diagnostic test system as required or output for offline diagnostic device development.

[0161] Thus, through the data linkage among the diagnostic platform, the product system platform, and the vehicle model platform, the present invention realizes the platformized management of diagnostic parameters and products. At the same time, an impact analysis of the platform and vehicle model for the alteration of diagnostic parameters is performed, and the corresponding platforms and vehicle models are automatically updated and synchronized to ensure the accurate output of platform and vehicle model diagnostic parameters. That is to say, through the platformized management of diagnostic parameters and products, the automatic verification of diagnostic data, and the alteration impact analysis, the present invention realizes the automatic update and synchronous release of the standard database of diagnostic data, greatly avoiding possible errors in the process of diagnostic development and application data transmission, improving the efficiency of diagnostic parameter design, and enhancing the quality of diagnostic data.

[0162] An embodiment of the present invention also provides a diagnostic parameter processing device 50 for a vehicle. Please refer to Figure 5, including: an acquisition module 501, configured to acquire diagnostic parameters input to a target platform, where the diagnostic parameters are used to monitor the health status and fault conditions of the 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 the functional requirements of the vehicle diagnostic system and the parameter attributes of the diagnostic parameters. The product system platform is used to manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively; a verification module 502, configured to perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes verified parameters and unverified parameters; a comparison module 503, configured to update the buffer area of the target platform based on the verified parameters, and compare the difference between the buffer area data and the platform database data of the target platform to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform; an update module 504, configured to update the platform database of the target platform based on the difference data.

[0163] Further, the update module 504 is further configured to, in response to receiving a diagnostic parameter change application for the target platform, generate a change record based on the difference data, and generate a change impact analysis according to the data impact scope and the change operation type, where the change record is used to record the modification, addition, or deletion operations on the diagnostic parameters, the data impact scope is used to represent the impact scope of the diagnostic parameter change on different platforms and vehicle models, and the change impact analysis is used to record the impact scope of the change of the diagnostic parameters of the target platform on the remaining platforms other than the target platform; update the platform database of the target platform based on the change record and the change impact analysis.

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

[0165] Further, the verification module 502 is further configured to perform data verification on the diagnostic parameters based on the verification rules of the target platform by using the verification engine of the target platform to obtain a verification result, where the verification rules are used to verify the data format, data standardization, and data association relationship of the diagnostic parameters.

[0166] Further, the device further includes: a processing module, configured to generate a verification report based on the parameters that fail verification, where the verification report is used to list the parameters that fail verification and the problem situations corresponding to the parameters that fail verification.

[0167] Further, the update module 504 is further configured to determine a target review object based on the data influence scope and the change operation type, and review the diagnostic parameter change application by using the target review object; in response to the review of the diagnostic parameter change application being passed, update the platform database based on the change record and the change impact analysis.

[0168] Further, the update module 504 is further configured to, in response to the change operation type being a modification operation or an addition operation, and the data influence scope having an impact on the target platform, determine the target review object as the review object corresponding to the target platform; or, in response to the change operation type being a deletion operation, determine whether it affects other platforms except the target platform based on the data influence scope; in response to having an impact on other platforms except the target platform, determine the target review object as the review object corresponding to other platforms except the target platform; in response to not having an impact on other platforms except the target platform, determine the target review object as the review object corresponding to the target platform.

[0169] Further, the update module 504 is further configured to, in response to the target platform being a diagnostic platform, update the 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, update the platform database of the diagnostic platform based on the change record and the 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 the 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 the change impact analysis.

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

[0171] Further, the device further includes: a second release module, configured to, in response to receiving an electronic control unit diagnostic parameter change application for a vehicle model platform, review the electronic control unit diagnostic parameter change application; and in response to the successful review of the electronic control unit diagnostic parameter change application, supplement the first frozen version data based on the electronic control unit variant and the vehicle model to obtain supplementary version data, where the electronic control unit variant is different electronic control unit versions designed for differences between different vehicle models; copy the supplementary version data to obtain second copied version data; freeze the second copied version data to obtain second frozen version data; and export and release the second frozen version data.

[0172] Further, the device further includes: a third release module, configured to generate a vehicle model release document based on a task plan and the second frozen version data, where the vehicle model release document includes technical parameters, configuration information, system status, and diagnostic parameters of a target vehicle model at any development stage; and release the vehicle model release document.

[0173] According to another aspect of the embodiments of the present invention, there is also provided a vehicle configured to execute the vehicle diagnostic parameter processing method in any one of the above.

[0174] According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium storing a computer program, where the computer program is configured to execute the vehicle diagnostic parameter processing method in any one of the above when running on a computer or a processor.

[0175] Optionally, in this embodiment, the above computer-readable storage medium may be configured to store a computer program for executing the following steps: Step S10: Obtain diagnostic parameters input to a target platform, where 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 manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively; Step S12: Perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes verified parameters and unverified parameters; Step S14: Update the buffer area of the target platform based on the verified parameters, and compare the difference between the buffer area data and the platform database data to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform; Step S16: Update the platform database of the target platform based on the difference data.

[0176] Optionally, in this embodiment, the above computer-readable storage medium may include, but is not limited to: various media such as USB flash drives, read-only memories (ROMs), random access memories (RAMs), mobile hard disks, magnetic disks, or optical discs that can store computer programs.

[0177] The embodiment of the present invention also provides an electronic device 60. Please refer to Figure 6 , which includes a memory 601 and a processor 602. Among them, the memory 601 is used to store a computer program; the processor 602 is used to execute the program stored on the memory 601 to implement the vehicle diagnostic parameter processing method introduced in any embodiment of the present invention.

[0178] Optionally, in this embodiment, the processor in the above electronic device may be set to run a computer program to execute the following steps: Step S10: Obtain the diagnostic parameters input to the target platform. Among them, 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, 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 manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively; Step S12: Perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result. Among them, the verification result includes verified parameters and unverified parameters; Step S14: Update the buffer area of the target platform based on the verified parameters, and compare the difference between the buffer area data and the platform database data to obtain difference data. Among them, the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform; Step S16: Update the platform database of the target platform based on the difference data.

[0179] In the present invention, "a plurality of" means two or more.

[0180] In the present invention, unless otherwise clearly defined, the terms "installation", "connection", and "coupling" shall be understood in a broad sense. For example, it may be a fixed connection, a detachable connection, or an integral connection; it may be a mechanical connection or an electrical connection; it may be a direct connection or an indirect connection through an intermediate medium, and it may be the communication inside two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

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

[0182] The term "and / or" in the present invention is merely a description of the relationship between related objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in the present invention generally represents an "or" relationship between the related objects before and after.

[0183] If there is no special instruction, all steps of the present invention can be carried out in sequence or randomly. For example, the method includes steps A and B, indicating that the method may include steps A and B carried out in sequence, or steps B and A carried out in sequence. For example, it is mentioned that the method may further include step C, indicating that step C can 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.

[0184] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for processing diagnostic parameters of a vehicle, characterized in that, Including: Obtain diagnostic parameters input to a target platform, where 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 the functional requirements of a vehicle diagnostic system and the parameter attributes of the diagnostic parameters. The product system platform is used to manage the diagnostic parameters corresponding to different products or systems respectively. The vehicle model platform is used to manage the diagnostic parameters corresponding to different vehicle models respectively; Perform data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result, where the verification result includes parameters that pass verification and parameters that fail verification; Update the buffer area of the target platform based on the parameters that pass verification, and compare the difference between the buffer area data and the platform database data to obtain difference data, where the buffer area data is the data stored in the updated buffer area, and the platform database data is the data stored in the platform database of the target platform; Update the platform database of the target platform based on the difference data.

2. The diagnostic parameter processing method for a vehicle according to claim 1, characterized in that The 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, generate a change record based on the difference data, and generate a change impact analysis according to the data impact scope and the change operation type. The change record is used to record operations such as modification, addition, or deletion of diagnostic parameters. The data impact scope is used to represent the impact scope of diagnostic parameter changes on different platforms and vehicle models. The change impact analysis is used to record the impact scope on other platforms except the target platform when the diagnostic parameters of the target platform change; Update the platform database of the target platform based on the change record and the change impact analysis.

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

4. The diagnostic parameter processing method for a vehicle according to claim 1, characterized in that, The performing data verification on the diagnostic parameters based on the verification rules of the target platform to obtain a verification result includes: 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 the verification result, where the verification rules are used to verify the data format, data standardization, and data association relationship of the diagnostic parameters.

5. The diagnostic parameter processing method for a vehicle according to claim 1, wherein The method further includes: Generate a verification report based on the parameters that fail the verification, where the verification report is used to list the parameters that fail the verification and the corresponding problem situations of the parameters that fail the verification.

6. The method for processing diagnostic parameters of a vehicle according to claim 2, 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 review object based on the data impact scope and the change operation type, and use the target review object to review the diagnostic parameter change application; In response to the approval of the diagnostic parameter change application, update the platform database based on the change record and the change impact analysis.

7. The method for processing diagnostic parameters of a vehicle according to claim 6, wherein, The determining of the target review 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 an addition operation, and the data impact scope having an impact on the target platform, determine the target review object as the review object corresponding to 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 scope; In response to having an impact on the remaining platforms other than the target platform, determine the target review object as the review object corresponding to the remaining platforms other than the target platform; In response to not having an impact on the remaining platforms other than the target platform, determine the target review object as the review object corresponding to the target platform.

8. The method for processing diagnostic parameters of a vehicle according to claim 6, characterized in that, The updating of the platform database based on the change record and the change impact analysis includes: In response to the target platform being a diagnostic platform, update the 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, update the platform database of the diagnostic platform based on the change record and the 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 the change impact analysis; or, In response to the target platform being the vehicle model platform, update the platform database of the vehicle model platform based on the change record and the change impact analysis.

9. The method for processing diagnostic parameters of a vehicle according to claim 8, characterized in that, 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 method further includes: Copy the updated target version data to obtain a first copied version data; Freeze the first copied version data to obtain a first frozen version data; Export the first frozen version data and publish the first frozen version data.

10. The diagnostic parameter processing method for a vehicle according to claim 9, characterized in that, The method further includes: In response to receiving an electronic control unit diagnostic parameter change application for the vehicle model platform, review the electronic control unit diagnostic parameter change application; In response to the approval of the electronic control unit diagnostic parameter change application, supplement the first frozen version data based on the electronic control unit variant and the vehicle model to obtain a supplemented version data, where the electronic control unit variant is different electronic control unit versions designed for the differences between different vehicle models. Copy the supplementary version data to obtain second copied version data; Freeze the second copied version data to obtain second frozen version data; Export the second frozen version data and release the second frozen version data.

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

Images