Vehicle detection method, device, equipment and computer medium

Abstract

The invention discloses a vehicle detection method, device and equipment and a computer medium. The method comprises the steps that at least one first diagnosis request is sent to at least one first operation unit in a vehicle; receiving at least one piece of first diagnosis information fed back by the at least one first operation unit based on the at least one first diagnosis request; generating a diagnosis report based on the at least one piece of first diagnosis information; and the diagnosis report is sent to the target equipment, so that the effect of improving the fault detection efficiency of the vehicle can be achieved.

Description

Technical Field

[0001] The present application belongs to the field of vehicle diagnosis technology, and in particular, relates to a vehicle detection method, device, equipment and computer medium. Background Art

[0002] In the related art, fault detection of various parts in a vehicle is usually carried out by users going to a specific location to perform fault detection or repair when the fault affects the user's normal use of certain functions of the vehicle or affects the user's use of the vehicle. This makes fault detection of the vehicle inefficient. Summary of the invention

[0003] The embodiment of the present application provides an implementation scheme different from the prior art to solve the technical problem of low efficiency in vehicle fault detection in the related art.

[0004] In a first aspect, the present application provides a vehicle detection method, applicable to a first diagnostic unit in a SOC, comprising:

[0005] sending at least one first diagnostic request to at least one first operating unit in the vehicle;

[0006] receiving at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request;

[0007] generating a diagnostic report based on the at least one first diagnostic information;

[0008] The diagnostic report is sent to the target device.

[0009] In a second aspect, the present application provides a vehicle detection device, applicable to a first diagnostic unit in a SOC, comprising:

[0010] a sending unit, configured to send at least one first diagnostic request to at least one first operating unit in the vehicle;

[0011] a receiving unit, configured to receive at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request;

[0012] A generating unit, configured to generate a diagnostic report based on the at least one first diagnostic information;

[0013] The sending unit is further used to send the diagnosis report to the target device.

[0014] In a third aspect, the present application provides an electronic device, including:

[0015] Processor; and

[0016] A memory, configured to store executable instructions of the processor;

[0017] The processor is configured to execute any method in the first aspect or any possible implementation manner of the first aspect by executing the executable instructions.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements any method in the first aspect or any possible implementation manner of the first aspect.

[0019] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method described in the first aspect or any possible implementation manner of the first aspect.

[0020] The method for the first diagnostic unit in the SOC provided by the present application includes: sending at least one first diagnostic request to at least one first operating unit in the vehicle; receiving at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request; generating a diagnostic report based on the at least one first diagnostic information; and sending the diagnostic report to a target device. The solution of the present application can automatically perform fault detection on each first operating unit connected to the first diagnostic unit, thereby improving the efficiency of fault detection on the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0022] Figure 1a A schematic diagram of the structure of a system provided in one embodiment of the present application;

[0023] Figure 1b A schematic diagram of the structure of a vehicle detection system provided in one embodiment of the present application;

[0024] Figure 2 A flow chart of a vehicle detection method is provided for an embodiment of the present application;

[0025] Figure 3 A schematic diagram of the structure of a vehicle detection device provided in one embodiment of the present application;

[0026] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, but cannot be understood as limiting the present application.

[0028] The terms "first" and "second" etc. in the specification, claims and drawings of the embodiments of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0029] First, some terms in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

[0030] In the automotive field, a domain controller refers to the integration of highly embedded controllers within a specific functional domain, or the centralization of vehicle-level software functions within a specific functional domain.

[0031] SOC, the full name of which is System on Chip, is a product that highly integrates the components required by the system on a single chip. SOC is a complex system that integrates the main components of the system, such as microprocessors, analog IP cores, digital IP cores, and memory (including RAM, ROM, Flash, etc.) on a single chip. It is usually manufactured using deep submicron technology and can implement complex system functions on a very small chip. SOC not only reduces the size and power consumption of the system, but also improves the reliability and performance of the system.

[0032] SWC (Software Component) is one of the core concepts in the AUTOSAR (Automotive Open System Architecture) system. In the AUTOSAR architecture, SWC represents the basic building block of vehicle applications, which is used to define and implement functional units. SWC can be independently developed, tested and deployed, and communicate with other components through standardized interfaces. This modular design makes software development, maintenance and upgrades more efficient and flexible.

[0033] MCU, or microcontroller, is a single-chip microcomputer that integrates CPU, memory, I / O interface and other functions. It is widely used in various embedded systems, such as automotive electronics, industrial automation, smart home and other fields. MCU controls external devices or performs specific tasks by executing programs stored in memory.

[0034] In the AUTOSAR architecture, SWC is usually deployed in the Application layer of the MCU. The Application layer contains SWCs that implement specific functions, which interact with BSW (Basic Software) and MCAL (MicroController Abstration Layer) through RTE (RunTime Environment).

[0035] M-ECU (Master ECU) plays a vital role in automotive electronic systems. It is usually used as the core ECU (Electronic Control Unit) device connected to the intelligent diagnostic middleware, that is, the master electronic control unit, and is one of the core components in automotive electronic systems. It is responsible for coordinating and managing the communication and data exchange between various ECUs in the vehicle to ensure the coordinated work between various vehicle systems. M-ECU usually has powerful data processing and communication capabilities, and can monitor and control the operating status of the vehicle in real time.

[0036] The intelligent diagnostic middleware Master is a diagnostic tool or software platform specifically for automotive electronic systems. It achieves comprehensive monitoring and diagnosis of various vehicle systems by connecting with M-ECU and other ECU devices. The intelligent diagnostic middleware Master can collect and analyze vehicle data in real time, provide accurate fault diagnosis and maintenance suggestions, and help technicians quickly locate and solve problems.

[0037] The 22 service in vehicle diagnostics, also known as the ReadDataByIdentifier service, is a standard service defined based on diagnostic protocols such as ISO 14229-1. The 22 service is a service used in vehicle diagnostics to request an electronic control unit (ECU) to provide its internal diagnostic data. This data may include ECU status, fault codes, sensor data, etc. Function: Through the 22 service, the diagnostic tool can send a request to the ECU to obtain the data value recorded by a specific data identifier (DID). DID is used to uniquely identify specific data items in the ECU, such as version information, vehicle mileage, diagnostic-related data, etc.

[0038] The 19 service in vehicle diagnostics, also known as the ReadDTCInformation service, is an important service defined in the ISO 14229 (also known as UDS, unified diagnostic service) standard. The 19 service allows a client (such as a diagnostic instrument) to read the status of diagnostic trouble code (DTC) information stored in a server (such as an ECU). These DTC information can be information in one or a group of servers on the vehicle, including emission-related and non-emission-related information.

[0039] DTC (Diagnostic Trouble Code) means diagnostic trouble code, which is a digital identifier of a car fault, used to help maintenance personnel quickly locate vehicle problems.

[0040] Diagnostic middleware is an important component of the vehicle diagnostic system. It is located between the underlying software (such as operating system, driver, etc.) of the ECU (electronic control unit) and the upper-level diagnostic application. The main function of the middleware is to provide a unified interface and standard so that the upper-level diagnostic application can easily communicate and exchange data with the underlying ECU.

[0041] The concept of vehicle log level mainly stems from the need to classify and record various information generated during vehicle operation. These log information are of great significance for monitoring vehicle status data, troubleshooting, and optimizing performance.

[0042] 31 diagnostic process instructions, namely RoutineControl (0x31) service in UDS (Unified Diagnostic Services), also known as routine control service. This is a service used to execute a series of operation sequences, allowing the diagnostic instrument to send diagnostic commands to the ECU (Engine Control Unit) to start or stop the execution of a program, or request the results of the routine execution.

[0043] In the related art, fault detection of various parts in a vehicle is usually carried out by users going to a specific location to perform fault detection or repair when the fault affects the user's normal use of certain functions of the vehicle or affects the user's use of the vehicle. This makes fault detection of the vehicle inefficient.

[0044] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0045] Figure 1aA schematic structural diagram of a system provided for an exemplary embodiment of the present application, the system comprising a vehicle and a target device, wherein a vehicle detection system may be deployed in the vehicle.

[0046] Figure 1b A structural diagram of a vehicle detection system provided for an exemplary embodiment of the present application, the system includes: SOC and MCU, wherein the SOC has a master intelligent diagnosis middleware built in, and the MCU has a slave intelligent diagnosis middleware built in; wherein the master intelligent diagnosis middleware can interact with multiple applications deployed in the SOC, and the slave intelligent diagnosis middleware can interact with multiple SWCs deployed in the MCU. The master intelligent diagnosis middleware can also interact with multiple ECUs, and the multiple ECUs can refer to Figure 1b The intelligent diagnostic middleware can also interact with multiple ECUs, which can refer to M-ECU1, M-ECU2, and M-ECU3. Figure 1b S-ECU1 and S-ECU2 in it.

[0047] Optionally, the vehicle detection system may specifically be a domain controller.

[0048] The execution principles and interaction processes of the various component units in the system embodiment, such as the master intelligent diagnosis middleware and the slave intelligent diagnosis middleware, can be found in the description of the following method embodiments.

[0049] Figure 2 The flowchart of a vehicle detection method provided by an exemplary embodiment of the present application is shown in FIG. 1 , wherein the execution subject of the method may be a first diagnostic unit in the SOC. Optionally, the first diagnostic unit may be Figure 1b The main intelligent diagnosis middleware in the method at least comprises the following steps S201-S204:

[0050] S201, sending at least one first diagnostic request to at least one first operating unit in a vehicle;

[0051] Optionally, the first operating unit may be an application or ECU that can interact with the first diagnostic unit. Specifically, when the first diagnostic unit is the main intelligent diagnostic middleware in the SOC, Figure 1b Applications such as APP1 and APP2 that can interact with the main intelligent diagnostic middleware, as well as ECUs such as M-ECU1 and M-ECU2 that can interact with the main intelligent diagnostic middleware, can all be the first operating units.

[0052] Optionally, each first operating unit may be connected to the first diagnosis unit via a network.

[0053] S202, receiving at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request;

[0054] The first operating unit corresponds to the first diagnostic information one by one, and the first diagnostic information of the first operating unit may include the operating status and / or operating data of the first operating unit. The operating status may include identification information indicating whether the first operating unit is operating normally. The operating data may include an operating log within a preset time period.

[0055] Optionally, when the first operating unit fails, the first diagnostic information of the first operating unit may further include a fault code of the first operating unit.

[0056] S203, generating a diagnosis report based on the at least one first diagnosis information;

[0057] Optionally, generating a diagnostic report based on the at least one first diagnostic information includes: using the at least one first diagnostic information as the diagnostic report.

[0058] Optionally, generating a diagnostic report based on the at least one first diagnostic information includes: taking at least one second diagnostic information in the at least one first diagnostic information indicating that a corresponding first operating unit has a fault as the diagnostic report.

[0059] S204: Send the diagnostic report to the target device.

[0060] Optionally, the target device may refer to a terminal device of a vehicle inspection center, wherein the vehicle inspection center may be a 4S store.

[0061] In some optional embodiments of the present application, in S203, generating a diagnostic report based on the at least one first diagnostic information includes the following steps S2031-S2033:

[0062] S2031. When the at least one first diagnostic information indicates that there is at least one second operating unit in the at least one first operating unit that has a fault, send at least one second diagnostic request to the at least one second operating unit; wherein the aforementioned second operating unit refers to the first operating unit that has a fault.

[0063] Optionally, for the same first operating unit, the second diagnostic request can be used to request more detailed data relative to the first diagnostic request, for example, more detailed operating data of the first operating unit can be obtained through the second diagnostic request.

[0064] Optionally, when the first diagnostic information of the first operating unit contains a DTC fault code, it is determined that a fault exists in the first operating unit.

[0065] S2032, receiving at least one second diagnostic information fed back by the at least one second operating unit based on the at least one second diagnostic request;

[0066] The second diagnostic information may include the operating status and / or operating data of the second operating unit. The operating status may include identification information indicating whether the second operating unit is operating normally. The operating data may include operating logs within a preset time period.

[0067] S2033. Generate a diagnosis report based on the at least one second diagnosis information.

[0068] Optionally, when the second diagnostic information includes an operation log, generating a diagnostic report based on the at least one second diagnostic information may include: obtaining a preset log level; and generating a diagnostic report based on the second diagnostic information containing log data having a log level of the preset log level.

[0069] Optionally, generating a diagnostic report based on second diagnostic information containing log data having a log level of the preset log level may include: using the second diagnostic information containing log data having a log level of the preset log level as the diagnostic report.

[0070] In some optional embodiments of the present application, the method further includes the following steps S1-S2:

[0071] S1. Sending a diagnosis assistance instruction to a second diagnosis unit, so that the second diagnosis unit diagnoses at least one third operating unit in the vehicle based on the diagnosis assistance instruction;

[0072] The first diagnostic unit and the second diagnostic unit may be connected via a network.

[0073] The second diagnosis unit is connected to at least some of the at least one third operating unit via a CAN bus.

[0074] Optionally, the second diagnostic unit may be Figure 1b From the intelligent diagnosis middleware.

[0075] Optionally, Figure 1b Applications such as SWC1 and SWC2 that can interact with the slave intelligent diagnostic middleware, and ECUs such as S-ECU1 and S-ECU2 that can interact with the slave intelligent diagnostic middleware can all be third operating units.

[0076] Optionally, each M-ECU may be connected to the main intelligent diagnosis middleware via a network connection.

[0077] The connection mode between the master intelligent diagnosis middleware and the slave intelligent diagnosis middleware may be a network connection.

[0078] The slave intelligent diagnosis middleware is connected to at least part of the at least one third operating unit via a CAN bus.

[0079] The solution in the present application can diagnose the third operating unit that is not connected to the main intelligent diagnosis middleware through the introduction of the slave intelligent diagnosis middleware.

[0080] S2, receiving at least one third diagnostic information corresponding to the diagnosis auxiliary instruction fed back by the second diagnostic unit;

[0081] Among them, the third operating unit corresponds one to one to the third diagnostic information.

[0082] The third diagnostic information of the third operation unit may include the operation status and / or operation data of the third operation unit, wherein the operation status may include identification information indicating whether the third operation unit operates normally, and the operation data may include operation logs within a preset time period.

[0083] Generating a diagnostic report based on the at least one first diagnostic information includes: generating a diagnostic report based on the at least one first diagnostic information and the at least one third diagnostic information.

[0084] Optionally, generating a diagnostic report based on the at least one first diagnostic information and the at least one third diagnostic information includes: using the at least one first diagnostic information and the at least one third diagnostic information as the diagnostic report.

[0085] In some optional embodiments of the present application, the method further includes: for each second operating unit in the at least one second operating unit, acquiring vehicle status data related to the second operating unit to obtain at least one set of vehicle status data;

[0086] The vehicle status data related to the second operating unit may refer to the vehicle status data of the operating unit related to the operation of the second operating unit.

[0087] Optionally, the vehicle status data of the operating unit related to the operation of the second operating unit may refer to freeze frame (snapshot) data of the operating unit related to the operation of the second operating unit, and the operation log of the operating unit related to the operation of the second operating unit (operation log within a preset time period).

[0088] The aforementioned generating a diagnostic report based on the at least one second diagnostic information includes: generating a diagnostic report based on the at least one second diagnostic information and the at least one set of vehicle status data.

[0089] Optionally, generating a diagnostic report based on the at least one second diagnostic information and the at least one set of vehicle status data includes: using the at least one second diagnostic information and the at least one set of vehicle status data as a diagnostic report.

[0090] In some optional embodiments of the present application, each first diagnostic information includes a target identification number of a corresponding first operating unit, and the method further includes: obtaining at least one existing identification number corresponding to the at least one first operating unit stored locally;

[0091] Optionally, the first operating unit corresponds one-to-one to the existing identification number.

[0092] The existing identification number corresponding to the first operating unit in the present application may refer to a pre-stored part number and / or software / hardware version number of the first operating unit.

[0093] Generating a diagnostic report based on the at least one first diagnostic information includes: generating a diagnostic report based on the at least one existing identification number and at least one target identification number of the at least one first operating unit.

[0094] The target identification number of the first operating unit refers to the part number and / or software / hardware version number of the first operating unit in the acquired first diagnostic information.

[0095] Optionally, generating a diagnostic report based on the at least one existing identification number and the at least one target identification number of the at least one first operating unit includes: using the at least one existing identification number and the at least one target identification number of the at least one first operating unit as the diagnostic report.

[0096] In some optional embodiments of the present application, the method further includes the following steps S21-S22:

[0097] S21, obtaining a feedback result of the target device with respect to the diagnostic report;

[0098] Optionally, the target device may determine a feedback result based on the acquired diagnostic report, wherein the feedback result may include at least one of the following information: a faulty operating unit, a cause of the fault, and a corresponding fault solution.

[0099] In some optional embodiments of the present application, after obtaining a detection report including at least one existing identification number and at least one target identification number, the aforementioned target device is further used to: determine a feedback result based on the diagnostic report. Optionally, when the target device is used to determine a feedback result based on the diagnostic report, it is specifically used to: determine at least one pending identification number among the at least one existing identification number that is different from the corresponding target identification number based on at least one existing identification number and at least one target identification number; obtain an adjustment instruction input by a relevant person for the at least one pending identification number; and generate a feedback result based on the adjustment instruction.

[0100] Optionally, the aforementioned adjustment instruction may be an upgrade or update instruction for the operating units corresponding to at least some of the at least one pending identification number.

[0101] Optionally, generating the feedback result based on the adjustment instruction may include: using the adjustment instruction as the feedback result.

[0102] S22. Execute corresponding tasks based on the feedback results.

[0103] When the feedback result is an instruction, executing the corresponding task based on the feedback result refers to executing the instruction indicated by the feedback result.

[0104] Optionally, the task corresponding to the feedback result may be shutting down the operating unit where the fault occurs, or displaying the feedback result.

[0105] In some optional embodiments of the present application, the method further includes the following steps S23-S24:

[0106] S23, obtaining a feedback result of the target device with respect to the diagnostic report;

[0107] Optionally, the feedback result may include at least one of the following information: the operating unit where the fault occurs, the cause of the fault, and a corresponding fault solution.

[0108] S24. Display the feedback result.

[0109] The feedback result may include fault prompt information, and the fault prompt information may include any one or more of the following: relevant information for prompting the second operating unit where the fault occurs, and information for prompting the severity of the fault and the method for handling the fault.

[0110] Optionally, the severity of the fault and the method for handling the fault may include: for a minor fault, it is recommended that the owner drive to a 4S shop for inspection; for a serious fault, it is recommended that the owner immediately pull over to the side of the road, etc. For example, for a minor fault, it is recommended that the owner go to a 4S shop to inflate the left front tire.

[0111] In this application, the main intelligent diagnosis middleware is deployed in the SOC, responsible for vehicle health scanning, vehicle data collection, fault analysis, report generation, data center notification, and execution of vehicle detection tasks issued by the target device. The slave intelligent diagnosis middleware is deployed in the MCU, responsible for forwarding the health scan data of the main intelligent diagnosis middleware, collecting data from the MCU and ECUs connected to the MCU, and reporting the data to the main intelligent diagnosis middleware.

[0112] Optionally, in the present application, the first diagnostic unit in the SOC may execute the vehicle detection method of the present application according to a preset detection cycle.

[0113] Optionally, the detection of the aforementioned identification number can be achieved through the 22 service.

[0114] Optionally, the acquisition of the aforementioned fault code can be achieved through service 19.

[0115] In some optional embodiments of the present application, the fault in the present application may be a fault such as a left front tire pressure being too low, an abnormal air conditioning shutdown, or the like.

[0116] Among them, the second diagnostic request in this application is used to retest the fault. For example, when the first diagnostic information indicates a low left front tire pressure fault, the second diagnostic request can be used to retest the fault (such as sending a 31 diagnostic process instruction to test whether the tire pressure sensor can work normally).

[0117] The solution of this application can automatically detect problems through health scanning; it can automatically collect problem data, automatically generate analysis reports, and notify the upper level; it can also automatically perform problem tests based on the analysis reports to improve the accuracy of problem analysis. The solution of this application can automatically scan vehicles, automatically collect data, automatically analyze faults, and automatically perform fault tests; it can play the role of fault warning, and can quickly and automatically locate the cause of the fault.

[0118] The method for the first diagnostic unit in the SOC provided by the present application includes: sending at least one first diagnostic request to at least one first operating unit in the vehicle; receiving at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request; generating a diagnostic report based on the at least one first diagnostic information; and sending the diagnostic report to a target device. The solution of the present application can automatically perform fault detection on each first operating unit connected to the first diagnostic unit, thereby improving the efficiency of fault detection on the vehicle.

[0119] Figure 3 A schematic diagram of the structure of a vehicle detection device provided by an exemplary embodiment of the present application, the device is applicable to a first diagnostic unit in a SOC, and includes:

[0120] A sending unit 31, configured to send at least one first diagnostic request to at least one first operating unit in the vehicle;

[0121] A receiving unit 32, configured to receive at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request;

[0122] A generating unit 33, configured to generate a diagnostic report based on the at least one first diagnostic information;

[0123] The sending unit 31 is further configured to send the diagnosis report to a target device.

[0124] In some optional embodiments of the present application, when the aforementioned apparatus is used to generate a diagnostic report based on the at least one first diagnostic information, it is specifically used to:

[0125] When the at least one first diagnostic information indicates that there is at least one second operating unit in the at least one first operating unit that has a fault, sending at least one second diagnostic request to the at least one second operating unit;

[0126] receiving at least one second diagnostic information fed back by the at least one second operating unit based on the at least one second diagnostic request;

[0127] A diagnosis report is generated based on the at least one second diagnosis information.

[0128] In some optional embodiments of the present application, the device is also used for:

[0129] sending a diagnosis assistance instruction to a second diagnosis unit, so that the second diagnosis unit diagnoses at least one third operating unit in the vehicle based on the diagnosis assistance instruction;

[0130] receiving at least one third diagnostic information corresponding to the diagnosis auxiliary instruction fed back by the second diagnostic unit;

[0131] Generating a diagnostic report based on the at least one first diagnostic information includes: generating a diagnostic report based on the at least one first diagnostic information and the at least one third diagnostic information.

[0132] In some optional embodiments of the present application, the device is also used for:

[0133] For each second operating unit in the at least one second operating unit, acquiring vehicle status data related to the second operating unit to obtain at least one set of vehicle status data;

[0134] The generating a diagnostic report based on the at least one second diagnostic information comprises: generating a diagnostic report based on the at least one second diagnostic information and the at least one set of vehicle status data.

[0135] In some optional embodiments of the present application, each piece of first diagnostic information includes a target identification number of a corresponding first operating unit, and the device is further configured to:

[0136] Obtaining at least one existing identification number corresponding to the at least one first operating unit stored locally;

[0137] Generating a diagnostic report based on the at least one first diagnostic information includes: generating a diagnostic report based on the at least one existing identification number and at least one target identification number of the at least one first operating unit.

[0138] In some optional embodiments of the present application, the device is also used for:

[0139] Obtaining a feedback result of the target device with respect to the diagnostic report;

[0140] Execute corresponding tasks based on the feedback results.

[0141] In some optional embodiments of the present application, the device is also used for:

[0142] Obtaining a feedback result of the target device with respect to the diagnostic report;

[0143] The feedback result is displayed.

[0144] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, no further description is given here. Specifically, the device may perform the above method embodiment, and the above and other operations and / or functions of each module in the device are the corresponding processes in each method in the above method embodiment, respectively, and no further description is given here for the sake of brevity.

[0145] The above describes the device of the embodiment of the present application from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.

[0146] Figure 4 is a schematic block diagram of an electronic device provided in an embodiment of the present application, and the electronic device may include:

[0147] The memory 301 and the processor 302, the memory 301 is used to store the computer program and transmit the program code to the processor 302. In other words, the processor 302 can call and run the computer program from the memory 301 to implement the method in the embodiment of the present application.

[0148] For example, the processor 302 may be configured to execute the above method embodiments according to instructions in the computer program.

[0149] In some embodiments of the present application, the processor 302 may include but is not limited to:

[0150] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0151] In some embodiments of the present application, the memory 301 includes but is not limited to:

[0152] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0153] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 301 and executed by the processor 302 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0154] like Figure 4 As shown, the electronic device may also include:

[0155] The transceiver 303 may be connected to the processor 302 or the memory 301 .

[0156] The processor 302 may control the transceiver 303 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 303 may include a transmitter and a receiver. The transceiver 303 may further include an antenna, and the number of antennas may be one or more.

[0157] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0158] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a computer, the computer can perform the method of the above method embodiment. In other words, the present application embodiment also provides a computer program product containing instructions, and when the instructions are executed by a computer, the computer can perform the method of the above method embodiment.

[0159] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state disk, SSD)), etc.

[0160] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0161] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0162] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

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

Claims

1. A vehicle detection method, characterized in that: Suitable for the first diagnostic unit in the SOC, including: sending at least one first diagnostic request to at least one first operating unit in the vehicle; receiving at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request; generating a diagnostic report based on the at least one first diagnostic information; The diagnostic report is sent to the target device.

2. The method according to claim 1, characterized in that The generating a diagnostic report based on the at least one first diagnostic information comprises: When the at least one first diagnostic information indicates that there is at least one second operating unit in the at least one first operating unit that has a fault, sending at least one second diagnostic request to the at least one second operating unit, the second operating unit being the first operating unit that has a fault; receiving at least one second diagnostic information fed back by the at least one second operating unit based on the at least one second diagnostic request; A diagnosis report is generated based on the at least one second diagnosis information.

3. The method according to claim 1, characterized in that The method further comprises: sending a diagnosis assistance instruction to a second diagnosis unit, so that the second diagnosis unit diagnoses at least one third operating unit in the vehicle based on the diagnosis assistance instruction; receiving at least one third diagnostic information corresponding to the diagnosis auxiliary instruction fed back by the second diagnostic unit; Generating a diagnostic report based on the at least one first diagnostic information includes: generating a diagnostic report based on the at least one first diagnostic information and the at least one third diagnostic information.

4. The method according to claim 2, characterized in that: The method further comprises: For each second operating unit in the at least one second operating unit, acquiring vehicle status data related to the second operating unit to obtain at least one set of vehicle status data; The generating a diagnostic report based on the at least one second diagnostic information comprises: generating a diagnostic report based on the at least one second diagnostic information and the at least one set of vehicle status data.

5. The method according to claim 1, characterized in that Each first diagnostic information includes a target identification number of a corresponding first operating unit, and the method further includes: Obtaining at least one existing identification number corresponding to the at least one first operating unit stored locally; Generating a diagnostic report based on the at least one first diagnostic information includes: generating a diagnostic report based on the at least one existing identification number and at least one target identification number of the at least one first operating unit.

6. The method according to claim 1, characterized in that The method further comprises: Obtaining a feedback result of the target device with respect to the diagnostic report; Execute corresponding tasks based on the feedback results.

7. The method according to claim 1, characterized in that The method further comprises: Obtaining a feedback result of the target device with respect to the diagnostic report; The feedback result is displayed.

8. A vehicle detection device, characterized in that: Suitable for the first diagnostic unit in the SOC, including: a sending unit, configured to send at least one first diagnostic request to at least one first operating unit in the vehicle; a receiving unit, configured to receive at least one first diagnostic information fed back by the at least one first operating unit based on the at least one first diagnostic request; A generating unit, configured to generate a diagnostic report based on the at least one first diagnostic information; The sending unit is further used to send the diagnosis report to the target device.

9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 7 by executing the executable instructions.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images