Boot-up detection system and method

Abstract

The application relates to a start-up detection system and method. In the application, a display graphic code is displayed by a to-be-tested device during a start-up process; a scanning device performs a graphic code scanning operation after the to-be-tested device displays the graphic code; if the scanning is successful, the graphic code scanning operation is performed again after a first set time interval; the first set time interval is consistent with a qualified start-up time interval of the to-be-tested device; and a control device determines a start-up detection result of the to-be-tested device according to a scanning record of the graphic code. The application uses the graphic code to identify the start-up process of the to-be-tested device; the start-up time point of the to-be-tested device can be accurately recorded by scanning the graphic code; and whether the start-up time interval meets the requirements can be judged according to the scanning record of the graphic code. Compared with a traditional mode, the application automates the detection of the start-up time interval, saves human resources, reduces errors caused by human factors, improves the accuracy of start-up testing, and is helpful for repeated detection of the same to-be-tested device.

Description

Technical Field

[0001] This application relates to the field of testing technology, and in particular to a power-on detection system and method. Background Technology

[0002] For smart devices (such as mobile phones, tablets, and televisions), boot time can indirectly reflect the device's hardware performance, memory status, and device loading status. Therefore, boot time is a necessary performance testing metric, and multiple tests are required to verify the test results.

[0003] Traditional testing methods typically involve testers timing the boot time to record the duration of operation. However, this method requires a significant investment of manpower, and due to the subjectivity of the testing process, the test results are prone to significant deviations. Furthermore, it is not suitable for scenarios involving a large number of repeated tests. Summary of the Invention

[0004] Therefore, it is necessary to provide a power-on detection system and method to address the aforementioned technical problems. This system and method can automate the detection of power-on duration, save human resources, reduce errors caused by human factors, and improve the accuracy of power-on testing.

[0005] In a first aspect, this application provides a power-on detection system, including a device under test, a scanning device, and a control device; wherein:

[0006] The device under test is used to display graphic codes during the power-on process;

[0007] The scanning device is used to perform a graphic code scanning operation after the graphic code is displayed on the device under test; if the scan is successful, the graphic code scanning operation is performed again after a first set time interval; the first set time interval is consistent with the qualified power-on time of the device under test;

[0008] Control equipment is used to determine the power-on test result of the device under test based on the scan record of the graphic code.

[0009] In one embodiment, the system further includes a network backend; the network backend is connected to the scanning device and the control device via a network;

[0010] The scanning device is also used to send a scan event to the network backend after a successful scan;

[0011] The network backend is used to generate scan records with graphic codes based on scan events; if the scan record with graphic codes determines that the scanning device has scanned the graphic code more than once within a second set time period after a successful scan, then an abnormal information is sent back to the control device.

[0012] The control equipment is also used to determine, based on abnormal information, that the power-on test result of the device under test is an abnormal power-on.

[0013] In one embodiment, the control device is further configured to, if no abnormal information is received from the network backend within the second set time period, clear the scanning record of the graphic encoding in the network backend and determine that the power-on test result of the device under test is normal.

[0014] In one embodiment, the scanning device is further configured to count down according to a first set duration after a successful scan; and to perform the graphic encoding scanning operation again after the countdown ends.

[0015] In one embodiment, the scanning device and the control device are connected via a data cable;

[0016] The scanning device is also used to send a scanning event to the control device after a successful scan;

[0017] The control device is also used to generate a graphic-coded scan record based on the scan event; and to enter a countdown based on a first set duration; and after the countdown ends, to control the scanning device to perform the graphic-coded scan operation again.

[0018] In one embodiment, the control device is connected to the device under test via a serial cable;

[0019] The control device is also used to read the log records of the device under test via a serial port when the power-on detection result of the device under test is determined to be an abnormal power-on. The read log records are then saved.

[0020] In one embodiment, the control device is further configured to send a power-on command to the device under test;

[0021] The device under test is also used to power on according to the power-on command and to display graphic codes during the power-on process;

[0022] The control device is also used to detect the existence of a graphic-coded scan record before sending the power-on command; if it exists, the graphic-coded scan record is cleared.

[0023] In one embodiment, the scanning device is further configured to perform a graphic encoding scanning operation again after an interval of a target duration; the target duration is a duration obtained by correcting the qualified power-on duration of the device under test based on the scanning response time.

[0024] In one embodiment, the system includes multiple test groups and control devices; each test group consists of a device under test (DUT) and a scanning device; wherein the DUT displays a different graphic code during the power-on process in each test group.

[0025] Secondly, this application also provides a power-on detection method, which is applied to the power-on detection system described in the first aspect above; the system includes a device under test, a scanning device, and a control device; the method includes:

[0026] The device under test displays a graphic code during the power-on process;

[0027] The scanning device performs a graphic code scanning operation after the device under test displays the graphic code; if the scan is successful, the graphic code scanning operation is performed again after a first set time interval; the first set time interval is consistent with the qualified power-on time of the device under test;

[0028] The control equipment determines the power-on test result of the device under test based on the scanning record of the graphic code.

[0029] In the aforementioned power-on detection system and method, the device under test (DUT) displays a graphic code during the power-on process. A scanning device performs a graphic code scanning operation after the DUT displays the graphic code. If the scan is successful, the graphic code scanning operation is performed again after a first set time interval. The first set time interval is consistent with the qualified power-on time of the DUT. The control device determines the power-on detection result of the DUT based on the graphic code scanning record. Through this method, the power-on process of the DUT can be identified using graphic codes; by scanning the graphic codes, the power-on time point of the DUT can be accurately recorded; and based on the graphic code scanning record, it can be determined whether the power-on time meets the requirements. Compared with traditional methods, the power-on detection system of this application automates the detection of power-on time, saves manpower, reduces errors caused by human factors, improves the accuracy of power-on testing, and facilitates repeated testing of the same DUT. The power-on detection system of this application has low complexity, low equipment requirements, low setup cost, and is easy to deploy and implement. Attached Figure Description

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

[0031] Figure 1 This is a schematic diagram of the power-on detection system in one embodiment;

[0032] Figure 2 This is a schematic diagram of the power-on detection system in another embodiment;

[0033] Figure 3This is a schematic diagram illustrating the interaction process of various devices in one embodiment;

[0034] Figure 4 This is a schematic diagram of a power-on detection system including multiple test groups in one embodiment;

[0035] Figure 5 This is a schematic diagram of a power-on detection system including multiple test groups in another embodiment;

[0036] Figure 6 This is a flowchart illustrating a power-on detection method in one embodiment. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0038] Understandably, traditional testing methods typically involve testers timing the boot time to record the duration of operation. However, this method requires a significant investment of manpower, and due to the subjectivity of the testing process, the test results can be highly biased. Furthermore, it is not suitable for scenarios involving a large number of repeated tests.

[0039] Another testing method involves using a camera to record the boot process of a smart device and recording the boot time by playing back the video. This method also requires human intervention, resulting in high labor costs.

[0040] Alternatively, a relatively accurate testing method exists: using a camera to record the boot process of a smart device, then using image analysis technology to analyze the video frame by frame to find keyframes and record the boot duration. This method requires significant computing resources from the analysis equipment, resulting in higher equipment costs.

[0041] Based on this, this application provides a power-on detection system and method. During the power-on process, the device under test (DUT) displays a graphic code. A scanning device performs a graphic code scanning operation after the DUT displays the graphic code. If the scan is successful, the graphic code scanning operation is performed again after a first set time interval. The first set time interval is consistent with the qualified power-on time of the DUT. A control device determines the power-on detection result of the DUT based on the graphic code scanning record. Through the above method, the power-on process of the DUT can be identified using graphic codes; by scanning the graphic codes, the power-on time point of the DUT can be accurately recorded; and based on the graphic code scanning record, it can be determined whether the power-on time meets the requirements. Compared with traditional methods, the power-on detection system of this application automates the detection of power-on time, saves manpower, reduces errors caused by human factors, improves the accuracy of power-on testing, and facilitates repeated testing of the same DUT. The power-on detection system of this application has low complexity, low equipment requirements, low setup cost, and is easy to deploy and implement.

[0042] In one exemplary embodiment, such as Figure 1 As shown, a power-on detection system is provided, including a device under test (DUT) 10, a scanning device 20, and a control device 30; wherein: the DUT 10 is used to display a graphic code during the power-on process; the scanning device 20 is used to perform a graphic code scanning operation after the DUT 10 displays the graphic code; if the scan is successful, the graphic code scanning operation is performed again after an interval of a first set time; the first set time is consistent with the qualified power-on time of the DUT 10; the control device 30 is used to determine the power-on detection result of the DUT 10 based on the graphic code scanning record.

[0043] It is understandable that graphic encoding can refer to different data graphics distributed according to a certain pattern using a specific geometric shape, including QR codes and barcodes, and can also be other graphics carrying additional information. The device under test 10 is a smart device such as a mobile phone, tablet, or television. For the device under test 10, the period from triggering power-on to entering the user interface is called the power-on process, and the power-on duration to be tested is the time spent in this process. Currently, during the power-on process of smart devices, a boot screen is displayed, typically showing the product brand logo. After the power-on process is complete, the device under test 10 has finished loading, stops playing the boot screen, and enters the user interface. The image used for the boot screen can be modified according to the code configuration. In this embodiment, the image of the boot screen of the device under test 10 is replaced with a pre-designed graphic encoding beforehand.

[0044] Optionally, the device under test (DUT) 10 can be powered on manually. Optionally, the DUT 10 is connected to the control device 30 via a serial cable, and the control device 30 sends a power-on command to the DUT 10 to control the DUT 10 to enter the power-on process.

[0045] The scanning device 20 is a device with graphic code scanning function, which can be a barcode scanner or a smart device such as a mobile phone or tablet. The scanning side of the scanning device 20 is directly facing the graphic code displayed on the device under test 10, and scans the graphic code. It can be understood that the scanning device 20 starts and maintains the graphic code scanning function. After the device under test 10 is powered on, the scanning device 20 can quickly scan the graphic code displayed on the device under test 10 to record the power-on time of the device under test 10.

[0046] After scanning the graphic code for the first time, the scanning device 20 stops the graphic scanning function and restarts it after a first set interval (e.g., 10 seconds). It can be understood that the acceptable power-on time is a set acceptable value based on the product requirements and historical operating data of the device under test 10. If the power-on time of the device under test 10 exceeds the acceptable power-on time, it indicates that the device under test 10 fails to meet the performance indicator of power-on time and needs to be optimized.

[0047] It should be noted that if the device under test 10 has completed the power-on process within the acceptable power-on time and the graphic encoding playback has ended, the device under test 10 will display the operation interface. At this time, the scanning device 20 will not be able to scan the graphic encoding again. Based on this, the control device 30 can determine whether the power-on time of the device under test 10 meets the requirements according to the scanning record of the graphic encoding, and obtain the power-on test result of the device under test 10. The power-on test result includes power-on abnormality or power-on normality. The control device 30 can be a computer or other device with control capabilities. In an optional implementation, if the control device 30 detects that the scanning device 20 scans the graphic encoding scanning record a second time, it determines that the power-on test result of the device under test 10 is a power-on abnormality.

[0048] For example, the scanning device 20 can be directly connected to the control device 30 via a data cable, or it can be indirectly connected via an intermediate device (such as a server). This embodiment does not impose any limitations on this. The scan record refers to the data recorded by the control device 30 or the intermediate device each time the scanning device 20 scans a graphic code, including the scan time.

[0049] In one alternative implementation, the power-on duration test suffers from sporadic issues; for example, a particular power-on process might take longer than usual, requiring numerous repeated tests for verification. After determining the power-on detection result of the device under test (DUT) 10, the control device 30 sends a power-off command to DUT 10. After a certain interval (a parameter that can be set according to actual conditions), it sends a power-on command to DUT 10 again; the power-on detection system performs repeated tests. In this way, the power-on duration of DUT 10 is repeatedly tested, ensuring the accuracy of the test results.

[0050] In the aforementioned power-on detection system, the device under test (DUT) displays a graphic code during the power-on process. The scanning device performs a graphic code scanning operation after the DUT displays the graphic code. If the scan is successful, the graphic code scanning operation is performed again after a first set time interval. The first set time interval is consistent with the qualified power-on time of the DUT. The control device determines the power-on detection result of the DUT based on the graphic code scanning record. Through this method, the power-on process of the DUT can be identified using graphic codes; by scanning the graphic codes, the power-on time of the DUT can be accurately recorded; and based on the graphic code scanning record, it can be determined whether the power-on time meets the requirements. Compared with traditional methods, the power-on detection system of this application automates the detection of power-on time, saves manpower, reduces errors caused by human factors, improves the accuracy of power-on testing, and facilitates repeated testing of the same DUT. The power-on detection system of this application has low complexity, low equipment requirements, low setup cost, and is easy to deploy and implement.

[0051] In one exemplary embodiment, such as Figure 2 As shown, the system also includes a network backend 40; the network backend 40 is connected to the scanning device 20 and the control device 30 via a network; the scanning device 20 is also used to send a scanning event to the network backend 40 after a successful scan; the network backend 40 is used to generate a scanning record with graphic codes based on the scanning event; if, based on the scanning record with graphic codes, it is determined that the scanning device 20 scans graphic codes more than once within a second set time period after a successful scan, it sends an abnormal information back to the control device 30; the control device 30 is also used to determine, based on the abnormal information, that the power-on detection result of the device under test 10 is a power-on abnormality.

[0052] The network backend 40 can run on a server, and the scanning device 20 runs a corresponding scanning application (APP). This application scans the graphic code, and upon successful scanning, sends a scan event to the server running the network backend 40. This scan event includes the identifier corresponding to the graphic code and the scanning time. Based on this scan event, the network backend 40 generates a scan record for the graphic code. Optionally, the system also includes a router to provide a network environment for the scanning device 20 and the control device 30.

[0053] Understandably, the second set duration is considered to end when the time interval reaches the first scanned time of the graphic code. If the graphic code is scanned again or multiple times within the second set duration, it indicates that the playback duration of the boot screen of the device under test 10 exceeds the qualified boot duration. At this time, the network backend 40 sends an abnormality message to the control device 30. Based on this abnormality message, the control device 30 determines that a problem has occurred and confirms that the boot test result of the device under test 10 is an abnormal boot.

[0054] In one optional implementation, the network backend 40 determines, based on the scanning record of the graphic code, whether the number of times the graphic code has been scanned within a second set time period is greater than 1. If so, it sends an error message to the control device 30. For example, if the network backend 40 detects that the scanning device 20 has scanned the graphic code's scanning record for the second time, it sends an error message to the control device 30.

[0055] In this embodiment, by setting up a network backend, the control device does not need to have a graphic encoding recording function, the control device requirements are low, and it is easy to deploy and implement.

[0056] In one exemplary embodiment, refer to Figure 2 The control device 30 is also used to clear the scanning record of the graphic encoding in the network backend 40 and determine that the power-on test result of the device under test 10 is normal if no abnormal information is received from the network backend 40 within the second set time period.

[0057] If the control device 30 monitors the network backend 40 and finds no abnormal information within a second set time period, it indicates that the playback duration of the boot screen of the device under test 10 is less than or equal to the qualified boot duration. At this time, the control device 30 clears the scanning records of the graphic code in the network backend 40, confirming that the boot test result of the device under test 10 is normal. Correspondingly, the network backend 40 only needs to check the number of scanning records of the graphic code. If the number of scanning records of the graphic code is greater than 1, it sends abnormal information back to the control device 30.

[0058] In this embodiment, the control device clears the scan record of the current test, which simplifies the test process and provides a stable test environment for the next test, avoiding interference with the test results of the next test.

[0059] In an exemplary embodiment, the scanning device 20 is further configured to count down according to a first set duration after a successful scan; and to perform the graphic encoding scanning operation again after the countdown ends.

[0060] The scanning device 20 uses a countdown timer to ensure that the graphic encoding scanning operation is performed again after a first set interval. Optionally, the scanning device 20 includes a display screen to show the countdown in real time during the countdown according to the first set interval, so that the testers can understand the test status.

[0061] In one exemplary embodiment, such as Figure 1 As shown, the scanning device 20 and the control device 30 are connected via a data cable; the scanning device 20 is also used to send a scanning event to the control device 30 after a successful scan; the control device 30 is also used to generate a graphic-coded scanning record based on the scanning event; and to enter a countdown based on a first set duration; after the countdown ends, the control device 20 is controlled to perform the graphic-coded scanning operation again.

[0062] In this embodiment, the scanning device 20 is a barcode scanner, which is directly connected to the control device 30 via a data cable. The control device 30 runs a management program corresponding to the barcode scanner, which generates scanning records corresponding to scanning events. The control device 30 controls the barcode scanner to perform graphic encoding scanning operations. After the barcode scanner completes the first graphic encoding scanning operation, the control device 30 starts a countdown according to a first set duration. After the countdown ends, the control device 20 performs the graphic encoding scanning operation again. This method simplifies the system configuration and reduces deployment costs.

[0063] In one optional implementation, at the start of the test, the control device 30 activates the barcode scanner to scan and sends a power-on command to the device under test (DUT) 10. The DUT 10 enters the power-on process and displays a graphic code. After the barcode scanner detects the graphic code, it transmits the scan event to the control device 30 via a data cable. Simultaneously, the control device 30 generates a scan record and begins a countdown based on a pre-set duration. After the countdown ends, the barcode scanner is triggered to scan again. If no graphic code is detected, it indicates that the DUT 10 has successfully powered on, and the power-on test result is considered normal. If a graphic code is detected, it indicates that the DUT 10 has not yet successfully powered on, and the power-on test result is considered abnormal. The control device 30 captures the abnormal log record and sends a power-off command to the DUT 10, entering the next cycle.

[0064] In one exemplary embodiment, such as Figure 1 and Figure 2 As shown, the control device 30 is connected to the device under test 10 via a serial cable; the control device 30 is also used to read the log records of the device under test 10 via the serial cable and save the read log records when the power-on detection result of the device under test 10 is determined to be a power-on abnormality.

[0065] In the event of a power-on anomaly in the device under test (DUT) 10, the control device 30 reads and saves the log records of DUT 10, which helps testers quickly locate the problem and optimize the power-on time of the test device. Optionally, if the control device 30 determines that the power-on detection result of DUT 10 is a power-on anomaly, it sends a log retrieval request to DUT 10. DUT 10 prints logs based on the log retrieval request and sends the printed logs back to the control device 30 for storage.

[0066] In one exemplary embodiment, such as Figure 1 and Figure 2 As shown, the control device 30 is also used to send a power-on command to the device under test 10; the device under test 10 is also used to power on according to the power-on command and display graphic codes during the power-on process; the control device 30 is also used to detect whether there is a scan record of graphic codes before sending the power-on command; if there is, the scan record of graphic codes is cleared.

[0067] In this process, the control device 30 controls the device under test (DUT) 10 to power on by sending a power-on command. Before powering on the DUT 10, the control device 30 checks whether there are any graphic code scanning records in its own memory or in the network backend 40. If graphic code scanning records exist, the control device 30 or the network backend 40 clears the stored graphic code scanning records. This method avoids interference from misoperation or redundant scanning records from the previous test, further improving the accuracy of the power-on detection.

[0068] In an exemplary embodiment, the scanning device 20 is further configured to perform a graphic encoding scanning operation again after an interval of a target duration; the target duration is a duration obtained by correcting the qualified power-on duration of the device under test 10 based on the scanning response time.

[0069] The scan response time refers to the time interval between the start of scanning by the scanning device 20 and the generation of a scan event. It can be a pre-set fixed parameter or data detected at regular intervals. The target duration is the difference between the qualified power-on time of the device under test 10 and the scan response time.

[0070] Optionally, refer to Figure 1The control device 30 periodically checks the scanning response time of the scanning device 20 and adjusts the acceptable power-on time of the device under test 10 based on this response time to obtain the target time. Upon receiving a scanning event transmitted by the graphic encoding scanned by the scanning device 20, the control device 30 generates a scan record and simultaneously begins a countdown based on the target time. After the countdown ends, the scanning device 20 is triggered to scan again. Optionally, the control device 30 determines the scanning response time of the scanning device 20 based on the time of issuing the power-on command and the time of receiving the scanning event.

[0071] Optionally, refer to Figure 2 The scanning device 20 performs a correction operation based on the pre-set scanning response time and the qualified power-on time of the device under test 10 to determine the target time. After successfully scanning the graphic code, the scanning device 20 enters a countdown based on the target time. After the countdown ends, it performs the graphic code scanning operation again.

[0072] In this embodiment, the interval time of the scanning device is corrected to avoid excessive scanning response time, which could lead to missed detection of abnormal startup conditions, thereby improving the accuracy of startup detection.

[0073] In one alternative implementation, combining Figure 2 ,like Figure 3 As shown, the interaction process between the devices includes:

[0074] 1. The control device 30 sends a power-on command to the device under test 10;

[0075] 2. The device under test (DUT) 10 is powered on and plays the graphic encoding screen;

[0076] 3. Once the scanning device 20 scans the graphic code, it begins a countdown based on the acceptable power-on duration; simultaneously, the network backend 40 receives the first scan record.

[0077] 4. (If the power-on time of the device under test 10 is less than or equal to the qualified power-on time) When the countdown ends, the device under test 10 has completed the power-on process, the graphic encoding screen has finished playing, and the operation interface has been entered; at this time, the scanning device 20, whose countdown has ended, will be unable to scan the code again and will not be able to scan the result.

[0078] 5. If the control device 30 does not report any abnormalities within a certain period of time, the scanning records of the network backend 40 are cleared.

[0079] 6. The control device 30 sends a shutdown command to the device under test 10. After the shutdown is completed, repeat step 1.

[0080] 7. (When the power-on time of device under test 10 exceeds the qualified power-on time) When the countdown ends, if device under test 10 has not completed the power-on process and is still playing the graphic encoding screen, the scanning device 20, whose countdown has ended, will scan the code again and will scan the graphic encoding again. The network backend 40 receives the second scan record and reports the abnormality.

[0081] 8. Control device 30 detects an anomaly reported by network backend 40, determines that a problem has occurred, records and saves the log of this anomaly, and then clears the scan record of network backend 40.

[0082] 9. The control device 30 sends a shutdown command to the device under test 10. After the shutdown is completed, repeat step 1.

[0083] Using the above method, testers only need to set up the test environment and trigger the control device 30 to start running, thus freeing up human resources. After running for a considerable period of time, the number of runs, the number of anomalies, the test results, and the log records recorded by the control device 30 can be viewed, and the abnormal log records can be provided to the R&D personnel for analysis and optimization.

[0084] In one exemplary embodiment, such as Figure 4 As shown, the system includes multiple test groups and control devices 30; each test group consists of a device under test 10 and a scanning device 20; wherein, the graphic codes displayed by the device under test 10 in each test group are different during the power-on process.

[0085] Here, different graphic codes refer to different information content contained in the graphic codes. For example... Figure 4 In the system shown, the control device 30 manages the scanning records of different graphic codes. Based on the scanning records of each graphic code during the testing process, the device under test 10 in multiple test groups can be powered on for testing.

[0086] In one optional implementation, the control device 30 sends a power-on command to each device under test (DUT) 10 synchronously or asynchronously. During the power-on process, each DUT 10 displays a corresponding graphic code. Each scanning device 20 scans the graphic codes displayed by the DUT 10 in the same test group. A scanning device 20 that successfully scans the graphic code performs the scanning operation again after a set interval; the set interval is consistent with the qualified power-on time of the DUT 10 in its test group. The control device 30 determines the power-on test result of each DUT 10 based on the scanning records of each graphic code.

[0087] In this way, different graphic codes are designed for different devices under test 10, avoiding confusion during testing. Based on this embodiment, the power-on detection system can simultaneously perform power-on detection on multiple devices under test 10, improving power-on testing efficiency.

[0088] In one exemplary embodiment, such as Figure 5 As shown, the system includes multiple test groups, a control device 30, and a network backend 40. The network backend 40 manages scan records for different graphic codes. Based on the scan records of each graphic code during the test, it can generate abnormal information for each graphic code and feed it back to the control device 30. The control device 30 determines the power-on test result, thus enabling simultaneous power-on testing of multiple devices under test 10.

[0089] Based on the same inventive concept, this application also provides a power-on detection method applied to the power-on detection system described above. The solution provided by this method is similar to the implementation scheme described in the above system; therefore, the specific limitations in one or more power-on detection method embodiments provided below can be found in the limitations of the power-on detection system described above, and will not be repeated here.

[0090] In one exemplary embodiment, such as Figure 6 As shown, a power-on detection method is provided, which can be applied to the power-on detection system provided in any embodiment of this application. The method includes:

[0091] Step 602: During the power-on process, the device under test displays a graphic code.

[0092] Step 604: After the graphic code is displayed on the device under test, the scanning device performs a graphic code scanning operation; if the scan is successful, the graphic code scanning operation is performed again after a first set time interval; the first set time interval is consistent with the qualified power-on time of the device under test.

[0093] Step 606: The control device determines the power-on test result of the device under test based on the scanning record of the graphic code.

[0094] In the aforementioned power-on detection method, the device under test (DUT) displays a graphic code during the power-on process; the scanning device performs a graphic code scanning operation after the DUT displays the graphic code; if the scan is successful, the graphic code scanning operation is performed again after a first set time interval; the first set time interval is consistent with the qualified power-on time of the DUT; the control device determines the power-on detection result of the DUT based on the graphic code scanning record. Through this method, the power-on process of the DUT can be identified using graphic codes; by scanning the graphic codes, the power-on time point of the DUT can be accurately recorded; and based on the graphic code scanning record, it can be determined whether the power-on time meets the requirements. Compared with traditional methods, the power-on detection method of this application automates the detection of power-on time, saves manpower, reduces errors caused by human factors, improves the accuracy of power-on testing, and facilitates repeated testing of the same DUT. The power-on detection system of this application has low complexity, low equipment requirements, low setup cost, and is easy to deploy and implement.

[0095] In an exemplary embodiment, the system further includes a network backend; the network backend is connected to the scanning device and the control device via a network; the method further includes: after a successful scan, the scanning device sends a scan event to the network backend; the network backend generates a scan record with graphic encoding based on the scan event; if, based on the scan record with graphic encoding, it is determined that the scanning device scans the graphic encoding more than once within a second set time period after a successful scan, it sends abnormal information back to the control device; the control device determines, based on the abnormal information, that the power-on detection result of the device under test is a power-on abnormality.

[0096] In an exemplary embodiment, step 606 includes: if the control device does not receive any abnormal information from the network backend within a second set time period, it clears the scanning record of the graphic encoding in the network backend and determines that the power-on test result of the device under test is normal.

[0097] In an exemplary embodiment, if the scanning device successfully scans, it performs a graphic encoding scanning operation again after a first set time interval, including: after a successful scan, the scanning device counts down according to the first set time interval; after the countdown ends, it performs a graphic encoding scanning operation again.

[0098] In an exemplary embodiment, the scanning device and the control device are connected via a data cable. If the scanning device successfully scans, it performs a graphic encoding scanning operation again after a first set time interval. This includes: after a successful scan, the scanning device sends a scanning event to the control device; the control device generates a graphic encoding scanning record based on the scanning event; and enters a countdown based on the first set time interval; after the countdown ends, the control device performs the graphic encoding scanning operation again.

[0099] In an exemplary embodiment, the control device is connected to the device under test via a serial cable; the method further includes: when the control device determines that the power-on detection result of the device under test is an abnormal power-on, the control device reads the log records of the device under test via the serial cable and saves the read log records.

[0100] In an exemplary embodiment, step 602 includes: the control device sending a power-on command to the device under test; the device under test powering on according to the power-on command and displaying graphic codes during the power-on process; the method further includes: before sending the power-on command, the control device detecting whether there is a scan record of graphic codes; if so, clearing the scan record of graphic codes.

[0101] In an exemplary embodiment, the method further includes: performing a graphic encoding scan operation again after the scanning device is spaced at a target time interval; the target time is a time obtained by correcting the qualified power-on time of the device under test based on the scanning response time.

[0102] In one exemplary embodiment, the system includes multiple test groups and control devices; each test group consists of a device under test (DUT) and a scanning device; wherein the DUT displays different graphic codes during the power-on process in each test group.

[0103] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0104] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0105] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. The memory, database, or other media mentioned in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0106] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0107] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A power-on detection system, characterized in that, The system includes a device under test, a scanning device, and a control device; wherein: The device under test is used to display graphic codes during the power-on process; The scanning device is used to perform a graphic code scanning operation after the graphic code is displayed on the device under test; if the scan is successful, the graphic code scanning operation is performed again after an interval of a first set time; the first set time is consistent with the qualified power-on time of the device under test; The control device is used to determine the power-on test result of the device under test based on the scanning record of the graphic code.

2. The system according to claim 1, characterized in that, The system also includes a network backend; the network backend is connected to the scanning device and the control device via a network. The scanning device is also used to send a scanning event to the network backend after a successful scan; The network backend is used to generate a scanning record of the graphic code based on the scanning event; if, based on the scanning record of the graphic code, it is determined that the scanning device scans the graphic code more than once within a second set time period after successfully scanning, then abnormal information is fed back to the control device. The control device is also used to determine, based on the abnormal information, that the power-on detection result of the device under test is a power-on abnormality.

3. The system according to claim 2, characterized in that, The control device is further configured to, if no abnormal information is received from the network backend within the second set time period, clear the scanning record of the graphic encoding in the network backend and determine that the power-on test result of the device under test is normal.

4. The system according to claim 2, characterized in that, The scanning device is also used to count down according to the first set duration after a successful scan; and to perform the graphic encoding scanning operation again after the countdown ends.

5. The system according to claim 1, characterized in that, The scanning device and the control device are connected via a data cable; The scanning device is also used to send a scanning event to the control device after a successful scan; The control device is further configured to generate a scan record of the graphic code based on the scan event; and to enter a countdown based on the first set duration; and after the countdown ends, to control the scanning device to perform the graphic code scanning operation again.

6. The system according to any one of claims 1 to 5, characterized in that, The control device is connected to the device under test via a serial cable; The control device is also used to read the log records of the device under test through the serial port line and save the read log records when the power-on detection result of the device under test is determined to be an abnormal power-on.

7. The system according to claim 6, characterized in that, The control device is also used to send a power-on command to the device under test; The device under test is also used to power on according to the power-on command and display graphic codes during the power-on process; The control device is further configured to detect whether there is a scan record of the graphic code before sending the power-on command; if there is, the scan record of the graphic code is cleared.

8. The system according to any one of claims 1 to 5, characterized in that, The scanning device is also used to perform a graphic encoding scanning operation again after an interval of a target duration; the target duration is a duration obtained by correcting the qualified power-on duration of the device under test based on the scanning response time.

9. The system according to any one of claims 1 to 5, characterized in that, The system includes multiple test groups and control devices; each test group consists of a device under test (DUT) and a scanning device; wherein, the DUT displays different graphic codes during the power-on process in each test group.

10. A power-on detection method, characterized in that, The power-on detection method is applied to the power-on detection system as described in any one of claims 1 to 9; the system includes a device under test, a scanning device, and a control device; the method includes: The device under test displays a graphic code during the power-on process; The scanning device performs a graphic code scanning operation after the graphic code is displayed on the device under test; if the scan is successful, the graphic code scanning operation is performed again after a first set time interval; the first set time interval is consistent with the qualified power-on time of the device under test; The control device determines the power-on test result of the device under test based on the scanning record of the graphic code.

Images