Vehicle diagnosis method, device and electronic equipment

Abstract

The application discloses a vehicle diagnosis method and device and electronic equipment, and belongs to the field of automobile data processing. A vehicle diagnosis method, the method comprises the following steps: receiving a target diagnosis request sent by a diagnosis platform, adding the target diagnosis request to a task list; in the case that the priority of the target diagnosis request is the highest according to the priority of the diagnosis request recorded in the task list, removing the target diagnosis request from the task list, and collecting target detection data of the vehicle in response to the target diagnosis request; and sending the target detection data to the diagnosis platform, so that the diagnosis platform performs vehicle diagnosis according to the target detection data. The application guarantees the diagnosis compatibility of multiple diagnosis platforms and improves the automobile diagnosis efficiency.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of automobile data processing, and particularly relates to a vehicle diagnosis method and device and electronic equipment. BACKGROUND

[0002] With the development of the automobile industry, automobile intelligent diagnosis technology has begun to emerge. In the case of functional failure of a vehicle or the need for routine system data maintenance of the vehicle, an automobile diagnosis platform can obtain running data of multiple electronic control units (ECUs) in the vehicle through a controller area network (CAN) bus to perform vehicle diagnosis according to the running data.

[0003] However, in the case of multiple automobile diagnosis platforms, all the automobile diagnosis platforms are connected with the ECUs through the CAN bus. Therefore, if multiple automobile diagnosis platforms simultaneously initiate automobile diagnosis through the CAN bus to obtain the running data of the ECUs, the ECUs cannot confirm the requestor of the running data, and thus can only return the running data to one automobile diagnosis platform, resulting in invalid automobile diagnosis initiated by other automobile diagnosis platforms, and poor diagnosis compatibility of the multiple automobile diagnosis platforms. SUMMARY

[0004] The embodiments of the present application provide a vehicle diagnosis method, device and electronic equipment, which can solve the problem of poor diagnosis compatibility of multiple automobile diagnosis platforms.

[0005] In a first aspect, the embodiments of the present application provide a vehicle diagnosis method applied to a vehicle machine of a vehicle, and the method comprises the following steps.

[0006] Receiving a target diagnosis request sent by a plurality of diagnosis platforms, and adding the target diagnosis request to a task list;

[0007] In the case that the priority of the target diagnosis request is the highest according to the priority of the diagnosis request recorded in the task list, removing the target diagnosis request from the task list, and collecting target detection data of the vehicle in response to the target diagnosis request;

[0008] Sending the target detection data to the diagnosis platform, so that the diagnosis platform performs vehicle diagnosis according to the target detection data.

[0009] In a second aspect, the embodiments of the present application provide a vehicle diagnosis method applied to a diagnosis platform, and the method comprises the following steps.

[0010] sending a plurality of target diagnostic requests to a vehicle computer of the vehicle, so that the vehicle computer adds the target diagnostic requests to a task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, removing the target diagnostic request from the task list, and collecting target detection data of the vehicle in response to the target diagnostic request, and sending the target detection data to the diagnostic platform;

[0011] receiving the target detection data sent by the vehicle computer;

[0012] Vehicle diagnosis is performed based on the target detection data.

[0013] In a third aspect, an embodiment of the present application provides a vehicle diagnostic device, which is applied to a vehicle computer, and the device includes:

[0014] A receiving module, configured to receive target diagnosis requests sent by multiple diagnosis platforms and add the target diagnosis requests to a task list;

[0015] a processing module, configured to, if it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, remove the target diagnostic request from the task list, and collect target detection data of the vehicle in response to the target diagnostic request;

[0016] The sending module is used to send the target detection data to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data.

[0017] In a fourth aspect, an embodiment of the present application provides a vehicle diagnostic device, applied to a diagnostic platform, the device comprising:

[0018] a sending module, configured to send a plurality of target diagnostic requests to a vehicle computer of the vehicle, so that the vehicle computer adds the target diagnostic requests to a task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, remove the target diagnostic request from the task list, and collect target detection data of the vehicle in response to the target diagnostic request, and send the target detection data to the diagnostic platform;

[0019] A receiving module, configured to receive the target detection data sent by the vehicle computer;

[0020] A diagnostic module is used to perform vehicle diagnosis based on the target detection data.

[0021] In a fifth aspect, an embodiment of the present application provides an electronic device comprising: a processor and a memory; the memory is used to store computer programs; the processor is used to implement the method steps described in any one of the first aspects when executing the program stored in the memory; or, implement the method steps described in any one of the second aspects.

[0022] In a sixth aspect, an embodiment of the present application provides a readable storage medium. When the instructions in the readable storage medium are executed by a processor of an electronic device, the electronic device can execute any of the methods described in the first aspect; or, execute any of the methods described in the second aspect.

[0023] In an embodiment of the present application, the vehicle computer adds target diagnostic requests sent by multiple diagnostic platforms to a task list. When the priority of the target diagnostic request is determined to be the highest according to the priority of the diagnostic requests recorded in the task list, the vehicle computer removes the target diagnostic request from the task list, collects the vehicle's target detection data in response to the target diagnostic request, and sends the target detection data to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform. Even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, the vehicle computer can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring effective diagnosis by multiple diagnostic platforms. Compared with related technologies, this avoids the situation where detection data can only be returned to one diagnostic platform when multiple diagnostic platforms initiate diagnostic requests at the same time, ensuring the diagnostic compatibility of multiple diagnostic platforms and improving vehicle diagnostic efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a block diagram of a vehicle diagnostic system provided by an embodiment of the present application;

[0025] Figure 2 This is a schematic diagram of a connection structure of multiple ECUs provided in an embodiment of the present application;

[0026] Figure 3 This is one of the flow charts of a vehicle diagnostic method provided in an embodiment of the present application;

[0027] Figure 4 This is the second flow chart of a vehicle diagnostic method provided in an embodiment of the present application;

[0028] Figure 5 This is the third flow chart of a vehicle diagnostic method provided in an embodiment of the present application;

[0029] Figure 6 FIG. 4 is a flowchart of a vehicle diagnosis method according to an embodiment of the present application;

[0030] Figure 7 FIG. 5 is a flowchart of a vehicle diagnosis method according to an embodiment of the present application;

[0031] Figure 8 FIG. 6 is a flowchart of a vehicle diagnosis method according to an embodiment of the present application;

[0032] Figure 9 FIG. 7 is a block diagram of a vehicle diagnosis apparatus according to an embodiment of the present application;

[0033] Figure 10 FIG. 8 is a block diagram of a vehicle diagnosis apparatus according to an embodiment of the present application;

[0034] Figure 11 FIG. 9 is a block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0036] The vehicle diagnosis method, apparatus and electronic device provided by the embodiments of the present application will be described in detail below with reference to the drawings and specific embodiments and application scenarios.

[0037] Referring to FIG. 10, Figure 1 which shows a block diagram of a vehicle diagnosis system according to an embodiment of the present application. As shown in FIG. 10, Figure 1 the vehicle diagnosis system includes a diagnosis platform 101 and a vehicle machine 102 of a vehicle. The diagnosis platform can be connected to the vehicle machine through a wireless network. The number of diagnosis platforms can be one or more. It should be noted that, Figure 1 three diagnosis platforms 101 are shown for illustrative purposes.

[0038] In an optional application scenario, the implementation environment further includes an electronic control unit (ECU) 103 of the vehicle. The ECU can be connected to the vehicle machine through a controller area network (CAN). The number of ECUs can also be one or more. It should be noted that, Figure 1The number of ECUs 103 is 3 for schematic illustration. Optionally, the vehicle computer can communicate with the ECU and the diagnostic platform respectively through the Unified Diagnostic Services (UDS) protocol to send the operating data obtained from the ECU to the diagnostic platform, so that the diagnostic platform can perform vehicle diagnosis based on the operating data.

[0039] In the case of a vehicle with multiple ECUs, the multiple ECUs can be connected to the vehicle through multiple CAN channels, and the multiple CAN channels are not interconnected. For example, please refer to Figure 2 , which shows a schematic diagram of a connection structure of multiple ECUs provided by an embodiment of the present application. Figure 2 As shown, the multiple ECUs include: a connected car entertainment module (T-ICE) 1031, an antilock brake system (ABS) filling module 1032, an airbag module (SDM) 1033, an engine control module (ECM) 1034, an electric power steering module (EPS) 1035, an electronic stability control system (ESC) 1036, an air conditioning control module (AC) 1037, an instrument cluster module (IC) 1038, a body control module (BCM) 1039, a radar sensor (RRS) 10310, an engine immobilizer coil module (IMMO COIL) 10311 and a data link connector (DLC) 10312.

[0040] The connected in-vehicle entertainment module 1031 and the DLC 10312 can both be connected to the vehicle via the first CAN (T / CAN). The DLC 10312, ABS charging module 1032, airbag module 1033, engine control module 1034, electric power steering module 1035, and electronic stability control system 1036 can all be connected to the vehicle via the second CAN (P / CAN). The air conditioning control module 1036, instrument cluster module 1038, body control module 1039, radar sensor 10310, and immobilizer coil module 10311 can all be connected to the vehicle via the third CAN (I / CAN).

[0041] Optionally, the vehicle may further include a gateway module 104. The gateway module is used to connect the vehicle computer and the CAN. Figure 2 As shown, the vehicle computer is connected to T / CAN, P / CAN and I / CAN through the gateway module.

[0042] Please refer to Figure 3 , which shows a flow chart of a vehicle diagnostic method provided by an embodiment of the present application. The vehicle diagnostic method can be applied to Figure 1 The vehicle diagnostic system shown in Figure 1 is as follows. Figure 3 As shown, the vehicle diagnosis method includes:

[0043] Step 301: The diagnostic platform sends a target diagnostic request to the vehicle computer.

[0044] Optionally, in the event of a vehicle anomaly, if the diagnostic platform detects the vehicle anomaly, it may send a target diagnostic request to the vehicle in which the anomaly occurred. The target diagnostic request is used to request target detection data from the vehicle. The detection data is currently used by the diagnostic platform to perform vehicle diagnosis. Optionally, the target diagnostic request may include a data source requirement. The target diagnostic request is used to request target detection data from a target data source in the vehicle, where the target data source is the data source indicated by the data source requirement. For example, the data source requirement is used to indicate a request for detection data from a target ECU. The target diagnostic request is used to request target detection data from a target ECU.

[0045] In some embodiments of the present application, as previously described, the vehicle diagnostic system may include one or more diagnostic platforms. When there are multiple diagnostic platforms, each of the multiple diagnostic platforms can send a diagnostic request to the vehicle computer upon detecting a vehicle anomaly. Alternatively, the same diagnostic platform can send multiple diagnostic requests to the vehicle computer upon detecting a vehicle anomaly.

[0046] Step 302: The vehicle computer adds the target diagnosis request to the task list.

[0047] In this embodiment of the present application, the vehicle computer performs at least the steps performed by the vehicle computer in this embodiment of the present application for each received diagnostic request, thereby collecting target detection data of the vehicle in response to each diagnostic request and transmitting the target detection data to the diagnostic platform. Based on this, this embodiment of the present application is described using one target diagnosis request among one or more diagnostic requests received by the vehicle computer as an example.

[0048] After receiving target diagnostic requests from multiple diagnostic platforms, the vehicle computer can add them to a task list. The task list records each diagnostic request received by the vehicle computer to form a task chain, where each task in the task chain is used to respond to a diagnostic request.

[0049] Step 303 : When the vehicle computer determines that the priority of the target diagnosis request is the highest according to the priorities of the diagnosis requests recorded in the task list, it removes the target diagnosis request from the task list and collects target detection data of the vehicle in response to the target diagnosis request.

[0050] In an embodiment of the present application, the diagnostic requests recorded in the task list have a priority. The vehicle computer can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to collect the target detection data of the vehicle. Optionally, the priority of the diagnostic request can be associated with the time when the diagnostic request is added to the task list. The higher the priority of the diagnostic request, the earlier the diagnostic request is added to the task list. Alternatively, the priority of the diagnostic request can also be associated with the priority of the diagnostic platform that sends the diagnostic request. The higher the priority of the diagnostic platform that sends the diagnostic request, the higher the priority of the diagnostic request. Among them, the priority of the diagnostic platform can be associated with the diagnostic accuracy of the diagnostic platform. Alternatively, the priority of the diagnostic platform can be a manually set priority.

[0051] For example, assume that the priority of a diagnostic request is associated with the time the diagnostic request was added to the task list. The vehicle computer traverses the diagnostic requests recorded in the task list. If it determines that the target diagnostic request was added earliest compared to other requests, it removes the target diagnostic request from the task list and collects target detection data for the vehicle in response to the target diagnostic request. The addition time of the diagnostic request refers to the time when the diagnostic request was added to the task list.

[0052] Optionally, the target detection data may be operating data of one or more components in the vehicle. For example, the operating data of each ECU in the vehicle. In one alternative implementation, when the target diagnostic request includes a data source requirement, the target detection data is the operating data of the component in the vehicle corresponding to the target data source. For example, the data source requirement indicates a request for detection data from a target ECU. The target detection data is the operating data of the target ECU.

[0053] In an optional implementation, the target diagnosis request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU. The process of the vehicle computer collecting the target detection data of the vehicle in response to the target diagnosis request may include:

[0054] In response to the target diagnosis request, an ECU request corresponding to the target diagnosis request is sent to the first ECU, and the target detection data sent by the first ECU is received. The ECU request is used to request the first ECU to collect and send the target detection data to the vehicle computer. After receiving the ECU request, the first ECU sends the target detection data to the vehicle computer.

[0055] Step 304: The vehicle computer sends the target detection data to the diagnosis platform.

[0056] In the embodiment of the present application, the vehicle computer sends the target detection data to the diagnostic platform through the connection network between the vehicle computer and the diagnostic platform.

[0057] Step 305: The diagnostic platform performs vehicle diagnosis based on the target detection data.

[0058] In an embodiment of the present application, after receiving the target detection data sent by the vehicle computer in response to the target diagnosis request, the diagnostic platform can perform vehicle diagnosis based on the target detection data.

[0059] In an embodiment of the present application, the vehicle computer adds target diagnostic requests sent by multiple diagnostic platforms to a task list. When the priority of the target diagnostic request is determined to be the highest according to the priority of the diagnostic requests recorded in the task list, the vehicle computer removes the target diagnostic request from the task list, collects the vehicle's target detection data in response to the target diagnostic request, and sends the target detection data to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform. Even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, the vehicle computer can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring effective diagnosis by multiple diagnostic platforms. Compared with related technologies, this avoids the situation where detection data can only be returned to one diagnostic platform when multiple diagnostic platforms initiate diagnostic requests at the same time, ensuring the diagnostic compatibility of multiple diagnostic platforms and improving vehicle diagnostic efficiency.

[0060] In an optional implementation, if the target diagnostic request includes a data source requirement, multiple diagnostic platforms can send diagnostic requests with the same data source requirement to the vehicle computer to request test data from the same data source requirement. Alternatively, a diagnostic platform can repeatedly send diagnostic requests with the same data source requirement to request test data from the same data source requirement.

[0061] Based on this, before the vehicle computer adds the target diagnosis request to the task list in step 302 , the method further includes the following steps 01A to 01B.

[0062] In step 01A, a completed task list is queried according to the target diagnosis request. The completed task list is used to record the responded diagnosis requests and the corresponding detection data.

[0063] In an embodiment of the present application, the vehicle computer also maintains a completed task list. This completed task list is used to record responded diagnostic requests and the corresponding test data. Specifically, each time the vehicle computer collects target test data for the vehicle in response to a diagnostic request, it adds the diagnostic request, the test data corresponding to the diagnostic request, and the correspondence between the diagnostic request and the test data to the completed task list. The test data corresponding to the diagnostic request refers to the vehicle test data collected by the vehicle computer in response to the diagnostic request.

[0064] After receiving the target diagnostic request, the vehicle computer queries the completed task list based on the target diagnostic request to determine whether the completed task list includes the first diagnostic request. A first diagnostic request is a diagnostic request that includes the same data source requirements as the target diagnostic request. In other words, the first diagnostic request can be considered the same as the target diagnostic request, and the test data requested by the first diagnostic request is the same as the target diagnostic request.

[0065] In step 01B, when it is determined that the completed task list includes the first diagnostic request, the detection data corresponding to the first diagnostic request in the completed task list is sent to the diagnostic platform.

[0066] In an embodiment of the present application, when it is determined that the completed task list includes the first diagnostic request, it means that the vehicle has collected the detection data requested by the target diagnostic request, and the detection data corresponding to the first diagnostic request in the completed task list is sent to the diagnostic platform.

[0067] Based on this, it is readily understood that if the completed task list does not include the first diagnostic request, that is, if the vehicle has not yet collected the test data requested by the target diagnostic request, the vehicle computer may collect the target test data of the vehicle in response to the target diagnostic request. Step 302 of the vehicle computer adding the target diagnostic request to the task list includes: if it is determined that the completed task list does not include the first diagnostic request, adding the target diagnostic request to the task list.

[0068] Accordingly, after collecting the target detection data of the vehicle in response to the target diagnosis request in step 303, the method further includes: adding the target diagnosis request and the target detection data to a completed task list, and recording the correspondence between the target diagnosis request and the target detection data in the completed task list.

[0069] In this embodiment of the present application, the vehicle computer adds a completed task list, allowing it to record the diagnostic requests it has responded to and the test data collected for each diagnostic request. This way, when the vehicle computer receives another diagnostic request that includes the same data source requirements as the already responded diagnostic request, it can directly read the test data corresponding to the same diagnostic request from the completed task list, avoiding repeated collection operations for the same diagnostic request, improving the response efficiency of test data, and ultimately improving vehicle diagnostic efficiency.

[0070] In one optional implementation, as described above, a vehicle may include multiple ECUs. These ECUs are connected to the vehicle computer via multiple CAN channels, and the multiple CAN channels are not interconnected. If the data source requirement included in the diagnostic request indicates the test data of the requesting ECU, the multiple diagnostic requests may request test data from ECUs on different CAN channels.

[0071] Based on this, it is assumed that the data source requirement included in the target diagnosis request is used to indicate that the detection data from the first ECU is requested. After the vehicle computer adds the target diagnosis request to the task list in step 302, the method further includes the following steps 02A to 02C.

[0072] In step 02A, the vehicle computer determines whether there is a second diagnostic request in the task list. If so, steps 02B and 02C are executed; if not, steps 303 and 304 are executed.

[0073] In an embodiment of the present application, the data source requirement of the second diagnostic request is used to indicate a request for detection data from the second ECU. The second ECU and the first ECU are connected to the vehicle computer through different CANs. After adding the target diagnostic request to the task list, the vehicle computer can traverse the diagnostic requests recorded in the task list to determine whether there is a second diagnostic request. Since the second ECU and the first ECU are connected to the vehicle computer through different CANs, and the multiple CANs are not interconnected. Therefore, it is not difficult to understand that the data path for transmitting the detection data of the first ECU to the vehicle computer is completely different from the data path for transmitting the detection data of the second ECU to the vehicle computer, and they do not affect each other. Therefore, it can be considered that the target diagnostic request and the second diagnostic request can be executed in parallel.

[0074] Optionally, the vehicle computer may store ECU connection data. The ECU connection data describes the connection relationship between the ECU and the CAN. The vehicle computer may determine a target CAN that connects the first ECU to the vehicle computer based on the ECU connection data, and further determine a second ECU that is not connected to the target CAN based on the ECU connection data. The vehicle computer then searches the task list for a second diagnostic request for the test data of the second ECU.

[0075] For example, assuming that the vehicle includes Figure 2The multiple ECUs shown in the figure are connected to the vehicle computer in a manner shown in Figure 2. The ECU connection data is used to record the correspondence between the connected car entertainment module, DLC, and the first CAN; the correspondence between the DLC, ABS charging module, airbag module, engine control module, electric power steering module, and electronic stability control system and the second CAN; and the correspondence between the air conditioning control module, instrument cluster module, body control module, radar sensor, and engine immobilizer coil module and the third CAN.

[0076] Assuming the first ECU is a radar sensor, the vehicle computer determines, based on the ECU connection data, that the target CAN connecting the first ECU and the vehicle computer is the third CAN. Based on the ECU connection data, the second ECU not connected to the target CAN is determined to be the connected vehicle entertainment module, DLC, ABS charging module, airbag module, engine control module, electric power steering module, and electronic stability control system. The vehicle computer searches the task list for a second diagnostic request. The data source requirement for the second diagnostic request indicates that the request is for test data from one or more ECUs among the connected vehicle entertainment module, DLC, ABS charging module, airbag module, engine control module, electric power steering module, and electronic stability control system.

[0077] In step 02B, when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest level, the vehicle computer removes the target diagnostic request and the second diagnostic request from the task list, and collects detection data through different CANs in response to the target diagnostic request and the second diagnostic request to obtain the target detection data corresponding to the target diagnostic request and the first detection data corresponding to the second diagnostic request.

[0078] In this embodiment of the present application, the presence of a second diagnostic request in the task list indicates that a diagnostic request exists in the task list that can be executed in parallel with the target diagnostic request. The vehicle computer can simultaneously respond to the target diagnostic request and the second diagnostic request when the second diagnostic request has the highest priority, or when the target diagnostic request has the highest priority, to obtain target detection data corresponding to the target diagnostic request and first detection data corresponding to the second diagnostic request.

[0079] Alternatively, the vehicle computer can determine the diagnostic request corresponding to the collected test data via the CAN bus that transmits the test data. Alternatively, the vehicle computer can determine the diagnostic request corresponding to the test data based on data characteristics of the collected test data. The data characteristics are used to reflect the ECU that the test data originated from.

[0080] Continuing with the example in step 02A, when the first ECU is a radar sensor and the second ECU is an engine control module, the vehicle computer collects detection data of the radar sensor through the third CAN and detection data of the engine control module through the second CAN, determines the detection data transmitted through the third CAN as target detection data, and determines the detection data transmitted through the second CAN as first detection data.

[0081] In step 02C, the vehicle computer sends the target detection data to the diagnostic platform and sends the first detection data to the diagnostic platform to which the second diagnostic request belongs.

[0082] In an embodiment of the present application, the vehicle computer sends the target detection data to the diagnostic platform through the connection network between it and the diagnostic platform, and sends the first detection data to the diagnostic platform to which the second diagnostic request belongs, so that the diagnostic platform that sends the target diagnostic request performs vehicle diagnosis based on the target detection data, and the diagnostic platform that sends the second diagnostic request performs vehicle diagnosis based on the first detection data.

[0083] It should be noted that, in some embodiments, when the data source requirement included in the diagnostic request is used to indicate the static detection data of the requesting ECU, the vehicle computer may execute steps 02A to 02C. The static detection data of the ECU refers to the detection data collected when the collection conditions are applied to the ECU without affecting other ECUs. The diagnostic request may include collection conditions, and the collection conditions may include but are not limited to the collection time, collection duration, control conditions of the ECU operating status, etc. For example, the detection data indicated by the data source requirement in the diagnostic request is data that needs to be read by the vehicle computer using a data identifier (Decentralized Identity, DID).

[0084] In this way, if a second diagnostic request exists in the task list, the target detection data requested by the target diagnostic request and the first detection data requested by the second diagnostic request are respectively the static detection data of the first ECU and the second ECU. Therefore, the process of collecting detection data from the first ECU by the vehicle computer will not affect the process of collecting detection data from the second ECU, ensuring the accuracy of the collected target detection data and the first detection data, and thus ensuring the accuracy of the diagnostic platform's vehicle diagnosis.

[0085] In the embodiment of the application, when the vehicle includes multiple ECUs, and the multiple ECUs are connected to the vehicle machine through multiple CANs that are not interconnected, whether the second diagnostic request exists in the task list is determined, and when it is determined that the second diagnostic request exists in the task list, the target diagnostic request and the second diagnostic request are simultaneously executed to obtain the target detection data requested by the target diagnostic request and the first detection data requested by the second diagnostic request. The data source requirement of the second diagnostic request is used to indicate that the detection data comes from the second ECU. The second ECU is connected to the vehicle machine through a different CAN from the first ECU. In this way, the technical solution realizes parallel collection of detection data of multiple ECUs by using CANs that are not interconnected, realizes parallel execution of diagnostic requests, and improves the execution efficiency of the vehicle machine for diagnostic requests.

[0086] In an optional implementation, after adding the target diagnostic request to the task list, the vehicle machine can execute a service maintenance mechanism to inform the diagnostic platform of the processing state of the diagnostic request sent by the vehicle machine. Thus, the diagnostic platform is prevented from generating repetitive diagnostic requests due to a long time of not receiving a response from the vehicle machine.

[0087] Optionally, after adding the target diagnostic request to the task list in step 302, the method further includes recording an addition duration of the target diagnostic request added to the task list, and sending a waiting message to the diagnostic platform when the addition duration reaches an integer multiple of a standard waiting duration.

[0088] The waiting message is used to inform the diagnostic platform that the target diagnostic request is in a waiting execution state. Optionally, the standard waiting duration can be a waiting duration before a negative response is sent according to the UDS protocol. For example, the standard waiting duration can be 5s, 30s, or 60s, etc. Further optionally, the waiting message can be a negative response according to the UDS protocol. For example, the waiting message includes a negative response code 0x78. The negative response code 0x78 indicates that the server has correctly received the diagnostic request, is processing the requested service, cannot give a final positive or negative response at present, and cannot receive other diagnostic requests, so that the diagnostic platform waits first.

[0089] In an optional implementation, the vehicle machine can also perform security access verification for the target diagnostic request. When the data source requirement included in the target diagnostic request is used to indicate that the detection data comes from the first ECU, after receiving the target diagnostic requests sent by the multiple diagnostic platforms in step 301, the method further includes steps 03A to 03B.

[0090] In step 03A, the vehicle computer determines that security access verification is to be performed based on the target diagnostic request and the first ECU is in an unlocked state, and performs security access verification to obtain a first verification result. The security access verification is used to verify whether the diagnostic platform is allowed to access the first ECU.

[0091] In an embodiment of the present application, the ECU has a secure access mechanism that enters a secure period after performing a secure access verification. During the secure period, the ECU is in an unlocked state and no secondary secure access verification is performed. Data of the target type of the ECU can only be collected when the ECU is in an unlocked state. Optionally, the ECU's secure access mechanism can be a protection mechanism provided to the ECU by the 27 service of the UDS protocol. The 27 service uses a seed and key to provide a protection mechanism for accessing diagnostic services that are restricted due to safety factors or emissions.

[0092] When the vehicle computer determines that security access verification is to be performed according to the target diagnostic request, it indicates that the vehicle computer determines that the detection data requested by the diagnostic request is data of the target type of the ECU, and the vehicle computer can determine whether the first ECU is in an unlocked state.

[0093] When the first ECU is unlocked, security access verification is performed to obtain a first verification result. The first verification result is used to reflect whether the diagnostic platform that sent the target diagnostic request is allowed to access the first ECU. In an optional implementation, the verification rules for the security access verification performed by the vehicle computer can be the same as the verification rules of service 27. Of course, the verification rules for the security access verification performed by the vehicle computer can also be customized rules to verify whether the diagnostic platform is allowed to access the first ECU.

[0094] Based on this, the process of collecting the target detection data of the vehicle in response to the target diagnosis request in the aforementioned step 303 may include: collecting the target detection data of the vehicle in response to the target diagnosis request when the first verification result indicates that the verification is passed.

[0095] It is readily understood that if the first verification result indicates that the verification failed, the vehicle computer may not execute the step of collecting target detection data in response to the target diagnostic request. Optionally, if the first verification result indicates that the verification failed, the vehicle computer may also send a verification failure message to the diagnostic platform. This verification failure message indicates that the target diagnostic request failed and that the diagnostic platform is not authorized to access the first ECU.

[0096] In an optional implementation, the process of the vehicle computer determining the security access verification to be performed based on the target diagnostic request may include: determining the security access verification to be performed if the target diagnostic request includes verification indication information. The verification indication information is used to indicate that the vehicle computer needs to perform security access verification on the first ECU before responding to the target diagnostic request.

[0097] In another optional implementation, the process of the vehicle computer determining the security access verification to be performed based on the target diagnostic request may include: when the request type of the target diagnostic request is a target type, the vehicle computer determining the security access verification to be performed. The target type diagnostic request is used to request detection data including target type data.

[0098] In step 03B, when the vehicle computer determines that security access verification is to be performed according to the target diagnosis request and the first ECU is in an unlocked state, it sends a security access request to the first ECU and receives a second verification result.

[0099] If security access verification is required based on the target diagnostic request and the first ECU is unlocked, indicating that the first ECU has not entered the security cycle and needs to perform security access verification, the vehicle computer sends a security access request to the first ECU. The security access request is used to request the first ECU to perform security access verification.

[0100] After receiving the security access request from the vehicle computer, the first ECU performs security access verification and sends a second verification result to the vehicle computer. The second verification result indicates whether the diagnostic platform that sent the target diagnostic request is allowed to access the first ECU. If the second verification result indicates that the verification is successful, the first ECU is unlocked; if the second verification result indicates that the verification is unsuccessful, the first ECU is unlocked.

[0101] Based on this, the process of collecting the target detection data of the vehicle in response to the target diagnosis request in the aforementioned step 303 may include: collecting the target detection data of the vehicle in response to the target diagnosis request when the second verification result indicates that the verification is passed.

[0102] It is readily understood that if the second verification result indicates that the verification failed, the vehicle computer may not execute the step of collecting target detection data in response to the target diagnostic request. Optionally, if the received second verification result indicates that the verification failed, the vehicle computer may also send a verification failure message to the diagnostic platform. This verification failure message indicates that the target diagnostic request failed and that the diagnostic platform is not authorized to access the first ECU.

[0103] In this way, when a security access verification is determined to be performed based on a target diagnostic request, the vehicle computer performs security access verification when the first ECU is unlocked, thereby performing a secondary security access verification on the first ECU within its security cycle, thereby ensuring access security for the first ECU. This technical solution avoids the situation where multiple diagnostic platforms (especially multiple different diagnostic platforms) request target-type data from the ECU during its security cycle without performing security access verification, thereby improving ECU access security.

[0104] In an embodiment of the present application, the vehicle computer adds the target diagnostic request sent by the diagnostic platform to a task list. When the priority of the diagnostic request recorded in the task list is determined to be the highest, the vehicle computer removes the target diagnostic request from the task list. In response to the target diagnostic request, the vehicle's target detection data is collected and sent to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform. Even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, the vehicle computer can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring effective diagnosis by multiple diagnostic platforms. Compared with related technologies, this avoids the situation where detection data can only be returned to one diagnostic platform when multiple diagnostic platforms simultaneously initiate diagnostic requests, ensuring the diagnostic compatibility of multiple diagnostic platforms and improving vehicle diagnostic efficiency.

[0105] As an example, the embodiment of the present application further illustrates the aforementioned vehicle diagnostic method with the following example.

[0106] like Figure 4 As shown, the vehicle diagnosis method includes:

[0107] Step 401: The vehicle computer receives a target diagnosis request sent by the diagnosis platform. The target diagnosis request includes a data source requirement, and the data source requirement is used to indicate a request for detection data from a first ECU.

[0108] Step 402: The vehicle computer queries a list of completed tasks according to the target diagnosis request.

[0109] Step 403 : When the vehicle computer determines that the completed task list includes the first diagnostic request, it sends the detection data corresponding to the first diagnostic request in the completed task list to the diagnostic platform. The first diagnostic request and the target diagnostic request include the same data source requirements.

[0110] Step 404 : When the vehicle computer determines that the completed task list does not include the first diagnostic request, the vehicle computer adds the target diagnostic request to the task list.

[0111] Step 405: If the vehicle computer has a second diagnostic request in the task list, and if it determines that the second diagnostic request or the target diagnostic request has the highest priority, the target diagnostic request and the second diagnostic request are removed from the task list. In response to the target diagnostic request and the second diagnostic request, test data is collected via different CANs to obtain target test data corresponding to the target diagnostic request and first test data corresponding to the second diagnostic request.

[0112] The data source requirement of the second diagnostic request is used to indicate a request for detection data from a second ECU, and the second ECU and the first ECU are connected to the vehicle computer via different CANs.

[0113] Step 406 : The vehicle computer sends the first detection data to the diagnostic platform to which the second diagnostic request belongs, and sends the target detection data to the diagnostic platform to which the target diagnostic request belongs.

[0114] Step 407: When the vehicle computer does not have a second diagnostic request in the task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priority of the diagnostic requests recorded in the task list, the target diagnostic request is removed from the task list, and the target detection data of the vehicle is collected in response to the target diagnostic request.

[0115] Step 408 : The vehicle computer adds the target diagnosis request and the target detection data to a completed task list, and records the corresponding relationship between the target diagnosis request and the target detection data in the completed task list.

[0116] Step 409: The vehicle computer sends the target detection data to the diagnosis platform.

[0117] It should be noted that the explanation and implementation of each step can refer to the relevant explanation and implementation of the aforementioned steps, and the embodiments of this application will not go into details.

[0118] As another example, the embodiment of the present application further illustrates the aforementioned vehicle diagnostic method with the following example. Figure 5 As shown, the vehicle diagnosis method includes:

[0119] Step 501: The diagnostic platform sends a target diagnostic request to the vehicle computer. The target diagnostic request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from a first ECU.

[0120] Step 502: The vehicle computer queries a list of completed tasks according to the target diagnosis request.

[0121] Step 503 : When the vehicle computer determines that the completed task list includes the first diagnostic request, it sends the detection data corresponding to the first diagnostic request in the completed task list to the diagnostic platform. The first diagnostic request and the target diagnostic request include the same data source requirements.

[0122] Step 504 : When the vehicle computer determines that the completed task list does not include the first diagnostic request, the vehicle computer adds the target diagnostic request to the task list.

[0123] Step 505 : When the vehicle computer determines that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, the vehicle computer removes the target diagnostic request from the task list.

[0124] Step 506: The vehicle computer sends an ECU request corresponding to the target diagnostic request to the first ECU.

[0125] Step 507: The first ECU collects target detection data and sends the target detection data to the vehicle computer.

[0126] Step 508 : The vehicle computer adds the target diagnosis request and the target detection data to a completed task list, and records the corresponding relationship between the target diagnosis request and the target detection data in the completed task list.

[0127] Step 509: The vehicle computer sends the target detection data to the diagnosis platform.

[0128] It should be noted that the explanation and implementation of each step can refer to the relevant explanation and implementation of the aforementioned steps, and the embodiments of this application will not go into details.

[0129] As another example, the embodiment of the present application further illustrates the above vehicle diagnostic method with the following example. Figure 6 As shown, the vehicle diagnosis method includes:

[0130] Step 601: The diagnostic platform sends a target diagnostic request to the vehicle computer. The target diagnostic request includes verification instruction information, which is used to instruct the execution of the service 27.

[0131] Step 602: The vehicle computer adds the target diagnosis request to the task list.

[0132] Step 603 : When the vehicle computer determines that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, the vehicle computer removes the target diagnostic request from the task list.

[0133] Step 604 : When it is determined according to the target diagnosis request that security access verification is to be performed and the first ECU is in an unlocked state, security access verification is performed to obtain a first verification result.

[0134] Step 605 : When the first verification result indicates that the verification is passed, the vehicle computer collects target detection data of the vehicle in response to the target diagnosis request.

[0135] Step 606: The vehicle computer sends the target detection data to the diagnostic platform.

[0136] Step 607 : When the vehicle computer determines that security access verification is to be performed according to the target diagnosis request and the first ECU is in an unlocked state, the vehicle computer sends a security access request to the first ECU.

[0137] Step 608: The first ECU performs security access verification and sends a second verification result to the vehicle computer.

[0138] Step 609 : When the second verification result indicates that the verification is passed, the vehicle computer collects target detection data of the vehicle in response to the target diagnosis request.

[0139] Step 610: The vehicle computer sends target detection data to the diagnostic platform.

[0140] In summary, the vehicle diagnostic method provided by the embodiment of the present application is that the vehicle computer adds target diagnostic requests sent by multiple diagnostic platforms to a task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priority of the diagnostic requests recorded in the task list, the target diagnostic request is removed from the task list, and the target detection data of the vehicle is collected in response to the target diagnostic request, and the target detection data is sent to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform, so that even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, it can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring effective diagnosis by multiple diagnostic platforms. Compared with related technologies, this avoids the situation where only detection data can be returned to one diagnostic platform when multiple diagnostic platforms initiate diagnostic requests at the same time, ensures the diagnostic compatibility of multiple diagnostic platforms, and improves the efficiency of automobile diagnosis.

[0141] Please refer to Figure 7 , which shows a flow chart of a vehicle diagnostic method provided by an embodiment of the present application. The vehicle diagnostic method is applied to Figure 1 The vehicle diagnostic system shown in FIG is executed by the vehicle computer. Figure 6 As shown, the vehicle diagnosis method includes:

[0142] Step 701: Receive target diagnosis requests sent by multiple diagnosis platforms, and add the target diagnosis requests to a task list.

[0143] Step 702: When it is determined that the priority of the target diagnosis request is the highest according to the priorities of the diagnosis requests recorded in the task list, remove the target diagnosis request from the task list, and collect target detection data of the vehicle in response to the target diagnosis request.

[0144] Step 703: Send the target detection data to the diagnostic platform so that the diagnostic platform performs vehicle diagnosis based on the target detection data.

[0145] Optionally, the target diagnosis request includes a data source requirement; before adding the target diagnosis request to the task list, the method further includes:

[0146] Query the completed task list according to the target diagnostic request. The completed task list is used to record the responded diagnostic requests and the corresponding test data;

[0147] In the case where it is determined that the completed task list includes the first diagnostic request, sending the detection data corresponding to the first diagnostic request in the completed task list to the diagnostic platform;

[0148] Adding the target diagnosis request to the task list includes: if it is determined that the completed task list does not include the first diagnosis request, adding the target diagnosis request to the task list, the data source requirement included in the first diagnosis request being the same as the data source requirement included in the target diagnosis request;

[0149] After collecting the target detection data of the vehicle in response to the target diagnosis request, the method further includes: adding the target diagnosis request and the target detection data to a completed task list, and recording a correspondence between the target diagnosis request and the target detection data in the completed task list.

[0150] Optionally, the vehicle includes multiple electronic control units (ECUs), the multiple ECUs are connected to the vehicle computer via a multi-channel controller area network (CAN), and the multiple CANs are not interconnected. The target diagnostic request includes a data source requirement, and the data source requirement is used to indicate a request for detection data from the first ECU. The method further includes:

[0151] In a case where the second diagnostic request exists in the task list, when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest, removing the target diagnostic request and the second diagnostic request from the task list, and collecting detection data through different CANs in response to the target diagnostic request and the second diagnostic request to obtain target detection data corresponding to the target diagnostic request and first detection data corresponding to the second diagnostic request;

[0152] The first detection data is sent to the diagnostic platform to which the second diagnostic request belongs. The data source requirement of the second diagnostic request is used to indicate that the detection data is requested from the second ECU. The second ECU and the first ECU are connected to the vehicle computer through different CANs.

[0153] Optionally, when it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, removing the target diagnostic request from the task list, and collecting target detection data of the vehicle in response to the target diagnostic request, including:

[0154] In the case that there is no second diagnostic request in the task list, when the priority of the target diagnostic request is determined to be the highest according to the priority of the diagnostic requests recorded in the task list, the target diagnostic request is removed from the task list, and target detection data of the vehicle is collected in response to the target diagnostic request.

[0155] Optionally, the target diagnostic request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU; after receiving the target diagnostic requests sent by the multiple diagnostic platforms, the method further includes:

[0156] When it is determined that security access verification is to be performed according to the target diagnostic request and the first ECU is in an unlocked state, performing security access verification to obtain a first verification result, wherein the security access verification is used to verify whether the diagnostic platform is allowed to access the first ECU;

[0157] collecting target detection data of the vehicle in response to the target diagnosis request, including: if the first verification result indicates that the verification is passed, collecting the target detection data of the vehicle in response to the target diagnosis request;

[0158] When it is determined according to the target diagnostic request that security access verification is to be performed and the first ECU is in an unlocked state, sending a security access request to the first ECU so that the first ECU performs the security access verification and sends a second verification result to the vehicle computer;

[0159] receiving a second verification result;

[0160] Collecting target detection data of the vehicle in response to a target diagnosis request includes: when a second verification result indicates that the verification is passed, collecting the target detection data of the vehicle in response to the target diagnosis request, wherein when the second verification result indicates that the verification is passed, the first ECU is in an unlocked state, and when the second verification result indicates that the verification is failed, the first ECU is in an unlocked state.

[0161] Optionally, determining security access verification to be performed based on the target diagnostic request includes:

[0162] In a case where the target diagnosis request includes verification instruction information, determining a security access verification to be performed;

[0163] Alternatively, when the request type of the target diagnostic request is a target type, it is determined that the security access verification is to be performed, the target type diagnostic request is used to request detection data including target type data, and the ECU is used to provide target type data when in an unlocked state.

[0164] Optionally, after adding the target diagnosis request to the task list, the method further includes:

[0165] Record the time it takes for the target diagnosis request to be added to the task list;

[0166] When the added time reaches an integer multiple of the standard waiting time, a waiting message is sent to the diagnosis platform. The waiting message is used to inform the diagnosis platform that the target diagnosis request is in a waiting execution state.

[0167] Optionally, the target diagnosis request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU; and collecting the target detection data of the vehicle in response to the target diagnosis request includes:

[0168] In response to the target diagnosis request, sending an ECU request corresponding to the target diagnosis request to the first ECU, so that the first ECU sends the target detection data to the vehicle computer after receiving the ECU request;

[0169] Receive target detection data.

[0170] In summary, the vehicle diagnostic method provided by the embodiment of the present application is that the vehicle computer adds the target diagnostic request sent by the diagnostic platform to the task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priority of the diagnostic request recorded in the task list, the target diagnostic request is removed from the task list, and the target detection data of the vehicle is collected in response to the target diagnostic request, and the target detection data is sent to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform, so that even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, it can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring the effective diagnosis of multiple diagnostic platforms. Compared with the related art, it avoids the situation where only detection data can be returned to one diagnostic platform when multiple diagnostic platforms initiate diagnostic requests at the same time, ensures the diagnostic compatibility of multiple diagnostic platforms, and improves the efficiency of automobile diagnosis.

[0171] Please refer to Figure 8 , which shows a flow chart of a vehicle diagnostic method provided by an embodiment of the present application. The vehicle diagnostic method is applied to Figure 1 The vehicle diagnosis system shown is executed by a diagnosis platform. As Figure 7 The vehicle diagnosis method shown includes:

[0172] Step 801, a target diagnosis request is sent to the vehicle machine, so that the vehicle machine adds the target diagnosis request to a task list, removes the target diagnosis request from the task list in a case where a priority of the target diagnosis request is determined to be the highest according to a priority of a diagnosis request recorded in the task list, and collects target detection data of the vehicle in response to the target diagnosis request, and sends the target detection data to the diagnosis platform.

[0173] Step 802, the target detection data sent by the vehicle machine is received.

[0174] Step 803, vehicle diagnosis is performed according to the target detection data.

[0175] Optionally, the method further includes receiving a waiting message sent by the vehicle machine, the waiting message being a message sent by the vehicle machine to the diagnosis platform when an addition duration reaches an integer multiple of a standard waiting duration, the addition duration being a duration for which the target diagnosis request is added to the task list, and the waiting message being used to inform the diagnosis platform that the target diagnosis request is in a waiting execution state.

[0176] To sum up, the vehicle diagnosis method provided by the embodiments of the present application, the vehicle machine adds the target diagnosis request sent by the diagnosis platform to the task list, so that the target diagnosis request is removed from the task list in a case where the priority of the target diagnosis request is determined to be the highest according to the priority of the diagnosis request recorded in the task list, and the target detection data of the vehicle is collected in response to the target diagnosis request, and the target detection data is sent to the diagnosis platform, so that the diagnosis platform performs vehicle diagnosis according to the target detection data. In this technical solution, the vehicle machine end records the diagnosis requests received from the diagnosis platform by increasing the task list, so that even if multiple diagnosis platforms send diagnosis requests, or one diagnosis platform sends multiple diagnosis requests, the diagnosis requests can be responded to in turn according to the priority of the diagnosis request recorded in the task list, the target detection data requested by the diagnosis request is obtained, and the target detection data is returned to the diagnosis platform for vehicle diagnosis, so as to guarantee the effective diagnosis of multiple diagnosis platforms. Compared with the related art, the situation that the detection data can only be returned to one diagnosis platform when multiple diagnosis platforms simultaneously initiate diagnosis requests is avoided, the diagnosis compatibility of multiple diagnosis platforms is guaranteed, and the automobile diagnosis efficiency is improved.

[0177] Please refer to Figure 9 which shows a block diagram of a vehicle diagnosis apparatus provided by an embodiment of the present application. The vehicle diagnosis apparatus is applied to a vehicle machine of a vehicle. As Figure 9 shown, the vehicle diagnosis apparatus 900 includes a receiving module 901, a processing module 902, and a sending module 903.

[0178] A receiving module 901 is configured to receive target diagnosis requests sent by multiple diagnosis platforms and add the target diagnosis requests to a task list;

[0179] a processing module 902 configured to, if it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, remove the target diagnostic request from the task list, and collect target detection data of the vehicle in response to the target diagnostic request;

[0180] The sending module 903 is used to send the target detection data to the diagnosis platform so that the diagnosis platform performs vehicle diagnosis based on the target detection data.

[0181] Optionally, the target diagnosis request includes a data source requirement; and the vehicle diagnostic device further includes:

[0182] A query module is used to query a completed task list according to a target diagnostic request. The completed task list is used to record the responded diagnostic requests and the corresponding test data;

[0183] The sending module 903 is further configured to send the detection data corresponding to the first diagnostic request in the completed task list to the diagnostic platform when it is determined that the completed task list includes the first diagnostic request;

[0184] an adding module, configured to add the target diagnostic request to the task list if it is determined that the completed task list does not include the first diagnostic request, the data source requirement included in the first diagnostic request being the same as the data source requirement included in the target diagnostic request;

[0185] The adding module is also used to add the target diagnosis request and the target detection data to the completed task list, and record the corresponding relationship between the target diagnosis request and the target detection data in the completed task list.

[0186] Optionally, the vehicle includes multiple electronic control units ECU, the multiple ECUs are connected to the vehicle computer via a multi-channel controller area network CAN, and the multiple CANs are not interconnected, and the target diagnostic request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU;

[0187] The processing module 902 is further configured to, if the second diagnostic request exists in the task list, remove the target diagnostic request and the second diagnostic request from the task list when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest, and acquire detection data through different CANs in response to the target diagnostic request and the second diagnostic request to obtain target detection data corresponding to the target diagnostic request and first detection data corresponding to the second diagnostic request;

[0188] The sending module 903 is also used to send the first detection data to the diagnostic platform to which the second diagnostic request belongs. The data source requirement of the second diagnostic request is used to indicate that the detection data requested comes from the second ECU. The second ECU and the first ECU are connected to the vehicle computer through different CANs.

[0189] Optionally, the processing module 902 is also used to remove the target diagnostic request from the task list when there is no second diagnostic request in the task list, and to collect target detection data of the vehicle in response to the target diagnostic request when the priority of the target diagnostic request is determined to be the highest level according to the priority of the diagnostic requests recorded in the task list.

[0190] Optionally, the target diagnosis request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU; the apparatus further includes:

[0191] an execution module, configured to, when it is determined that security access verification is to be performed according to the target diagnostic request and the first ECU is in an unlocked state, perform the security access verification to obtain a first verification result, wherein the security access verification is used to verify whether the diagnostic platform is allowed to access the first ECU;

[0192] The processing module 902 is further configured to collect target detection data of the vehicle in response to the target diagnosis request if the first verification result indicates that the verification is passed;

[0193] The sending module 903 is further configured to, when it is determined according to the target diagnostic request that security access verification is to be performed and the first ECU is in an unlocked state, send a security access request to the first ECU, so that the first ECU performs the security access verification and sends a second verification result to the vehicle computer;

[0194] Receiving module 901, configured to receive a second verification result;

[0195] The processing module 902 is also used to collect target detection data of the vehicle in response to a target diagnosis request when the second verification result indicates that the verification is passed, wherein when the second verification result indicates that the verification is passed, the first ECU is in an unlocked state; when the second verification result indicates that the verification is failed, the first ECU is in an unlocked state.

[0196] Optionally, the execution module is further configured to: determine a security access verification to be performed when the target diagnosis request includes verification instruction information;

[0197] Alternatively, when the request type of the target diagnostic request is a target type, it is determined that the security access verification is to be performed, the target type diagnostic request is used to request detection data including target type data, and the ECU is used to provide target type data when in an unlocked state.

[0198] Optionally, the device further comprises:

[0199] A recording module, used to record the time it takes for a target diagnosis request to be added to a task list;

[0200] The sending module 903 is further configured to send a waiting message to the diagnosis platform when the added time reaches an integer multiple of the standard waiting time. The waiting message is configured to inform the diagnosis platform that the target diagnosis request is in a waiting state.

[0201] Optionally, the target diagnosis request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU; the processing module 902 is further configured to:

[0202] In response to the target diagnosis request, sending an ECU request corresponding to the target diagnosis request to the first ECU, so that the first ECU sends the target detection data to the vehicle computer after receiving the ECU request;

[0203] Receive target detection data.

[0204] In summary, the vehicle diagnostic device provided by the embodiment of the present application, the vehicle computer adds the target diagnostic request sent by the diagnostic platform to the task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priority of the diagnostic request recorded in the task list, the target diagnostic request is removed from the task list, and the target detection data of the vehicle is collected in response to the target diagnostic request, and the target detection data is sent to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform, so that even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, it can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring the effective diagnosis of multiple diagnostic platforms. Compared with the related art, it avoids the situation where only detection data can be returned to one diagnostic platform when multiple diagnostic platforms initiate diagnostic requests at the same time, ensures the diagnostic compatibility of multiple diagnostic platforms, and improves the efficiency of automobile diagnosis.

[0205] Please refer to Figure 10 , which shows a block diagram of another vehicle diagnostic device provided by an embodiment of the present application. The vehicle diagnostic device is applied to a diagnostic platform. Figure 10 As shown, the vehicle diagnostic device 900 includes: a sending module 1001 , a receiving module 1002 and a diagnostic module 1003 .

[0206] a sending module 1001, configured to send a target diagnosis request to a vehicle computer, so that the vehicle computer adds the target diagnosis request to a task list; if the priority of the target diagnosis request is determined to be the highest according to the priorities of the diagnostic requests recorded in the task list, remove the target diagnosis request from the task list; collect target detection data of the vehicle in response to the target diagnosis request, and send the target detection data to the diagnostic platform;

[0207] Receiving module 1002, used to receive target detection data sent by the vehicle computer;

[0208] The diagnosis module 1003 is used to perform vehicle diagnosis based on the target detection data.

[0209] Optionally, the receiving module 1002 is also used to receive a waiting message sent by the vehicle computer. The waiting message is a message sent by the vehicle computer to the diagnostic platform when the adding time reaches an integer multiple of the standard waiting time. The adding time is the time it takes for the target diagnostic request to be added to the task list. The waiting message is used to inform the diagnostic platform that the target diagnostic request is in a waiting execution state.

[0210] In summary, the vehicle diagnostic device provided by the embodiment of the present application, the vehicle computer adds the target diagnostic request sent by the diagnostic platform to the task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priority of the diagnostic request recorded in the task list, the target diagnostic request is removed from the task list, and the target detection data of the vehicle is collected in response to the target diagnostic request, and the target detection data is sent to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data. In this technical solution, the vehicle computer adds a task list to record the diagnostic requests it receives from the diagnostic platform, so that even if multiple diagnostic platforms send diagnostic requests, or a diagnostic platform sends multiple diagnostic requests, it can respond to the diagnostic requests in sequence according to the priority of the diagnostic requests recorded in the task list to obtain the target detection data requested by the diagnostic request, and return the target detection data to the diagnostic platform for the diagnostic platform to perform vehicle diagnosis, thereby ensuring the effective diagnosis of multiple diagnostic platforms. Compared with the related art, it avoids the situation where only detection data can be returned to one diagnostic platform when multiple diagnostic platforms initiate diagnostic requests at the same time, ensures the diagnostic compatibility of multiple diagnostic platforms, and improves the efficiency of automobile diagnosis.

[0211] Please refer to Figure 11 , which shows a block diagram of an electronic device provided by this application. Figure 11 As shown, the electronic device includes: a processor 1101, a memory 1102, and a computer program stored in the memory 1102 and executable on the processor 1101. When the processor 1101 executes the computer program, the progress bar drawing method provided in the above embodiment is implemented.

[0212] An embodiment of the present application further provides a readable storage medium. When instructions in the readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the progress bar drawing method provided in the aforementioned embodiment.

[0213] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A vehicle diagnostic method, characterized in that: Applied to a vehicle computer, the method includes: receiving target diagnosis requests sent by multiple diagnosis platforms, and adding the target diagnosis requests to a task list; If it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, removing the target diagnostic request from the task list, and collecting target detection data of the vehicle in response to the target diagnostic request; sending the target detection data to the diagnostic platform so that the diagnostic platform performs vehicle diagnosis based on the target detection data; The vehicle includes multiple electronic control units (ECUs), the multiple ECUs are connected to the vehicle computer via a multi-channel controller area network (CAN), and the multiple CANs are not interconnected. The target diagnostic request includes a data source requirement, and the data source requirement is used to indicate a request for detection data from a first ECU. The method further includes: In a case where a second diagnostic request exists in the task list, when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest, removing the target diagnostic request and the second diagnostic request from the task list, and collecting detection data through different CANs in response to the target diagnostic request and the second diagnostic request to obtain the target detection data corresponding to the target diagnostic request and the first detection data corresponding to the second diagnostic request; The first detection data is sent to the diagnostic platform to which the second diagnostic request belongs. The data source requirement of the second diagnostic request is used to indicate that the detection data is requested from a second ECU. The second ECU and the first ECU are connected to the vehicle computer through different CANs.

2. The method according to claim 1, characterized in that The target diagnosis request includes a data source requirement; before adding the target diagnosis request to the task list, the method further includes: querying a completed task list according to the target diagnostic request, wherein the completed task list is used to record the responded diagnostic requests and corresponding detection data; In a case where it is determined that the completed task list includes a first diagnostic request, sending the detection data corresponding to the first diagnostic request in the completed task list to the diagnostic platform; The adding the target diagnosis request to the task list includes: if it is determined that the completed task list does not include the first diagnosis request, adding the target diagnosis request to the task list, wherein the data source requirement included in the first diagnosis request is the same as the data source requirement included in the target diagnosis request; After collecting the target detection data of the vehicle in response to the target diagnosis request, the method further includes: adding the target diagnosis request and the target detection data to the completed task list, and recording the correspondence between the target diagnosis request and the target detection data in the completed task list.

3. The method according to claim 1, characterized in that The step of removing the target diagnostic request from the task list when it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, and collecting target detection data of the vehicle in response to the target diagnostic request includes: In the case that the second diagnostic request does not exist in the task list, when the priority of the target diagnostic request is determined to be the highest according to the priority of the diagnostic requests recorded in the task list, the target diagnostic request is removed from the task list, and the target detection data of the vehicle is collected in response to the target diagnostic request.

4. The method according to claim 1, wherein The target diagnosis request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU; After receiving the target diagnosis requests sent by the multiple diagnosis platforms, the method further includes: When it is determined that security access verification is to be performed according to the target diagnostic request and the first ECU is in an unlocked state, performing security access verification to obtain a first verification result, wherein the security access verification is used to verify whether the diagnostic platform is allowed to access the first ECU; The collecting the target detection data of the vehicle in response to the target diagnosis request includes: collecting the target detection data of the vehicle in response to the target diagnosis request if the first verification result indicates that the verification is passed; When it is determined according to the target diagnostic request that security access verification is to be performed and the first ECU is in an unlocked state, sending a security access request to the first ECU so that the first ECU performs the security access verification and sends a second verification result to the vehicle computer; receiving the second verification result; The collecting of target detection data of the vehicle in response to the target diagnostic request includes: when the second verification result indicates that the verification is passed, collecting the target detection data of the vehicle in response to the target diagnostic request, wherein when the second verification result indicates that the verification is passed, the first ECU is in an unlocked state; when the second verification result indicates that the verification is failed, the first ECU is in an unlocked state.

5. The method according to claim 1, wherein After adding the target diagnosis request to the task list, the method further includes: Recording the duration of adding the target diagnosis request to the task list; When the added time reaches an integral multiple of the standard waiting time, a waiting message is sent to the diagnosis platform, where the waiting message is used to inform the diagnosis platform that the target diagnosis request is in a waiting execution state.

6. The method according to claim 1, characterized in that The target diagnosis request includes a data source requirement, where the data source requirement is used to indicate a request for detection data from the first ECU; The collecting target detection data of the vehicle in response to the target diagnosis request includes: In response to the target diagnosis request, sending an ECU request corresponding to the target diagnosis request to the first ECU, so that the first ECU sends the target detection data to the vehicle computer after receiving the ECU request; The target detection data is received.

7. A vehicle diagnostic method, characterized in that: Applied to a diagnostic platform, the method comprises: sending a plurality of target diagnostic requests to a vehicle computer of a vehicle so that the vehicle computer adds the target diagnostic requests to a task list; if it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, removing the target diagnostic request from the task list; collecting target detection data of the vehicle in response to the target diagnostic request, and sending the target detection data to the diagnostic platform; the vehicle includes a plurality of electronic control units (ECUs), the plurality of ECUs are connected to the vehicle computer via a multi-channel controller area network (CAN), and the multi-channel CANs are not interconnected; the target diagnostic request includes a data source requirement, the data source requirement being used to indicate a request for detection data from a first ECU; The method further includes: when a second diagnostic request exists in the task list, when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest, removing the target diagnostic request and the second diagnostic request from the task list, and collecting detection data through different CANs in response to the target diagnostic request and the second diagnostic request to obtain the target detection data corresponding to the target diagnostic request and the first detection data corresponding to the second diagnostic request; sending the first detection data to a diagnostic platform to which the second diagnostic request belongs, the data source requirement of the second diagnostic request is used to indicate that the detection data is requested from a second ECU, and the second ECU and the first ECU are connected to the vehicle computer through different CANs; receiving the target detection data sent by the vehicle computer; Vehicle diagnosis is performed based on the target detection data.

8. A vehicle diagnostic device, characterized in that: The device is applied to a vehicle computer, and includes: a receiving module, configured to receive target diagnostic requests sent by multiple diagnostic platforms, add the target diagnostic requests to a task list, the vehicle comprising multiple electronic control units (ECUs), the multiple ECUs being connected to the vehicle computer via a multi-channel controller area network (CAN), and the multiple CANs being not interconnected, the target diagnostic request comprising a data source requirement, the data source requirement being used to indicate a request for detection data from a first ECU; and further comprising: in the event that a second diagnostic request exists in the task list, when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest, removing the target diagnostic request and the second diagnostic request from the task list, and collecting detection data in response to the target diagnostic request and the second diagnostic request via different CANs to obtain the target detection data corresponding to the target diagnostic request and the first detection data corresponding to the second diagnostic request; and sending the first detection data to the diagnostic platform to which the second diagnostic request belongs, the data source requirement of the second diagnostic request being used to indicate a request for detection data from a second ECU, the second ECU and the first ECU being connected to the vehicle computer via different CANs; a processing module, configured to, if it is determined that the priority of the target diagnostic request is the highest according to the priorities of the diagnostic requests recorded in the task list, remove the target diagnostic request from the task list, and collect target detection data of the vehicle in response to the target diagnostic request; The sending module is used to send the target detection data to the diagnostic platform, so that the diagnostic platform performs vehicle diagnosis based on the target detection data.

9. A vehicle diagnostic device, characterized in that: Applied to a diagnostic platform, the device comprises: A sending module is used to send multiple target diagnostic requests to the vehicle's on-board computer, so that the on-board computer adds the target diagnostic requests to a task list, and when it is determined that the priority of the target diagnostic request is the highest according to the priority of the diagnostic request recorded in the task list, remove the target diagnostic request from the task list, and collect target detection data of the vehicle in response to the target diagnostic request, and send the target detection data to the diagnostic platform, the vehicle includes multiple electronic control units ECU, the multiple ECUs are connected to the on-board computer through a multi-channel controller area network CAN, and the multiple CANs are not interconnected, the target diagnostic request includes a data source requirement, and the data source requirement is used to indicate the detection request from the first ECU test data; further comprising: in a case where there is a second diagnostic request in the task list, when it is determined that the priority of the second diagnostic request or the target diagnostic request is the highest, removing the target diagnostic request and the second diagnostic request from the task list, and collecting test data in response to the target diagnostic request and the second diagnostic request through different CANs to obtain the target test data corresponding to the target diagnostic request and the first test data corresponding to the second diagnostic request; sending the first test data to the diagnostic platform to which the second diagnostic request belongs, the data source requirement of the second diagnostic request is used to indicate a request for test data from a second ECU, and the second ECU and the first ECU are connected to the vehicle computer through different CANs; A receiving module, configured to receive the target detection data sent by the vehicle computer; A diagnostic module is used to perform vehicle diagnosis based on the target detection data.

10. An electronic device, characterized in that: include: processor and memory; The memory is used to store computer programs; The processor, when used to execute the program stored in the memory, implements the method steps described in any one of claims 1 to 6; or implements the method steps described in claim 8.

11. A readable storage medium, characterized in that: When the instructions in the readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method according to any one of claims 1 to 6; or execute the method according to claim 8.

Images