Vehicle data diagnosis method and device and readable storage medium

Abstract

The invention discloses a vehicle data diagnosis method and device and a readable storage medium, and relates to the technical field of vehicles. The data diagnosis method of the vehicle comprises the steps of obtaining request data and response data between a diagnosis device and the vehicle under the condition that the diagnosis device performs data diagnosis on the vehicle; determining a first data size of the request data and a second data size of the response data; determining a diagnosis scene between the diagnosis device and the vehicle according to the first data size and the second data size; and based on the diagnosis scene, performing data diagnosis on the vehicle to obtain a diagnosis result of the vehicle. The data diagnosis efficiency of the vehicle is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more particularly to a data diagnostic method, apparatus, and readable storage medium for vehicles. Background Technology

[0002] Currently, vehicle data diagnostics typically involve parsing offline BLF (Binary Logging Format) files to determine the diagnostic results. However, offline BLF files require manual keyframe selection, which is inefficient. Therefore, existing vehicle data diagnostic methods suffer from technical problems such as low diagnostic efficiency. Summary of the Invention

[0003] This application provides a vehicle data diagnostic method, apparatus, and readable storage medium to solve technical problems such as low diagnostic efficiency in the prior art.

[0004] A first aspect of this application provides a vehicle data diagnostic method, the method comprising: When the diagnostic device performs data diagnostics on the vehicle, acquire the request data and response data between the diagnostic device and the vehicle. Determine the first data size of the requested data and the second data size of the response data; The diagnostic scenario between the diagnostic device and the vehicle is determined based on the first data size and the second data size. Based on the diagnostic scenario, data diagnostics are performed on the vehicle to obtain the vehicle's diagnostic results.

[0005] The vehicle data diagnostic method in this embodiment determines the diagnostic scenario between the diagnostic device and the vehicle based on the first data size of the requested data and the second data size of the response data. Then, based on the diagnostic scenario, the vehicle data is diagnosed to obtain the vehicle diagnostic result. This eliminates the need for manual screening of diagnostic scenarios and improves the efficiency of vehicle data diagnostics.

[0006] A second aspect of this application provides a vehicle data diagnostic device, the device comprising: The acquisition unit is used to acquire request data and response data between the diagnostic device and the vehicle when the diagnostic device performs data diagnostics on the vehicle. The first processing unit is used to determine the first data size of the requested data and the second data size of the response data; The second processing unit is used to determine the diagnostic scenario between the diagnostic device and the vehicle based on the first data size and the second data size. The third processing unit is used to perform data diagnosis on the vehicle based on the diagnostic scenario in order to obtain the vehicle's diagnostic results.

[0007] The vehicle data diagnostic device in this embodiment determines the diagnostic scenario between the diagnostic device and the vehicle based on the first data size of the requested data and the second data size of the response data. Then, based on the diagnostic scenario, it performs data diagnostics on the vehicle to obtain the vehicle's diagnostic results. This eliminates the need for manual screening of diagnostic scenarios and improves the efficiency of vehicle data diagnostics.

[0008] A third aspect of this application provides another vehicle data diagnostic apparatus, including a processor and a memory. The memory stores a computer program that, when executed by the processor, implements the steps of the vehicle data diagnostic method as described in any of the above embodiments. Therefore, this vehicle data diagnostic apparatus possesses all the beneficial effects of the vehicle data diagnostic method in any of the above embodiments, which will not be elaborated further here.

[0009] A fourth aspect of this application provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the vehicle data diagnostic method as described in any of the above embodiments. Therefore, this readable storage medium possesses all the beneficial effects of the vehicle data diagnostic method in any of the above embodiments, which will not be elaborated further here. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 A flowchart of a vehicle data diagnostic method provided in an embodiment of this application; Figure 2 A functional block diagram of the vehicle data diagnostic device provided in the embodiments of this application; Figure 3 This is a structural block diagram of a vehicle data diagnostic device provided in an embodiment of this application. Detailed Implementation

[0012] To better understand the technical solutions provided in the embodiments of this specification, the technical solutions of the embodiments of this specification will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

[0013] In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, without necessarily requiring or implying any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. The term "two or more" includes two or more cases.

[0014] In some embodiments, such as Figure 1 As shown, an embodiment of this application provides a vehicle data diagnostic method, including: Step S101: When the diagnostic device performs data diagnostics on the vehicle, obtain the request data and response data between the diagnostic device and the vehicle. Step S102: Determine the first data size of the requested data and the second data size of the response data; Step S103: Determine the diagnostic scenario between the diagnostic device and the vehicle based on the first data size and the second data size; Step S104: Based on the diagnostic scenario, perform data diagnostics on the vehicle to obtain the vehicle's diagnostic results.

[0015] In this embodiment, a vehicle data diagnostic method is proposed to diagnose specific vehicle functions and determine whether the vehicle functions can operate normally.

[0016] For example, the vehicle may specifically be a new energy electric vehicle.

[0017] For example, the vehicle may specifically be an autonomous vehicle.

[0018] When performing data diagnostics on a vehicle, it is necessary to connect a diagnostic device to the vehicle, wherein the diagnostic device is a device used for data diagnostics.

[0019] For example, the diagnostic device can be a data processing device external to the vehicle.

[0020] For example, the diagnostic device can be a data processing device inside the vehicle.

[0021] For example, diagnostic devices are indispensable "car doctors" when repairing and maintaining vehicles. Diagnostic devices can quickly read fault codes, analyze data streams, and accurately locate problems.

[0022] For example, diagnostic devices are indispensable tools in automotive repair and testing, helping to quickly locate problems by reading fault codes and real-time data from the vehicle's ECU (Electronic Control Unit).

[0023] When the diagnostic device performs data diagnostics on the vehicle, request data and response data between the diagnostic device and the vehicle are acquired. The request data is the instruction data requesting diagnostics, and the response data is the feedback data responding to the request data.

[0024] For example, the requested data may specifically be a diagnostic request instruction.

[0025] For example, the response data may specifically be a feedback instruction for a diagnostic request instruction.

[0026] For example, the request data can be a single-frame request instruction.

[0027] For example, the request data can be a multi-frame request instruction.

[0028] For example, the response data can be a single frame of response instructions.

[0029] For example, the response data can be a multi-frame response command.

[0030] Determine a first data size for the requested data and a second data size for the response data, wherein the first data size is the data size of the requested data and the second data size is the data size of the response data.

[0031] For example, the first data size may be a single frame or multiple frames.

[0032] For example, the second data size can be a single frame or multiple frames.

[0033] For example, the first data size and the second data size can be represented by bytes.

[0034] For example, the first data size and the second data size can be represented by bits.

[0035] Based on the first data size and the second data size, a diagnostic scenario between the diagnostic device and the vehicle is determined, wherein the diagnostic scenario is used to represent different functional diagnostic scenarios.

[0036] For example, the diagnostic scenario can be specifically a functional diagnostic scenario for reading fault codes.

[0037] For example, the diagnostic scenario can be specifically a functional diagnostic scenario for switching session modes.

[0038] For example, the diagnostic scenario can be specifically a functional diagnostic scenario involving writing a VIN (identity verification) code.

[0039] For example, the diagnostic scenario can be specifically a functional diagnostic scenario for parameter calibration.

[0040] Based on the diagnostic scenario, data diagnostics are performed on the vehicle to obtain the vehicle diagnostic results, where the diagnostic results represent the outcome of the vehicle diagnostics.

[0041] For example, the diagnostic result could be specifically "functionally normal".

[0042] For example, the diagnostic result may be specifically a functional abnormality.

[0043] For example, the diagnostic result could be specifically that the function of reading fault codes is normal.

[0044] For example, the diagnostic result may specifically be a functional abnormality in reading fault codes.

[0045] For example, the diagnostic result could be specifically that the function of switching session modes is normal.

[0046] For example, the diagnostic result may specifically be a functional abnormality in switching session modes.

[0047] For example, the diagnostic result could be specifically that the function of writing the VIN code is normal.

[0048] For example, the diagnostic result could be a functional abnormality in writing the VIN code.

[0049] For example, the diagnostic result could be specifically that the parameter calibration is normal.

[0050] For example, the diagnostic result may specifically be a functional abnormality calibrated by the parameters.

[0051] For example, the diagnostic result can be specifically a DTC (Diagnostic Trouble Code) list retrieval success rate of 98%.

[0052] For example, the diagnostic result could be a session context reconstruction rate of 95%.

[0053] For example, the diagnostic result can be specifically a 90% write repair rate for the VIN code.

[0054] For example, the diagnostic result could be specifically a parameter calibration completeness rate of 97%.

[0055] It should be noted that, in this embodiment, the diagnostic scenario for data diagnosis can be quickly determined based on the first data size of the requested data and the second data size of the response data. Based on the diagnostic scenario, data diagnosis is performed on the vehicle to obtain the vehicle's diagnostic results, thus ensuring the efficiency of determining the diagnostic results and thereby ensuring the efficiency of vehicle data diagnosis.

[0056] The vehicle data diagnostic method in this embodiment determines the diagnostic scenario between the diagnostic device and the vehicle based on the first data size of the requested data and the second data size of the response data. Then, based on the diagnostic scenario, the vehicle data is diagnosed to obtain the vehicle diagnostic result. This eliminates the need for manual screening of diagnostic scenarios and improves the efficiency of vehicle data diagnostics.

[0057] In some embodiments, this application provides a vehicle data diagnostic method, which determines a diagnostic scenario between a diagnostic device and a vehicle based on a first data size and a second data size, including: Under the condition that the first data size is less than or equal to the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined as the first scenario; Under the condition that the first data size is less than or equal to the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the second scenario; Under the condition that the first data size is greater than the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the third scenario; Given that the first data size is greater than the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined to be the fourth scenario.

[0058] In this embodiment, a preset size threshold is obtained, wherein the size threshold is a threshold used to determine the size of the data.

[0059] For example, the size threshold can be specifically 8 bytes.

[0060] For example, the size threshold can be specifically the data size of a frame.

[0061] Under the condition that the first data size is less than or equal to the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined as the first scenario, wherein the first scenario is a preset functional diagnostic scenario.

[0062] For example, the first scenario can be specifically a functional diagnostic scenario of reading fault codes.

[0063] Under the condition that the first data size is less than or equal to the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the second scenario, wherein the second scenario is a preset functional diagnostic scenario.

[0064] For example, the second scenario can be specifically a functional diagnostic scenario for switching session modes.

[0065] Under the condition that the first data size is greater than the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the third scenario, wherein the third scenario is a preset functional diagnostic scenario.

[0066] For example, the third scenario can be specifically a functional diagnostic scenario involving writing the VIN code.

[0067] Under the condition that the first data size is greater than the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined to be the fourth scenario, wherein the fourth scenario is a preset functional diagnostic scenario.

[0068] For example, the fourth scenario can be specifically a functional diagnostic scenario for parameter calibration.

[0069] For example, when the first data size is less than or equal to a size threshold, the requested data is determined to be single-frame requested data.

[0070] For example, when the first data size is greater than a size threshold, the requested data is determined to be multi-frame request data.

[0071] For example, when the second data size is greater than a size threshold, the response data is determined to be multi-frame request data.

[0072] For example, when the second data size is less than or equal to the size threshold, the response data is determined to be single-frame request data.

[0073] In some embodiments, this application provides a vehicle data diagnostic method, wherein the diagnostic result includes a fault code list, and based on a diagnostic scenario, data diagnostics are performed on the vehicle to obtain the vehicle's diagnostic result, including: In the case of the diagnosis scenario being the first scenario, obtain the first consecutive frame data and the sequence number corresponding to the first consecutive frame data from the response data; Based on the sequence number, the first consecutive frame data is reassembled to obtain the second consecutive frame data; The fault code list is determined based on the data from the second consecutive frame.

[0074] In this embodiment, when the diagnostic scenario is the first scenario, the first consecutive frame data and the sequence number corresponding to the first consecutive frame data are obtained from the response data. The first consecutive frame data refers to the consecutive frame data in the response data, and the sequence number indicates the arrangement order of the first consecutive frame data.

[0075] Based on the sequence number, the first consecutive frame data is reassembled to obtain the second consecutive frame data.

[0076] For example, data is filled in order of sequence number. If the sequence numbers are not consecutive, L2 level repair is initiated (historical mode filling, using the most recent 10 frames of data for estimation).

[0077] The fault code list is determined based on the data from the second consecutive frame.

[0078] For example, the fault code list can be a DTC list.

[0079] In some embodiments, this application provides a vehicle data diagnostic method, which performs data diagnostics on the vehicle based on a diagnostic scenario to obtain a vehicle diagnostic result, including: In the case of the second diagnostic scenario, temporal proximity matching is performed on the request data and response data to obtain the matching results between the request data and response data; If the matching result is no match, determine the response time between the request data and the response data; If the response time is longer than the preset duration, the diagnostic result is determined to be a response timeout.

[0080] In this embodiment, when the diagnostic scenario is the second scenario, temporal proximity matching is performed on the request data and response data to obtain the matching result between the request data and response data, wherein the matching result represents the matching situation between the request data and response data.

[0081] For example, the matching result can be specifically a successful match or a failed match.

[0082] For example, the matching result can be specifically either no match or a match.

[0083] If the matching result is no match, determine the response time between the request data and the response data, where the response time represents the duration for the response data to respond to the request data.

[0084] For example, the response time can be specifically 100ms.

[0085] If the response time is longer than the preset duration, the diagnostic result is determined to be a response timeout.

[0086] For example, the preset duration can be specifically 200ms.

[0087] For example, request-response matching is performed based on temporal proximity. Service code consistency is verified (request SID=0x10, response SID=0x50). If no matching response is found: check if subsequent messages contain a negative response (0x7F); mark the session as timed out (Level 3 fault tolerance, timeout threshold 500ms).

[0088] In some embodiments, this application provides a vehicle data diagnostic method, wherein the diagnostic result includes an identification code writing result. Based on a diagnostic scenario, data diagnostics are performed on the vehicle to obtain a vehicle diagnostic result, including: In the case of the third diagnostic scenario, the request data is reorganized to obtain the updated request data; Based on the updated request data, control the vehicle to perform an identification code writing operation to obtain the identification code writing result.

[0089] In this embodiment, the diagnostic results include the identification code writing results, wherein the identification code writing results represent the diagnostic results of the identification code writing process.

[0090] For example, the identification code writing result can be specifically the identification code writing success rate.

[0091] In the case of the third diagnostic scenario, the request data is reorganized to obtain updated request data.

[0092] Based on the updated request data, control the vehicle to perform an identification code writing operation to obtain the identification code writing result.

[0093] For example, reassemble multiple request frames: infer the missing flow control frame parameters (default BS=10, STmin=15ms) and fill the request data in SN (sequence number) order.

[0094] For example, the associated response frame: verify the response service code (0x7E); if the response CRC does not match, trigger L1 level repair (based on parity check algorithm).

[0095] In some embodiments, this application provides a vehicle data diagnostic method, wherein the diagnostic result includes a data response result. Based on a diagnostic scenario, data diagnostics are performed on the vehicle to obtain a vehicle diagnostic result, including: In the case of the fourth diagnostic scenario, determine the parameter control rate of the requested data; Based on parameter-controlled rates, the response data to the requested data is determined.

[0096] In this embodiment, when the diagnostic scenario is the fourth scenario, the parameter control rate of the requested data is determined, wherein the parameter control rate is the frequency or speed of the set parameter.

[0097] For example, the parameter control rate can be specifically 8 bits / s.

[0098] Based on parameter-controlled rates, the response data to the requested data is determined.

[0099] For example, bidirectional multi-frame management: the request channel buffers the sent frames and controls the rate according to the BS parameter (BS=8); the response channel independently reassembles the response data.

[0100] For example, cross-transmission processing includes: priority arbitration (response frames are processed first, with a weighting factor of 0.7); and a timeout interruption mechanism (request frame transmission is paused for 500ms).

[0101] In some embodiments, this application provides a vehicle data diagnostic method for determining a first data size of requested data and a second data size of response data, including: Determine the number of the first data frames for the requested data and the number of the second data frames for the response data; The first data size is determined based on the first data frame number, and the second data size is determined based on the second data frame number.

[0102] In this embodiment, a first data frame number of the request data and a second data frame number of the response data are determined, wherein the first data frame number is the number of frames of the request data and the second data frame number is the number of frames of the response data.

[0103] For example, the first data frame number can be a single frame or multiple frames.

[0104] For example, the second data frame number can be a single frame or multiple frames.

[0105] The first data size is determined based on the first data frame number, and the second data size is determined based on the second data frame number.

[0106] For example, this embodiment has the following technical effects: Full-scene coverage: Utilizing a multi-scene adaptive parsing engine, it supports single / multi-frame combination interaction with a parsing success rate of ≥95% (actual test dataset), solving the problem that existing technologies cannot handle mixed diagnostic protocols.

[0107] Anomaly recovery capability: Through L2-level repair mechanism and L3-level fault tolerance, the automatic repair rate of multi-frame broken scenes reaches 88.7%, reducing manual intervention.

[0108] Efficiency Improvement: Based on last-digit rules and time-series matching, BLF parsing speed is increased to 5 minutes / MB, which is 12 times more efficient than existing technologies.

[0109] In some embodiments, such as Figure 2 As shown, an embodiment of this application provides a vehicle data diagnostic device 200, including: The acquisition unit 202 is used to acquire request data and response data between the diagnostic device and the vehicle when the diagnostic device performs data diagnostics on the vehicle. The first processing unit 204 is used to determine the first data size of the requested data and the second data size of the response data; The second processing unit 206 is used to determine the diagnostic scenario between the diagnostic device and the vehicle based on the first data size and the second data size. The third processing unit 208 is used to perform data diagnosis on the vehicle based on the diagnostic scenario in order to obtain the vehicle's diagnostic results.

[0110] The vehicle data diagnostic device 200 in this embodiment determines the diagnostic scenario between the diagnostic device and the vehicle based on the first data size of the requested data and the second data size of the response data. Then, based on the diagnostic scenario, it performs data diagnostics on the vehicle to obtain the vehicle's diagnostic results. This eliminates the need for manual screening of diagnostic scenarios and improves the efficiency of vehicle data diagnostics.

[0111] In some embodiments of this application, a vehicle data diagnostic device 200 is provided, wherein the second processing unit 206 is further configured to: Under the condition that the first data size is less than or equal to the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined as the first scenario; Under the condition that the first data size is less than or equal to the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the second scenario; Under the condition that the first data size is greater than the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the third scenario; Given that the first data size is greater than the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined to be the fourth scenario.

[0112] In some embodiments of this application, a vehicle data diagnostic device 200 is provided, wherein the third processing unit 208 is further configured to: In the case of the diagnosis scenario being the first scenario, obtain the first consecutive frame data and the sequence number corresponding to the first consecutive frame data from the response data; Based on the sequence number, the first consecutive frame data is reassembled to obtain the second consecutive frame data; The fault code list is determined based on the data from the second consecutive frame.

[0113] In some embodiments of this application, a vehicle data diagnostic device 200 is provided, wherein the third processing unit 208 is further configured to: In the case of the second diagnostic scenario, temporal proximity matching is performed on the request data and response data to obtain the matching results between the request data and response data; If the matching result is no match, determine the response time between the request data and the response data; If the response time is longer than the preset duration, the diagnostic result is determined to be a response timeout.

[0114] In some embodiments of this application, a vehicle data diagnostic device 200 is provided, wherein the third processing unit 208 is further configured to: In the case of the third diagnostic scenario, the request data is reorganized to obtain the updated request data; Based on the updated request data, control the vehicle to perform an identification code writing operation to obtain the identification code writing result.

[0115] In some embodiments of this application, a vehicle data diagnostic device 200 is provided, wherein the third processing unit 208 is further configured to: In the case of the fourth diagnostic scenario, determine the parameter control rate of the requested data; Based on parameter-controlled rates, the response data to the requested data is determined.

[0116] In some embodiments of this application, a vehicle data diagnostic device 200 is provided, wherein the first processing unit 204 is further configured to: Determine the number of the first data frames for the requested data and the number of the second data frames for the response data; The first data size is determined based on the first data frame number, and the second data size is determined based on the second data frame number.

[0117] In some embodiments, such as Figure 3 As shown, a vehicle data diagnostic device 300 is proposed. The vehicle data diagnostic device 300 includes a processor 302 and a memory 304. The memory 304 stores a computer program, which, when executed by the processor 302, implements the steps of the vehicle data diagnostic method as described in any of the above embodiments. Therefore, the vehicle data diagnostic device 300 possesses all the beneficial effects of the vehicle data diagnostic method in any of the above embodiments, which will not be elaborated further here.

[0118] In some embodiments, a readable storage medium is provided having a program stored thereon, which, when executed by a processor, implements the steps of the vehicle data diagnostic method as described in any of the above embodiments, and thus has all the beneficial technical effects of the vehicle data diagnostic method in any of the above embodiments.

[0119] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

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

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

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

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

[0124] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to execute a process of a vehicle data diagnostic method.

[0125] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0126] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0127] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.

[0128] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0129] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0130] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0131] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

[0132] Although preferred embodiments have been described in this specification, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this specification.

[0133] Obviously, those skilled in the art can make various modifications and variations to this specification without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims and their equivalents, this specification is also intended to include such modifications and variations.

Claims

1. A method for data diagnosis of a vehicle, characterized in that, The method includes: When the diagnostic device performs data diagnostics on the vehicle, the request data and response data between the diagnostic device and the vehicle are acquired. Determine the first data size of the request data and the second data size of the response data; Based on the first data size and the second data size, the diagnostic scenario between the diagnostic device and the vehicle is determined; Based on the diagnostic scenario, data diagnostics are performed on the vehicle to obtain the diagnostic results for the vehicle.

2. The method according to claim 1, characterized in that, The step of determining the diagnostic scenario between the diagnostic device and the vehicle based on the first data size and the second data size includes: If the first data size is less than or equal to the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined to be the first scenario. Under the condition that the first data size is less than or equal to the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be the second scenario; If the first data size is greater than the size threshold and the second data size is less than or equal to the size threshold, the diagnostic scenario is determined to be a third scenario. If the first data size is greater than the size threshold and the second data size is greater than the size threshold, the diagnostic scenario is determined to be the fourth scenario.

3. The method according to claim 2, characterized in that, The diagnostic results include a list of fault codes. The process of performing data diagnostics on the vehicle based on the diagnostic scenario to obtain the vehicle's diagnostic results includes: When the diagnostic scenario is the first scenario, the first consecutive frame data and the sequence number corresponding to the first consecutive frame data are obtained from the response data; Based on the sequence number, the first consecutive frame data is reassembled to obtain the second consecutive frame data; The fault code list is determined based on the second consecutive frame data.

4. The method according to claim 2, characterized in that, The step of performing data diagnostics on the vehicle based on the diagnostic scenario to obtain the diagnostic results for the vehicle includes: In the case where the diagnostic scenario is the second scenario, temporal proximity matching is performed on the request data and the response data to obtain the matching result between the request data and the response data; If the matching result is no match, determine the response time between the request data and the response data; If the response time is greater than a preset duration, the diagnostic result is determined to be a response timeout.

5. The method according to claim 2, characterized in that, The diagnostic results include the identification code writing results. The process of performing data diagnostics on the vehicle based on the diagnostic scenario to obtain the vehicle's diagnostic results includes: In the case where the diagnostic scenario is the third scenario, the request data is reorganized to obtain updated request data; Based on the updated request data, the vehicle is controlled to perform an identification code writing operation to obtain the identification code writing result.

6. The method according to claim 2, characterized in that, The diagnostic results include data response results. The process of performing data diagnostics on the vehicle based on the diagnostic scenario to obtain the vehicle's diagnostic results includes: In the case where the diagnostic scenario is the fourth scenario, the parameter control rate of the requested data is determined; Based on the parameter control rate, the data response result of the response data to the request data is determined.

7. The method according to any one of claims 1 to 6, characterized in that, Determining the first data size of the request data and the second data size of the response data includes: Determine the first data frame number of the request data and the second data frame number of the response data; The first data size is determined based on the first data frame number, and the second data size is determined based on the second data frame number.

8. A vehicle data diagnostic device, characterized in that, The device includes: The acquisition unit is used to acquire request data and response data between the diagnostic device and the vehicle when the diagnostic device performs data diagnostics on the vehicle. A first processing unit is configured to determine a first data size of the request data and a second data size of the response data; The second processing unit is used to determine the diagnostic scenario between the diagnostic device and the vehicle based on the first data size and the second data size; The third processing unit is used to perform data diagnosis on the vehicle based on the diagnostic scenario to obtain the diagnostic result of the vehicle.

9. A vehicle data diagnostic device, characterized in that, include: processor; A memory, which stores programs or instructions, wherein a processor, when executing the programs or instructions in the memory, implements the steps of the vehicle data diagnostic method as described in any one of claims 1 to 7.

10. A readable storage medium, characterized in that, A program or instructions are stored on a readable storage medium, which, when executed by a processor, implement the steps of the data diagnostic method for a vehicle as described in any one of claims 1 to 7.

Images