Vehicle cloud diagnosis system, method and device and storage medium

Abstract

The invention discloses a vehicle cloud diagnosis system, method and device and a storage medium, and relates to the technical field of intelligent network connection automobiles, and the vehicle cloud diagnosis system comprises a communication protocol module which is used for integrating all communication protocols; the vehicle end module is used for collecting fault information and vehicle type information of a vehicle, receiving the diagnosis file issued by the cloud end module, analyzing the diagnosis file, generating a downloading address, obtaining a diagnosis script by accessing the downloading address, and executing the diagnosis script by calling a script engine; the cloud module is used for receiving the fault information and the vehicle type information sent by the vehicle end module, making a diagnosis script according to the fault information and the vehicle type information, packaging the diagnosis script into a diagnosis file, issuing the diagnosis file to the vehicle end module through the communication protocol module, determining a diagnosis result after the diagnosis process is finished, and sending the diagnosis result to the vehicle end module. And performing statistical analysis according to the diagnosis result, and determining an analysis result. The diagnosis efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of intelligent connected vehicle technology, and in particular to a vehicle cloud diagnostic system, method, device and storage medium. Background Art

[0002] In the traditional automobile repair industry, the detection and diagnosis of vehicle faults has long relied on manual work, from preliminary visual inspection and auditory judgment to reading fault codes with professional tools, and then to fault analysis based on experience and vehicle manuals. Each step requires the professional skills and rich experience of maintenance technicians. However, manual diagnosis relies on the personal experience and skills of maintenance technicians. When faced with complex or rare faults, technicians may need to spend a lot of time troubleshooting, including multiple attempts and error correction, which not only prolongs the diagnosis cycle, but also increases the waiting time of customers, resulting in low efficiency in vehicle fault diagnosis.

[0003] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0004] The main purpose of the present application is to provide a vehicle cloud diagnosis system, method, device and storage medium, aiming to solve the technical problem that vehicle failures require manual fault detection, resulting in low fault diagnosis efficiency.

[0005] To achieve the above objectives, the present application proposes a vehicle cloud diagnostic system, the vehicle cloud diagnostic system comprising:

[0006] A communication protocol module, used to integrate all communication protocols, wherein the communication protocols include at least MQTT (Message Queuing Telemetry Transport) protocol, HTTPS (Hypertext Transfer Protocol Secure) protocol and TLS (Transport Layer Security) protocol;

[0007] The vehicle-side module is used to collect the fault information and vehicle model information of the vehicle, upload the fault information and the vehicle model information to the cloud module, receive the diagnosis file sent by the cloud module, parse the diagnosis file, generate a download address, obtain the diagnosis script by accessing the download address, load the diagnosis script, execute the diagnosis script by calling the script engine, and display the execution process on the HMI (Human Machine Interface) interface;

[0008] The cloud module is used to receive the fault information and vehicle model information sent by the vehicle-side module, determine the diagnosis script according to the fault information and vehicle model information, package the diagnosis script into a diagnosis file, send the diagnosis file to the vehicle-side module through the MQTT protocol in the communication protocol module, and display the diagnosis process on the cloud interface when the vehicle-side module executes the diagnosis script, and determine the diagnosis result after the diagnosis process is completed.

[0009] In one embodiment, the vehicle cloud diagnostic system further includes a diagnostic database module, and the diagnostic database module includes:

[0010] A basic diagnostic database, used to store basic diagnostic data and share the basic diagnostic data to the cloud and the vehicle side, wherein the basic diagnostic data includes a specification template, vehicle model information, bus information, diagnostic protocol information, and parts information;

[0011] A diagnostic database, used to store diagnostic data for implementing diagnostic functions, the diagnostic data including diagnostic service information, diagnostic data information, fault code information, diagnostic process information, refresh process information and session information;

[0012] A version management database, used to store and record version data of updates and iterations of the vehicle cloud diagnostic system, the version data including version release information, version review information, version export information, version comparison information and version verification information;

[0013] The log management database is used to record operation logs according to the execution process of the diagnostic script executed by the vehicle side and the process of vehicle fault analysis performed by the cloud, and store the operation logs.

[0014] In one embodiment, the vehicle cloud diagnostic system further includes an interaction module, and the interaction module includes:

[0015] An engineer interaction unit, used to input configuration factors to the cloud, obtain a diagnostic range, a diagnostic script, a diagnostic strategy, and a diagnostic result corresponding to the configuration factors from the cloud, and upload the diagnostic range, the diagnostic script, the diagnostic strategy, and the diagnostic result to the cloud;

[0016] A maintenance interaction unit, used to determine a diagnostic strategy corresponding to a diagnostic script, and perform maintenance operations on the vehicle according to the diagnostic strategy, wherein the maintenance operations include reading fault information, clearing fault information, and remote real-time diagnosis connection;

[0017] A collaborative interaction unit, used to send the vehicle fault information and vehicle model information collected by the vehicle-side module to the cloud module, and send the diagnostic file generated by the cloud module to the vehicle-side module;

[0018] The MAS interaction unit (Mobile Agent Server) is used to regularly synchronize vehicle model information and parts information with the cloud module, and iteratively update the diagnostic data in the diagnostic database module.

[0019] In one embodiment, the vehicle cloud diagnostic system further includes an information security module, and the information security module includes:

[0020] The server security unit is used to assist the vehicle-side module in installing the host security software, ensure that the data uploaded through the interactive module complies with the preset security specifications, and record and audit important security events on the vehicle side;

[0021] Data security unit, used to back up key business data in real time, encrypt and store sensitive data and keys, and protect data using verification codes and encryption technology;

[0022] A communication security unit is used to establish a secure connection between the diagnostic script and the cloud module through the HTTPS protocol in the communication protocol module, encrypt and authenticate data transmission through the TLS protocol in the communication protocol module, continuously perform two-way identity authentication between the cloud module and the vehicle-side module, and provide a PKI (Public Key Infrastructure) interface. The cloud module and the vehicle-side module are developed for compatibility based on the PKI interface. The cloud module calls the PKI interface to perform signature verification on the issued diagnostic tasks, and the vehicle-side module uses the vehicle-side certificate API (Application Programming Interface) interface to verify the signature of the diagnostic tasks.

[0023] In one embodiment, the cloud module includes a management unit, and the management unit is used for system management, vehicle basic data management, diagnostic data management, multi-level diagnostic management and diagnostic task configuration management;

[0024] The system management includes creating and managing user accounts, assigning access rights, dynamically adjusting the type and number of users corresponding to the user accounts, restricting access to specific IP (Internet Protocol) addresses, and configuring account attributes;

[0025] The vehicle basic data management includes information management of vehicle models, parts, vehicles and fault displays;

[0026] The diagnostic data management includes management of diagnostic database and diagnostic sequence files;

[0027] The multi-level diagnosis management includes dividing the whole vehicle into levels according to the whole vehicle level, ECU (Electronic Control Unit) level, multi-vehicle task, and high level, so as to perform fault analysis on the whole vehicle in different levels;

[0028] The diagnostic task configuration management includes managing the diagnostic tasks of multiple vehicles simultaneously and performing task strategy management according to the needs and priorities of each vehicle.

[0029] In one embodiment, the cloud module further includes a diagnosis and repair solution unit, and the diagnosis and repair solution unit is used to:

[0030] Determine a fault entity according to the diagnostic basic data in the diagnostic basic database of the diagnostic database module, wherein the fault entity includes a vehicle, an assembly, a system and a part;

[0031] Determine fault definition information according to the diagnostic data in the diagnostic database in the diagnostic database module, wherein the fault definition information includes a fault phenomenon, a fault code, a fault description and a fault mode;

[0032] Associating the fault entity with the fault definition information;

[0033] Generate a vehicle model-based fault tree according to the association relationship between the fault entity and the fault definition information, wherein the fault tree is used to describe the fault path and fault cause of each vehicle model;

[0034] generating fault attributes according to the fault definition information, wherein the fault attributes include vehicle operation impact level, focus fault service investigation, owner disposal plan and maintenance skill level;

[0035] A diagnosis scheme is determined based on the fault entity, the fault definition information and the fault attribute.

[0036] In one embodiment, the cloud module also includes a fault analysis unit, and the vehicle fault analysis unit is used to perform fault analysis based on the fault information and the vehicle model information to determine a diagnostic strategy, and the fault analysis includes online diagnostic instrument intervention, full vehicle data collection, parts fault analysis, vehicle fault analysis and bus data analysis.

[0037] In addition, to achieve the above purpose, the present application also proposes a vehicle cloud diagnosis method, the vehicle cloud diagnosis system comprising the following steps:

[0038] Integrate all communication protocols, including at least MQTT protocol, HTTPS protocol and TLS protocol;

[0039] Collecting fault information and vehicle model information of the vehicle, uploading the fault information and vehicle model information to the cloud module, receiving the diagnostic file sent by the cloud module, parsing the diagnostic file, generating a download address, obtaining a diagnostic script by accessing the download address, loading the diagnostic script, executing the diagnostic script by calling a script engine, and displaying the execution process on an HMI interface;

[0040] Receive fault information and vehicle type information sent by the vehicle-side module, determine a diagnostic script based on the fault information and vehicle type information, package the diagnostic script into a diagnostic file, send the diagnostic file to the vehicle-side module through the MQTT protocol in the communication protocol module, and when the vehicle-side module executes the diagnostic script, display the diagnostic process on the cloud interface, and determine the diagnostic result after the diagnostic process is completed.

[0041] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle cloud diagnostic device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the vehicle cloud diagnostic method described above.

[0042] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the vehicle cloud diagnostic method described above are implemented.

[0043] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the vehicle cloud diagnostic method described above.

[0044] The vehicle cloud diagnostic system of the present application ensures effective communication between the cloud and the vehicle through standardized communication protocols. The vehicle-side module actively collects the vehicle's fault information and vehicle condition data, and automatically uploads it to the cloud, reducing the delay and errors of manual reporting, and improving the timeliness and accuracy of the data. By receiving the diagnostic script sent from the cloud, the vehicle-side module can autonomously parse and execute without human intervention, greatly improving the diagnostic efficiency; based on the received fault information and vehicle condition data, the cloud-side module can intelligently generate targeted diagnostic scripts, reducing invalid test steps, and improving the pertinence and efficiency of diagnosis. In the present application, the system achieves rapid response and high-precision diagnosis of vehicle fault diagnosis through efficient data transmission of the communication protocol module, automated fault information processing of the vehicle-side module, and intelligent diagnostic script generation and data analysis of the cloud-side module, thereby significantly improving the efficiency of the entire diagnostic process. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0046] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0047] Figure 1 A schematic diagram of the module structure provided for the first embodiment of the vehicle cloud diagnostic system of the present application;

[0048] Figure 2 A schematic diagram of the design of a diagnostic database module provided in Example 2 of the vehicle cloud diagnostic system of the present application;

[0049] Figure 3 A schematic diagram of the design of the vehicle-cloud interconnection process of the vehicle cloud diagnostic system provided in Example 3 of the present application;

[0050] Figure 4 A diagnostic task script and a diagnostic data security flow diagram of a vehicle cloud diagnostic system provided in Example 4 of the present application;

[0051] Figure 5 A schematic diagram of the diagnosis and repair scheme of the vehicle cloud diagnosis system of this application;

[0052] Figure 6 A schematic diagram of the cloud diagnostic system deployment and expansion architecture of the vehicle cloud diagnostic system of this application;

[0053] Figure 7 A schematic diagram of the process flow of the vehicle cloud diagnosis method of this application;

[0054] Figure 8 Schematic diagram of the device structure of the hardware operating environment involved in the vehicle cloud diagnostic method in the embodiment of the present application.

[0055] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0056] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0057] The present application embodiment provides a vehicle cloud diagnostic system, referring to Figure 1 , Figure 1 This is a schematic diagram of the module structure of the vehicle cloud diagnostic system of this application.

[0058] In this embodiment, the vehicle cloud diagnostic system 100 includes: a communication protocol module 10, a cloud module 30 and a vehicle-side module 20.

[0059] The communication protocol module 10 is used to integrate all communication protocols, and the communication protocols at least include the MQTT protocol, the HTTPS protocol and the TLS protocol;

[0060] It should be noted that the communication protocol module 10 is responsible for data transmission and communication security in the vehicle cloud diagnostic system 100. This module can ensure the efficiency and security of data exchange during the vehicle-cloud interaction process by integrating and managing multiple communication protocols.

[0061] The communication protocol is a preset communication protocol, which may include the MQTT (Message Queuing Telemetry Transport) protocol, the HTTPS (Hypertext Transfer Protocol Secure) protocol and the TLS (Transport Layer Security) protocol, etc. These protocols provide encrypted communication and identity authentication functions to ensure the security and reliability of data transmission. In this solution, all communication protocols are integrated separately; vehicle model information may include engine temperature, oil pressure, battery voltage, etc.; fault information may include fault code, time of fault occurrence, etc. The cloud receives vehicle model information and fault information from the vehicle side, and can perform diagnostic script matching or fault diagnosis based on this information; the vehicle side is responsible for collecting the vehicle's real-time operating status information and any detected fault information through various sensors (such as temperature sensors, pressure sensors, etc.).

[0062] MQTT is a lightweight "publish / subscribe" network protocol used in high-latency or unreliable network environments, especially suitable for IoT applications. In the vehicle cloud diagnostic system, MQTT supports the transmission of real-time data streams, enabling the cloud to quickly send diagnostic tasks to the vehicle, and also supports the vehicle to instantly report diagnostic status and results to the cloud. The HTTPS (Hypertext Transfer Protocol Secure) protocol is a protocol that adds a TLS / SSL encryption layer to HTTP. It is mainly used to protect the privacy of network communications and prevent data from being eavesdropped or tampered with during transmission. In the vehicle cloud diagnostic system, HTTPS is mainly used to encrypt data using the TLS / SSL protocol to ensure that sensitive information (such as diagnostic data, user information, etc.) transmitted between the cloud and the vehicle will not be intercepted and interpreted by a third party, protecting user privacy and data security. At the same time, HTTPS uses digital certificates for identity authentication to ensure the legitimacy of both parties in communication and prevent man-in-the-middle attacks and impersonation.

[0063] TLS (Transport Layer Security) is a protocol used in HTTPS to encrypt and decrypt data. TLS provides an encrypted tunnel to ensure that data transmission between the cloud and the vehicle is encrypted, protecting the security of data during transmission. Before data transmission begins, TLS will conduct a handshake process to negotiate encryption algorithms and keys to ensure the security of subsequent communications. TLS supports a secure key exchange mechanism, so even if the communication is monitored, the data cannot be decrypted, further enhancing the security of the system.

[0064] The communication protocol module 10 integrates MQTT, HTTPS and TLS protocols to ensure that the vehicle cloud diagnostic system can communicate in real time during the vehicle-cloud interaction process, improve the efficiency of communication resource utilization, and protect data security and data privacy.

[0065] The vehicle-side module 20 is used to collect fault information and vehicle model information of the vehicle, upload the fault information and the vehicle model information to the cloud module, receive the diagnosis file sent by the cloud module, parse the diagnosis file, generate a download address, obtain the diagnosis script by accessing the download address, load the diagnosis script, execute the diagnosis script by calling the script engine, and display the execution process on the HMI interface;

[0066] It should be noted that the vehicle-side module 20 maintains a connection with the cloud module through the network and receives the diagnostic task issued by the cloud module. After receiving the task, the module will parse the task and obtain a download address pointing to the diagnostic file. By accessing this download address, the required diagnostic file can be downloaded and loaded. The diagnostic script will be added to the task bar and wait for execution. These scripts contain the execution logic of specific diagnostic instructions. When receiving a locally triggered diagnostic instruction, the vehicle-side module will call the script engine, execute the diagnostic script corresponding to the diagnostic instruction, and start the diagnosis. The key steps and information in the execution process will be displayed on the vehicle's human-computer interaction interface (HMI).

[0067] Optionally, the vehicle-side module is the basic unit for implementing diagnostic functions and has a unified communication protocol standard. The cloud diagnostic vehicle-side architecture is mainly composed of the client control end, which has multiple diagnostic components set up inside to meet the diagnostic function requirements. The vehicle-side module divides the diagnostic function into diagnostic script download, script decryption, diagnostic command signature verification and decompression. Among them, the diagnostic script download includes: when the cloud module issues a diagnostic task, it will contain one or more download links or addresses of diagnostic scripts. The vehicle-side module downloads the diagnostic script from the cloud server to local storage based on this information; script decryption includes: in order to protect the confidentiality and integrity of the diagnostic script, the script may be encrypted and stored in the cloud. After receiving the script, the vehicle-side module needs to use a pre-configured key to decrypt and restore the original state of the script; diagnostic command signature verification includes: the cloud module needs to add a digital signature when generating the script to prove the source of the script and that it has not been tampered with. Before executing the diagnostic script, the vehicle-side module will verify the digital signature of the diagnostic instructions in the script to ensure the integrity and authenticity of the diagnostic instructions; decompression includes: the diagnostic script is stored and transmitted in a compressed format, so after the signature verification is successful, the vehicle-side module will decompress these compressed diagnostic instructions. The decompressed instructions can be directly executed by the script engine, thereby starting the vehicle diagnostic process.

[0068] The transmission of vehicle-to-cloud data needs to consider storage space and upload traffic. The cloud diagnostic system adopts a cyclic overwrite method. Older log files will be overwritten by new files. At the same time, the size of log files is reduced by compression processing, thereby saving storage space and traffic consumption during upload. In addition, when storage space is limited, choose to save new log files. Regarding the upload of log files, the system allows users to manually choose to upload logs to the server on the vehicle side, and the cloud can also actively request log files from the vehicle side, or set a preset time interval to automatically upload logs. When the diagnosis fails, the vehicle side will actively upload the log file, which can be transmitted to the corresponding server address according to the trigger function mechanism. In summary, the cloud diagnostic vehicle-side architecture has a high degree of flexibility and scalability, and can effectively be compatible with the Ethernet-based domain controller architecture to realize diagnostic tasks at the vehicle level. At the same time, the vehicle side can extend near-field diagnosis and trigger diagnosis functions.

[0069] The cloud module 30 is used to receive the fault information and vehicle type information sent by the vehicle-side module, determine the diagnostic script according to the fault information and vehicle type information, package the diagnostic script into a diagnostic file, send the diagnostic file to the vehicle-side module through the MQTT protocol in the communication protocol module, and display the diagnostic process on the cloud interface when the vehicle-side module executes the diagnostic script, and determine the diagnostic result after the diagnostic process is completed.

[0070] Optionally, the preset database refers to a database storing various vehicle models and their corresponding diagnostic scripts. This database contains diagnostic scripts corresponding to different vehicle models and different fault conditions, as well as related diagnostic logic and steps; the diagnostic script is a collection of instructions used to guide the vehicle to perform specific diagnostic tasks. These scripts are usually written based on technical documents provided by the manufacturer and contain detection and repair steps for specific faults or problems. The diagnostic logic defines how to select the most appropriate diagnostic script based on fault information and vehicle model information.

[0071] Regarding the matching process, one implementation example may be that the cloud platform first receives fault information and vehicle model information from the vehicle side, parses the information, and extracts key parameters, such as fault codes, vehicle model information, etc.; based on the extracted key parameters, searches for matching diagnostic scripts in a preset database; uses some algorithms or logical judgments to determine the most appropriate diagnostic script. For example, if there are multiple similar scripts, further select the best one based on the vehicle model information; once the best matching diagnostic script is found, the system selects it for subsequent diagnostic tasks; and sends the selected diagnostic script to the vehicle side module to perform specific diagnostic tasks.

[0072] In this embodiment, the vehicle cloud diagnostic system ensures effective communication between the cloud and the vehicle through a standardized communication protocol. The vehicle-side module actively collects the vehicle's fault information and vehicle condition data, and automatically uploads it to the cloud, reducing the delay and errors of manual reporting, and improving the timeliness and accuracy of the data. By receiving the diagnostic script sent from the cloud, the vehicle-side module can autonomously parse and execute it without human intervention, greatly improving the diagnostic efficiency; based on the received fault information and vehicle condition data, the cloud-side module can intelligently generate targeted diagnostic scripts, reducing invalid test steps, and improving the pertinence and efficiency of diagnosis. In this embodiment, the system achieves rapid response and high-precision diagnosis of vehicle fault diagnosis through efficient data transmission of the communication protocol module, automated fault information processing of the vehicle-side module, and intelligent diagnostic script generation and data analysis of the cloud-side module, thereby significantly improving the efficiency of the entire diagnostic process.

[0073] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. On this basis, the vehicle cloud diagnostic system 100 also includes a diagnostic database module 40, see Figure 2 The schematic diagram of the design of the diagnostic database module shown in FIG. 40 includes:

[0074] A basic diagnosis database 41 is used to store basic diagnosis data and share the basic diagnosis data to the cloud and the vehicle side, wherein the basic diagnosis data includes a specification template, vehicle model information, bus information, diagnosis protocol information and parts information;

[0075] A diagnostic database 42, for storing diagnostic data for implementing diagnostic functions, the diagnostic data including diagnostic service information, diagnostic data information, fault code information, diagnostic process information, refresh process information and session information;

[0076] A version management database 43, used to store version data recording the updated iterations of the vehicle cloud diagnostic system, wherein the version data includes version release information, version review information, version export information, version comparison information and version verification information;

[0077] The log management database 44 is used to record operation logs according to the execution process of the diagnostic script executed by the vehicle side and the process of vehicle fault analysis performed by the cloud side, and store the operation logs.

[0078] Specifically, the database module is used to determine the diagnosis script in the cloud.

[0079] According to the vehicle model information, the bus information, the diagnostic protocol information and the parts information corresponding to the vehicle model information are matched in the diagnostic basic database;

[0080] Optionally, the diagnostic basic database is queried based on the vehicle model information to find the bus information, diagnostic protocol information and parts information corresponding to the vehicle model information, ensuring that the data used in the subsequent diagnostic process is consistent with the specific vehicle model, thereby improving the accuracy of the diagnosis and ensuring that the diagnostic script can diagnose the characteristics and configuration of the specific vehicle model.

[0081] Determine a preset script matching the fault information, vehicle model information, bus information, diagnostic protocol information, and part information in a diagnostic database;

[0082] Optionally, the matching conditions include fault information, vehicle model information, bus information, diagnostic protocol information and parts information. The preset script found in the diagnostic database matches the fault condition and configuration of the specific vehicle. The diagnostic database is a database that stores relevant vehicle fault diagnostic scripts, ensuring that the cloud can obtain the correct diagnostic script based on vehicle model information, fault information and other related information; find one or more preset scripts as candidates, which match the input matching conditions, ensuring that the preset script found can effectively diagnose the fault condition of the specific vehicle model.

[0083] Determine whether the preset script meets the preset version standard according to the version information in the version management database;

[0084] Optionally, the version information of the preset script includes the version number, release date, etc. of the script, which is used to verify the compatibility and timeliness of the script. The version management database is a database that stores information about the preset script version, which may contain the version information of all preset scripts, including the version number, release date, applicable vehicle model, etc. The cloud determines whether the preset script meets the preset version standard based on the version information in the version management database, ensuring that the diagnostic script used is the latest or compatible with the current vehicle version, avoiding diagnostic errors caused by version mismatch.

[0085] If it does, the preset script is determined to be a diagnostic script.

[0086] Optionally, if the preset script meets the preset version standard, it is determined as the final diagnosis script.

[0087] For example, suppose that a 2019 Mercedes-Benz EC l ass sedan has a problem with the engine fault warning light on, and the owner requires remote diagnosis. The steps at this time are as follows: match the vehicle model information (S21), input the vehicle model information "2019Mercedes-Benz EC l ass", match the bus information to "CAN bus", the diagnostic protocol information to "OBD-II", and the part information to "engine control unit model X"; determine the preset script (S22), the fault information is "engine fault warning light on", the vehicle model information is "2019Mercedes-Benz EC l ass", the bus information is "CAN bus", the diagnostic protocol information is "OBD-II", and the part information is "engine control unit model X", and determine the matching preset script A; version verification (S23), obtain the version information of the preset script A to be "V2.0", confirm that the preset script A meets the preset version standard; determine the diagnostic script (S24), if the preset script A meets the judgment result of the version standard, then determine the preset script A as the final diagnostic script.

[0088] Based on the second embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the above-mentioned second embodiment can be referred to the above introduction, and will not be repeated in the following. On this basis, the vehicle cloud diagnostic system 100 also includes an interaction module 50, and the interaction module 50 includes:

[0089] An engineer interaction unit 51 is used to input configuration factors to the cloud, obtain a diagnostic range, a diagnostic script, a diagnostic strategy, and a diagnostic result corresponding to the configuration factors from the cloud, and upload the diagnostic range, the diagnostic script, the diagnostic strategy, and the diagnostic result to the cloud;

[0090] It should be noted that the configuration factors may be the vehicle model, year, engine type, known fault codes, recent maintenance records, driving patterns, environmental conditions, etc. By inputting the configuration factors, the cloud-based diagnostic system can customize the diagnostic process based on the specific vehicle conditions and historical data.

[0091] Optionally, after the diagnostic engineer inputs the configuration factors, the cloud diagnostic system returns the corresponding diagnostic scope, diagnostic script, diagnostic strategy and diagnostic results based on the input configuration factors. Among them, the diagnostic scope refers to the list of vehicle components or systems that need to be checked and evaluated determined by the cloud based on the configuration factors; the diagnostic script is a series of preset test steps and procedures for diagnosing specific configuration factors; the diagnostic strategy defines how to execute the diagnostic script, including priority, sequence, conditional branches, etc.; after completing a series of diagnostic steps, the cloud system will generate a report on the vehicle diagnostic results, including any problems found, possible causes, recommended solutions or next actions. After obtaining the above information, it needs to be uploaded directly to the cloud module for subsequent reference.

[0092] A maintenance interaction unit 52, used to determine a diagnostic strategy corresponding to the diagnostic script, and perform maintenance operations on the vehicle according to the diagnostic strategy, wherein the maintenance operations include reading fault information, clearing fault information, and remote real-time diagnosis connection;

[0093] It should be noted that after receiving the diagnostic scripts, which contain the inspection process and steps for the fault conditions, the maintenance interaction unit 52 will determine the corresponding diagnostic strategy based on the content of the diagnostic scripts, including a series of inspection sequences, possible components involved, and required professional tools and equipment.

[0094] Optionally, based on the determined diagnostic strategy, the maintenance interaction unit 52 performs a series of maintenance operations. The maintenance interaction unit 52 will read detailed fault information from the vehicle's electronic control unit (ECU), including fault code, occurrence time and frequency, etc., read the fault code and other related data stored in the vehicle's electronic control unit (ECU), and after the fault is identified and repaired, clear the fault code in the ECU and restore the normal operation of the vehicle; in some cases, advanced technical support may be required to complete the repair. Through the remote real-time diagnostic connection, more professional technicians or manufacturers' experts can be contacted for remote assistance. Remote assistance allows remote experts to directly access the vehicle's ECU to perform more in-depth diagnosis or guide on-site maintenance personnel to perform complex operations.

[0095] The collaborative interaction unit 53 is used to send the fault information and vehicle model information of the vehicle collected by the vehicle-side module to the cloud module, and send the diagnostic file generated by the cloud module to the vehicle-side module;

[0096] As a key component of the vehicle-cloud collaborative system, the collaborative interaction unit 53 is mainly responsible for the information transmission task between the vehicle and the cloud. That is, it uploads the vehicle fault information and vehicle model information collected by the vehicle module to the cloud, and also receives the diagnostic files from the cloud and sends them to the vehicle module for execution, thus realizing the two-way flow of data. Through efficient information interaction, the collaborative ability between the vehicle and the cloud is enhanced.

[0097] The MAS interaction unit 54 is used to periodically synchronize vehicle model information and parts information with the cloud module, and iteratively update the diagnostic data in the diagnostic database module.

[0098] Optionally, the technical center team has built a MAS system for the cloud diagnosis business, which can regularly synchronize vehicle data and vehicle model structure data with the cloud module, and iteratively update the fault information and response methods in the database.

[0099] The design diagram of the vehicle-cloud interconnection process in the above interaction module is as follows: Figure 3 As shown. Among them, the system management module and the diagnostic engineer correspond to the engineer interaction unit, the Dongfeng independent brand 4S store corresponds to the maintenance interaction unit, the vehicle client corresponds to the collaborative interaction unit, and the Dongfeng MAS system corresponds to the MAS interaction unit. This embodiment realizes efficient communication and data exchange between different users and system components through its built-in interaction module. The vehicle cloud diagnostic system can not only provide instant diagnostic support, but also continuously optimize its diagnostic capabilities, while ensuring that the information flow between all relevant parties is unimpeded, thereby improving the vehicle diagnostic effect.

[0100] Based on the third embodiment of the present application, in the fourth embodiment of the present application, the same or similar contents as those in the third embodiment can be referred to the above introduction, and will not be repeated in the following. On this basis, the vehicle cloud diagnostic system 100 also includes an information security module 60, and the information security module 60 includes:

[0101] The server security unit 61 is used to assist the vehicle-side module in installing the host security software, ensure that the data uploaded through the interactive module complies with the preset security specifications, and record and audit important security events on the vehicle side;

[0102] For cloud server security, the system assists the client to complete the installation of host security software to achieve all-round detection and protection of computer viruses and vulnerabilities. The cloud diagnostic system also provides data validity verification function to ensure that the content transmitted through the human-machine input interface meets the system setting requirements. The security audit function can fully cover the client node and conduct an audit process for important security events to avoid unexpected malicious interference.

[0103] Data security unit 62, used to back up key business data in real time, encrypt and store sensitive data and keys, and protect data using verification codes and encryption technology;

[0104] In terms of data security, the cloud diagnostic system provides real-time and regular backup of key business data on the server, encrypts and stores sensitive data and keys, and ensures that internal data is tamper-proof, theft-proof, and loss-proof. Checksum technology and encryption technology are widely used in the security design of the cloud diagnostic system, effectively ensuring the integrity of important data during storage.

[0105] The communication security unit 63 is used to establish a secure connection between the diagnostic script and the cloud module through the HTTPS protocol in the communication protocol module, encrypt and authenticate data transmission through the TLS protocol in the communication protocol module, continuously perform two-way identity authentication between the cloud module and the vehicle-side module, and provide a PKI interface. The cloud module and the vehicle-side module are developed for compatibility based on the PKI interface. The cloud module calls the PKI interface to perform signature verification on the issued diagnostic tasks, and the vehicle-side module uses the vehicle-side certificate API interface to verify the signature of the diagnostic tasks.

[0106] like Figure 4 As shown, Figure 4The diagnostic task script and diagnostic data security process diagram are made public. The diagnostic script is securely connected to the cloud server through the HTTPS protocol. The diagnostic tasks published on the cloud are loaded by the client in an encrypted and signed manner. The cloud diagnostic server and the client are authenticated through the TLS protocol. The vehicle and the cloud both continuously perform two-way identity authentication and information identification based on encrypted communication to ensure the safe operation of cloud diagnosis in real time. The technical center team provides a PKI interface for the cloud diagnostic service. The cloud diagnostic server and the client are developed for compatibility based on the standard interface. Through signature verification, session symmetric encryption and other methods, middle-level hidden dangers such as attacks or replay are avoided to ensure the safe passage of cloud diagnostic data. The cloud diagnostic server calls the PKI system of the technical center to perform signature verification on the issued diagnostic tasks. The client module uses the vehicle-side certificate API interface for signature verification, so that the security design of the cloud diagnostic system meets expectations.

[0107] This embodiment uses various security units to enable the vehicle cloud diagnostic system to build a solid defense system to protect vehicle data from network attacks, while ensuring that communications between all participants are secure and reliable, which not only improves the user experience but also enhances the stability of the entire system.

[0108] In a feasible implementation manner, the cloud module 30 includes a management unit 31, and the management unit 31 is used for system management, vehicle basic data management, diagnostic data management, multi-level diagnostic management and diagnostic task configuration management;

[0109] The system management includes creating and managing user accounts, assigning access rights, dynamically adjusting the type and number of users corresponding to the user accounts, restricting access to specific IP addresses and configuring account attributes;

[0110] Optionally, system management is a functional module for authority division, which mainly realizes user login management and user authority division, and can dynamically adjust the user type and number of clients. At the same time, the system management function establishes a safe and long-term mechanism for IP address control and account attribute configuration, which effectively guarantees the information security of vehicle users.

[0111] The vehicle basic data management includes information management of vehicle models, parts, vehicles and fault displays;

[0112] Optionally, basic vehicle data management includes information management of vehicle models, parts, vehicles and fault displays, and can complete data such as basic vehicle content and vehicle topology, diagnostic specification information, parts configuration and replacement history, fault-related records, etc.

[0113] The diagnostic data management includes management of diagnostic database and diagnostic sequence files;

[0114] Optionally, diagnostic data management is a collection of diagnostic database and diagnostic sequence file storage. The vehicle diagnostic specifications independently developed by the technical center will be imported into the diagnostic database. The management end can review, download, save, update and version iteration of diagnostic data in this module. At the same time, the closed-loop management of diagnostic data is achieved through the processes of compiling and importing sequence files, reviewing and publishing, downloading and saving, and dividing permissions.

[0115] The multi-level diagnosis management includes dividing the whole vehicle into levels according to the whole vehicle level, ECU level, multi-vehicle task, and high level, so as to perform fault analysis on the whole vehicle in different levels;

[0116] The implementation method of multi-level diagnosis quantitative basic diagnosis can complete the functional requirements of vehicle level, ECU level, multi-vehicle task, and high-level respectively, and comprehensively complete the troubleshooting of the whole vehicle.

[0117] The diagnostic task configuration management includes managing the diagnostic tasks of multiple vehicles simultaneously and performing task strategy management according to the needs and priorities of each vehicle.

[0118] Diagnostic task configuration management mainly realizes multi-vehicle task diagnosis. Task division is refined into task strategy management, diagnostic task viewing, diagnostic task review and diagnostic task release according to different energy levels. The cloud diagnosis cloud platform will eventually conduct a comprehensive statistical analysis of the diagnostic tasks, view and analyze the diagnostic results, and execute processes such as log download and result storage.

[0119] This implementation method can ensure the stable operation of the vehicle cloud diagnosis system through various management units, while improving the diagnosis efficiency, optimizing resource utilization, and providing users with a better service experience. At the same time, its powerful data management and authority control capabilities further improve the security of the system.

[0120] In a feasible implementation manner, the cloud module 30 further includes a diagnosis and repair solution unit 32, and the diagnosis and repair solution unit 32 is used to:

[0121] Determine a fault entity according to the diagnostic basic data in the diagnostic basic database of the diagnostic database module, wherein the fault entity includes a vehicle, an assembly, a system and a part;

[0122] Determine fault definition information according to the diagnostic data in the diagnostic database in the diagnostic database module, wherein the fault definition information includes a fault phenomenon, a fault code, a fault description and a fault mode;

[0123] Associating the fault entity with the fault definition information;

[0124] Generate a vehicle model-based fault tree according to the association relationship between the fault entity and the fault definition information, wherein the fault tree is used to describe the fault path and fault cause of each vehicle model;

[0125] generating fault attributes according to the fault definition information, wherein the fault attributes include vehicle operation impact level, focus fault service investigation, owner disposal plan and maintenance skill level;

[0126] A diagnosis scheme is determined based on the fault entity, the fault definition information and the fault attribute.

[0127] It should be noted that after receiving the fault information and vehicle model information sent by the vehicle-side module, the cloud module matches the fault information and vehicle model information in the diagnosis and repair plan unit to obtain a diagnosis plan, and then the diagnostic script is created by the preset tools in the cloud module.

[0128] like Figure 5 As shown, Figure 5 The schematic diagram of the association of the diagnosis and repair schemes was made public. The cloud diagnosis system retrieves and classifies faults based on the diagnostic information in the database, and associates the fault entity with the fault definition. The fault entity is a mechanical device that may have problems at the vehicle-side user level, such as vehicles, assemblies, systems and components. The definition part divides the fault phenomenon, fault code, fault description and fault mode according to the specific fault occurrence. The cloud diagnosis system generates a vehicle-specific fault tree by associating the fault entity with the fault definition, and further improves the interoperability of the two through a large amount of data training and analysis. The fault attributes are generated based on the content of the fault definition, and the four-level attributes of vehicle operation impact level, focus fault service investigation, owner disposal plan and maintenance skills are gradually improved. The final after-sales diagnosis plan associates the above three contents, and publishes the fault tree, diagnosis plan, maintenance procedure and verification plan to the cloud respectively. The specific diagnosis and repair plan implements targeted disposal according to the specific definition attributes.

[0129] In this implementation, the diagnosis and repair solution unit is an important component of the cloud module. Its main responsibility is to process diagnostic data, generate detailed fault analysis and repair suggestions, and quickly locate the cause of the fault problem by establishing a fault tree. This not only improves the accuracy of diagnosis, but also speeds up the maintenance process and reduces the time for fault handling.

[0130] In a feasible implementation, the cloud module 300 also includes a fault analysis unit 33, and the vehicle fault analysis unit 33 is used to perform fault analysis based on the fault information and the vehicle model information to determine a diagnostic strategy, and the fault analysis includes online diagnostic instrument intervention, full vehicle data collection, parts fault analysis, vehicle fault analysis and bus data analysis.

[0131] It should be noted that the system can complete the fault collection and vehicle condition data collection steps based on the basic fault alarm. After the basic information is obtained, the fault analysis module takes over the diagnostic process and adopts diagnostic processes such as online diagnostic instrument intervention, full vehicle data collection, parts fault analysis, vehicle fault analysis and bus data analysis to perform fault analysis, determine the diagnostic strategy, and then the cloud module generates a diagnostic script corresponding to the diagnostic strategy based on the preset tool.

[0132] Alternatively, if Figure 6 The diagram of the deployment and expansion architecture of the cloud diagnostic system is shown in the figure. After the above basic diagnosis is completed, the cloud module can also combine big data to build a vehicle model and train and strengthen the model, so as to perform predictive, machine intelligent and virtual diagnosis of fault types. The new diagnostic method combines fault warning and cutting-edge algorithms such as edge computing to effectively improve the execution efficiency and accuracy of system diagnosis.

[0133] This implementation method conducts in-depth analysis based on the collected fault information and vehicle status information to determine an effective diagnostic strategy. Combined with the trained model, it can further improve the accuracy and efficiency of diagnosis and reduce unnecessary disassembly and trial-and-error repairs.

[0134] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the vehicle cloud diagnostic system of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0135] The present application also provides a vehicle cloud diagnosis method, such as Figure 7 As shown, the vehicle cloud diagnosis method is applied to a vehicle cloud diagnosis system, comprising the following steps:

[0136] Step S10, integrating all communication protocols, where the communication protocols at least include MQTT protocol, HTTPS protocol and TLS protocol;

[0137] Step S20, collecting the fault information and vehicle model information of the vehicle, uploading the fault information and the vehicle model information to the cloud module, receiving the diagnosis file sent by the cloud module, parsing the diagnosis file, generating a download address, obtaining a diagnosis script by accessing the download address, loading the diagnosis script, executing the diagnosis script by calling the script engine, and displaying the execution process on the HMI interface;

[0138] Step S30, receiving the fault information and vehicle type information sent by the vehicle-side module, determining a diagnostic script according to the fault information and vehicle type information, packaging the diagnostic script into a diagnostic file, sending the diagnostic file to the vehicle-side module through the MQTT protocol in the communication protocol module, and displaying the diagnostic process on the cloud interface when the vehicle-side module executes the diagnostic script, and determining the diagnostic result after the diagnostic process is completed.

[0139] In a feasible implementation manner, applied to the cloud, the vehicle cloud diagnosis method includes:

[0140] Receiving vehicle model information and fault information uploaded by the vehicle end based on a preset communication protocol, wherein the vehicle end collects the vehicle model information and fault information of the vehicle, and uploads the fault information and the vehicle model information to the cloud based on a preset communication protocol, wherein the preset communication protocol includes MQTT protocol, HTTPS protocol and TLS protocol;

[0141] matching a diagnostic script in a preset database according to the fault information and the vehicle model information;

[0142] The matched diagnostic script is packaged into a diagnostic file, and the diagnostic file is sent to the vehicle end based on the preset communication protocol, wherein the vehicle end receives the diagnostic file sent by the cloud based on the preset communication protocol, parses the diagnostic file, determines the diagnostic script, executes the diagnostic script, and displays the execution process of the diagnostic script, and simultaneously uploads the execution process to the cloud through the preset communication protocol;

[0143] The execution process is received based on the preset communication protocol, a diagnosis result corresponding to the execution process is obtained, and the diagnosis result is output.

[0144] Optionally, the vehicle model information includes vehicle model information, the preset database includes a diagnostic basic database, a diagnostic database, a version database and a log database, and the step of matching the diagnostic script in the preset database according to the fault information and the vehicle model information includes:

[0145] According to the vehicle type information, matching bus information, diagnostic protocol information and parts information corresponding to the vehicle type information in a basic diagnosis database;

[0146] Determining in a diagnostic database a preset script that matches the fault information, the vehicle model information, the bus information, the diagnostic protocol information, and the part information;

[0147] Determining whether the preset script meets the preset version standard according to the version information in the version management database;

[0148] If it does, it is determined that the preset script is a diagnostic script.

[0149] Optionally, after the step of packaging the matched diagnostic script into a diagnostic file, the method further includes:

[0150] generating a symmetric encryption key, and using the symmetric encryption key to encrypt the diagnosis file;

[0151] Encrypting the symmetric encryption key by using a preset vehicle-side public key;

[0152] Sign the encrypted diagnostic file using the preset cloud private key to generate a digital signature file;

[0153] The encrypted diagnostic file, the digital signature file and the encrypted symmetric encryption key are sent to the vehicle end based on the communication protocol.

[0154] Optionally, after the step of receiving the execution process based on the preset communication protocol, the method further includes:

[0155] Receiving the diagnostic log file or the regular log file uploaded by the vehicle end based on the communication protocol, wherein if the vehicle end detects that the diagnostic script execution fails, a diagnostic log file corresponding to the diagnostic script execution process is generated; if an external input log upload instruction is received, a regular log file of the vehicle is generated; deleting historical log files and storing the diagnostic log file or the regular log file; uploading the diagnostic log file or the regular log file to the cloud based on the communication protocol;

[0156] The diagnostic log file or the regular log file is stored in a log database.

[0157] In a feasible implementation manner, applied to a vehicle side, the vehicle cloud diagnosis method includes:

[0158] Collect vehicle model information and fault information, upload the fault information and vehicle model information to the cloud based on a preset communication protocol, wherein the preset communication protocol includes the MQTT protocol, the HTTPS protocol and the TLS protocol, the cloud receives the vehicle model information and fault information uploaded by the vehicle end based on the preset communication protocol, matches the diagnostic script in a preset database according to the fault information and the vehicle model information, packages the matched diagnostic script into a diagnostic file, and sends the diagnostic file to the vehicle end based on the preset communication protocol;

[0159] Receiving the diagnostic file sent by the cloud based on the preset communication protocol, parsing the diagnostic file, and determining a diagnostic script;

[0160] Execute the diagnostic script and display the execution process of the diagnostic script, and simultaneously upload the execution process to the cloud via the preset communication protocol, wherein the cloud receives the execution process based on the preset communication protocol, obtains the diagnostic result corresponding to the execution process, and outputs the diagnostic result.

[0161] In a feasible implementation manner, the step of receiving the diagnostic file sent by the cloud based on the preset communication protocol, parsing the diagnostic file, and determining the diagnostic script includes:

[0162] Receiving the encrypted diagnosis file, the digital signature file, and the encrypted symmetric encryption key sent by the cloud based on the communication protocol;

[0163] Verify the digital signature file using a preset cloud public key;

[0164] After the signature verification is passed, the encrypted symmetric encryption key is decrypted by the preset vehicle-side private key;

[0165] Decrypting the encrypted diagnosis file using the decrypted symmetric encryption key to obtain a decrypted diagnosis file;

[0166] The decrypted diagnosis file is parsed to determine the diagnosis script.

[0167] In a feasible implementation manner, after the step of executing the diagnostic script, the step further includes:

[0168] If it is detected that the execution of the diagnostic script fails, a diagnostic log file corresponding to the execution process of the diagnostic script is generated;

[0169] If an externally input log upload instruction is received, a conventional log file of the vehicle is generated;

[0170] Deleting the historical log file and storing the diagnostic log file or the regular log file;

[0171] The diagnostic log file or the regular log file is uploaded to the cloud based on the communication protocol, wherein the cloud receives the diagnostic log file or the regular log file uploaded by the vehicle based on the communication protocol, and stores the diagnostic log file or the regular log file in a log database.

[0172] The vehicle cloud diagnosis method provided by the present application adopts the vehicle cloud diagnosis system in the above-mentioned embodiment, which can solve the technical problem that vehicle faults require manual fault detection, resulting in low fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the vehicle cloud diagnosis method provided by the present application are the same as the beneficial effects of the vehicle cloud diagnosis system provided by the above-mentioned embodiment, and the other technical features in the vehicle cloud diagnosis method are the same as the features disclosed in the above-mentioned embodiment, which will not be repeated here.

[0173] The present application provides a vehicle cloud diagnostic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above-mentioned vehicle cloud diagnostic method.

[0174] Reference below Figure 8 , which shows a schematic diagram of the structure of a vehicle cloud diagnostic device suitable for implementing the embodiment of the present application. The vehicle cloud diagnostic device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Multimedia Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The vehicle cloud diagnostic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0175] like Figure 8As shown, the vehicle cloud diagnostic device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read On ly Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle cloud diagnostic device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 may allow the vehicle cloud diagnostic device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a vehicle cloud diagnostic device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have instead.

[0176] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0177] The vehicle cloud diagnostic device provided by the present application adopts the vehicle cloud diagnostic system in the above embodiment, which can solve the technical problem that vehicle faults require manual fault detection, resulting in low fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the vehicle cloud diagnostic device provided by the present application are the same as the beneficial effects of the vehicle cloud diagnostic system provided by the above embodiment, and the other technical features in the vehicle cloud diagnostic device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0178] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0179] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0180] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the vehicle cloud diagnostic method in the above-mentioned embodiment.

[0181] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle cloud diagnosis method, and can solve the technical problem that vehicle failures require manual fault detection, resulting in low fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle cloud diagnosis method provided by the above-mentioned embodiment, and will not be repeated here.

[0182] The present application also provides a computer program product, including a computer program, which implements the steps of the vehicle cloud diagnostic method as described above when executed by a processor.

[0183] The computer program product provided by the present application can solve the technical problem that vehicle faults require manual fault detection, resulting in low fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the vehicle cloud diagnosis method provided by the above embodiment, which will not be repeated here.

[0184] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A vehicle cloud diagnostic system, characterized in that: The vehicle cloud diagnostic system comprises: A communication protocol module, used to integrate all communication protocols, wherein the communication protocols at least include MQTT protocol, HTTPS protocol and TLS protocol; The vehicle-side module is used to collect fault information and vehicle model information of the vehicle, upload the fault information and the vehicle model information to the cloud module, receive the diagnosis file sent by the cloud module, parse the diagnosis file, generate a download address, obtain the diagnosis script by accessing the download address, load the diagnosis script, execute the diagnosis script by calling the script engine, and display the execution process on the HMI interface; The cloud module is used to receive the fault information and vehicle model information sent by the vehicle-side module, determine the diagnosis script according to the fault information and vehicle model information, package the diagnosis script into a diagnosis file, send the diagnosis file to the vehicle-side module through the MQTT protocol in the communication protocol module, and display the diagnosis process on the cloud interface when the vehicle-side module executes the diagnosis script, and determine the diagnosis result after the diagnosis process is completed.

2. The vehicle cloud diagnostic system according to claim 1, characterized in that: The vehicle cloud diagnostic system further includes a diagnostic database module, which includes: A basic diagnostic database, used to store basic diagnostic data and share the basic diagnostic data to the cloud and the vehicle side, wherein the basic diagnostic data includes a specification template, vehicle model information, bus information, diagnostic protocol information, and parts information; A diagnostic database, used to store diagnostic data for implementing diagnostic functions, the diagnostic data including diagnostic service information, diagnostic data information, fault code information, diagnostic process information, refresh process information and session information; A version management database, used to store and record version data of updates and iterations of the vehicle cloud diagnostic system, the version data including version release information, version review information, version export information, version comparison information and version verification information; The log management database is used to record operation logs according to the execution process of the diagnostic script executed by the vehicle side and the process of vehicle fault analysis performed by the cloud, and store the operation logs.

3. The vehicle cloud diagnostic system according to claim 2, characterized in that: The vehicle cloud diagnostic system further includes an interaction module, which includes: An engineer interaction unit, used to input configuration factors to the cloud, obtain a diagnostic range, a diagnostic script, a diagnostic strategy, and a diagnostic result corresponding to the configuration factors from the cloud, and upload the diagnostic range, the diagnostic script, the diagnostic strategy, and the diagnostic result to the cloud; A maintenance interaction unit, used to determine a diagnostic strategy corresponding to a diagnostic script, and perform maintenance operations on the vehicle according to the diagnostic strategy, wherein the maintenance operations include reading fault information, clearing fault information, and remote real-time diagnosis connection; A collaborative interaction unit, used to send the vehicle fault information and vehicle model information collected by the vehicle-side module to the cloud module, and send the diagnostic file generated by the cloud module to the vehicle-side module; The MAS interaction unit is used to periodically synchronize vehicle model information and parts information with the cloud module and iteratively update the diagnostic data in the diagnostic database module.

4. The vehicle cloud diagnostic system according to claim 3, characterized in that: The vehicle cloud diagnostic system further includes an information security module, which includes: The server security unit is used to assist the vehicle-side module in installing the host security software, ensure that the data uploaded through the interactive module complies with the preset security specifications, and record and audit important security events on the vehicle side; Data security unit, used to back up key business data in real time, encrypt and store sensitive data and keys, and protect data using verification codes and encryption technology; A communication security unit is used to establish a secure connection between the diagnostic script and the cloud module through the HTTPS protocol in the communication protocol module, encrypt and authenticate data transmission through the TLS protocol in the communication protocol module, continuously perform two-way identity authentication between the cloud module and the vehicle-side module, and provide a PKI interface. The cloud module and the vehicle-side module are developed for compatibility based on the PKI interface. The cloud module calls the PKI interface to perform signature verification on the issued diagnostic tasks, and the vehicle-side module uses the vehicle-side certificate API interface to verify the signature of the diagnostic tasks.

5. The vehicle cloud diagnostic system according to claim 4, characterized in that: The cloud module includes a management unit, which is used for system management, vehicle basic data management, diagnostic data management, multi-level diagnostic management and diagnostic task configuration management; The system management includes creating and managing user accounts, assigning access rights, dynamically adjusting the type and number of users corresponding to the user accounts, restricting access to specific IP addresses and configuring account attributes; The vehicle basic data management includes information management of vehicle models, parts, vehicles and fault displays; The diagnostic data management includes management of diagnostic database and diagnostic sequence files; The multi-level diagnosis management includes dividing the whole vehicle into levels according to the whole vehicle level, ECU level, multi-vehicle task, and high level, so as to perform fault analysis on the whole vehicle in different levels; The diagnostic task configuration management includes managing the diagnostic tasks of multiple vehicles simultaneously and performing task strategy management according to the needs and priorities of each vehicle.

6. The vehicle cloud diagnostic system according to claim 5, characterized in that: The cloud module also includes a diagnosis and repair solution unit, which is used to: Determine a fault entity according to the diagnostic basic data in the diagnostic basic database of the diagnostic database module, wherein the fault entity includes a vehicle, an assembly, a system and a part; Determine fault definition information according to the diagnostic data in the diagnostic database in the diagnostic database module, wherein the fault definition information includes a fault phenomenon, a fault code, a fault description and a fault mode; Associating the fault entity with the fault definition information; Generate a vehicle model-based fault tree according to the association relationship between the fault entity and the fault definition information, wherein the fault tree is used to describe the fault path and fault cause of each vehicle model; generating fault attributes according to the fault definition information, wherein the fault attributes include vehicle operation impact level, focus fault service investigation, owner disposal plan and maintenance skill level; A diagnosis scheme is determined based on the fault entity, the fault definition information and the fault attribute.

7. The vehicle cloud diagnostic system according to claim 6, characterized in that: The cloud module also includes a fault analysis unit, and the vehicle fault analysis unit is used to perform fault analysis based on the fault information and the vehicle model information to determine the diagnosis strategy. The fault analysis includes online diagnostic instrument intervention, full vehicle data collection, parts fault analysis, vehicle fault analysis and bus data analysis.

8. A vehicle cloud diagnosis method, characterized in that: The vehicle cloud diagnosis method is applied to the vehicle cloud diagnosis system as claimed in claim 1, comprising the following steps: Integrate all communication protocols, including at least MQTT protocol, HTTPS protocol and TLS protocol; Collecting fault information and vehicle model information of the vehicle, uploading the fault information and vehicle model information to the cloud module, receiving the diagnostic file sent by the cloud module, parsing the diagnostic file, generating a download address, obtaining a diagnostic script by accessing the download address, loading the diagnostic script, executing the diagnostic script by calling a script engine, and displaying the execution process on an HMI interface; Receive fault information and vehicle type information sent by the vehicle-side module, determine a diagnostic script based on the fault information and vehicle type information, package the diagnostic script into a diagnostic file, send the diagnostic file to the vehicle-side module through the MQTT protocol in the communication protocol module, and when the vehicle-side module executes the diagnostic script, display the diagnostic process on the cloud interface, and determine the diagnostic result after the diagnostic process is completed.

9. A vehicle cloud diagnostic device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the vehicle cloud diagnostic method according to claim 8.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the vehicle cloud diagnostic method as claimed in claim 8 are implemented.

Images