Fault positioning method and device based on vehicle machine screenshot and electronic equipment
By acquiring and associating screenshots of the vehicle's user interface, system logs, and CAN bus signal data, the problem of low efficiency in locating vehicle software faults was solved, enabling rapid fault location and cost reduction, and improving the efficiency of vehicle software delivery.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- VOYAH AUTOMOBILE TECH CO LTD
- Filing Date
- 2026-01-16
- Publication Date
- 2026-06-02
AI Technical Summary
In existing technologies, vehicle infotainment software fault location is inefficient, inaccurate, and costly, resulting in low vehicle infotainment software delivery efficiency.
By acquiring screenshots of the vehicle's user interface, system log data, and CAN bus signal data, and associating them based on operation flag information, the data is structured and stored according to a preset time series to generate a display interface containing thumbnails of the user interface screenshots, thereby enabling fault location.
It enables rapid location and reproduction of vehicle infotainment system faults, shortens the fault location cycle, reduces location costs, and improves vehicle infotainment system software delivery efficiency.
Smart Images
Figure CN122132278A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle inspection technology, and in particular to a fault location method, device and electronic equipment based on vehicle screen screenshots. Background Technology
[0002] Currently, with the development of automotive intelligence, the in-vehicle infotainment functions are becoming increasingly complex. Automated testing has become a key link in ensuring system stability. In the process of automated testing of vehicle software quality, fault analysis is usually performed by combining system logs and vehicle underlying bus signals.
[0003] However, in existing technologies, the acquisition and storage of system logs and vehicle underlying bus signals are often carried out independently, lacking an effective correlation mechanism. This means that after a vehicle infotainment system malfunctions, operators need to manually compare the time records in the log files with the bus signal data recorded at the corresponding time in order to try to reconstruct the system context at the time of the malfunction. The above-mentioned data correlation method is inefficient, has poor accuracy, and is labor-intensive. Furthermore, the above-mentioned vehicle infotainment system software fault location method is difficult to locate, has a long location cycle, and is costly, which can seriously lead to low delivery efficiency of vehicle infotainment system software. Summary of the Invention
[0004] This application provides a fault location method, device, and electronic device based on vehicle infotainment system screenshots. The embodiments provided by this application solve the technical problems of low efficiency, poor accuracy, and high labor costs in the prior art regarding data association methods. Furthermore, the aforementioned fault location methods for vehicle infotainment system software are difficult to locate, have long location cycles, and high location costs, which seriously lead to low delivery efficiency of vehicle infotainment system software. The embodiments provided by this application realize rapid location and reproduction of vehicle infotainment system faults, shorten the fault location cycle, reduce the fault location cost, and thus improve the delivery efficiency of vehicle infotainment system software.
[0005] In a first aspect, this application provides a fault location method based on vehicle infotainment system screenshots, the fault location method based on vehicle infotainment system screenshots comprising: Obtain atomic interface test instructions for testing the vehicle infotainment system; wherein, the atomic interface test instructions include operation flag information, and the atomic interface test instructions are used to characterize the minimum independent user interaction action instructions for testing the vehicle infotainment system. Based on the atomic interface test instructions, the user interface screenshot data, system log data, and CAN bus signal data of the vehicle system are obtained; Based on the operation flag information, the user interface screenshot data, the system log data, and the CAN bus signal data are correlated to determine the test data corresponding to the operation flag information; The test data is structured and stored according to a preset time series, and a display interface containing user interface screenshot thumbnails is generated to support fault location of the vehicle system.
[0006] In one feasible implementation, the method further includes: Based on the target query operation command, target test data that matches the target query operation command is determined from a preset structured database, and a target user interface screenshot thumbnail is displayed on the display interface; and / or the target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are expanded and displayed on the display interface.
[0007] In one feasible implementation, obtaining the user interface screenshot data of the vehicle system based on the atomic interface test instructions includes: Based on the atomic interface test instructions, the rendering wait time for the user interface of the vehicle system is determined; After waiting for the rendering time, the screenshot interface is called to capture the current user interface and obtain the user interface screenshot data of the vehicle system; wherein, the user interface screenshot data includes metadata such as the timestamp of the user interface screenshot data acquisition and operation description information.
[0008] In one feasible implementation, obtaining the vehicle system log data based on the atomic interface test instructions includes: After executing the atomized interface test command, the first preset time window is started; From the real-time collected vehicle system log data stream, determine the candidate system log data of the vehicle system within the first preset time window; Based on preset log keyword rules and preset log levels, the candidate system log data is filtered to determine the system log data of the vehicle system.
[0009] In one feasible implementation, acquiring the CAN bus signal data of the vehicle system based on the atomic interface test instructions includes: Based on the atomic interface test command, start the second preset time window; The CAN bus signal data of the vehicle unit within the second preset time window is determined from the real-time acquired CAN bus data stream; Based on a preset identifier whitelist, the CAN bus signal data of the vehicle system that has a mapping relationship with the atomic interface test command is determined from the CAN bus signal data.
[0010] In one feasible implementation, the target query operation instruction includes a target time node click operation instruction. Based on the target query operation instruction, target test data matching the target query operation instruction is determined from a preset structured database. The target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are then displayed on the display interface, including: Based on the click operation instruction at the target time node, the user interface screenshot data corresponding to the target time node is parsed to determine the operation identification information in the user interface screenshot data; Based on the operation identification information, the preset structured database is queried to determine the target system log data, target CAN bus signal data, and target user interface screenshot data that are compatible with the target time node click operation instruction. The target fields in the target system log data, the target CAN bus signal data, and the target user interface screenshot data that are related to the target time node click operation instruction are highlighted.
[0011] In one feasible implementation, the method further includes: Based on a preset time range or preset keywords, the test data is filtered to determine the fault characteristic information for testing the vehicle system. The preset keywords include error log keywords and CAN bus signal IDs. The fault feature information is matched with the fault types pre-stored in the preset fault mode knowledge base to determine the target fault type of the vehicle system and generate a fault analysis report.
[0012] In a second aspect, this application provides a fault location device based on vehicle infotainment system screenshots, the fault location device based on vehicle infotainment system screenshots comprising: The first acquisition module is used to acquire atomic interface test instructions for testing the vehicle infotainment system; wherein, the atomic interface test instructions include operation flag information, and the atomic interface test instructions are used to characterize the minimum independent user interaction action instructions for testing the vehicle infotainment system. The second acquisition module is used to acquire user interface screenshot data, system log data, and CAN bus signal data of the vehicle system based on the atomic interface test command. The determination module is used to associate the user interface screenshot data, the system log data, and the CAN bus signal data based on the operation flag information to determine the test data corresponding to the operation flag information; The generation module is used to store the test data in a structured manner according to a preset time series and generate a display interface that includes user interface screenshot thumbnails, so as to support fault location of the vehicle system.
[0013] In a third aspect of this application, an electronic device is provided, including a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus, and the machine-readable instructions are executed by the processor to perform the steps of the fault location method based on vehicle screen screenshots as described above.
[0014] In a fourth aspect of this application, an embodiment of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the fault location method based on vehicle screen screenshots as described above.
[0015] The fault location method, apparatus, and electronic device based on vehicle infotainment system screenshots provided in this application, compared with the prior art, obtain an atomic interface test command for testing the vehicle infotainment system. Then, based on the atomic interface test command, the user interface screenshot data, system log data, and CAN bus signal data of the vehicle infotainment system are obtained. Based on the operation flag information, the user interface screenshot data, system log data, and CAN bus signal data are associated to determine the test data corresponding to the operation flag information. The test data is then structured and stored according to a preset time sequence, and a display interface containing user interface screenshot thumbnails is generated to support fault location of the vehicle infotainment system. This application achieves rapid fault location and reproduction of the vehicle infotainment system by collecting multi-source data and aligning the collected and interconnected multi-source test data along the time axis. This shortens the fault location cycle, reduces the fault location cost, and improves the efficiency of vehicle infotainment system software delivery. Attached Figure Description
[0016] Figure 1 A flowchart illustrating a fault location method based on vehicle-mounted screen screenshots provided in an embodiment of this application is shown. Figure 2 This paper shows a structural block diagram of a fault location device based on vehicle screen screenshots provided in an embodiment of this application; Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown.
[0017] Figure 2 and Figure 3 The correspondence between the figure labels and figure titles in the accompanying drawings is as follows: 200 Fault location device based on vehicle screen screenshot; 210 First acquisition module; 220 Second acquisition module; 230 Determination module; 240 Generation module; 250 Display module; 300 Electronic device; 310 Processor; 320 Memory; 330 Bus. Detailed Implementation
[0018] To better understand the technical solutions provided in the embodiments of this specification, the technical solutions of the embodiments of this specification will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.
[0019] In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, without necessarily requiring or implying any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. The term "two or more" includes two or more cases.
[0020] First, the applicable application scenarios of this application will be introduced. The embodiments provided in this application are applicable to the field of vehicle detection technology, and in particular, they relate to a fault location method, device and electronic equipment based on vehicle screenshots.
[0021] Currently, the acquisition and storage of system logs and vehicle underlying bus signals are often carried out independently, lacking an effective correlation mechanism. This means that after a vehicle infotainment system malfunctions, operators need to manually compare the time records in the log files with the bus signal data recorded at the corresponding time in order to try to reconstruct the system context at the time of the malfunction. This data correlation method is inefficient, has poor accuracy, and is labor-intensive. Furthermore, the fault location method of the vehicle infotainment system is difficult to locate, has a long location cycle, and is costly, which can seriously lead to low delivery efficiency of the vehicle infotainment system software.
[0022] Based on this, the embodiments of this application provide a fault location method, device, and electronic device based on vehicle screen screenshots. The embodiments provided by this application solve the technical problems of low efficiency, poor accuracy, and high labor costs in the data association methods of the prior art, as well as the difficulty, long location cycle, and high location cost of the above-mentioned vehicle screen software fault location methods, which seriously lead to low delivery efficiency of vehicle screen software. The embodiments provided by this application realize the rapid location and reproduction of vehicle screen faults, shorten the fault location cycle, reduce the fault location cost, and thus improve the delivery efficiency of vehicle screen software.
[0023] Figure 1 A flowchart illustrating a fault location method based on vehicle infotainment system screenshots provided in an embodiment of this application is shown. Figure 1 As shown, the fault location method based on vehicle infotainment system screenshots includes the following steps: S101. Obtain atomic interface test instructions for testing the vehicle infotainment system; wherein, the atomic interface test instructions include operation flag information, and the atomic interface test instructions are used to characterize the minimum independent user interaction action instructions for testing the vehicle infotainment system.
[0024] In this step, the embodiments provided in this application typically use atomic interface test instructions, which are used to characterize the minimum independent user interaction action instructions for testing the vehicle system, to synchronously trigger and collect multi-source vehicle system software test data, so as to ensure that the time of generation of the multi-source vehicle system software test data is consistent.
[0025] It is understood that the atomic interface test instructions provided in the embodiments of this application have multiple features such as independence, observability, and test script binding.
[0026] It should be noted that the independence of atomic interface test instructions refers to instructions that can be completed without relying on other preceding or following operations, such as a single click, a single swipe, or the completion of a single field input on the user interface.
[0027] The observability of atomic interface test commands refers to the clear feedback or response commands triggered after the operation is executed, such as the interface switching after clicking a button on the user interface, or the text box content being updated after input is completed.
[0028] Test script binding of atomic interface test instructions refers to the operation instructions that are bound to the script of the automated test framework, such as the click() and sendKeys() method calls of Appium and uiautomator2, or the tap(x,y) coordinate click instruction in the custom test script.
[0029] For example, the atomic interface test instruction in the embodiments provided in this application refers to: clicking the "navigation" icon on the user interface of the vehicle system (click(nav_icon)), entering "Beijing" in the search box and confirming (sendKeys(search_box,"Beijing")+click(confirm_button) if necessary).
[0030] The non-atomic interface test instruction provided in the embodiments of this application refers to "slide from the home page to the settings page". That is, the user interface of the vehicle system may contain multiple sliding test instructions, which need to be broken down into single sliding atomic events.
[0031] S102. Based on the atomic interface test command, obtain the user interface screenshot data, system log data, and CAN bus signal data of the vehicle system.
[0032] In this step, in the embodiments provided in this application, after determining the atomic interface test instructions, the embodiments provided in this application will start a high-precision time synchronization service and synchronize and calibrate the host executing the test, the vehicle device under test, and the CAN bus signal data according to the corresponding time to ensure that the timestamp reference of all multi-source acquired data is consistent.
[0033] It is understood that, when the embodiments provided in this application acquire user interface screenshot data, they will first automatically acquire the screenshot data of the current screen when performing each user interface operation, and generate metadata containing a precise timestamp for each user interface screenshot.
[0034] The embodiments provided in this application will monitor and collect system log data output by various software in the vehicle in real time, and automatically extract log content within a specific time window before and after the user interface operation time point, focusing on capturing log entries of critical levels such as errors and warnings.
[0035] In the above-described embodiments, after obtaining the user interface screenshot data, system log data, and CAN bus signal data of the vehicle system, the embodiments provided in this application will perform data cleaning and timestamp conversion on the above data. For example, redundancy removal processing will be performed on continuous user interface screenshot data to eliminate multiple consecutive user interface screenshots with identical content; irrelevant system log data and CAN bus signal data generated by the system background process will be filtered out.
[0036] Here, the filtering of system log data in the embodiments provided in this application can be specifically constrained by a time window, that is, only system log data within ±500ms before and after the operation timestamp is retained, and the retained system log data can be adaptively adjusted according to the operation type, such as extending the time-consuming operation to ±1s.
[0037] Furthermore, the embodiments provided in this application will prioritize filtering out media playback level logs, and at the same time, by matching keywords in the operating system log data through regular expressions, logs generated by operations that are not generated by the application process under test will also be prioritized for filtering out. In addition, the embodiments provided in this application will remove periodic heartbeat frames, such as CAN signals with fixed IDs and unchanged data fields, and CAN signals with a period of ≤100ms.
[0038] The embodiments provided in this application will first establish an operation mapping table associated with the operation flag. The specific contents of the operation mapping table in the embodiments provided in this application can be customized and used according to different application scenarios and usage conditions. The specific contents of the operation mapping table in the embodiments provided in this application can be specifically set as follows: for example, "navigation click" corresponds to CAN ID 0x123, 0x456.
[0039] S103. Based on the operation flag information, associate the user interface screenshot data, system log data, and CAN bus signal data to determine the test data corresponding to the operation flag information.
[0040] In this step, the core association strategy of the embodiments provided in this application is to introduce operation flag information. The system assigns a globally unique operation flag information to each user interface and strongly binds all data generated by this operation, including one or more screenshots, one log fragment, and zero or more related CAN bus signal data, to this operation flag information.
[0041] The embodiments provided in this application can be customized in terms of settings and usage according to different application scenarios and usage conditions. The embodiments provided in this application determine that a top-mounted... S104. The test data is stored in a structured manner according to a preset time series, and a display interface containing user interface screenshot thumbnails is generated to support fault location of the vehicle system.
[0042] In this step, the embodiments provided in this application will store the above test data in a structured manner according to a preset time series, that is, store it in a dedicated database. The dedicated database will be designed to be optimized for time series data, and indexes will be established for timestamps and operation flag information to support fast queries by time range or operation type. In addition, the screenshots will be stored in both thumbnail and original image formats to balance the needs of display performance and viewing details.
[0043] The fault location method based on vehicle infotainment system screenshots provided in this application, compared with the prior art, obtains atomic interface test instructions for testing the vehicle infotainment system. Then, based on these instructions, it acquires user interface screenshot data, system log data, and CAN bus signal data. Based on operation flag information, it associates the user interface screenshot data, system log data, and CAN bus signal data to determine the test data corresponding to the operation flag information. The test data is then structured and stored according to a preset time series, and a display interface containing user interface screenshot thumbnails is generated to support fault location of the vehicle infotainment system. This application achieves rapid fault location and reproduction of the vehicle infotainment system by collecting multi-source data and aligning the collected, interconnected multi-source test data along the time axis. This shortens the fault location cycle, reduces fault location costs, and improves the efficiency of vehicle infotainment system software delivery.
[0044] In one feasible implementation, based on the target query operation command, target test data that matches the target query operation command is determined from a preset structured database, and a target user interface screenshot thumbnail is displayed on the display interface; and / or the target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are expanded and displayed on the display interface.
[0045] In the above-described embodiments, after storing the associated data in a digitized manner, when a target user or operator wants to locate the fault in the vehicle's infotainment system, the target user or operator's target query operation command is determined. Then, based on the target test data that matches the target query operation command determined from a preset structured database, a thumbnail of the target user interface screenshot is displayed on the display interface; and / or the target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are expanded and displayed on the display interface.
[0046] Whether the target user interface screenshot thumbnail, the target system log data, the target CAN bus signal data, and the target user interface screenshot data are displayed on the display interface depends on the target user's custom requirements. If the target user wants to accurately locate and analyze the files and causes when the vehicle system malfunction occurs, then the target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data need to be expanded and displayed.
[0047] In one feasible implementation, based on atomic interface testing instructions, screenshot data of the vehicle's user interface is obtained, including: Based on the atomic interface test command, the rendering wait time for the vehicle's user interface is determined; after waiting for the rendering wait time, the screenshot interface is called to capture the current user interface and obtain the user interface screenshot data of the vehicle's user interface; the user interface screenshot data includes the timestamp of the user interface screenshot data acquisition and metadata of operation description information.
[0048] It should be noted that, after determining the atomic interface test instruction, the embodiments provided in this application will determine that the user interface rendering is complete after the rendering wait time, such as 200ms after clicking a button or 500ms after sliding a list. After the rendering is completed, the screenshot interface is immediately called to capture the current user interface screenshot data and record the metadata of the timestamp and operation description information.
[0049] The embodiments provided in this application can confirm whether the rendering of the user interface is complete by detecting changes in the state of interface elements, such as when the target page title has been loaded.
[0050] In one feasible implementation, system log data of the vehicle's infotainment system is obtained based on atomic interface test commands, including: After executing the atomic interface test command, the first preset time window is started; candidate system log data of the vehicle system within the first preset time window is determined from the real-time collected vehicle system log data stream; the candidate system log data is filtered based on preset log keyword rules and preset log levels to determine the system log data of the vehicle system.
[0051] The embodiments provided in this application will monitor and collect system log data output by various software in the vehicle in real time, and automatically extract log content within a specific time window before and after the user interface operation time point, and capture key log entries such as errors and warnings based on preset log keyword rules and preset log levels.
[0052] In the above-described embodiments, the first preset time window can be customized and used according to different application scenarios and usage conditions.
[0053] In one feasible implementation, the CAN bus signal data of the vehicle's infotainment system is acquired based on atomic interface test instructions, including: Based on the atomic interface test command, a second preset time window is started; the CAN bus signal data of the vehicle unit within the second preset time window is determined from the real-time acquired CAN bus data stream; based on the preset identifier whitelist, the CAN bus signal data of the vehicle unit that has a mapping relationship with the atomic interface test command is determined from the CAN bus signal data.
[0054] In the above-described embodiments, the identifier whitelist provided in this application can be customized and used according to different application scenarios and usage conditions.
[0055] In one feasible implementation, the target query operation instruction includes a target time node click operation instruction. Based on the target query operation instruction, target test data matching the target query operation instruction is determined from a preset structured database. The target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are then displayed on the display interface, including: Based on the click operation command at the target time node, the user interface screenshot data corresponding to the target time node is parsed to determine the operation identification information in the user interface screenshot data. Based on the operation identification information, a preset structured database is queried to determine the target system log data, target CAN bus signal data, and target user interface screenshot data that are compatible with the click operation command at the target time node. Target fields related to the click operation command at the target time node in the target system log data, target CAN bus signal data, and target user interface screenshot data are highlighted.
[0056] It should be noted that, after determining the target system log data, target CAN bus signal data, and target user interface screenshot data that are compatible with the click operation command at the target time node, the embodiments provided in this application will highlight the target fields in the above data to help the target user quickly locate the fault location.
[0057] In one feasible implementation, the embodiments provided in this application will filter the test data based on a preset time range or preset keywords to determine the fault characteristic information for testing the vehicle system. The preset keywords include error log keywords and CAN bus signal IDs. It is understood that the embodiments provided in this application support users to filter test data based on a preset time range, thereby determining the fault characteristic information for testing the vehicle system; or users can search using preset keywords, such as error log keywords and CAN bus signal IDs, to quickly determine fault characteristic information and locate the fault location.
[0058] In one feasible implementation, this application will match the fault feature information with the fault types pre-stored in the preset fault mode knowledge base to determine the target fault type of the vehicle system and generate a fault analysis report.
[0059] It is understood that the embodiments provided in this application can automatically generate fault analysis reports, summarize the fault time point, related operations, interface status, system logs and bus signals to form a complete fault context, which greatly simplifies the process of fault reproduction and root cause analysis, so as to realize automated quality monitoring and fault tracking of vehicle system faults.
[0060] Figure 2 This diagram illustrates a structural block diagram of a fault location device based on a vehicle-mounted camera screenshot, as provided in an embodiment of this application. Figure 2 As shown, the fault location device 200 based on the vehicle's infotainment system screenshot includes: The first acquisition module 210 is used to acquire atomic interface test instructions for testing the vehicle infotainment system; wherein, the atomic interface test instructions include operation flag information, and the atomic interface test instructions are used to characterize the minimum independent user interaction action instructions for testing the vehicle infotainment system.
[0061] The second acquisition module 220 is used to acquire user interface screenshot data, system log data, and CAN bus signal data of the vehicle system based on atomic interface test commands.
[0062] The determination module 230 is used to correlate user interface screenshot data, system log data, and CAN bus signal data based on operation flag information to determine the test data corresponding to the operation flag information.
[0063] The generation module 240 is used to store the test data in a structured manner according to a preset time series and generate a display interface that includes user interface screenshot thumbnails to support fault location of the vehicle system.
[0064] The display module 250 is used to determine the target test data that matches the target query operation command from a preset structured database based on the target query operation command, and display a thumbnail of the target user interface screenshot on the display interface; and / or expand and display the target system log data, target CAN bus signal data and target user interface screenshot data under the target test data on the display interface.
[0065] In one feasible implementation, the second acquisition module 220 is specifically used for: Based on atomic interface test instructions, the rendering wait time for the vehicle's user interface is determined.
[0066] After waiting for the rendering time, the screenshot interface is called to capture the current user interface and obtain the user interface screenshot data of the vehicle system; the user interface screenshot data includes metadata such as the timestamp of the user interface screenshot data acquisition and operation description information.
[0067] In one feasible implementation, the second acquisition module 220 is specifically used for: After executing the atomic interface test command, the first preset time window is started.
[0068] Candidate system log data for the vehicle system within the first preset time window are determined from the real-time collected vehicle log data stream.
[0069] Based on preset log keyword rules and preset log levels, candidate system log data are filtered to determine the system log data of the vehicle system.
[0070] In one feasible implementation, the second acquisition module 220 is specifically used for: Based on the atomic interface test command, start the second preset time window; The CAN bus signal data of the vehicle's system within the second preset time window is determined from the real-time acquired CAN bus data stream.
[0071] Based on a preset identifier whitelist, the CAN bus signal data of the vehicle system that has a mapping relationship with the atomic interface test command is determined from the CAN bus signal data.
[0072] In one feasible implementation, the target query operation instruction includes a target time node click operation instruction, and the display module 250 is specifically used for: Based on the click operation command at the target time node, the user interface screenshot data corresponding to the target time node is parsed to determine the operation identification information in the user interface screenshot data.
[0073] Based on the operation identification information, the system queries a pre-set structured database to determine the target system log data, target CAN bus signal data, and target user interface screenshot data that are compatible with the click operation command at the target time node. The target fields in the target system log data, target CAN bus signal data, and target user interface screenshot data that are related to the click operation command at the target time node are highlighted.
[0074] In one feasible implementation, test data is filtered based on a preset time range or preset keywords to determine the fault characteristic information for testing the vehicle system. The preset keywords include error log keywords and CAN bus signal IDs.
[0075] The fault characteristic information is matched with the fault types pre-stored in the preset fault mode knowledge base to determine the target fault type of the vehicle system and generate a fault analysis report.
[0076] The fault location device 200 based on vehicle infotainment system screenshots provided in this application embodiment, compared with the prior art, obtains atomic interface test instructions for testing the vehicle infotainment system, and then obtains user interface screenshot data, system log data, and CAN bus signal data based on the atomic interface test instructions. Based on operation flag information, it associates the user interface screenshot data, system log data, and CAN bus signal data to determine the test data corresponding to the operation flag information. The test data is then structured and stored according to a preset time series, and a display interface containing user interface screenshot thumbnails is generated to support fault location of the vehicle infotainment system. This application achieves rapid fault location and reproduction of the vehicle infotainment system by collecting multi-source data and aligning the collected, interconnected multi-source test data along the time axis. This shortens the fault location cycle, reduces fault location costs, and improves the efficiency of vehicle infotainment system software delivery.
[0077] Please see Figure 3 , Figure 3 This application provides a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 3 As shown, the electronic device 300 includes a processor 310, a memory 320, and a bus 330.
[0078] Memory 320 stores machine-readable instructions executable by processor 310. When electronic device 300 is running, processor 310 and memory 320 communicate via bus 330. When the machine-readable instructions are executed by processor 310, they can perform the operations described above. Figure 1 The specific implementation of the fault location method based on vehicle screen screenshots in the method embodiment shown can be found in the method embodiment, and will not be repeated here.
[0079] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figure 1 The specific implementation of the fault location method based on vehicle screen screenshots in the method embodiment shown can be found in the method embodiment, and will not be repeated here.
[0080] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0081] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0082] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-readable program code.
[0083] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0084] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0085] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0086] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to execute a process for determining a fault identification model.
[0087] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line, DSL) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk, SSD), etc.
[0088] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0089] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.
[0090] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0091] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0092] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0093] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
[0094] Although preferred embodiments have been described in this specification, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this specification.
[0095] Obviously, those skilled in the art can make various modifications and variations to this specification without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims and their equivalents, this specification is also intended to include such modifications and variations.
Claims
1. A fault location method based on vehicle infotainment system screenshots, characterized in that, The fault location method based on vehicle infotainment system screenshots includes: Obtain atomic interface test instructions for testing the vehicle infotainment system; wherein, the atomic interface test instructions include operation flag information, and the atomic interface test instructions are used to characterize the minimum independent user interaction action instructions for testing the vehicle infotainment system. Based on the atomic interface test instructions, the user interface screenshot data, system log data, and CAN bus signal data of the vehicle system are obtained; Based on the operation flag information, the user interface screenshot data, the system log data, and the CAN bus signal data are correlated to determine the test data corresponding to the operation flag information; The test data is structured and stored according to a preset time series, and a display interface containing user interface screenshot thumbnails is generated to support fault location of the vehicle system.
2. The fault location method based on vehicle infotainment system screenshots according to claim 1, characterized in that, The method further includes: Based on the target query operation command, target test data that matches the target query operation command is determined from a preset structured database, and a target user interface screenshot thumbnail is displayed on the display interface; and / or the target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are expanded and displayed on the display interface.
3. The fault location method based on vehicle infotainment system screenshots according to claim 1, characterized in that, The step of obtaining the user interface screenshot data of the vehicle system based on the atomic interface test command includes: Based on the atomic interface test instructions, the rendering wait time for the user interface of the vehicle system is determined; After waiting for the rendering time, the screenshot interface is called to capture the current user interface and obtain the user interface screenshot data of the vehicle system; wherein, the user interface screenshot data includes metadata such as the timestamp of the user interface screenshot data acquisition and operation description information.
4. The fault location method based on vehicle infotainment system screenshots according to claim 1, characterized in that, The process of obtaining the vehicle system log data based on the atomic interface test instructions includes: After executing the atomized interface test command, the first preset time window is started; From the real-time collected vehicle system log data stream, determine the candidate system log data of the vehicle system within the first preset time window; Based on preset log keyword rules and preset log levels, the candidate system log data is filtered to determine the system log data of the vehicle system.
5. The fault location method based on vehicle-mounted screen screenshots according to claim 1, characterized in that, The step of acquiring the CAN bus signal data of the vehicle system based on the atomic interface test instructions includes: Based on the atomic interface test command, start the second preset time window; The CAN bus signal data of the vehicle unit within the second preset time window is determined from the real-time acquired CAN bus data stream; Based on a preset identifier whitelist, the CAN bus signal data of the vehicle system that has a mapping relationship with the atomic interface test command is determined from the CAN bus signal data.
6. The fault location method based on vehicle-mounted screen screenshots according to claim 2, characterized in that, The target query operation instruction includes a target time node click operation instruction. Based on the target query operation instruction, target test data matching the target query operation instruction is determined from a preset structured database. The target system log data, target CAN bus signal data, and target user interface screenshot data under the target test data are then displayed on the display interface, including: Based on the click operation instruction at the target time node, the user interface screenshot data corresponding to the target time node is parsed to determine the operation identification information in the user interface screenshot data; Based on the operation identification information, the preset structured database is queried to determine the target system log data, target CAN bus signal data, and target user interface screenshot data that are compatible with the target time node click operation instruction. The target fields in the target system log data, the target CAN bus signal data, and the target user interface screenshot data that are related to the target time node click operation instruction are highlighted.
7. The fault location method based on vehicle infotainment system screenshots according to claim 1, characterized in that, The method further includes: Based on a preset time range or preset keywords, the test data is filtered to determine the fault characteristic information for testing the vehicle system. The preset keywords include error log keywords and CAN bus signal IDs. The fault feature information is matched with the fault types pre-stored in the preset fault mode knowledge base to determine the target fault type of the vehicle system and generate a fault analysis report.
8. A fault location device based on vehicle infotainment system screenshots, characterized in that, The fault location device based on vehicle screen screenshots includes: The first acquisition module is used to acquire atomic interface test instructions for testing the vehicle infotainment system; wherein, the atomic interface test instructions include operation flag information, and the atomic interface test instructions are used to characterize the minimum independent user interaction action instructions for testing the vehicle infotainment system. The second acquisition module is used to acquire user interface screenshot data, system log data, and CAN bus signal data of the vehicle system based on the atomic interface test command. The determination module is used to associate the user interface screenshot data, the system log data, and the CAN bus signal data based on the operation flag information to determine the test data corresponding to the operation flag information; The generation module is used to store the test data in a structured manner according to a preset time series and generate a display interface that includes user interface screenshot thumbnails, so as to support fault location of the vehicle system.
9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. The machine-readable instructions are executed by the processor to perform the steps of the fault location method based on vehicle screenshots as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the steps of the fault location method based on vehicle screen screenshots as described in any one of claims 1-7.