A vehicle detection method and apparatus

Abstract

This invention provides a vehicle inspection method and apparatus, relating to the field of vehicle inspection technology. The vehicle inspection method includes: acquiring inspection task configuration information for vehicle function inspection; verifying the operating status of the vehicle to be inspected based on the inspection task configuration information; after the operating status of the vehicle to be inspected passes the verification, accessing the vehicle attributes of the vehicle to be inspected through a vehicle attribute management interface to obtain vehicle function inspection results, and obtaining diagnostic information of the vehicle to be inspected through a diagnostic protocol middleware; and generating vehicle function inspection result data based on the vehicle function inspection results and the diagnostic information. This invention achieves a complete closed loop for vehicle function inspection from task distribution to result generation, enabling unified management of the vehicle inspection process, avoiding manual intervention, and is applicable to the inspection of different vehicles, thereby improving the efficiency and applicability of vehicle function inspection.

Description

Technical Field

[0001] This invention relates to the field of vehicle inspection technology, and more specifically, to a vehicle inspection method and apparatus. Background Technology

[0002] With the rapid development of intelligent vehicles and vehicle networking technology, the functional complexity of in-vehicle electronic systems is constantly increasing. In scenarios such as factory testing, quality inspection, after-sales maintenance and remote operation and maintenance, the demand for vehicle functional status detection and fault diagnosis is growing. How to efficiently and accurately obtain various functional status and fault information of vehicles while ensuring safety has become an urgent technical problem to be solved in the field of in-vehicle systems.

[0003] In related technologies, vehicle function testing mainly relies on manual inspection, where inspectors operate and confirm vehicle functions one by one through the central control system or external devices. This method is not only inefficient and time-consuming, but also highly dependent on the experience of the inspectors, which can easily lead to inconsistent test results due to differences in human operation. Furthermore, when a vehicle has fault codes, it is usually necessary to use professional diagnostic tools to communicate with the vehicle's electronic control unit through diagnostic protocols in order to obtain relevant fault information. The operation process is complex and the equipment cost is high, making it difficult to meet the needs of large-scale, standardized testing. Summary of the Invention

[0004] The problem addressed by this invention is how to improve the efficiency and applicability of vehicle inspection.

[0005] To address the above problems, the present invention provides a vehicle detection method and apparatus.

[0006] In a first aspect, the present invention provides a vehicle detection method, comprising: Obtain the detection task configuration information for vehicle function detection, and verify the operating status of the vehicle to be tested according to the detection task configuration information; Once the operating status of the vehicle under test passes the verification, the vehicle attributes of the vehicle under test are accessed through the vehicle attribute management interface to obtain the vehicle function test results, and the diagnostic information of the vehicle under test is obtained through the diagnostic protocol middleware. Vehicle function test result data is generated based on the vehicle function test results and the diagnostic information.

[0007] Optionally, obtaining the detection task configuration information for vehicle function detection includes: After the vehicle-mounted detection application is started, the background execution mechanism retrieves the detection task configuration information from the cloud server according to a preset strategy. After obtaining the detection task configuration information for vehicle function detection, the vehicle detection method further includes: The detection logic description data in the detection task configuration information is parsed, and an executable detection file for vehicle function detection is generated on the vehicle terminal based on the parsing results.

[0008] Optionally, after obtaining the detection task configuration information for vehicle function detection, the vehicle detection method further includes: The interface description data in the detection task configuration information is parsed to generate an operation interface for vehicle function detection on the vehicle terminal. The interactive operations in the user interface are associated with the executable detection file to trigger the corresponding vehicle function detection when a user operation is received.

[0009] Optionally, the step of verifying the operating status of the vehicle to be tested according to the detection task configuration information includes: Based on the detection task configuration information, at least one operating status parameter of the vehicle to be detected is obtained through the vehicle attribute management interface; The operating status parameters are compared with preset detection execution conditions to determine whether the vehicle under test meets the execution requirements of vehicle function detection.

[0010] Optionally, accessing the vehicle attributes of the vehicle to be tested through the vehicle attribute management interface to obtain the vehicle function test results includes: Based on preset vehicle attribute mapping rules, the vehicle attribute identifiers used in the detection task are converted into the vehicle attribute identifiers corresponding to the vehicle to be detected. The detection task configuration information is used to configure and describe the detection task. Based on the converted vehicle attribute identifier, the corresponding vehicle attributes are set or obtained through the vehicle attribute management interface, and the return value or execution status of the vehicle attributes is analyzed to determine the vehicle function detection result.

[0011] Optionally, obtaining the diagnostic information of the vehicle to be tested through the diagnostic protocol middleware includes: A diagnostic communication connection is established between the diagnostic protocol middleware and at least one electronic control unit of the vehicle under test. Based on the diagnostic communication connection, the diagnostic information of the vehicle under test is obtained, including vehicle fault code information and / or electronic control unit status information related to vehicle functions.

[0012] Optionally, generating vehicle function test result data based on the vehicle function test results and the diagnostic information includes: Based on the vehicle function test results and the diagnostic information, test result data is generated to characterize the functional status and fault status of the vehicle under test; The test results data are reported to the cloud server for processing, and the vehicle function test results data returned by the cloud server are received.

[0013] Optionally, the vehicle detection method further includes: determining the corresponding vehicle attribute definition and diagnostic strategy based on the vehicle model information of the vehicle to be detected, and performing corresponding vehicle function detection based on the vehicle attribute definition and the diagnostic strategy.

[0014] Optionally, the vehicle detection method further includes: uploading vehicle bus communication signal data during the detection phase to a cloud server, wherein the cloud server is used to perform statistical analysis on the vehicle bus communication signal data to determine the response of the vehicle controller to the vehicle function detection task, and to generate corresponding vehicle function detection result data based on the statistical analysis results.

[0015] In a second aspect, the present invention provides a vehicle detection device, comprising: The first module is used to obtain the detection task configuration information for vehicle function detection, and to verify the operating status of the vehicle to be tested according to the detection task configuration information. The second module is used to access the vehicle attributes of the vehicle under test through the vehicle attribute management interface to obtain the vehicle function test results after the operating status of the vehicle under test passes the verification, and to obtain the diagnostic information of the vehicle under test through the diagnostic protocol middleware. The third module is used to generate vehicle function test result data based on the vehicle function test results and the diagnostic information.

[0016] The beneficial effects of the vehicle detection method of the present invention are as follows: by acquiring the task configuration information of vehicle function detection and verifying the operating status of the vehicle to be detected based on the configuration information, the safety of vehicle operation can be taken into account, ensuring that the detection operation is carried out under the premise that the vehicle status meets the requirements. Then, by accessing the vehicle attributes and diagnostic information, the vehicle function detection results are generated, realizing a complete closed loop of vehicle function detection from task distribution to result generation. It can uniformly manage the vehicle detection process, avoid manual intervention, and is applicable to the detection of different vehicles, thereby improving the efficiency and applicability of vehicle function detection. Attached Figure Description

[0017] Figure 1 This is a schematic flowchart of a vehicle detection method according to an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the principle of the vehicle detection method according to an embodiment of the present invention; Figure 3This is a schematic diagram of the process for obtaining detection task configuration information according to an embodiment of the present invention. Figure 1 ; Figure 4 This is a schematic diagram of the process for obtaining detection task configuration information according to an embodiment of the present invention. Figure 2 ; Figure 5 This is a schematic diagram of the running status verification process according to an embodiment of the present invention; Figure 6 This is a schematic diagram of the process for obtaining vehicle function test results according to an embodiment of the present invention; Figure 7 This is a schematic diagram of the process for obtaining diagnostic information according to an embodiment of the present invention; Figure 8 This is a schematic diagram of the process for generating vehicle function test result data according to an embodiment of the present invention; Figure 9 This is a system architecture diagram of the vehicle detection device according to an embodiment of the present invention; Figure 10 This is a system architecture diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0018] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present invention. It should be understood that the accompanying drawings and embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of protection of the present invention.

[0019] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0020] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to"; the term "based on" means "at least partially based on"; the term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments"; and the term "optionally" means "optional embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first," "second," etc., mentioned in this invention are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0021] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0022] The names of the messages or information exchanged between the multiple devices in the embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0023] like Figure 1 As shown, an embodiment of the present invention provides a vehicle detection method, comprising: S100: Obtain the detection task configuration information for vehicle function detection, and verify the operating status of the vehicle to be tested according to the detection task configuration information.

[0024] Specifically, the system obtains the detection task configuration information for vehicle function testing. This information can be uniformly distributed by the cloud server and describes the detection items, detection logic, detection conditions, and detection parameters related to vehicle functions to be executed in this vehicle test. After obtaining the detection task configuration information, the system verifies the operating status of the vehicle to be tested based on the information to determine whether the execution conditions of the detection task are met. The detection task can be pre-configured with operating conditions such as the vehicle being in a parked state, the doors being closed, or the battery level meeting a preset threshold.

[0025] S200: After the operating status of the vehicle under test passes the verification, the vehicle attributes of the vehicle under test are accessed through the vehicle attribute management interface to obtain the vehicle function test results, and the diagnostic information of the vehicle under test is obtained through the diagnostic protocol middleware.

[0026] Specifically, once the operating status of the vehicle under test is verified, the vehicle attributes of the vehicle under test are accessed (e.g., read, write, or listen) through the vehicle attribute management interface to perform vehicle function testing and obtain the vehicle function testing results. At the same time, the vehicle electronic control unit is communicated through the diagnostic protocol middleware (e.g., the middleware corresponding to UDS, UDS stands for Unified Diagnostic Services) to obtain the diagnostic information of the vehicle under test. For example, through the encapsulated UDS method, the attributes of some ECUs and the vehicle's DTC (Diagnostic Trouble Code) fault information are called to obtain the fault code information of the whole vehicle or each subsystem.

[0027] Among them, combined Figure 2As shown, the in-vehicle application (vehicle app) in this application is an application layer program that runs on the in-vehicle terminal. It communicates with the vehicle diagnostic middleware by calling the API interface provided by the vehicle system to realize vehicle attribute access, diagnostic information acquisition and vehicle function detection.

[0028] Among them, the vehicle attribute management interface is an intermediate layer interface used to access the underlying functions of the vehicle. Car Property Manager can be used. As a core system service interface in Android Automotive OS (AAOS for short, Android vehicle operating system), Car Property Manager is a key intermediate layer component connecting in-vehicle applications and vehicle hardware. It is used to enable in-vehicle applications to securely and uniformly access the underlying attributes of the vehicle. It can perform standardized reading, listening and setting of the underlying state and control items of the vehicle at the application layer.

[0029] Vehicle attributes are abstract descriptions of vehicle status or control items, which typically include vehicle speed, gear position, air conditioning temperature, door lock status, battery level, and seat position. Each vehicle attribute has a corresponding data type (e.g., int), scope (e.g., left door, right door), and read / write permissions.

[0030] S300: Generate vehicle function test result data based on the vehicle function test results and the diagnostic information.

[0031] Specifically, after completing vehicle function testing and obtaining diagnostic information, vehicle function testing result data is generated based on the vehicle function testing results and diagnostic information. The vehicle function testing result data is used to comprehensively reflect the functional status and fault status of the vehicle, and can be further used for storage, reporting or display.

[0032] In this embodiment, by acquiring the task configuration information for vehicle function testing and verifying the operating status of the vehicle to be tested based on the configuration information, the safety of vehicle operation can be taken into account, ensuring that the testing operation is performed under the premise that the vehicle status meets the requirements. Then, the vehicle attributes and diagnostic information are accessed to generate the vehicle function testing results, realizing a complete closed loop of vehicle function testing from task distribution to result generation. This allows for unified management of the vehicle testing process, avoids manual intervention, and is applicable to testing different vehicles, thereby improving the efficiency and applicability of vehicle function testing.

[0033] Optionally, obtaining the detection task configuration information for vehicle function detection includes: S110: After the vehicle detection application is started, the detection task configuration information is obtained from the cloud server according to the preset strategy through the background execution mechanism.

[0034] Specifically, in combination Figure 3As shown, after the vehicle-mounted detection application (vehicle-side app) is launched, a background detection process is initiated through a background execution mechanism. This background execution mechanism can include a timed trigger mechanism, an event trigger mechanism, or a combination of both, such as combining... Figure 2 As shown, based on the heartbeat mechanism, a timer (e.g., via Alam Helper) can periodically send data to a cloud server (e.g., via a preset time interval, e.g., every 5 minutes) at a set interval. Figure 2 The cloud-based backend (HTTP backend) requests the latest detection task configuration information.

[0035] After obtaining the detection task configuration information for vehicle function detection, the vehicle detection method further includes: S120: Parse the detection logic description data in the detection task configuration information, and generate an executable detection file for vehicle function detection on the vehicle terminal based on the parsing result.

[0036] Specifically, after obtaining the detection task configuration information from the cloud server, the detection logic description data in the configuration information is parsed. This data describes the execution rules, steps, and methods of the vehicle detection task and can exist in script, bytecode, or other structured forms. It typically includes task identifier, task name, execution conditions, and detection steps. Based on the parsing results, an executable detection file for vehicle function detection is generated so that the corresponding vehicle function detection logic can be executed subsequently based on user operations or system triggers. For example, if the data returned by the cloud server contains a ClassValue field (the encoding and encapsulation form of the detection logic description data), it is first converted into binary byte data using Base64 encoding, and then written into a .dex file (an executable file that can be loaded at the Android runtime). The dalvik.system.DexHelper utility class (Dex DynamicLoading Helper) is used to load the file, generating an executable .Class file (a Java Class object that can call methods via reflection) as the executable detection file.

[0037] In this optional embodiment, after the vehicle application starts, the task configuration information is obtained through the background mechanism, and the detection logic description data is parsed to generate an executable file, enabling the vehicle detection task to be dynamically updated and deployed, improving the flexibility and scalability of the detection task, while ensuring the secure execution and immediacy of the vehicle detection logic on the vehicle terminal, which is conducive to adapting to changes in different vehicle models and detection needs.

[0038] Optionally, after obtaining the detection task configuration information for vehicle function detection, the vehicle detection method further includes: S130: Parse the interface description data in the detection task configuration information to generate an operation interface for vehicle function detection on the vehicle terminal.

[0039] Specifically, in combination Figure 4 As shown, the detection task configuration information can also include interface description data to describe the detection operation interface. The interface description data is parsed, and based on the view type, view identifier, position parameters, and size parameters defined in the interface description data (such as data represented by the UIJson field), an operation interface for vehicle function detection is generated on the vehicle terminal. For example, the UIJson field (User Interface JSON, user interface description data; JSON stands for JavaScript Object Notation, a lightweight structured data format) is encoded and parsed. First, the aspect ratio conversion value of width and height is calculated (scaling is done according to the actual screen resolution). Then, the view ID and view type are read, corresponding to the original Android native component. The component is set in the layout size and position, and then rendered onto the layout canvas for user operation.

[0040] Specifically, for the `initUi` (Initialize User Interface) key (a key in a JSON array used to identify data used to initialize the user interface) identified in the `UIJson` field, the value content (a list of controls that need to be generated in the application interface) can be transformed into a list, converting child elements into corresponding view objects. For example, based on the `type`, it can be converted into different native view components, including `TextView` (a text view used to display text, such as titles, descriptions, etc.), `Button` (a button that can be clicked to perform operations, such as submit, cancel, next step, etc.), `listView` (a list view used to display a scrollable list of items, such as a task list or a list of test results), and `ImageView` (an image view used to display images or icons, such as vehicle status icons, marker images, etc.). Based on the `position` and `size` values, the elements are positioned and displayed in the canvas. The `ID` (name) can be used to generate internal references. The `click Method Name` field can be used to reflectively call the method in the script's `Dex` object and call the method to achieve the click event.

[0041] S140: Associate the interactive operations in the operation interface with the executable detection file to trigger the corresponding vehicle function detection when a user operation is received.

[0042] Specifically, after generating the operation interface, the interactive operations in the operation interface are associated with the aforementioned executable detection file. For example, when there is a detection button in the operation interface, the click operation of the button can be bound to the corresponding detection logic. When the user's interactive operation is received on the operation interface, the vehicle function detection logic corresponding to the interactive operation is triggered.

[0043] In this optional embodiment, an operation interface is generated by parsing the interface description data in the detection task configuration, and the user operation is associated with the executable detection file. This allows vehicle function detection to be triggered through intuitive interaction, and operators can directly execute detection tasks through a visual interface. At the same time, it avoids misoperation caused by the separation of operation logic and interface, and improves the accuracy and convenience of detection task execution.

[0044] Optionally, the step of verifying the operating status of the vehicle to be tested according to the detection task configuration information includes: S150: Based on the detection task configuration information, obtain at least one operating status parameter of the vehicle to be detected through the vehicle attribute management interface.

[0045] Specifically, in combination Figure 5 As shown, based on the detection logic description data in the detection task configuration information (the interface description data is mainly used for interface display and user interaction, and is usually not directly used to obtain operating status parameters), at least one operating status parameter of the vehicle to be detected is obtained through the vehicle attribute management interface. The operating status parameter may include vehicle door status, vehicle working mode, vehicle battery status, parking status, etc.

[0046] S160: Compare the operating status parameters with the preset detection execution conditions to determine whether the vehicle to be tested meets the execution requirements of vehicle function detection.

[0047] Specifically, the obtained operating status parameters are compared with the preset detection execution conditions in the detection task configuration information. If the operating status parameters meet the detection execution conditions, such as the doors being closed, the battery being fully charged, the vehicle being parked, and the engine being off, then the vehicle under test is determined to meet the execution requirements for vehicle function detection. Otherwise, it is determined that the current detection execution requirements are not met, and the detection process can be terminated or the user can be prompted to adjust the vehicle status. For example, after instantiating the Car class in the API (Application Programming Interface) and establishing a connection and communication with the DHU Framework (DHU stands for Desktop Head Unit, the desktop vehicle simulation / communication framework in Android Automotive development), the diagnostic middleware is used to verify and judge the status (doors, vehicle mode, battery level, etc.) of the vehicle under test to ensure that the vehicle under test meets the execution requirements.

[0048] In this optional embodiment, based on the detection task configuration, the running status parameters are obtained through the vehicle attribute management interface and compared with preset conditions to ensure that the task is executed only after the vehicle meets the detection requirements. This can effectively avoid the risk of executing detection tasks under unsafe or abnormal vehicle conditions, improve the safety and reliability of the vehicle detection process, and ensure the validity and repeatability of the detection results.

[0049] Optionally, accessing the vehicle attributes of the vehicle to be tested through the vehicle attribute management interface to obtain the vehicle function test results includes: S210: Based on preset vehicle attribute mapping rules, the vehicle attribute identifier used in the detection task is converted into the vehicle attribute identifier corresponding to the vehicle to be detected. The detection task configuration information is used to configure and describe the detection task.

[0050] Specifically, in combination Figure 6 As shown, vehicle attribute identifiers can be used in the detection task configuration information to describe the vehicle attributes that need to be detected or set. Therefore, based on the preset vehicle attribute mapping rules, the vehicle attribute identifiers used in the detection task can be converted into vehicle attribute identifiers corresponding to the current vehicle model or configuration to be detected.

[0051] Among them, the preset vehicle attribute mapping rules can be a set of predefined rules or tables used to convert the general logical attribute identifiers used in the detection task into the actual attribute identifiers corresponding to the vehicle to be detected, so as to ensure that the same detection task can be executed across vehicle models.

[0052] S220: Based on the converted vehicle attribute identifier, the corresponding vehicle attribute is set or obtained through the vehicle attribute management interface, and the return value or execution status of the vehicle attribute is analyzed to determine the vehicle function detection result.

[0053] Specifically, after the vehicle attribute identifier conversion is completed, the corresponding vehicle attributes are set or retrieved through the vehicle attribute management interface based on the converted vehicle attribute identifier. For example, attributes related to a certain vehicle function can be set, and its return value or execution status can be read. The return value or execution status of the vehicle attribute is analyzed to determine whether the corresponding vehicle function is normal, thereby obtaining the vehicle function detection result.

[0054] For vehicle attributes with "read-only" permissions, their current value can be obtained through the vehicle attribute management interface, and the function status can be determined based on the return value and preset conditions. For vehicle attributes with "write" permissions, a specified value can be set through the vehicle attribute management interface, and the success of the operation can be determined based on the execution status returned by the interface.

[0055] Among them, combined Figure 2 As shown, each method in the Dex utility class (Dex stands for Dalvik Executable, an Android executable bytecode file) may collect vehicle attributes synchronously or asynchronously. For example, it may synchronously or asynchronously call the collected vehicle attribute value ID, vehicle scope (area ID), and vehicle specific attribute value value in sequence.

[0056] Among them, combined Figure 2 As shown, the EOL (End Of Line, Vehicle Off-Line Inspection) utility class is a secondary encapsulation of vehicle properties (CarProperty) for reflecting and obtaining vehicle property IDs. It uses the class name and property name to reflectively obtain the corresponding ID, avoiding property ID leakage and errors after modifying values ​​for different vehicle models. It can also use an ID conversion method (i.e., an attribute identifier conversion method, used to convert logical attribute identifiers in the inspection task into the actual vehicle attribute identifiers corresponding to the vehicle being inspected) to achieve a secondary conversion of custom IDs (i.e., to convert custom attribute identifiers to actual vehicle attribute identifiers). For example, the `get Wrapped Property Id` method (used to convert logical attribute identifiers into the actual attribute IDs corresponding to the vehicle being inspected) in `adaptapi.car.IWrapper` (a vehicle attribute adaptation utility class used to uniformly manage the mapping between vehicle attribute identifiers and actual vehicle attribute IDs) can be used to obtain the correct ID. Furthermore, the corresponding vehicle attributes can be set through the vehicle attribute setting interface (`setProperty`), and the corresponding execution status is returned. After each method call, a call record is inserted into the database.

[0057] In this optional embodiment, the attribute identifiers used in the detection task are converted into actual vehicle attribute identifiers by a preset attribute mapping rule, and then the access or setting and analysis of the return values ​​are performed. This achieves standardization and accuracy in obtaining vehicle function detection results, avoids leakage of vehicle attribute identifiers or errors caused by vehicle model differences, and improves the accuracy of detection results and the universality of the task across different vehicle models.

[0058] Optionally, obtaining the diagnostic information of the vehicle to be tested through the diagnostic protocol middleware includes: S230: Establish a diagnostic communication connection with at least one electronic control unit of the vehicle under test through the diagnostic protocol middleware.

[0059] Specifically, in combination Figure 7 As shown, a diagnostic communication connection is established with at least one electronic control unit of the vehicle under test through a diagnostic protocol middleware. The diagnostic protocol middleware can be a middleware corresponding to the Unified Diagnostic Service Protocol or other vehicle diagnostic communication protocols.

[0060] S240: Based on the diagnostic communication connection, obtain the diagnostic information of the vehicle to be tested, the diagnostic information including vehicle fault code information and / or electronic control unit status information related to vehicle functions.

[0061] Specifically, after establishing a diagnostic communication connection, a diagnostic request is sent to the electronic control unit based on the diagnostic communication connection to obtain vehicle diagnostic information. The diagnostic information may include vehicle fault code information and electronic control unit status information related to vehicle functions, thereby reflecting the current fault status and operating status of the vehicle.

[0062] In this optional embodiment, communication is established with the vehicle's electronic control unit through the diagnostic protocol middleware to obtain fault codes and electronic control unit status information, thereby realizing real-time monitoring of the overall functional status of the vehicle. This can comprehensively reflect the vehicle's functional and fault status, providing a reliable data foundation for subsequent test result analysis and improving the completeness of vehicle functional testing.

[0063] Optionally, generating vehicle function test result data based on the vehicle function test results and the diagnostic information includes: S310: Generate detection result data to characterize the functional state and fault state of the vehicle under test based on the vehicle function detection results and the diagnostic information.

[0064] Specifically, in combination Figure 8As shown, the vehicle function test results and diagnostic information obtained through the diagnostic protocol are recorded and summarized to generate test result data that characterizes the functional and fault states of the vehicle under test. The test result data can be stored in structured data form for subsequent processing.

[0065] S320: The detection result data is reported to the cloud server for processing, and the vehicle function detection result data returned by the cloud server is received.

[0066] Specifically, the test results data are reported to the cloud server. The cloud server summarizes (e.g., in the form of an MDP file) and analyzes the received test results data. For example, it performs threshold judgment on numerical attributes (such as battery power), checks whether the status attributes are logically consistent, and parses the fault codes in the diagnostic information. It also generates corresponding vehicle function test results data, receives the vehicle function test results data returned by the cloud server, and can display or output the test results as needed so that users can check the vehicle test status.

[0067] In this optional embodiment, complete test data is generated based on the vehicle function test results and diagnostic information, and then reported to the cloud server for processing, enabling centralized management and unified analysis of the test data. Through the data returned from the cloud, operators or the system can obtain vehicle function status and fault information in real time, making the test results traceable, statistically verifiable, and analyzable. This improves the intelligence level and data value of vehicle testing, providing strong support for subsequent maintenance, diagnosis, and remote management.

[0068] Optionally, the vehicle detection method further includes: determining the corresponding vehicle attribute definition and diagnostic strategy based on the vehicle model information of the vehicle to be detected, and performing corresponding vehicle function detection based on the vehicle attribute definition and the diagnostic strategy.

[0069] Specifically, upon receiving a vehicle function testing task, the system first obtains the vehicle model information, such as vehicle model, configuration version, or vehicle platform number. Then, based on the model information, it loads the corresponding vehicle attribute definitions and diagnostic strategies from local cache or a cloud server. The vehicle attribute definitions can include general vehicle attribute definitions and model-specific attribute definitions. Based on the loaded vehicle attribute definitions, the actual vehicle attribute identifier corresponding to the current model can be determined. The diagnostic strategies can describe the testing methods, diagnostic processes, or diagnostic parameters corresponding to different models. For example, for a first model, a first diagnostic strategy can be used to perform battery management system testing; for a second model, a second diagnostic strategy can be used to perform diagnostic communication with the corresponding electronic control unit. Subsequently, vehicle function testing is performed based on the vehicle attribute definitions and diagnostic strategies. For example, the system accesses the corresponding vehicle attributes through the vehicle attribute management interface to obtain vehicle operating status such as door status, battery level, and vehicle mode. Based on the diagnostic strategies, diagnostic communication is established with the corresponding electronic control unit through diagnostic protocol middleware to perform fault detection or function testing.

[0070] In this optional embodiment, the corresponding vehicle attribute definitions and diagnostic strategies can be dynamically adapted according to different vehicle models, thereby supporting vehicle function detection for different vehicle models and improving the versatility and scalability of the vehicle detection system.

[0071] Optionally, the vehicle detection method further includes: uploading vehicle bus communication signal data during the detection phase to a cloud server, wherein the cloud server is used to perform statistical analysis on the vehicle bus communication signal data to determine the response of the vehicle controller to the vehicle function detection task, and to generate corresponding vehicle function detection result data based on the statistical analysis results.

[0072] Specifically, during vehicle function testing, vehicle bus communication signal data of the vehicle under test can be collected synchronously. This data can include CAN bus data, LIN bus data, Ethernet communication data, and communication messages between electronic control units. For example, during headlight testing, control signals, feedback signals, and status change signals corresponding to the headlight controller can be collected via the vehicle bus. During door locking testing, locking command signals and execution feedback signals corresponding to the door controller can be collected. After the testing task is completed, the vehicle bus communication signal data collected during the testing period can be uploaded to a cloud server. The cloud server can perform statistical analysis on the vehicle bus communication signal data, such as analyzing whether the vehicle controller returns a response signal within a preset time, whether the response signal conforms to preset rules, and whether the controller's execution status is normal. For example, the cloud server can analyze whether the headlight controller returns a corresponding status feedback signal after issuing a headlight-on command. If no corresponding feedback signal is received within a preset time, the controller's response can be determined to be abnormal. Furthermore, the cloud server can statistically analyze the controller response time, response success rate, and number of abnormalities in different testing tasks to generate corresponding vehicle function testing result data.

[0073] In this optional embodiment, statistical analysis can be performed on the response of the vehicle controller in the detection task, thereby improving the accuracy and reliability of the vehicle function detection results.

[0074] like Figure 9 As shown, an embodiment of the present invention provides a vehicle detection device 900, comprising: The first module 910 is used to obtain the detection task configuration information for vehicle function detection and to verify the operating status of the vehicle to be tested according to the detection task configuration information. The second module 920 is used to access the vehicle attributes of the vehicle under test through the vehicle attribute management interface to obtain the vehicle function test results after the operating status of the vehicle under test passes the verification, and to obtain the diagnostic information of the vehicle under test through the diagnostic protocol middleware. The third module 930 is used to generate vehicle function test result data based on the vehicle function test results and the diagnostic information.

[0075] like Figure 10 As shown, an electronic device 1000 provided in this embodiment of the invention includes a memory 1020 and a processor 1010; the memory 1020 is used to store a computer program; the processor 1010 is used to implement the vehicle detection method as described above when the computer program is executed.

[0076] Alternatively, an electronic device 1000 includes a memory 1020 and a processor 1010 coupled to the memory 1020; the memory 1020 is configured to store a computer program; the processor 1010 is configured to perform the following operations when the computer program is executed: Obtain the detection task configuration information for vehicle function detection, and verify the operating status of the vehicle to be tested according to the detection task configuration information; Once the operating status of the vehicle under test passes the verification, the vehicle attributes of the vehicle under test are accessed through the vehicle attribute management interface to obtain the vehicle function test results, and the diagnostic information of the vehicle under test is obtained through the diagnostic protocol middleware. Vehicle function test result data is generated based on the vehicle function test results and the diagnostic information.

[0077] This invention provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the vehicle detection method described above.

[0078] Alternatively, a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the following operations: Obtain the detection task configuration information for vehicle function detection, and verify the operating status of the vehicle to be tested according to the detection task configuration information; Once the operating status of the vehicle under test passes the verification, the vehicle attributes of the vehicle under test are accessed through the vehicle attribute management interface to obtain the vehicle function test results, and the diagnostic information of the vehicle under test is obtained through the diagnostic protocol middleware. Vehicle function test result data is generated based on the vehicle function test results and the diagnostic information.

[0079] The present invention will now be described an electronic device 1000 that can serve as a server or client of the present invention, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device 1000 is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device 1000 can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0080] Electronic device 1000 includes a computing unit that can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) or a computer program loaded from a storage unit into random access memory (RAM). The RAM may also store various programs and data required for device operation. The computing unit, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0081] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. In this application, the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention according to actual needs. Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units can be implemented in hardware or as software functional units.

[0082] While the present invention has been disclosed above, its scope of protection is not limited thereto. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, and all such changes and modifications will fall within the scope of protection of the present invention.

Claims

1. A vehicle detection method characterized by, include: Obtain the detection task configuration information for vehicle function detection, and verify the operating status of the vehicle to be tested according to the detection task configuration information; Once the operating status of the vehicle under test passes the verification, the vehicle attributes of the vehicle under test are accessed through the vehicle attribute management interface to obtain the vehicle function test results, and the diagnostic information of the vehicle under test is obtained through the diagnostic protocol middleware. Vehicle function test result data is generated based on the vehicle function test results and the diagnostic information.

2. The vehicle detection method according to claim 1, characterized by, The acquisition of the detection task configuration information for vehicle function detection includes: After the vehicle-mounted detection application is started, the background execution mechanism retrieves the detection task configuration information from the cloud server according to a preset strategy. After obtaining the detection task configuration information for vehicle function detection, the vehicle detection method further includes: The detection logic description data in the detection task configuration information is parsed, and an executable detection file for vehicle function detection is generated on the vehicle terminal based on the parsing results.

3. The vehicle detection method according to claim 2, characterized by, After obtaining the detection task configuration information for vehicle function detection, the vehicle detection method further includes: The interface description data in the detection task configuration information is parsed to generate an operation interface for vehicle function detection on the vehicle terminal. The interactive operations in the user interface are associated with the executable detection file to trigger the corresponding vehicle function detection when a user operation is received.

4. The vehicle detection method according to claim 1, characterized by, The step of verifying the operating status of the vehicle to be tested according to the detection task configuration information includes: Based on the detection task configuration information, at least one operating status parameter of the vehicle to be detected is obtained through the vehicle attribute management interface; The operating status parameters are compared with preset detection execution conditions to determine whether the vehicle under test meets the execution requirements of vehicle function detection.

5. The vehicle detection method according to claim 1, characterized by, The step of accessing the vehicle attributes of the vehicle to be tested through the vehicle attribute management interface to obtain the vehicle function test results includes: Based on preset vehicle attribute mapping rules, the vehicle attribute identifiers used in the detection task are converted into the vehicle attribute identifiers corresponding to the vehicle to be detected. The detection task configuration information is used to configure and describe the detection task. Based on the converted vehicle attribute identifier, the corresponding vehicle attributes are set or obtained through the vehicle attribute management interface, and the return value or execution status of the vehicle attributes is analyzed to determine the vehicle function detection result.

6. The vehicle detection method according to claim 1, characterized by, The process of obtaining the diagnostic information of the vehicle under test through the diagnostic protocol middleware includes: A diagnostic communication connection is established between the diagnostic protocol middleware and at least one electronic control unit of the vehicle under test. Based on the diagnostic communication connection, the diagnostic information of the vehicle under test is obtained, including vehicle fault code information and / or electronic control unit status information related to vehicle functions.

7. The vehicle inspection method according to claim 1, characterized in that, The step of generating vehicle function test result data based on the vehicle function test results and the diagnostic information includes: Based on the vehicle function test results and the diagnostic information, test result data is generated to characterize the functional status and fault status of the vehicle under test; The test results data are reported to the cloud server for processing, and the vehicle function test results data returned by the cloud server are received.

8. The vehicle inspection method according to claim 1, characterized in that, Also includes: Based on the vehicle model information of the vehicle to be tested, the corresponding vehicle attribute definition and diagnostic strategy are determined, and the corresponding vehicle function test is performed based on the vehicle attribute definition and the diagnostic strategy.

9. The vehicle inspection method according to claim 1, characterized in that, Also includes: The vehicle bus communication signal data during the detection phase is uploaded to a cloud server. The cloud server is used to perform statistical analysis on the vehicle bus communication signal data to determine the response of the vehicle controller to the vehicle function detection task, and to generate corresponding vehicle function detection result data based on the statistical analysis results.

10. A vehicle detection apparatus characterized by comprising: include: The first module is used to obtain the detection task configuration information for vehicle function detection, and to verify the operating status of the vehicle to be tested according to the detection task configuration information. The second module is used to access the vehicle attributes of the vehicle under test through the vehicle attribute management interface to obtain the vehicle function test results after the operating status of the vehicle under test passes the verification, and to obtain the diagnostic information of the vehicle under test through the diagnostic protocol middleware. The third module is used to generate vehicle function test result data based on the vehicle function test results and the diagnostic information.

Images