Test system, method and related device of vehicle-mounted tablet computer

By maintaining a continuous power-on state and storing freeze frame data during vehicle-mounted tablet testing, the problem of reproducing abnormal situations in vehicle-mounted tablet power-on/off testing is solved, improving testing efficiency and analysis accuracy.

CN120948949AActive Publication Date: 2025-11-14SHENZHEN CONGPING TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202511476822.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-10-16
Publication Date
2025-11-14
Estimated Expiration
2045-10-16

AI Technical Summary

Technical Problem

When anomalies occur during power-on/off testing of the vehicle-mounted tablet, R&D personnel find it difficult to accurately reproduce the test environment, resulting in low testing efficiency and poor results, and difficulty in locating the test parameters at the moment of the anomaly.

Method used

By keeping the vehicle-mounted tablet continuously powered on during testing, freeze frame data at the time of anomalies is generated and stored, including device identification, hardware operating parameters, and software service logs, so as to trace the test parameters at the time of the anomaly later.

Benefits of technology

It improves the efficiency of vehicle-mounted tablet testing, reduces the time spent on anomaly reproduction, and provides reliable data support for quickly locating and analyzing anomalies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120948949A_ABST
    Figure CN120948949A_ABST
Patent Text Reader

Abstract

The invention discloses a test system and method of a vehicle-mounted tablet computer and a related device. The system comprises the vehicle-mounted tablet computer, a relay and upper computer equipment, the vehicle-mounted tablet is used for generating a target test strategy; performing a target test according to the target test strategy; sending a first power supply instruction to the relay according to the target test strategy; when there is an abnormal result in the plurality of test results, sending a second power supply instruction to the relay; the upper computer equipment is used for displaying abnormal information on the display when an abnormal result of the vehicle-mounted tablet computer is detected; and the relay is used for responding to the first power supply instruction and the second power supply instruction and conducting connection and disconnection. Therefore, when the vehicle-mounted tablet computer test is abnormal, the frozen frame data when the tablet computer is abnormal is generated and stored by keeping the continuous power-on state of the vehicle-mounted tablet computer, data support is provided for subsequent test personnel to trace the abnormal tablet computer operation parameters, and the efficiency of the vehicle-mounted tablet computer test is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer testing technology, and in particular to a testing system, method and related apparatus for an in-vehicle tablet. Background Technology

[0002] Before being officially released to customers, the system firmware of in-vehicle tablets undergoes various reliability and stability tests, one of which is power-on / off testing. This involves repeatedly powering on and off to determine the probability of various service anomalies, such as baseband drops, Wi-Fi and Bluetooth loading failures, and network connectivity issues. These services need to be reloaded every time the in-vehicle tablet is powered on. If any service fails to load during a boot, it will affect the user experience, and in severe cases, may even render the tablet unusable, requiring a power cycle to resolve the anomaly.

[0003] However, after power is restored, the abnormal situation may disappear with the previous power-off. The abnormal situation may be an occasional problem that occurs only once. When an abnormal situation occurs, the R&D personnel cannot accurately reproduce the test environment of a specific power-on test. They need to spend a lot of time troubleshooting and matching abnormal vehicle equipment. Even after locating the abnormal tablet, they cannot reproduce the test parameters at the time of the abnormality. This results in low test efficiency and poor test results. Summary of the Invention

[0004] In view of this, embodiments of this application provide a testing system, method, and related apparatus for vehicle-mounted tablets. When an anomaly occurs during vehicle-mounted tablet testing, the system maintains the vehicle-mounted tablet in a continuously powered state to generate and store frozen frame data at the time of the anomaly. This provides data support for subsequent testers to trace the tablet's operating parameters when the anomaly occurs, thereby improving the efficiency of vehicle-mounted tablet testing.

[0005] In a first aspect, embodiments of this application provide a testing system for vehicle-mounted tablets. The system includes a sample rack, multiple vehicle-mounted tablets to be tested disposed on the sample rack, a relay, and a host computer device disposed on a computer equipment rack. The host computer device includes a display. The communication ports of the vehicle-mounted tablets are electrically connected to the host computer device and the relays respectively via a CAN bus. The vehicle-mounted tablet is used to respond to user configuration operations for the test application, generate a target test strategy, wherein the test application is installed on the vehicle-mounted tablet; respond to user startup operations for the test application, perform target testing according to the target test strategy; send a first power supply command to the relay according to the target test strategy; and send a second power supply command to the relay when at least one abnormal result exists among multiple test results of the vehicle-mounted tablet. The host computer device is used to display abnormal information on the display when it detects the abnormal result of the vehicle-mounted tablet. The abnormal information includes: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result and the frozen frame data of the abnormal vehicle-mounted tablet. The relay is used to respond to the first power supply command by turning on and off at a preset period to enable repeated power-on and power-off of multiple vehicle-mounted tablets, and the target test strategy includes the preset period; and to respond to the second power supply command by maintaining the on state.

[0006] In one possible embodiment, regarding the display of abnormal information, the host computer device is specifically configured to: retrieve the basic configuration data of the abnormal vehicle-mounted tablet at the time of the abnormality, the basic configuration data including the test item name, the total number of power-on / off cycles, and the number of power-on / off cycles completed, the target test strategy including the test item name, and the time of the abnormality referring to the moment when at least one of the multiple test results is determined to be abnormal; obtain the hardware operating parameters and software service logs of the abnormal vehicle-mounted tablet at the time of the abnormality; and package the basic configuration data, hardware operating parameters, and software service logs to generate the freeze frame data.

[0007] In one possible embodiment, the host computer device is further configured to: determine the anomaly type of the abnormal vehicle-mounted tablet and record the timestamp of the anomaly; generate test information based on the anomaly type, the timestamp of the anomaly, and the device identifier of the abnormal vehicle-mounted tablet; establish an association between the test information of the abnormal vehicle-mounted tablet and the frozen frame data; generate a mapping table based on the association and store the mapping table.

[0008] In one possible embodiment, the in-vehicle tablet is equipped with a flash memory module; the in-vehicle tablet is further used for: recording a work log through the flash memory module when the in-vehicle tablet detects a system crash; the data in the flash memory module is not lost when the in-vehicle tablet is powered on or off; performing a restart operation; and checking the flash memory module through the test application, obtaining the work log, and recording the automatic restart test count incremented by one; and clearing the data in the flash memory module. In one possible embodiment, regarding the response to the user's configuration operation for the test application, the in-vehicle tablet is specifically used for: responding to the user's interface startup operation, displaying the main interface of the test application, the main interface of the test application including: project creation controls and test configuration controls; responding to the user's trigger operation for the test configuration controls, displaying a test configuration interface, the test configuration interface including: at least one target test project and a test startup control, the target test project being determined based on the user's configuration operation; responding to the user's selection operation on the test configuration interface, determining the target test project selected by the user; and responding to the user's configuration operation on the test configuration interface, determining the target number of the target test strategy.

[0009] In one possible embodiment, before responding to the user's trigger operation on the test configuration control, the vehicle-mounted tablet is further configured to: respond to the user's trigger operation on the project creation control, display a test project creation interface, the test project creation interface including: a test project information bar and test sub-projects, the test project information including the name, tag, and identifier of the test project, the test sub-project referring to multiple sub-items associated with the target test project; respond to the user's input operation on the test project information bar, determine the name of the target test project; respond to the user's project configuration operation on the test project information bar, determine the tag of the target test project, the project configuration operation referring to an input operation or a selection operation; generate the identifier of the target test project and the test sequence of the test sub-projects based on the tag of the target test project; generate the target test project based on the test project information and the test sequence of the test sub-projects.

[0010] In one possible embodiment, regarding the aspect of determining the tag of the target test item in response to the user's item configuration operation for the test item information bar, the in-vehicle tablet is specifically configured to: display multiple test item tags when the user's item configuration operation is a selection operation, the multiple test item tags being item tags pre-stored in the in-vehicle tablet; and determine the tag of the target test item in response to the user's selection operation for the multiple test item tags.

[0011] In one possible embodiment, regarding the aspect of determining the tag of the target test item in response to the user's item configuration operation for the test item information bar, the vehicle-mounted tablet is specifically configured to: when the user's item configuration operation is an input operation, retrieve a test database from the host computer device, the test database including a mapping table of test item tags and test sub-items; analyze and confirm the test sub-item corresponding to the user's item configuration operation through the host computer device; and determine the tag of the target test item based on the test sub-item and the test database.

[0012] In one possible embodiment, the host computer device is further configured to: display a test result interface of multiple vehicle-mounted tablets after completing the target test strategy via the display of the host computer device. The test result interface includes: the current display interface of the multiple vehicle-mounted tablets, the test item results of the multiple vehicle-mounted tablets, and test event handling controls; wherein, the test item results include: test status, number of successful tests, and number of failed tests, and the test event handling controls include: log capture control, restart control, ignore error control, and alarm control.

[0013] Secondly, embodiments of this application provide a testing method for an in-vehicle tablet, applied to an in-vehicle tablet testing system. The in-vehicle tablet testing system includes a sample rack, multiple in-vehicle tablets to be tested mounted on the sample rack, a relay, and a host computer device mounted on a computer equipment rack. The host computer device includes a display. The communication ports of the in-vehicle tablets are electrically connected to the host computer device and the relays via a CAN bus. The method includes: responding to a strategy determined by a user's configuration operation for a test application, generating a target test strategy, wherein the test application is installed on the in-vehicle tablet; and sending a first test signal to the relay according to the target test strategy. The system includes: a power supply command, wherein the first power supply command instructs the relay to turn on and off at a preset cycle to control the repeated power-on and power-off of the vehicle-mounted tablet; testing is performed according to the target testing strategy to obtain multiple test results; when at least one abnormal result exists among the multiple test results, a second power supply command is sent to the relay, the second power supply command instructing the relay to remain in the on state; and a recording message is sent to the host computer device, the recording message instructing the host computer device to record abnormal information and display the abnormal information on the display, the abnormal information including: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result, and the frozen frame data of the abnormal vehicle-mounted tablet.

[0014] Thirdly, embodiments of this application provide a testing device for an in-vehicle tablet, applied to an in-vehicle tablet testing system. The in-vehicle tablet testing system includes a sample rack, multiple in-vehicle tablets to be tested mounted on the sample rack, a relay, and a host computer device mounted on a computer equipment rack. The host computer device includes a display. The communication ports of the in-vehicle tablets are electrically connected to the host computer device and the relays via a CAN bus. The device includes a response unit, a first instruction unit, a second instruction unit, and a third instruction unit. Specifically, the response unit is used to respond to a strategy determined by a user's configuration operation for a test application and generate a target test strategy. The test application is installed on the in-vehicle tablet. The first instruction unit is specifically used to generate a target test strategy based on the target... The testing strategy includes sending a first power supply command to the relay, which instructs the relay to turn on and off at a preset cycle to control the repeated power-on and power-off of the vehicle-mounted tablet; a second command unit, specifically used to perform tests according to the target testing strategy and obtain multiple test results; when at least one abnormal result exists among the multiple test results, a second power supply command is sent to the relay, which instructs the relay to remain in the on state; and a third command unit, specifically used to send a recording message to the host computer device, which instructs the host computer device to record abnormal information and display the abnormal information on the display, the abnormal information including: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result, and the frozen frame data of the abnormal vehicle-mounted tablet.

[0015] Fourthly, embodiments of this application provide an electronic device including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing the steps in the second aspect of embodiments of this application.

[0016] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the second aspect of embodiments of this application.

[0017] Sixthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in the second aspect of embodiments of this application. The computer program product may be a software installation package.

[0018] As can be seen, the vehicle-mounted tablet testing system, method, and related apparatus provided in this application include a sample rack, multiple vehicle-mounted tablets to be tested mounted on the sample rack, relays, and a host computer mounted on a computer equipment rack, the host computer including a display; the vehicle-mounted tablets are used to respond to user configuration operations for the test application, generate a target test strategy, the test application being installed on the vehicle-mounted tablet; respond to user startup operations for the test application, perform target tests according to the target test strategy; send a first power supply command to the relay according to the target test strategy; and send a second power supply command to the relay when at least one abnormal result exists among the multiple test results of the vehicle-mounted tablet; the host computer is used to display abnormal information on the display when an abnormal result of the vehicle-mounted tablet is detected, the abnormal information including: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result, and the frozen frame data of the abnormal vehicle-mounted tablet; the relays are used to respond to the first power supply command, turn on and off at a preset period to realize repeated power-on and power-off of multiple vehicle-mounted tablets, the target test strategy including the preset period; and to respond to the second power supply command, maintain the on state. Thus, when an anomaly occurs during the testing of the vehicle-mounted tablet, by keeping the tablet continuously powered on, freeze frame data at the time of the anomaly can be generated and stored. This facilitates the reproduction of the test environment at the moment of the anomaly and provides data support for subsequent testers to trace the tablet's operating parameters at the time of the anomaly, thereby improving the efficiency of vehicle-mounted tablet testing. Attached Figure Description

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

[0020] Figure 1 This is a schematic diagram of the architecture of a vehicle-mounted tablet testing system provided in an embodiment of this application; Figure 2 This is a schematic diagram of the hardware architecture of a vehicle-mounted tablet test site provided in an embodiment of this application; Figure 3 This is a schematic diagram of the interface of a relay display provided in an embodiment of this application; Figure 4 This is a schematic diagram illustrating a specific process for displaying abnormal information provided in an embodiment of this application; Figure 5 This is a schematic diagram of the main interface of a test application provided in an embodiment of this application; Figure 6 This is a schematic diagram of a test configuration interface provided in an embodiment of this application; Figure 7 This is a schematic diagram of a test project creation interface provided in an embodiment of this application; Figure 8 This is a schematic diagram of the interface of a test item information bar provided in an embodiment of this application; Figure 9 This is a schematic diagram of a host computer device test result interface provided in an embodiment of this application; Figure 10 This is a flowchart illustrating a testing method for an in-vehicle tablet provided in an embodiment of this application; Figure 11 This is a functional unit block diagram of a vehicle-mounted tablet testing device provided in an embodiment of this application; Figure 12 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0022] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0023] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article indicates that the preceding and following related objects have an "or" relationship.

[0024] In this application's embodiments, "multiple" refers to two or more. In this application's embodiments, "connection" refers to various connection methods, such as direct or indirect connections, to achieve communication between devices; this application's embodiments do not impose any limitations on this.

[0025] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0026] The following describes the relevant content, concepts, meanings, technical issues, technical solutions, and beneficial effects involved in the embodiments of this application.

[0027] CAN (Controller Area Network) is a serial communication protocol bus for real-time applications. It uses twisted-pair cables to transmit signals and is one of the most widely used fieldbuses in the world. CAN is used for communication connections between various components in automobiles.

[0028] Before being officially released to customers, the system firmware of in-vehicle tablets undergoes various reliability and stability tests, one of which is power-on / off testing. This involves repeatedly powering on and off to determine the probability of various service anomalies, such as baseband drops, Wi-Fi and Bluetooth loading failures, and network connectivity issues. These services need to be reloaded every time the in-vehicle tablet is powered on. If any service fails to load during a boot, it will affect the user experience, and in severe cases, may even render the tablet unusable, requiring a power cycle to resolve the anomaly.

[0029] However, after power is restored, the abnormal situation may disappear with the previous power-off. The abnormal situation may be an occasional problem that occurs only once. When an abnormal situation occurs, the R&D personnel cannot accurately reproduce the test environment of a specific power-on test. They need to spend a lot of time troubleshooting and matching abnormal vehicle equipment. Even after locating the abnormal tablet, they cannot reproduce the test parameters at the time of the abnormality. This results in low test efficiency and poor test results.

[0030] To address the aforementioned issues, this application provides a testing system, method, and related apparatus for vehicle-mounted tablets. When an anomaly occurs during the testing of the vehicle-mounted tablet, the system keeps the tablet powered on continuously to store the device's operating parameters at the time of the anomaly. This improves the efficiency of testing the vehicle-mounted tablet and provides data support for subsequent analysis of the anomaly.

[0031] First, please refer to the details. Figure 1 , Figure 1 This is a schematic diagram of the architecture of a vehicle-mounted tablet testing system provided in an embodiment of this application, as shown below. Figure 1As shown, the vehicle-mounted tablet testing system 100 includes a sample rack 110, multiple vehicle-mounted tablets 120 to be tested mounted on the sample rack 110, a relay 130, and a host computer device 140 mounted on a computer equipment rack 111. The host computer device 140 includes a display 141. The communication port of the vehicle-mounted tablet 120 is electrically connected to the host computer device 140 via a CAN bus 150, and the vehicle-mounted tablet 120 is electrically connected to the relay 130 via a power port. Specifically, the vehicle-mounted tablet testing system 100 also includes an external power supply 160 connected to the relay 130. The power-on and power-off of the vehicle-mounted tablet 120 is controlled by the on / off state of the relay 130, thereby realizing the repeated power-on and power-off of the vehicle-mounted tablet 120.

[0032] The vehicle-mounted tablet 120 is used to respond to user configuration operations for the test application, generate a target test strategy, and install the test application on the vehicle-mounted tablet 120; respond to user startup operations for the test application and perform target tests according to the target test strategy; send a first power supply command to the relay 130 according to the target test strategy; and send a second power supply command to the relay 130 when at least one abnormal result exists among multiple test results of the vehicle-mounted tablet 120; the host computer device 140 is used to display abnormal information on the display 141 when an abnormal result of the vehicle-mounted tablet 120 is detected, and the abnormal information includes: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result and the frozen frame data of the abnormal vehicle-mounted tablet; the relay 130 is used to respond to the first power supply command, turn on and off at a preset period to realize repeated power-on and power-off of multiple vehicle-mounted tablets 120, the target test strategy includes the preset period; and to respond to the second power supply command and maintain the on state.

[0033] Specifically, the sample frame 110 and the computer equipment frame 111 serve as the load-bearing foundation, possessing the structural stability of the testing machine frame. A high-strength steel frame can be used for construction, with anchor bolts and other fixing methods to reduce test vibration. A specialized design is incorporated for the testing requirements of the vehicle-mounted tablet 120. The frame internally includes multiple independent power supply interfaces and a CAN bus 150 communication port. Each vehicle-mounted tablet 120 under test is fixed to the frame slot using standardized fixtures to ensure stable testing. The vehicle-mounted tablet 120 under test, as an in-vehicle intelligent terminal, has a baseband module, a WIFI module, a Bluetooth module, a GPS module, and a SIM card slot. It is configured with a CAN communication port and a power port, and has a built-in test application. It should be understood that... Figure 1The example shown only depicts two vehicle-mounted tablets 120; in actual applications, two or more can be used, with no limit on the number. Each relay 130 controls one vehicle-mounted tablet 120. The control terminal of the relay 130 is connected to the power port of the vehicle-mounted tablet 120 via a wire, and the input terminal is connected to an external power supply 160. The vehicle-mounted tablet 120 is connected to the host computer device 140 and the relays 130 via the CAN bus 150, enabling data interaction with multiple devices. The host computer device 140 also includes a display 141 and peripheral devices such as a speaker.

[0034] In other possible embodiments, the vehicle tablet 120 also includes a speaker; after at least one abnormal result exists among multiple test results of the vehicle tablet 120, the vehicle tablet is further configured to: perform an alarm action based on the abnormal result, the alarm action being used to prompt the user to handle the abnormal vehicle tablet, the alarm action including playing an alarm prompt through the speaker and displaying alarm information.

[0035] Specifically, the speaker can have multiple sets of standardized alarm audio built-in, matching different prompts according to the type of anomaly. For example, a continuous beep corresponds to a baseband loading failure, and an intermittent beep corresponds to a network outage. It also supports configuring the audio volume and duration via the in-vehicle tablet, and by default, it will continue to sound until manually turned off or the anomaly is resolved. In addition, when an anomaly occurs, the alarm information is displayed with multi-level visual prompts, including: a global prompt, a red floating window pops up at the top of the interface, displaying the device anomaly: Device_002 Baseband Loading Failure; a local marker, the test item corresponding to the anomaly in the in-vehicle tablet is highlighted with a flashing red border; and a details entry, with a built-in button to view the frozen frame, which directly jumps to the data details page based on the user's click, and the information includes the device identifier, anomaly type, anomaly time, number of power on / off cycles, etc.

[0036] As can be seen, in this embodiment, after displaying abnormal information, the vehicle-mounted tablet executes an alarm based on the abnormal result. This reduces the time spent troubleshooting abnormal vehicle-mounted tablets and helps system testing and maintenance personnel quickly locate abnormal vehicle-mounted tablets, thereby further improving the testing efficiency of the testing system.

[0037] Please refer to the details. Figure 2 , Figure 2 This is a schematic diagram of the hardware architecture of a vehicle-mounted tablet test site provided in an embodiment of this application, as shown below. Figure 2 As shown, an external power supply 160 is used to provide DC power, and a relay 130 is used to control the on / off connection of the external power supply to the vehicle-mounted tablet 120, thereby realizing the power-on / off control of the vehicle-mounted tablet 120. It should be understood that... Figure 2This includes multiple relays 130, two of which are shown here as an example; a vehicle-mounted tablet 120 is used for target testing; a sample rack 110 is used to place the vehicle-mounted tablet 120; and a host computer device 140 is used to store freeze frame data when abnormal results occur, based on the test results. Figure 2 The middle part is a laptop computer, and the host computer device 140 can also be an industrial control computer or a server.

[0038] Specifically, relay 130 includes relay display 131, see [link to relevant documentation]. Figure 3 , Figure 3 This is a schematic diagram of the interface of a relay display provided in an embodiment of this application, such as... Figure 3 As shown, the relay display 131 displays the power-on duration of the currently connected vehicle tablet 120 in the display box 1311 as 00:00:xx, the power-off duration in the display box 1312 as 00:00:xx, and the number of power-on and power-off cycles completed in the display box 1313 as xx times. This makes it easier for the operation and maintenance personnel of the test system to intuitively and efficiently obtain test details, and is more conducive to the operation and maintenance personnel to grasp the test progress.

[0039] In one possible embodiment, in displaying abnormal information, the host computer device 140 specifically performs the following: Figure 4 Chinese method, Figure 4 This is a schematic diagram illustrating a specific process for displaying abnormal information provided in an embodiment of this application, such as... Figure 4 As shown, the host computer device 140 performs the following steps: S310, retrieve the basic configuration data of the abnormal vehicle tablet at the time of the abnormality.

[0040] The basic configuration data includes the test project name, the total number of power-on / off cycles, and the number of power-on / off cycles completed. The target test strategy includes the test project name. The abnormal moment refers to the moment when at least one of the multiple test results is determined to be abnormal.

[0041] Specifically, the basic configuration data is the data configured by the user of the test system. Test items may include baseband detection, network detection, power detection, etc. The total number of power-on and power-off cycles is the total number of power-on and power-off cycles set by the user in the test configuration interface. The abnormal moment refers to the moment when the host computer device receives the test results of the vehicle tablet through the CAN bus and determines that any detection sub-item, such as baseband loading or WIFI connection, has failed to provide a service connection. It should be understood that the following users refer to the operation and maintenance personnel of this system.

[0042] S320: Obtain the hardware operating parameters and software service logs of the abnormal vehicle tablet at the time of the abnormality.

[0043] Specifically, hardware operating parameters are the real-time status data of hardware detection sub-items, such as power supply detection, clock frequency stability parameters, baseband and RF interface connection signal strength, SIM card slot power supply current, etc.; software service logs are the operation records of software detection sub-items, such as register cache detection read / write response time, encryption engine detection initialization result log, communication link detection handshake failure reason record, SIM card reading authentication error code, etc.

[0044] S330 packages basic configuration data, hardware operating parameters, and software service logs to generate freeze frame data.

[0045] Specifically, the packaging method can be to use a standardized data format, such as JSON, for encapsulation. The data header includes the test ID, the timestamp of the abnormal moment, and the device identifier. The main body is stored in layers according to basic configuration, hardware parameters, and software logs, and a data verification code is attached at the end.

[0046] As can be seen, in this embodiment, the host computer retrieves the basic configuration data of the malfunctioning vehicle tablet at the time of the anomaly, then obtains the hardware operating parameters and software service logs of the malfunctioning vehicle tablet at that time, and finally packages the basic configuration data, hardware operating parameters, and software service logs to generate freeze frame data. This allows system maintenance personnel to accurately reconstruct the test environment at the time of the vehicle tablet anomaly based on the freeze frame data, reducing the cost of reproducing intermittent anomalies, shortening the troubleshooting cycle, and providing reliable data support for anomaly analysis.

[0047] In other possible embodiments, the host computer device is further configured to: determine the anomaly type of the abnormal vehicle-mounted tablet and record the timestamp of the anomaly; generate test information based on the anomaly type, the timestamp of the anomaly, and the device identifier of the abnormal vehicle-mounted tablet; establish the association between the test information of the abnormal vehicle-mounted tablet and the frozen frame data; generate a mapping table based on the association and store the mapping table.

[0048] The host computer identifies the detection sub-item results uploaded by the vehicle-mounted tablet, such as baseband and RF interface connection failure in hardware detection or communication link handshake timeout in software detection, to determine the specific anomaly type. Subsequent system maintenance personnel can use a mapping table to quickly retrieve the frozen frame data at the time of the anomaly by inputting the test information of the vehicle-mounted tablet, facilitating anomaly analysis and determining the operational status of various service parameters within the vehicle-mounted tablet at the time of the anomaly.

[0049] Specifically, test information can be generated using a fixed field structure, such as: Device Identifier: Device_003 / Anomaly Type: Baseband Loading Failure / Timestamp: 2025-xx-xx15:00:00.123 / Test ID: xxxxx1, ensuring machine recognition and rapid human interpretation; a core index for correlation can also be established: using the test ID, device identifier, and the number of occurrences corresponding to the anomaly time as a unique correlation index, for example, test ID xxxxx1, device identifier Device_003, and number of occurrences 382 form a joint index, ensuring that one anomaly scenario corresponds to only one set of frozen frame data, avoiding confusion between multiple sets of data; an example mapping table is shown in Table 1: Table 1

[0050] In other possible embodiments, the host computer device has a built-in mapping library of detection sub-items and anomaly types. For example, SIM card reading failure is associated with SIM card authentication anomaly, and radio frequency data calibration error is associated with radio frequency module anomaly. When the test results of the vehicle tablet are received, the system automatically matches the rules in the library and outputs standardized anomaly type names. If a new anomaly result that is not preset occurs, it is marked as an unknown anomaly and a manual annotation prompt is triggered to prompt the user to name the unknown anomaly.

[0051] As can be seen, in this embodiment, the host computer determines the anomaly type of the abnormal vehicle-mounted tablet and records the timestamp of the anomaly; then it generates test information; next, it establishes the association between the test information of the abnormal vehicle-mounted tablet and the frozen frame data; finally, it generates a mapping table based on the association. This provides maintenance personnel with the ability to quickly pinpoint the abnormal scenario of a device at a specific time and during a specific power-on / off cycle through the mapping table, reducing the difficulty of reproducing abnormal situations and improving the efficiency of vehicle-mounted tablet anomaly testing.

[0052] In one possible embodiment, the in-vehicle tablet is equipped with a flash memory module; the in-vehicle tablet is further used for: recording a work log through the flash memory module when the in-vehicle tablet detects a system crash; ensuring that the data in the flash memory module is not lost when the in-vehicle tablet is powered on or off; performing a restart operation; and checking the flash memory module through a test application, obtaining the work log, and recording the automatic restart test count incremented by one; and clearing the data in the flash memory module.

[0053] System crashes and errors (oops) are typically caused by kernel-level abnormal operations. Common causes in in-vehicle tablet testing scenarios include: memory access errors, such as kernel programs attempting to read or write to non-existent memory addresses or accessing memory out of bounds; driver defects, such as hardware driver incompatibility with the kernel interface or driver execution of illegal instructions; resource contention; and instruction execution exceptions. When an in-vehicle tablet experiences an abnormal restart, the kernel triggers log writing to the FLASH memory module, and since the restart occurs within the power-on / off test cycle, the relay continues its power supply cycle; both simultaneously activate data protection.

[0054] When an OPS occurs, the vehicle-mounted tablet kernel detects the anomaly and immediately writes a log containing OPS details to a dedicated storage area reserved in the FLASH memory module. This area retains data even when power is off, preventing log loss during subsequent reboots. If the OPS causes system instability and triggers a reboot, or directly triggers a hardware watchdog reset, the test app will read the OPS log from the dedicated storage area in the flash memory module upon the next boot, synchronously update the count of abnormal reboots, and archive the logs for analysis. Furthermore, the data in the FLASH memory module is cleared to prepare for the next OPS; if an abnormal reboot occurs again, the above operations will be repeated.

[0055] As can be seen, in this embodiment, when the in-vehicle tablet detects a system crash, it records a work log through the flash memory module; performs a restart operation; and checks the flash memory module through a test application, obtains the work log, increments the automatic restart test count by one, and clears the data in the flash memory module. This avoids missed test detections due to missed restart anomalies, fills the testing gap for overall system anomaly restarts, and, in conjunction with the freeze frame mechanism, constructs a multi-faceted and multi-dimensional anomaly testing system, solving the problem of the difficulty in reproducing occasional anomalies in in-vehicle tablet testing.

[0056] In one possible embodiment, in responding to a user's configuration operation for the test application, the in-vehicle tablet is specifically configured to: respond to a user's interface launch operation by displaying the main interface of the test application, the main interface of the test application including: a project creation control and a test configuration control; respond to a user's trigger operation on the test configuration control by displaying a test configuration interface, the test configuration interface including: at least one target test item and a test launch control, the target test item being determined based on the user's configuration operation; respond to a user's selection operation on the test configuration interface by determining the target test item selected by the user; and respond to a user's configuration operation on the test configuration interface by determining the target number of times for the target test strategy.

[0057] Specifically, please refer to Figure 5 , Figure 5This is a schematic diagram of the main interface of a test application provided in an embodiment of this application, such as... Figure 5 As shown, the main interface 40 of the test application includes a project creation control 41 and a test configuration control 42; in response to a user's trigger operation 43 on the test configuration control 42, the test configuration interface is displayed. It should be understood that the trigger operation 43 refers to the user touching the control 42 with their finger... Figure 1 The operation of the touchscreen on the vehicle-mounted tablet 120 is shown.

[0058] Among them, the project creation control 41 is used to provide users with the ability to create new testing projects, such as baseband function testing and communication link testing. It supports custom project names and adding testing sub-items, including hardware and software sub-items. The test configuration control 42, when clicked, enters the parameter setting stage, which is the intermediate stage connecting project creation and test startup.

[0059] Specifically, please refer to Figure 6 , Figure 6 This is a schematic diagram of a test configuration interface provided in an embodiment of this application, such as... Figure 6 As shown, the test configuration interface 50 includes a test information display bar 51, a test item display bar 52, a test start control 53, and a test count display bar 54. The test information display bar 51 includes a test name bar 511 and a test ID bar 512. The test item display bar 52 includes a preset item bar 521 and a target test item display bar 522. The test name bar 511 includes the content of the Xth power-on test, and the test ID bar 512 includes the test ID content of xxxxx1. The preset item bar 521 contains user-defined test item labels, such as test item 1, test item 2, test item 3… test item N, for user selection. The items selected by the user in the preset item bar 521 will be displayed in the target test item display bar 522. Figure 6 The baseband detection, network monitoring, location detection, BT detection, etc., are shown; the start test control 53 can be as follows: Figure 6 The Start button is shown; the Test Count display bar 54 is a display bar for users to input a custom number of tests, such as displaying Test Count: 500.

[0060] The user's selection operations include clicking the labels in the preset item bar 521 or dragging and sorting to adjust the execution order of the items. The user can input a custom number of tests by entering a specific number in the test count display bar 54 or by setting the number of tests using a slider, such as 100-5000 times.

[0061] As can be seen, in this embodiment, by displaying the main interface of the test application on the in-vehicle tablet, responding to user trigger operations on the test configuration controls, displaying the test configuration interface, responding to user selection operations on the test configuration interface, determining the target test item selected by the user, and responding to user configuration operations on the test configuration interface to determine the target number of times the target test strategy is performed. This enables personalized configuration of in-vehicle tablet test items, meeting flexible and ever-changing testing needs. Users do not need to design their own test strategies; the system generates test strategies based on user configuration operations, improving the freedom and efficiency of creating in-vehicle tablet tests.

[0062] In one possible embodiment, before responding to a user's trigger operation on the test configuration control, the vehicle-mounted tablet is further configured to: respond to a user's trigger operation on the project creation control, displaying a test project creation interface, the test project creation interface including: a test project information bar and test sub-projects, the test project information including the name, tag, and identifier of the test project, and test sub-projects referring to multiple sub-items associated with the target test project; respond to a user's input operation on the test project information bar, determining the name of the target test project; respond to a user's project configuration operation on the test project information bar, determining the tag of the target test project, the project configuration operation referring to an input operation or a selection operation; generate the identifier of the target test project and the test sequence of the test sub-projects based on the tag of the target test project; and generate the target test project based on the test project information and the test sequence of the test sub-projects.

[0063] The test project information section records basic project attributes, including project name, category label, project ID, etc., and serves as an input or display area. Test sub-projects are specific test items associated with the target project, such as hardware test sub-projects: power supply, clock, interface, etc., and software test sub-projects: registers, encryption engine, communication link, etc. The identifier is a unique code for the test project, used for internal system identification and data association. The test sequence is the execution order of the sub-projects, which is automatically sorted according to the labels. For example, the default label sequence for hardware tests is: power supply test to clock test to interface test, ensuring that the hardware is ready before executing the sub-projects that depend on it.

[0064] Specifically, please refer to Figure 7 , Figure 7 This is a schematic diagram of a test project creation interface provided in an embodiment of this application, such as... Figure 7As shown, the test project creation interface 60 includes a test project information bar 61 and test sub-projects 62. The test project information bar 61 includes a test project name bar 611, a test project label bar 612, a project ID bar 613, and a first confirmation control 614. The test sub-projects 62 include hardware function test boxes 621, including hardware test sub-item 1, hardware test sub-item 2, hardware test sub-item 3 and a settings button, and software function test boxes 622, including software test sub-item 1, software test sub-item 2, software test sub-item 3 and a settings button. The test project creation interface 60 also includes a second confirmation control 63.

[0065] As can be seen, in this embodiment, the vehicle-mounted tablet displays the test project creation interface in response to the user's trigger operation on the project creation control, and determines the name of the target test project in response to the user's input operation on the test project information bar. It also determines the tag of the target test project in response to the user's project configuration operation on the test project information bar, and generates the target test project's identifier and the test sequence of the test sub-projects based on the target test project's tag. Finally, it generates the target test project based on the test project information and the test sequence of the test sub-projects. In this way, the association between test project tags, the sub-project database, and the test sequence is established, providing users with an efficient way to configure test projects and generate target test strategies, thus improving the testing efficiency of the vehicle-mounted tablet.

[0066] In one possible embodiment, in responding to a user's project configuration operation on the test project information bar and determining the label of the target test project, the vehicle-mounted tablet is specifically used to: display multiple test project labels when the user's project configuration operation is a selection operation, wherein the multiple test project labels are project labels pre-stored in the vehicle-mounted tablet; and determine the label of the target test project in response to the user's selection operation on the multiple test project labels.

[0067] The preset labels are pre-configured and stored locally on the vehicle-mounted tablet by testers or system administrators. Examples include labels for baseband testing scenarios such as power connection, 4G baseband, 5G baseband, and signal generator. When a user selects a label in the label configuration area of ​​the test project creation interface, the preset label list automatically pops up for the user to choose from. Furthermore, different color schemes can be used for different label categories, such as blue for hardware labels and green for software labels, and the usage frequency can be indicated, such as 4G baseband (high frequency), guiding users to prioritize standardized and highly reusable test labels.

[0068] Once the labels are determined, they enable accurate classification of projects and provide a basis for generating identification numbers and matching test sub-items. For example, the baseband RF interface label corresponds to the interface detection-related sub-item, which is the link between project naming and sub-item configuration.

[0069] Please refer to the details. Figure 8 , Figure 8 This is a schematic diagram of the interface of a test item information bar provided in an embodiment of this application, such as... Figure 7 The test item label bar 612, as shown, displays multiple test item labels 72 after responding to the user's item configuration operation 71 (selection operation). Based on the user's selection operation 73 for multiple test item labels, the label of the target test item is checked, for example... Figure 8 The power connection label 74 and the 4G baseband label 75 are shown as checked.

[0070] As can be seen, in this embodiment, the vehicle-mounted tablet displays multiple test item tags in response to the user's project configuration operation, and then determines the tag of the target test item in response to the user's selection operation of multiple test item tags. In this way, standardized test tags make project classification and retrieval more accurate, and through the linkage between test item tags and sub-items, it avoids situations such as missing key sub-items or incorrectly selecting irrelevant sub-items, thereby reducing the error rate in the test configuration process.

[0071] In one possible embodiment, in responding to a user's project configuration operation in the test project information bar and determining the tag of the target test project, the vehicle-mounted tablet is specifically used to: when the user's project configuration operation is an input operation, retrieve a test database from a host computer device, the test database including a mapping table of test project tags and test sub-projects; analyze and confirm the test sub-project corresponding to the user's project configuration operation through the host computer device; and determine the tag of the target test project based on the test sub-project and the test database.

[0072] The test database is a structured data collection stored on the host computer, containing a mapping relationship between test item tags and test sub-items. For example, the vehicle-to-everything (V2X) communication tag corresponds to sub-items such as 5G module antenna signal strength testing. For instance, when a user enters custom content, such as "SIM card communication service," in the tag input box of the test item information column, the on-board tablet sends a database retrieval request to the host computer via the CAN bus. This resolves the issue of user-input tags not being associated with system sub-items, ensuring that custom tags still correspond to valid test content.

[0073] The host computer is responsible for parsing the user-inputted tag text and matching sub-items. Based on the host computer's database, it uses keyword matching (e.g., if the user inputs "vehicle networking") to match tag mapping relationships containing "vehicle networking" and "5G IoT" and semantic association (e.g., if the user inputs "vehicle networking"), it matches related sub-items such as "cockpit interaction" and "touch and voice" to determine the most likely test sub-items). It then returns the 3-5 sub-items with the highest matching degree (e.g., if the user inputs "intelligent cockpit interaction") to return "touch response test," "voice recognition detection," and "screen display calibration," which are used by the system to generate tags subsequently, thus solving the problem of sub-item matching failure caused by non-standard user input tag descriptions.

[0074] If the matching degree between the input tag and a sub-item of a tag in the database is ≥90%, the tag is directly reused. For example, if the input tag "vehicle networking function" matches all sub-items of the "vehicle networking communication" tag in the database, the tag is determined to be "vehicle networking communication". If it is a brand new tag, a new tag is created and associated with the sub-items obtained from the analysis, and stored in the database. For example, "intelligent cockpit interaction" is used as a new tag and associated with the "touch" and "voice" sub-items to realize the dynamic expansion of tags.

[0075] As can be seen, in this embodiment, the vehicle-mounted tablet, in response to the user's project configuration operation, retrieves the test database from the host computer. The host computer then analyzes and confirms the test sub-items corresponding to the user's project configuration operation, and determines the tags for the target test items based on the test sub-items and the test database. This avoids the problem of inconsistencies between user input and tags with the same meaning, solves the problem of consistency in the inherent meaning of custom tags, reduces the need for users to manually associate sub-items, improves the efficiency of test item configuration, and thus further improves the efficiency of vehicle-mounted tablet testing.

[0076] In one possible embodiment, the host computer device is further configured to: display a test result interface of multiple vehicle-mounted tablets after completing the target test strategy via the display of the host computer device. The test result interface includes: the current display interface of multiple vehicle-mounted tablets, the test results of multiple vehicle-mounted tablets, and test event handling controls; wherein, the test results include: test status, number of successful tests, and number of failed tests, and the test event handling controls include: log capture control, restart control, ignore error control, and alarm control.

[0077] The test results interface serves as an interactive window for the host computer to centrally manage multiple devices, integrating test data and operation entry points scattered across multiple vehicle tablets into a single interface. The current display interfaces of multiple vehicle tablets show the current screen of each tablet's test application in real time. For example, when a tablet experiences a baseband loading failure, its local interface's error message will be simultaneously displayed in the corresponding window on the host computer. A log capture control, when clicked, synchronously captures the corresponding tablet's frozen frame data and real-time logs. A restart control allows remote control of abnormal tablets to restart and re-execute tests, avoiding manual power plugging and unplugging. An ignore error control is used for non-critical anomalies, such as a single SIM card read timeout; clicking it skips the anomaly and continues the test without interrupting the loop. An alarm control stops the horn alarm and interface alarm prompts triggered by abnormal tablets.

[0078] Specifically, it also includes global function controls, such as the Clear History Data control, which is used to delete historical results of completed tests; the Turn Off Alarm control, which is used to achieve global mute and adapt to scenarios where multiple devices malfunction simultaneously; the Exit Application control, which is used to close the host computer test management software and automatically saves unfinished test data before exiting; the Custom Settings control, which is used to configure parameters such as interface refresh rate, log storage path, and alarm volume; and the Turn Off Startup control, which is used to control whether the test application runs automatically when the vehicle tablet is powered on.

[0079] Specifically, please refer to Figure 9 , Figure 9 This is a schematic diagram of a host computer device test result interface provided in an embodiment of this application, such as... Figure 9 As shown, the test result interface 80 displayed on the monitor of the host computer device includes: the current display interface 81 of multiple vehicle tablets, the test results of multiple vehicle tablets, and test event handling controls; among which, the test results of multiple vehicle tablets include: test name 821, number of successful tests 822, number of failed tests 823, and test status 824; the test event handling controls also include: log capture control 831, restart control 832, ignore error control 833, and alarm control 834; the test result interface 80 includes: clear historical data control 84, turn off alarm control (single time) 85, exit application control 86, custom settings control 87, and turn off startup control 88.

[0080] As can be seen, in this embodiment, the host computer displays the test results interface of multiple vehicle-mounted tablets after they have completed the target test strategy via a monitor. This includes the current display interface of the multiple vehicle-mounted tablets, the test results of the multiple vehicle-mounted tablets, and test event handling controls. In this way, system maintenance personnel do not need to inspect each device individually; a single screen can monitor the test status of multiple vehicle-mounted tablets, improving test management efficiency and increasing the accuracy of maintenance personnel in locating abnormal vehicle-mounted tablets.

[0081] This application also provides a testing method for an in-vehicle tablet, which is applied to, for example... Figure 1 The vehicle-mounted tablet 120 in the test system 100 shown is described in detail. Figure 10 , Figure 10 This is a flowchart illustrating a testing method for an in-vehicle tablet provided in an embodiment of this application, as shown below. Figure 10 As shown, the method includes the following steps: S901: In response to the strategy determined by the user's configuration operation for the test application, generate the target test strategy.

[0082] The target test strategy is determined in response to user configuration operations on the test application, which is installed on the in-vehicle tablet. The configuration operations involve the user first configuring test items through a project creation control, such as baseband detection, which includes sub-items like power detection and clock detection; then, using the test configuration control, selecting the current test item and setting the number of power on / off cycles. The final generated strategy is the target test strategy.

[0083] S902. According to the target test strategy, send the first power supply command to the relay.

[0084] The first power supply command instructs the relay to turn on and off at a preset cycle to control the repeated power-on and power-off of the vehicle-mounted tablet. The preset cycle is defined by the target test strategy, such as powering on for 30 seconds and then powering off for 10 seconds, repeating this 500 times to ensure the tablet completes power-on loading and testing. After receiving the command, the relay periodically turns on or off to achieve the repeated power-on and power-off of the vehicle-mounted tablet.

[0085] S903. Perform tests according to the target test strategy and obtain multiple test results. When at least one abnormal result exists among the multiple test results, send a second power supply command to the relay.

[0086] The second power supply command is used to instruct the relay to remain in the on state. When an abnormal result occurs, power is continuously supplied to the tablet to preserve the abnormal situation and instruct the relay to remain in the on state to prevent the abnormality from disappearing when power is off, thus preserving the hardware or software state at the time of the abnormality for subsequent analysis.

[0087] S904. Send a recording message to the host computer device. The recording message is used to instruct the host computer device to record the abnormal information and display the abnormal information on the display.

[0088] The anomaly information includes: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result, and the frozen frame data of the abnormal vehicle-mounted tablet. The device identifier of the abnormal vehicle-mounted tablet is used to distinguish multiple tablets; the frozen frame data of the abnormal vehicle-mounted tablet contains basic configuration data such as test items, power-on / off counts, hardware parameters, and software logs, which is a complete data set of the abnormal scenario and state.

[0089] As can be seen, in this embodiment, the target test strategy of the vehicle-mounted tablet is first received; then, according to the target test strategy, a first power supply command is sent to the relay, which instructs the relay to turn on and off at a preset cycle to control the repeated power-on and power-off of the vehicle-mounted tablet; then, multiple test results of multiple vehicle-mounted tablets are judged, and when at least one abnormal result exists among the multiple test results, a second power supply command is sent to the relay, which instructs the relay to remain in the on state; simultaneously, the abnormal information is recorded and displayed on the display. Thus, when an abnormality occurs during the testing of the vehicle-mounted tablet, by maintaining the continuous power-on state of the vehicle-mounted tablet, freeze frame data at the time of the tablet abnormality is generated and stored, facilitating the reproduction of the test environment at the time of the abnormality. This provides data support for subsequent testers to trace the tablet's operating parameters at the time of the abnormality, which is beneficial to improving the efficiency of vehicle-mounted tablet testing.

[0090] The above mainly describes the solutions of the embodiments of this application from the perspective of the method execution process. It is understood that, in order to achieve the above functions, the host computer device includes the corresponding hardware structure and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments provided herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0091] This application embodiment can divide the electronic device into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0092] and Figure 10 The implementation is consistent with the previous one; please refer to [link / reference]. Figure 11 , Figure 11 This is a functional unit block diagram of a vehicle-mounted tablet testing device provided in an embodiment of this application. The vehicle-mounted tablet testing device 1010 is applied to, for example... Figure 1The vehicle-mounted tablet 120 in the vehicle-mounted tablet testing system 100 shown, and the vehicle-mounted tablet testing device 1010 include: a response unit 1011, a first instruction unit 1012, a second instruction unit 1013, and a third instruction unit 1014; wherein, the response unit 1011 is specifically used to respond to the strategy determined by the user for the configuration operation of the test application, and generate a target test strategy, the test application being installed in the vehicle-mounted tablet; the first instruction unit 1012 is specifically used to send a first power supply command to the relay according to the target test strategy, the first power supply command being used to instruct the relay to turn on and off at a preset cycle. The system has several functions: a first, to control the repeated power-on and power-off of the vehicle-mounted tablet; a second instruction unit 1013, specifically used to perform tests according to the target test strategy and obtain multiple test results; when at least one abnormal result exists among the multiple test results, a second power supply instruction is sent to the relay, which is used to instruct the relay to remain in the on state; and a third instruction unit 1014, specifically used to send a recording message to the host computer device, which is used to instruct the host computer device to record abnormal information and display the abnormal information on the display, the abnormal information including: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result, and the frozen frame data of the abnormal vehicle-mounted tablet.

[0093] It is understood that since the method embodiments and the device embodiments are different presentations of the same technical concept, the content of the method embodiment section in this application should be adapted to the device embodiment section in a synchronous manner, and will not be repeated here.

[0094] Figure 12 This is a structural block diagram of an electronic device provided in an embodiment of this application. For example... Figure 12 As shown, the electronic device 1100 may include one or more components: a processor 1101 and a memory 1102 coupled to the processor 1101, wherein the memory 1102 may store one or more computer programs, which may be configured to implement the methods described in the examples above when executed by one or more processors 1101. Figure 12 The electronic device 1100 shown can be the one described above. Figure 1 The vehicle-mounted tablet 120.

[0095] Processor 1101 may include one or more processing cores. Processor 1101 connects to various parts within the electronic device 1100 using various interfaces and lines, and performs various functions and processes data of the electronic device 1100 by running or executing instructions, programs, code sets, or instruction sets stored in memory 1102, and by calling data stored in memory 1102. Optionally, processor 1101 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 1101 may integrate one or more of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. It is understood that the aforementioned modem may also not be integrated into processor 1101, but may be implemented separately through a communication chip.

[0096] The memory 1102 may include random access memory (RAM) or read-only memory (ROM). The memory 1102 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 1102 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), and instructions for implementing the various method examples described above. The data storage area may also store data created during the use of the electronic device 1100.

[0097] It is understood that the electronic device 1100 may include more or fewer structural elements than those shown in the above block diagram, such as a power module, physical buttons, WiFi (Wireless Fidelity) module, speaker, Bluetooth module, sensor, etc., without limitation.

[0098] This application also provides a computer storage medium storing a computer program / instructions thereon, which, when executed by a processor, implements some or all of the steps of any of the methods described in the above method embodiments.

[0099] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments.

[0100] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0101] In the several embodiments provided in this application, it should be understood that the disclosed methods, apparatuses, and systems can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and there may be other division methods in actual implementation; 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, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0102] 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.

[0103] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit described above can be implemented in hardware or in the form of hardware plus software functional units.

[0104] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute partial steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes: a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, volatile memory, or non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM), etc., which are various media capable of storing program code.

[0105] While the present invention has been disclosed above, it is not limited thereto. Any person skilled in the art can easily conceive of variations or substitutions without departing from the spirit and scope of the present invention, and various modifications and alterations can be made, including combinations of the different functions and implementation steps described above, as well as software and hardware implementation methods, all of which are within the protection scope of the present invention.

Claims

1. A testing system for an in-vehicle tablet, characterized in that, The system includes a sample rack, multiple vehicle-mounted tablets to be tested mounted on the sample rack, a relay, and a host computer device mounted on a computer equipment rack. The host computer device includes a display. The communication ports of the vehicle-mounted tablets are electrically connected to the host computer device and the relays via a CAN bus. The vehicle-mounted tablet is used to respond to user configuration operations for the test application, generate a target test strategy, wherein the test application is installed on the vehicle-mounted tablet; respond to user startup operations for the test application, perform target testing according to the target test strategy; send a first power supply command to the relay according to the target test strategy; and send a second power supply command to the relay when at least one abnormal result exists among multiple test results of the vehicle-mounted tablet. The host computer device is used to display abnormal information on the display when it detects the abnormal result of the vehicle-mounted tablet. The abnormal information includes: the device identifier of the abnormal vehicle-mounted tablet corresponding to the abnormal result and the frozen frame data of the abnormal vehicle-mounted tablet. The relay is used to respond to the first power supply command by turning on and off at a preset period to enable repeated power-on and power-off of multiple vehicle-mounted tablets, and the target test strategy includes the preset period; and to respond to the second power supply command by maintaining the on state.

2. The system according to claim 1, characterized in that, Regarding the display of abnormal information, the host computer device is specifically used for: Retrieve the basic configuration data of the abnormal vehicle-mounted tablet at the abnormal time. The basic configuration data includes the test item name, the total number of power-on and power-off times, and the number of power-on and power-off times that have been completed. The target test strategy includes the test item name. The abnormal time refers to the time when it is determined that at least one of the multiple test results is abnormal. Obtain the hardware operating parameters and software service logs of the abnormal vehicle-mounted tablet at the time of the abnormality; The basic configuration data, hardware operating parameters, and software service logs are packaged to generate the freeze frame data.

3. The system according to claim 2, characterized in that, The host computer device is also specifically used for: Determine the anomaly type of the abnormal vehicle-mounted tablet and record the timestamp of the anomaly. Test information is generated based on the anomaly type, the timestamp of the anomaly time, and the device identifier of the abnormal vehicle-mounted tablet. Establish the correlation between the test information of the abnormal vehicle-mounted tablet and the frozen frame data; A mapping table is generated based on the association relationship, and the mapping table is stored.

4. The system according to any one of claims 1-3, characterized in that, The in-vehicle tablet is equipped with a flash memory module; the in-vehicle tablet is also specifically used for: When the vehicle-mounted tablet detects a system crash, it records a work log through the flash memory module; the data in the flash memory module is not lost when the vehicle-mounted tablet is powered on or off. Perform a restart operation; and, The test application checks the flash memory module, obtains the working log, and records the number of automatic restart tests plus one. Clear the data in the flash memory module.

5. The system according to claim 4, characterized in that, In responding to user configuration operations for the test application, the in-vehicle tablet is specifically used for: In response to the user's interface startup operation, the main interface of the test application is displayed, which includes: project creation controls and test configuration controls; In response to the user's trigger operation on the test configuration control, a test configuration interface is displayed. The test configuration interface includes at least one target test item and a test start control. The target test item is determined based on the user's configuration operation. In response to the user's selection operation on the test configuration interface, determine the target test item selected by the user; and in response to the user's configuration operation on the test configuration interface, determine the target number of times the target test strategy is performed.

6. The system according to claim 5, characterized in that, Before responding to the user's trigger operation on the test configuration control, the in-vehicle tablet is further configured to: In response to the user's trigger operation on the project creation control, a test project creation interface is displayed. The test project creation interface includes: a test project information bar and test sub-projects. The test project information includes the name, tag, and identifier of the test project. The test sub-projects refer to multiple sub-items associated with the target test project. In response to the user's input operation on the test item information field, determine the name of the target test item; In response to the user's project configuration operation in the test project information bar, determine the label of the target test project, where the project configuration operation refers to an input operation or a selection operation; Based on the tags of the target test item, generate the identifier of the target test item and the test sequence of the test sub-item; The target test project is generated based on the test project information and the test sequence of the test sub-projects.

7. The system according to claim 6, characterized in that, In responding to the user's configuration operation for the test item information bar and determining the tag of the target test item, the vehicle-mounted tablet is specifically used for: When the user's project configuration operation is a selection operation, multiple test project tags are displayed. These multiple test project tags are project tags pre-stored in the vehicle tablet. In response to the user's selection of tags for the multiple test items, the tag for the target test item is determined.

8. The system according to claim 6, characterized in that, In responding to the user's configuration operation for the test item information bar and determining the tag of the target test item, the vehicle-mounted tablet is specifically used for: When the user's project configuration operation is an input operation, the test database is retrieved from the host computer device. The test database includes a mapping table between test project tags and test sub-projects. The host computer device is used to analyze and confirm the test sub-projects corresponding to the user's project configuration operations; as well as, The tags for the target test item are determined based on the test sub-items and the test database.

9. The system according to claim 1, characterized in that, The host computer device is also specifically used for: The host computer device displays the test results interface after the multiple vehicle-mounted tablets have completed the target test strategy. The test results interface includes: the current display interface of the multiple vehicle-mounted tablets, the test results of the multiple vehicle-mounted tablets, and test event handling controls. The test results include: test status, number of successful tests, and number of failed tests. The test event handling controls include: log capture control, restart control, ignore error control, and alarm control.

10. A testing method for a vehicle-mounted tablet, characterized in that, A vehicle-mounted tablet is used in a testing system for vehicle-mounted tablets. The testing system includes a sample rack, multiple vehicle-mounted tablets to be tested mounted on the sample rack, a relay, and a host computer mounted on a computer equipment rack. The host computer includes a display. The communication ports of the vehicle-mounted tablets are electrically connected to the host computer and the relays via a CAN bus. The method includes: In response to the strategy determined by the user's configuration operation for the test application, a target test strategy is generated, wherein the test application is installed in the vehicle tablet. According to the target test strategy, a first power supply command is sent to the relay. The first power supply command is used to instruct the relay to turn on and off at a preset cycle in order to control the repeated power-on and power-off of the vehicle tablet. Tests are performed according to the target testing strategy, resulting in multiple test results. When at least one abnormal result is found among the multiple test results, a second power supply command is sent to the relay, the second power supply command instructing the relay to remain in the on state; and... A recording message is sent to the host computer device. The recording message is used to instruct the host computer device to record the abnormal information and display the abnormal information on the display. The abnormal information includes: the device identifier of the abnormal vehicle tablet corresponding to the abnormal result and the frozen frame data of the abnormal vehicle tablet.

Citation Information

Patent Citations

  • Power-off testing device of solid-state drive and testing method

    CN106294050A

  • Equipment power-on and power-off test system and equipment power-on and power-off test method

    CN116665565A

  • Whole vehicle function detection method and system, electronic equipment and storage medium

    CN119247928A

  • A method for testing electronic devices

    WO2006024698A1