Vehicle diagnosis method, vehicle diagnosis server and storage medium

Abstract

The invention provides a vehicle diagnosis method, a vehicle diagnosis server and a storage medium, and the method comprises the steps: obtaining the vehicle information of a to-be-diagnosed vehicle, the vehicle information comprising a vehicle type and ECU information, and the ECU information comprising each functional part in the to-be-diagnosed vehicle and a data structure of each functional part; a target diagnosis sequence is matched from the diagnosis sequence set according to the functions corresponding to the vehicle types and the functional parts, the diagnosis sequences in the diagnosis sequence set are constructed according to the data structures of the functional parts in the vehicle types, and the diagnosis sequences comprise diagnosis data packets of various functions in the vehicle types; issuing the target diagnosis sequence to the to-be-diagnosed vehicle for diagnosis, and obtaining diagnosis log information; and in combination with a preset diagnosis database and an exception pool, analyzing the diagnosis log information, positioning an exception error reporting point and feeding back a repair method. The diagnosis of the vehicle is realized by means of a diagnosis sequence issued by the server, a framework with a heavy cloud and a light client is provided, and the high expansibility of the diagnosis system is realized.

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnosis technology, and in particular to a vehicle diagnosis method, a vehicle diagnosis server and a storage medium. Background Art

[0002] With the rapid development of the new energy vehicle industry in recent years, the huge number of new energy vehicles has brought about a greater demand for fault diagnosis. Vehicle diagnosis mainly relies on diagnostic instruments, which use vehicle communication protocols to communicate with the vehicle's ECU (Electronic Control Unit). For example, the OBD-II (On-Board Diagnostics II, the second-generation on-board diagnostic system) protocol is one of the most commonly used communication protocols. OBD-II allows the diagnostic instrument to read the fault codes stored in the ECU. Through OBD-II, the diagnostic instrument can monitor the data streams of various sensors of the vehicle in real time, such as engine speed, vehicle speed, water temperature and oxygen sensor data. In addition, the diagnostic instrument also has a human-computer interaction interface, including a display screen, buttons and a touch screen, so that users can easily perform diagnostic operations.

[0003] In related technologies, diagnostic instruments usually adopt a "heavy client, light cloud" architecture, that is, the diagnosis-related codes, resources, etc. are all placed locally on the client, and the cloud is only responsible for account issuance. This architecture leads to two serious problems with diagnostic instruments. The first is low scalability. Currently, diagnostic instruments can usually only diagnose one or two specific models, and the entire client must be updated for any slight modification to the client; the second is low security. Diagnostic instruments usually collect vehicle data and fault information, which involves data privacy and security issues. The local storage of these data may lead to unauthorized access to user data and malicious swiping. Therefore, it is urgent to propose a highly scalable and secure vehicle intelligent diagnosis solution. Summary of the invention

[0004] In view of the above-mentioned shortcomings of the prior art, the present application discloses a vehicle diagnosis method, a vehicle diagnosis server and a storage medium, which are used to solve the technical problem of low scalability of the diagnosis system in the prior art.

[0005] In a first aspect, the present application provides a vehicle diagnosis method, the method comprising: obtaining vehicle information of a vehicle to be diagnosed, the vehicle information comprising vehicle model and ECU information, the ECU information comprising each functional component in the vehicle to be diagnosed and a data structure of each functional component; matching a target diagnostic sequence from a diagnostic sequence set according to the functions corresponding to the vehicle model and each functional component, wherein the diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each functional component in each vehicle model, and the diagnostic sequence comprises a diagnostic data packet of various functions in each vehicle model; issuing the target diagnostic sequence to the vehicle to be diagnosed, diagnosing the vehicle to be diagnosed, and obtaining diagnostic log information; analyzing the diagnostic log information in combination with a preset diagnostic database and anomaly pool, locating anomaly error points and feeding back a repair method.

[0006] In one embodiment of the present application, the method for constructing the diagnostic sequence set includes: obtaining the data structure corresponding to the diagnostic script file and the function of each component in each vehicle model, and creating a diagnostic sequence file according to the diagnostic script file; based on the diagnostic sequence file, converting the data structure corresponding to each functional component in each vehicle model into a diagnostic sequence file format, and obtaining an initial diagnostic data packet for each functional component in each vehicle model; separating the diagnostic logic from the diagnostic data in the initial diagnostic sequence, and obtaining the diagnostic data packet corresponding to each functional component in each vehicle model, wherein the diagnostic logic is sent to the client for storage; based on the diagnostic data packet corresponding to each functional component in each vehicle model, generating the diagnostic sequence for each vehicle model, and obtaining the diagnostic sequence set.

[0007] In one embodiment of the present application, after generating the diagnostic sequence for each vehicle model, it also includes: sending the diagnostic sequence to the client so that the client loads the diagnostic sequence, and verifying and debugging the diagnostic sequence, wherein the verification step includes: diagnostic sequence format, diagnostic sequence content, the diagnostic logic and diagnostic compatibility; configuring exception handling logic in the diagnostic sequence, wherein the exception handling logic is used to handle diagnostic abnormalities in the diagnosis.

[0008] In one embodiment of the present application, before allocating a target diagnostic sequence from the diagnostic sequence set based on the functions corresponding to the vehicle model and each of the functional components, it also includes: monitoring new vehicle models and / or new functions in each vehicle model; if the new vehicle model and / or the new function is detected, constructing a new diagnostic sequence corresponding to the new vehicle model and / or the new function; and adding the new diagnostic sequence to the diagnostic sequence set.

[0009] In one embodiment of the present application, the method for determining the vehicle model includes: obtaining part number information of the vehicle to be diagnosed, the part number information including multiple part numbers; determining whether there is a unique part number in the part number information, wherein the unique part number is used to directly distinguish different vehicle models; if so, determining the vehicle model based on the unique part number; if not, determining a unique intersection of the vehicle models corresponding to all the part numbers in the part number information, and determining the vehicle model based on the unique intersection.

[0010] In one embodiment of the present application, the vehicles to be diagnosed are multiple vehicles, and the diagnostic data packet includes a software upgrade package; the target diagnostic sequence is sent to the vehicles to be diagnosed, the vehicles to be diagnosed are diagnosed, and diagnostic log information is obtained, including: creating a task pool, and putting the electronic control unit flashing operation in each of the vehicles to be diagnosed into the task pool as a flashing task; establishing a connection between the client and each of the vehicles to be diagnosed, and assigning multiple flashing tasks in the task pool to corresponding channels; flashing multiple software upgrade packages concurrently, and after monitoring that multiple flashing tasks are completed, restoring the entire vehicle network and receiving the diagnostic log information returned by each of the vehicles to be diagnosed.

[0011] In one embodiment of the present application, before obtaining the vehicle information of the vehicle to be diagnosed, it also includes: monitoring whether the diagnostic agent in the vehicle to be diagnosed is turned on; if not, using a preset key to securely unlock the ECU of the vehicle to be diagnosed; if so, obtaining the vehicle identification code of the vehicle to be diagnosed, and determining whether the vehicle identification code is pre-stored; if so, requesting a random key to securely unlock the ECU of the vehicle to be diagnosed; if not, generating a temporary authorization file based on the vehicle identification code, and securely unlocking the ECU of the vehicle to be diagnosed based on the validity period and temporary authorization key in the temporary authorization file.

[0012] In one embodiment of the present application, the diagnostic log information is analyzed in combination with a preset diagnostic database and an exception pool, the abnormal error point is located and a repair method is fed back, including: matching the diagnostic log information with the diagnostic database to locate the abnormal error point; based on the abnormal error point, matching the repair method from the exception pool, wherein the exception pool includes the repair method corresponding to each abnormal error point.

[0013] In a second aspect, the present application provides a vehicle diagnostic server, which includes: a determination module for obtaining vehicle information of a vehicle to be diagnosed, wherein the vehicle information includes vehicle model and ECU information, wherein the ECU information includes each functional component in the vehicle to be diagnosed and the data structure of each functional component; a matching module for matching a target diagnostic sequence from a diagnostic sequence set according to the functions corresponding to the vehicle model and each functional component, wherein the diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each functional component in each vehicle model, and the diagnostic sequence includes diagnostic data packets of various functions in each vehicle model; a diagnostic module for sending the target diagnostic sequence to the vehicle to be diagnosed, diagnosing the vehicle to be diagnosed, and obtaining diagnostic log information; an analysis module for analyzing the diagnostic log information in combination with a preset diagnostic database and anomaly pool, locating abnormal error points and feeding back repair methods.

[0014] In a third aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor of a computer, enables the computer to execute the vehicle diagnostic method described in the first aspect.

[0015] As described above, the vehicle diagnosis method, vehicle diagnosis server, and storage medium provided by the embodiments of the present application have the following beneficial effects:

[0016] First, the vehicle model and ECU information of the vehicle to be diagnosed are obtained. The ECU information includes the functional components in the vehicle to be diagnosed and the data structure of each functional component. Then, according to the functions corresponding to the vehicle model and each functional component, the target diagnostic sequence is matched from the diagnostic sequence set. The diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each functional component in each vehicle model. The diagnostic sequence includes the diagnostic data packets of various functions in each vehicle model. The target diagnostic sequence is sent to the vehicle to be diagnosed for diagnosis to obtain the diagnostic log information. Finally, the diagnostic database and the abnormality pool are combined to analyze the diagnostic log information to locate the abnormal error point and feedback the repair method. The diagnostic sequence of various functional components in various vehicle models is constructed through the server, so that the vehicle diagnosis is realized by the diagnostic sequence sent by the server. A heavy cloud and light client architecture is proposed, which is suitable for various functional components of various vehicle models and realizes the high scalability of the diagnostic system.

[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0019] Figure 1 is a schematic diagram of an implementation environment of a vehicle diagnostic service end shown in an exemplary embodiment of the present application;

[0020] Figure 2 is a flow chart of a vehicle diagnosis method shown in an exemplary embodiment of the present application;

[0021] Figure 3 is a schematic diagram of a diagnostic system architecture shown in an exemplary embodiment of the present application;

[0022] Figure 4 is a flowchart of a safe unlocking shown by an exemplary embodiment of the present application;

[0023] Figure 5 is a flowchart of automatic adaptation of a new vehicle model shown in an exemplary embodiment of the present application;

[0024] Figure 6 is a flow chart of vehicle parallel flashing shown in an exemplary embodiment of the present application;

[0025] Figure 7 It is a block diagram of a vehicle diagnostic service end shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0027] It should be noted that the illustrations provided in the following embodiments are only used to illustrate the basic concept of the present application in a schematic manner, and therefore the illustrations only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0028] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0029] Diagnostic instruments usually adopt a "heavy client, light cloud" architecture, that is, the diagnosis-related codes, resources, etc. are all placed locally on the client, and the cloud is only responsible for account issuance. However, the inventors of this application have found that such an architecture still causes two relatively serious problems with diagnostic instruments. The first is low scalability. Currently, diagnostic instruments can usually only diagnose one or two specific car models, and any slight modification to the client must update the entire client; the second is low security. Diagnostic instruments usually collect vehicle data and fault information, which involves data privacy and security issues. The local storage of these data makes user data subject to unauthorized access and malicious swiping.

[0030] Therefore, see Figure 1 , Figure 1 FIG. 1 is a schematic diagram of an implementation environment of a vehicle diagnostic service end shown in an exemplary embodiment of the present application. Figure 1 As shown, the implementation environment includes a vehicle to be diagnosed, a diagnostic system client and a diagnostic system server, wherein the diagnostic system client is connected to the vehicle to be diagnosed, and the diagnostic system server is connected to the diagnostic system client. The diagnostic system server is used to diagnose the vehicle to be diagnosed, and the diagnostic sequences of various functional components in various vehicle models are constructed through the server, so that the diagnosis of the vehicle is realized by relying on the diagnostic sequence issued by the server. A heavy cloud and light client architecture is proposed, which is suitable for various functional components of various vehicle models and realizes high scalability of the diagnostic system.

[0031] See also Figure 2 , Figure 2 is a flow chart of a vehicle diagnostic method shown in an exemplary embodiment of the present application. The method can be applied to Figure 1 The implementation environment shown is a schematic diagram. It should be understood that the method may also be applicable to other exemplary implementation environments, and this embodiment does not limit the implementation environment to which the method is applicable.

[0032] like Figure 2 As shown, in an exemplary embodiment, the vehicle diagnosis method includes at least steps S210 to S240, which are described in detail as follows:

[0033] Step S210, obtaining vehicle information of the vehicle to be diagnosed, wherein the vehicle information includes vehicle type and ECU information, and the ECU information includes each functional component in the vehicle to be diagnosed and the data structure of each functional component.

[0034] See also Figure 3 , Figure 3 FIG. 1 is a schematic diagram of a diagnostic system architecture shown in an exemplary embodiment of the present application. Figure 3 As shown, the diagnostic system architecture includes a vehicle to be diagnosed, a diagnostic system client, and a diagnostic system server. The diagnostic system client establishes a connection with the vehicle to be diagnosed through the OBD (On-Board Diagnostics) interface, and establishes a connection with the diagnostic system client through WLAN (Wireless Local Area Networks). The diagnostic system client locally stores vehicle diagnostic communication protocols, such as the DOCAN (Diagnostic Over CAN) protocol, which performs diagnostic communications on the CAN (Controller Area Network) bus, such as the DOIP (Diagnostic over IP) protocol, which is an Ethernet-based vehicle diagnostic protocol that can adapt to a variety of vehicle diagnostic protocols, store diagnostic logic, write and send diagnostic instructions, and respond to parsing codes. The various vehicle diagnostic functions implemented by the diagnostic system client are all implemented in the form of diagnostic sequences issued by the server.

[0035] After the diagnostic system client establishes a connection with the vehicle to be diagnosed, it first determines whether the vehicle diagnosis uses the DOCAN protocol, the DOIP protocol, or other protocols through the collision protocol. In this way, the diagnostic system can be directly applicable to vehicles with multiple diagnostic protocols, which enhances the scalability of the diagnostic system. After determining the protocol, the diagnostic system client uses the corresponding protocol interface to read the data of the vehicle to be diagnosed. Based on the diagnostic request, the diagnostic system server can obtain the vehicle equipment information and ECU information corresponding to the vehicle to be diagnosed through the diagnostic system client. It should be noted that the ECU information includes the various functional components in the vehicle to be diagnosed and the data structure of each functional component, wherein the functional components include hardware and software, and the data structure of each functional component is the data format of data transmission, function operation, etc. in the functional components.

[0036] In one embodiment, before obtaining the vehicle information of the vehicle to be diagnosed, it also includes: monitoring whether the diagnostic agent in the vehicle to be diagnosed is turned on; if not, using a preset key to securely unlock the ECU of the vehicle to be diagnosed; if so, obtaining the vehicle identification code of the vehicle to be diagnosed, and determining whether the vehicle identification code is pre-stored; if so, requesting a random key to securely unlock the ECU of the vehicle to be diagnosed; if not, generating a temporary authorization file based on the vehicle identification code, and securely unlocking the ECU of the vehicle to be diagnosed based on the validity period and temporary authorization key in the temporary authorization file.

[0037] It should be noted that in order to improve the security of communication between the diagnostic system and the vehicle to be diagnosed, the diagnostic system client directly communicates with the diagnostic agent in the vehicle to be diagnosed, and then communicates with the ECU through the diagnostic agent, where the diagnostic agent is the intermediate layer between the vehicle and the ECU.

[0038] In addition, the ECU is securely unlocked to prevent unauthorized access and malicious attacks from external devices.

[0039] In this example, see Figure 4 , Figure 4 FIG. 1 is a flowchart of a secure unlocking method shown in an exemplary embodiment of the present application. Figure 4 As shown, after the diagnosis system client is connected to the vehicle to be diagnosed, if it is detected that the diagnosis agent in the vehicle to be diagnosed is not turned on, the diagnosis system client communicates with the ECU. At this time, the preset key is used to securely unlock the ECU of the vehicle to be diagnosed, wherein the preset key is the key written by the supplier when leaving the factory; if it is detected that the diagnosis agent is turned on, the diagnosis system client communicates with the diagnosis agent. At this time, the diagnosis system server needs to further determine whether the VIN (Vehicle Identification Number) of the vehicle to be diagnosed is pre-stored. If it is, the vehicle to be diagnosed is in the diagnosis system server, and the diagnosis system server requests a random key for security unlocking. If it is not stored, the vehicle to be diagnosed is not in the diagnosis system server, so the VIN is written into the temporary authorization file, and based on the temporary authorization key in the temporary authorization file, the ECU of the vehicle to be diagnosed is securely unlocked within the validity period, wherein the validity period can be set according to the specific situation to improve the security of accessing ECU data.

[0040] In this embodiment, please continue to see Figure 4 If the temporary authorization file is invalid, it is determined that an abnormal situation has occurred. At this time, the user needs to be reminded to close the diagnostic agent and continue to use the preset key to securely unlock the ECU.

[0041] In this embodiment, the key for securely unlocking the ECU is no longer stored in the diagnostic system client. Instead, the key is obtained through the diagnostic system server and sent to the diagnostic system client through encryption. The logical judgment of determining the method of securely unlocking the ECU is also performed by the diagnostic system server. By judging whether the diagnostic agent is turned on and whether the vehicle to be diagnosed is in the diagnostic system server, the above three methods can meet the diagnostic needs of the three life cycles of automobiles: automobile research and development, production off-line, and after-sales service, that is, the secure unlocking of the ECU in these three periods. It has wide applicability, improves the applicability of the diagnostic system, and can also significantly improve the diagnostic efficiency of staff in the above three scenarios.

[0042] In one embodiment, a method for determining a vehicle model includes: obtaining part number information of a vehicle to be diagnosed, the part number information including multiple part numbers; determining whether there is a unique part number in the part number information, wherein the unique part number is used to directly distinguish different vehicle models; if so, determining the vehicle model based on the unique part number; if not, determining a unique intersection of vehicle models corresponding to all part numbers in the part number information, and determining the vehicle model based on the unique intersection.

[0043] In this embodiment, the diagnostic system client stores various part numbers corresponding to various vehicle models, and the model of the vehicle to be diagnosed can be determined by the part number of the vehicle to be diagnosed. The subsequent newly added vehicle models only need to adapt the part numbers on the diagnostic system server to adapt to the diagnostic needs of multiple vehicle models.

[0044] In addition, in this embodiment, the vehicle models corresponding to all the part numbers in the part number information are a unique intersection, that is, there is a unique vehicle model in the intersection, and it is the vehicle model of the vehicle to be diagnosed.

[0045] In a possible embodiment, according to the difference algorithm and the vehicle type information stored in the diagnostic system server, the new vehicle type is automatically adapted to determine the vehicle type to be diagnosed to adapt to multiple vehicle type requirements, and the steps are as follows: input the stored vehicle type information, cluster all entries according to the vehicle type, part number and supplier; place the new vehicle type configuration in the cluster center; starting from the cluster center, use the difference algorithm to search for all cluster bars that are adapted to the new vehicle type; after determining the cluster bar, screen the unique part number (for example, the uniqueness means that the ECU part number of the vehicle type has only one) to determine the vehicle type; if the part number is not unique, select at least two part number combinations to determine the vehicle type.

[0046] See also Figure 5 , Figure 5 FIG. 1 is a flowchart of automatic adaptation of a new vehicle model shown in an exemplary embodiment of the present application. Figure 5As shown, first input the vehicle model data for clustering, the clustering method is K-means (k-means clustering algorithm), hierarchical clustering or other clustering algorithms, and the class includes two fields, namely, part number and supplier; then configure the new vehicle model as the cluster center, and obtain the number of subclusters of the cluster center, that is, the number of different vehicle models corresponding to the same part number and supplier COUNT1; then determine whether COUNT1 is greater than 1; if COUNT1 is greater than 1, then use the part number fitness as an indicator to calculate the shortest distance D from the adjacent cluster points of each subcluster to all the cluster points in the cluster family that violate the access, and use each subcluster as the cluster center, Re-obtain the number of sub-clusters in the cluster center until COUNT1 is not greater than 1; if COUNT1 is not greater than 1, determine whether COUNT1 is equal to 1; if COUNT1 is equal to 1, add the sub-cluster to the path, and use the sub-cluster as the cluster center, and re-obtain the number of sub-clusters in the cluster center until COUNT1 is less than 1; if COUNT1 is less than 1, take the shortest path and determine whether the path is unique; if there is one and only one path, determine the vehicle model based on the unique path; if the path is not unique, select at least two part numbers to combine and determine the vehicle model.

[0047] As a possible implementation example, by using a difference algorithm, the logic can be automatically organized according to the model information of the vehicle to be diagnosed to adapt to the needs of multiple models. A car brand usually includes multiple models. By using a difference algorithm to integrate all models into one diagnostic system, it can also automatically adapt to the diagnostic needs of new models. The difference algorithm is placed on the diagnostic system server, which improves the intelligence of the diagnostic system.

[0048] Step S220, matching a target diagnostic sequence from a diagnostic sequence set according to the functions corresponding to the vehicle model and each functional component, wherein the diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each functional component in each vehicle model, and the diagnostic sequence includes diagnostic data packets of various functions in each vehicle model.

[0049] In this embodiment, considering that different vehicle models or different functional components of the same vehicle model require different diagnostic data packets corresponding to functions, the diagnostic system server matches a target diagnostic sequence from the diagnostic sequence set according to the specific vehicle model and the specific function to be diagnosed. Therefore, the target diagnostic sequence may include diagnostic data packets of all functional components in the vehicle to be diagnosed, and may also include diagnostic data packets of some functional components in the vehicle to be diagnosed. The diagnostic system server matches and sends the diagnostic sequence according to the specific diagnostic requirements.

[0050] It should be noted that the above-mentioned diagnosis sequence set is stored in the diagnosis database.

[0051] In one embodiment, a method for constructing a diagnostic sequence set includes: obtaining a diagnostic script file and a data structure corresponding to the function of each component in each vehicle model, and creating a diagnostic sequence file according to the diagnostic script file; based on the diagnostic sequence file, converting the data structure corresponding to each functional component in each vehicle model into a diagnostic sequence file format, and obtaining an initial diagnostic data packet for each functional component in each vehicle model; separating the diagnostic logic from the diagnostic data in the initial diagnostic sequence, and obtaining a diagnostic data packet corresponding to each functional component in each vehicle model, wherein the diagnostic logic is sent to a client for storage; based on the diagnostic data packet corresponding to each functional component in each vehicle model, generating a diagnostic sequence for each vehicle model, and obtaining a diagnostic sequence set.

[0052] In this embodiment, the data structure corresponding to the vehicle ECU is defined, a diagnostic sequence file (e.g., a diagnostic sequence file in json format) is created, the data structure is converted into the diagnostic sequence file format, the logic and data of the initial diagnostic data packet are separated, and it is ensured that the diagnostic data packet contains only data, not logic or functions, and the logic and functions are placed locally on the diagnostic system client, that is, only basic running codes are stored locally, and all diagnostic functions are implemented through the diagnostic sequence issued by the diagnostic system server. In this way, the diagnostic system server stores diagnostic data packets of various functions in various vehicle models, which improves the practicality of the diagnostic system.

[0053] In one embodiment, after generating the diagnostic sequence for each vehicle model, it also includes: sending the diagnostic sequence to the client so that the client loads the diagnostic sequence, verifying and debugging the diagnostic sequence, wherein the verification step includes: diagnostic sequence format, diagnostic sequence content, diagnostic logic and diagnostic compatibility; configuring exception handling logic in the diagnostic sequence, wherein the exception handling logic is used to handle diagnostic abnormalities during diagnosis.

[0054] In this embodiment, the generated diagnostic sequence is verified and debugged, so that when the diagnostic system client needs to use a certain diagnostic function, when the diagnostic system server is requested to send the corresponding diagnostic sequence and load it to the client, the client can smoothly implement the corresponding diagnostic function according to the diagnostic sequence, and the exception handling logic is pre-configured in the diagnostic sequence. In this way, in the process of the diagnostic system client loading the diagnostic sequence for vehicle diagnosis, it can promptly and effectively handle loading failures or data format errors, etc., and proposes the construction, use and maintenance of the diagnostic sequence to realize a highly scalable diagnostic system, thereby enhancing the user experience.

[0055] In one embodiment, before allocating a target diagnostic sequence from a diagnostic sequence set based on the functions corresponding to the vehicle model and each functional component, the method further includes: monitoring new vehicle models and / or new functions in each vehicle model; if a new vehicle model and / or new function is detected, constructing a new diagnostic sequence corresponding to the new vehicle model and / or new function; and adding the new diagnostic sequence to the diagnostic sequence set.

[0056] In this embodiment, as the number of vehicle models and functions increases, the diagnostic sequence set needs to be updated and maintained in a timely manner to ensure that the data therein is consistent with the data of the latest vehicle models and functions. When new vehicle models or new functions are added, when the diagnostic system client needs to add new diagnostic functions, no modification of the diagnostic system client is required, that is, the diagnostic system client does not need to be updated, and only a new diagnostic sequence needs to be configured on the diagnostic system server. All diagnostic functions of the diagnostic system client are implemented by the diagnostic sequence issued by the diagnostic system server. The diagnostic system client does not need to store any information about the vehicle model project, which solves the problem of low scalability of the diagnostic system and improves the user experience.

[0057] Step S230 , sending the target diagnostic sequence to the vehicle to be diagnosed, diagnosing the vehicle to be diagnosed, and obtaining diagnostic log information.

[0058] In this embodiment, the diagnostic system server sends the target diagnostic sequence to the diagnostic system client based on the diagnostic request. The diagnostic system client diagnoses the vehicle to be diagnosed according to the logic of the stored diagnostic sequence. The diagnostic system client reads the message log, operation log and operation log of the functions in the vehicle to be diagnosed, that is, the diagnostic log information, and uploads it to the diagnostic system server.

[0059] It should also be noted that the data returned to the diagnostic system by the diagnosed vehicle are stored in an encrypted format locally on the diagnostic system client. After the diagnostic process is completed, they are uploaded to the diagnostic system server together with the diagnostic log information for parsing and management. That is, all data generated by the user during the use of the diagnostic system are first encrypted and then uploaded to the diagnostic system server for storage, parsing, and management. The diagnostic system server can trace back all diagnostic operations through these data, avoiding malicious access to user data and malicious swiping, thereby improving the traceability of the use of the diagnostic system and the security of vehicle diagnostic data.

[0060] In one embodiment, the number of vehicles to be diagnosed is multiple, and the diagnostic data packet includes a software upgrade package; a target diagnostic sequence is sent to the vehicles to be diagnosed, the vehicles to be diagnosed are diagnosed, and diagnostic log information is obtained, including: creating a task pool, and putting the electronic control unit flashing operation in each vehicle to be diagnosed into the task pool as a flashing task; establishing a connection between the client and each vehicle to be diagnosed, and assigning multiple flashing tasks in the task pool to corresponding channels; flashing multiple software upgrade packages concurrently, and after monitoring that multiple flashing tasks are completed, restoring the entire vehicle network and receiving the diagnostic log information returned by each vehicle to be diagnosed.

[0061] It should be noted that software flashing is divided into local flashing and online flashing. Online flashing is the distribution of software upgrade packages by the diagnostic system server. After the software upgrade package is downloaded to the local diagnostic system client, the byte stream is XOR encrypted. After the flashing is completed, the encrypted software package is automatically deleted; local flashing is the local storage and parsing of the software upgrade package by the diagnostic system client.

[0062] In this embodiment, there are two ways to create a task pool. One is that the diagnostic system server distributes the software upgrade package. At this time, the task pool is created through OTA (Over-the-Air Technology). The other is that the diagnostic system client locally stores and analyzes the software upgrade package. At this time, the task pool is created by flashing the diagnostic system client. In addition, both local flashing and online flashing adopt parallel flashing solutions, and parallel flashing needs to be determined according to the network topology diagram of each vehicle model.

[0063] In this example, see Figure 6 , Figure 6 FIG. 1 is a flow chart of a vehicle parallel flashing method shown in an exemplary embodiment of the present application. Figure 6 As shown, each ECU flashing is regarded as a task and put into the task pool, and a connection is created between the upper computer (i.e., the diagnostic system client) and the VDC (Vehicle Dynamic Control) of each vehicle to be diagnosed. The connection is used to send vehicle-level instructions to each vehicle to be diagnosed for preparations before flashing, including the whole vehicle entering an extended session, prohibiting the recording of DTC (Diagnostic Trouble Code), etc., and then a classifier is used to distribute the tasks in the task pool to the corresponding channels. All channels share the connection created above, and then concurrently process the parsing of the software package and the transmission of data, and determine whether all tasks are completed. If all tasks in the task pool are not completed, the flashing operation will continue to be performed. After all tasks are completed, the connection created above will continue to be used to send vehicle-level instructions for vehicle network recovery and DTC recording functions after the flashing is completed, so as to return the diagnostic log information of each vehicle to be diagnosed.

[0064] In this embodiment, the diagnostic system integrates a parallel flashing method, which improves the efficiency and success rate of ECU software flashing.

[0065] Step S240, combining the preset diagnosis database and exception pool, analyzing the diagnosis log information, locating the abnormal error point and feeding back the repair method.

[0066] In this embodiment, due to the different states of the vehicles to be diagnosed, many unexpected situations may occur when using the diagnostic system client. In order to deal with such abnormal situations, the diagnostic system server has built a set of abnormal monitoring, that is, various abnormal codes are defined in the diagnostic database, and the abnormal pool includes various vehicle abnormalities and corresponding recovery methods. It can combine the diagnostic database and the abnormal pool to analyze the diagnostic log information, locate the abnormal error point and feedback the repair method.

[0067] In one embodiment, the diagnostic log information is analyzed in combination with a preset diagnostic database and an exception pool, the abnormal error points are located and the repair methods are fed back, including: matching the diagnostic log information with the diagnostic database to locate the abnormal error points; based on the abnormal error points, matching the repair methods from the exception pool, wherein the exception pool includes the repair methods corresponding to each abnormal error point.

[0068] In this embodiment, the diagnostic system server also builds an alarm system that can define monitoring indicators, abnormal thresholds, alarm rules and other data, locate abnormal error points according to the diagnostic database of each ECU, and prompt the user with the corresponding error, and prompt the user how to solve the problem in the error pop-up box. If the problem is not in the abnormal pool, the system will record the problem and upload it to the diagnostic system server with the log file. The operation and maintenance personnel of the diagnostic system server can continuously improve the diagnostic sequence through the problem, thereby ensuring the stability of the entire diagnostic system.

[0069] Please continue to see Figure 3 In the embodiment of the present application, the diagnostic system server implements the above solution by integrating unified login authentication, ECU key management, vehicle configuration information, maintenance plan integration, software flashing, electrical configuration information, vehicle authorization management and diagnostic database.

[0070] The above-mentioned vehicle diagnosis method first obtains the vehicle model and ECU information of the vehicle to be diagnosed, and the ECU information includes each functional component in the vehicle to be diagnosed and the data structure of each functional component. Then, according to the function corresponding to the vehicle model and each functional component, the target diagnostic sequence is matched from the diagnostic sequence set. The diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each functional component in each vehicle model. The diagnostic sequence includes the diagnostic data packet of various functions in each vehicle model. The target diagnostic sequence is sent to the vehicle to be diagnosed for diagnosis to obtain diagnostic log information. Finally, the diagnostic database and the abnormality pool are combined to analyze the diagnostic log information to locate the abnormal error point and feedback the repair method. The diagnostic sequence of various functional components in various vehicle models is constructed through the server, so that the vehicle diagnosis is realized by the diagnostic sequence sent by the server. A heavy cloud and light client architecture is proposed, which is suitable for various functional components of various vehicle models and realizes the high scalability of the diagnostic system.

[0071] See also Figure 7 , Figure 7 is a block diagram of a vehicle diagnostic service end shown in an exemplary embodiment of the present application. The service end can be applied to Figure 1 The implementation environment shown, it should be understood that the server can also be applicable to other exemplary implementation environments, and this embodiment does not limit the implementation environment applicable to the server.

[0072] like Figure 7 As shown, in an exemplary embodiment, the vehicle diagnosis service end 700 includes at least a determination module 710, a matching module 720, a diagnosis module 730 and an analysis module 740, which are described in detail as follows:

[0073] The determination module 710 is used to obtain vehicle information of the vehicle to be diagnosed, wherein the vehicle information includes vehicle model and ECU information, and the ECU information includes each functional component in the vehicle to be diagnosed and the data structure of each functional component;

[0074] A matching module 720 is used to match a target diagnostic sequence from a diagnostic sequence set according to the functions corresponding to the vehicle model and each functional component, wherein the diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each functional component in each vehicle model, and the diagnostic sequence includes diagnostic data packets of various functions in each vehicle model;

[0075] The diagnostic module 730 is used to send the target diagnostic sequence to the vehicle to be diagnosed, diagnose the vehicle to be diagnosed, and obtain diagnostic log information;

[0076] The analysis module 740 is used to analyze the diagnostic log information in combination with the preset diagnostic database and the abnormality pool, locate the abnormal error point and feedback the repair method.

[0077] It should be noted that the vehicle diagnostic server provided in the above embodiment and the vehicle diagnostic method provided in the above embodiment belong to the same concept, wherein the contents of the operations performed by each module have been described in detail in the method embodiment and will not be repeated here.

[0078] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer executes the vehicle diagnostic method as described above. The computer-readable storage medium may be included in an electronic device, or may exist independently without being assembled into the electronic device.

[0079] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0080] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0081] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0082] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A vehicle diagnostic method, characterized in that: Applied to the server, the method includes: Acquire vehicle information of the vehicle to be diagnosed, wherein the vehicle information includes vehicle model and ECU information, and the ECU information includes each functional component in the vehicle to be diagnosed and a data structure of each functional component; According to the functions corresponding to the vehicle model and each of the functional components, a target diagnostic sequence is matched from a diagnostic sequence set, wherein the diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each of the functional components in each vehicle model, and the diagnostic sequence includes diagnostic data packets of various functions in each vehicle model; Sending the target diagnostic sequence to the vehicle to be diagnosed, diagnosing the vehicle to be diagnosed, and obtaining diagnostic log information; Combined with the preset diagnostic database and exception pool, the diagnostic log information is analyzed to locate the abnormal error point and feedback the repair method.

2. The vehicle diagnostic method according to claim 1, characterized in that: The method for constructing the diagnostic sequence set includes: Acquire the data structure corresponding to the diagnostic script file and the functions of each component in each vehicle model, and create a diagnostic sequence file according to the diagnostic script file; Based on the diagnostic sequence file, converting the data structure corresponding to each functional component in each vehicle model into a diagnostic sequence file format to obtain an initial diagnostic data packet for each functional component in each vehicle model; Separating the diagnostic logic from the diagnostic data in the initial diagnostic sequence to obtain the diagnostic data packet corresponding to each component function component in each vehicle model, wherein the diagnostic logic is sent to the client for storage; Based on the diagnostic data packets corresponding to the functional components in each vehicle model, the diagnostic sequence of each vehicle model is generated to obtain the diagnostic sequence set.

3. The vehicle diagnostic method according to claim 2, characterized in that: After generating the diagnostic sequence for each vehicle model, the method further includes: Sending the diagnostic sequence to the client so that the client loads the diagnostic sequence, and verifying and debugging the diagnostic sequence, wherein the verification step includes: diagnostic sequence format, diagnostic sequence content, the diagnostic logic and diagnostic compatibility; An exception handling logic is configured in the diagnosis sequence, wherein the exception handling logic is used to handle diagnosis exceptions in the diagnosis.

4. The vehicle diagnostic method according to claim 1, characterized in that: Before allocating a target diagnostic sequence from a diagnostic sequence set according to the functions corresponding to the vehicle type and each functional component, the method further includes: Monitoring of new vehicle models and / or new features within vehicle models; If the new vehicle model and / or the new function is detected, constructing a new diagnostic sequence corresponding to the new vehicle model and / or the new function; The newly added diagnostic sequence is added to the diagnostic sequence set.

5. The vehicle diagnostic method according to claim 1, characterized in that: The method for determining the vehicle model includes: Acquiring part number information of the vehicle to be diagnosed, wherein the part number information includes a plurality of part numbers; Determine whether there is a unique part number in the part number information, wherein the unique part number is used to directly distinguish different vehicle models; If so, the vehicle model is determined based on the unique part number; if not, the unique intersection of the vehicle models corresponding to all part numbers in the part number information is determined, and the vehicle model is determined based on the unique intersection.

6. The vehicle diagnostic method according to claim 1, characterized in that: The vehicles to be diagnosed are multiple vehicles, and the diagnostic data package includes a software upgrade package; The sending of the target diagnostic sequence to the vehicle to be diagnosed, diagnosing the vehicle to be diagnosed, and obtaining diagnostic log information includes: Creating a task pool, and placing the flashing operation of each electronic control unit in the vehicle to be diagnosed into the task pool as a flashing task; Establishing a connection between the client and each of the vehicles to be diagnosed, and allocating the plurality of flashing tasks in the task pool to corresponding channels; Flashing multiple software upgrade packages concurrently, and after monitoring that multiple flashing tasks are completed, restoring the entire vehicle network and receiving the diagnostic log information returned by each vehicle to be diagnosed.

7. The vehicle diagnosis method according to any one of claims 1 to 6, characterized in that: Before obtaining the vehicle information of the vehicle to be diagnosed, the method further includes: monitoring whether a diagnostic agent in the vehicle to be diagnosed is turned on; If not, the ECU of the vehicle to be diagnosed is securely unlocked using a preset secret key; if yes, the vehicle identification code of the vehicle to be diagnosed is obtained, and it is determined whether the vehicle identification code is pre-stored; If so, a random key is requested to securely unlock the ECU of the vehicle to be diagnosed; if not, a temporary authorization file is generated based on the vehicle identification code, and the ECU of the vehicle to be diagnosed is securely unlocked based on the validity period and temporary authorization key in the temporary authorization file.

8. The vehicle diagnosis method according to claims 1 to 6, characterized in that: The method combines the preset diagnostic database and the abnormality pool to analyze the diagnostic log information, locate the abnormal error point and feedback the repair method, including: Matching the diagnostic log information with the diagnostic database to locate the abnormal error point; Based on the abnormal error reporting point, the repair method is matched from the abnormal pool, wherein the abnormal pool includes the repair method corresponding to each abnormal error reporting point.

9. A vehicle diagnostic service terminal, characterized in that: The server includes: A determination module, used to obtain vehicle information of the vehicle to be diagnosed, wherein the vehicle information includes vehicle type and ECU information, and the ECU information includes each functional component in the vehicle to be diagnosed and a data structure of each functional component; a matching module, configured to match a target diagnostic sequence from a diagnostic sequence set according to the functions corresponding to the vehicle model and each of the functional components, wherein the diagnostic sequence in the diagnostic sequence set is constructed according to the data structure of each of the functional components in each vehicle model, and the diagnostic sequence includes diagnostic data packets of various functions in each vehicle model; A diagnosis module, used for sending the target diagnosis sequence to the vehicle to be diagnosed, diagnosing the vehicle to be diagnosed, and obtaining diagnosis log information; The analysis module is used to analyze the diagnostic log information in combination with a preset diagnostic database and anomaly pool, locate the abnormal error point and feedback the repair method.

10. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the vehicle diagnosis method according to any one of claims 1 to 8.

Images