Terminal power-on test method and system

Abstract

The embodiment of the present invention provides a terminal power-on test method and system, the method comprising: receiving registration messages sent by each controller in real time, and assigning source device ID numbers to each controller according to the registration messages, so that each controller can communicate; binding each controller with a corresponding terminal under test, and sending information to each controller so that it can test the corresponding terminal under test. By controlling the binding and testing between the terminal under test and the controller through the host, efficient testing of the terminal under test is achieved, reducing testing costs and improving testing efficiency.

Description

Technical Field

[0001] The present invention relates to the field of hardware testing, and in particular to a terminal power-on testing method and system. Background Art

[0002] Electronic products (hereinafter referred to as "terminals") often need to be turned on and off during use. However, due to defects in the terminal itself or software vulnerabilities, it is inevitable that the terminal will not be able to start up. The probability of this failure is often very small. For example, it may fail to start up once out of 100,000 times of power-on. In order to find the reason why the terminal cannot start up, we usually need to power on the terminal repeatedly. When it is found that the terminal cannot start up normally, we will further analyze the cause of the problem with the terminal.

[0003] Therefore, in order to discover and solve the problem of the terminal not being able to start normally in advance, equipment manufacturers usually need to test the terminals they produce. However, since the probability of problems occurring in each terminal is relatively small, in order to improve the efficiency of testing and problem solving, it is usually necessary to increase the number of test samples for testing.

[0004] In the prior art, the terminal test is usually performed by a tester on each terminal separately, which often requires a lot of manpower. Therefore, the prior art has the problems of high test cost and low efficiency in the terminal test process. Summary of the invention

[0005] The embodiment of the present invention provides a terminal power-on test method and system, which are used to solve the problems of high test cost and low efficiency in the terminal test process in the prior art.

[0006] In a first aspect, an embodiment of the present invention provides a terminal power-on test method, comprising:

[0007] receiving registration messages sent by each controller in real time, and assigning source device ID numbers to each controller according to the registration messages, so that each controller can communicate;

[0008] Bind each controller with the corresponding terminal under test, and send information to each controller to enable it to test the corresponding terminal under test.

[0009] Optionally, allocating a source device ID number to each controller according to the registration message so that each controller can communicate specifically includes:

[0010] According to the received registration message, it is determined that the controller is not registered, and a source device ID number is allocated to the unregistered controller to enable the controller to communicate.

[0011] Optionally, binding the controller with the terminal under test specifically includes:

[0012] Send information to the controller to enable it to power on the terminal under test, and receive a registration message with a terminal ID sent by the terminal under test;

[0013] It is determined according to the registration message that the terminal ID is unregistered, and the controller and the terminal under test are bound.

[0014] Optionally, the sending information to the controller to test the terminal under test specifically includes:

[0015] Information is sent to the controller to enable it to power on the terminal under test, and the test result is determined according to whether a registration message sent by the terminal under test is received.

[0016] Optionally, determining the test result according to whether a registration message sent by the tested terminal is received specifically includes:

[0017] If a registration message sent by the terminal under test is received, it is determined that the startup is successful, and the controller is notified to power off the terminal under test; or

[0018] If the registration message sent by the terminal under test is not received, it is determined that the startup fails, and the tester is reminded through sound and light signals.

[0019] In a second aspect, an embodiment of the present invention provides a terminal power-on test system, including:

[0020] A host, at least one controller and a terminal under test, wherein the host, at least one controller and the terminal under test are connected via a CAN bus;

[0021] The controller is used to send a registration message to the host in real time for registration, obtain the source device ID number assigned by the host for communication; determine in real time whether the binding with the terminal under test is completed, and if the binding is completed, perform real-time testing on the terminal under test according to the instructions sent by the host;

[0022] The host is used to receive the registration message sent by each controller in real time, and assign the source device ID number to the controller according to the registration message so that the controller can communicate; bind the controller with the terminal under test, and send information to the controller so that it can test the terminal under test;

[0023] The terminal under test is used to determine whether binding with the controller is completed, and if binding is completed, send a registration message to the host according to the instruction of the controller.

[0024] Optionally, allocating a source device ID number to the controller according to the registration message so that the controller can communicate specifically includes:

[0025] It is determined that the controller is not registered according to the received registration message, and a source device ID number is allocated to the unregistered controller to enable the controller to communicate.

[0026] Optionally, binding the controller with the terminal under test specifically includes:

[0027] Send information to the controller to enable it to power on the terminal under test, and receive a registration message with a terminal ID sent by the terminal under test;

[0028] It is determined according to the registration message that the terminal ID is not registered, and the controller and the terminal under test are bound.

[0029] Optionally, the sending information to the controller to test the terminal under test specifically includes:

[0030] Information is sent to the controller to enable it to power on the terminal under test, and the test result is determined according to whether a registration message sent by the terminal under test is received.

[0031] Optionally, determining the test result according to whether a registration message sent by the tested terminal is received specifically includes:

[0032] If a registration message sent by the terminal under test is received, it is determined that the startup is successful, and the controller is notified to power off the terminal under test; or

[0033] If the registration message sent by the terminal under test is not received, it is determined that the startup fails, and the tester is reminded through sound and light signals.

[0034] The terminal power-on test method and system provided by the embodiment of the present invention realizes efficient testing of the terminal under test by controlling the binding and testing between the terminal under test and the controller through the host, reduces the testing cost and improves the testing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1 A schematic diagram of a flow chart of a terminal power-on test method provided by an embodiment of the present invention;

[0037] Figure 2 A schematic diagram of the structure of a terminal power-on test system provided by an embodiment of the present invention;

[0038] Figure 3 Schematic diagram of the structure of the controller in an embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] like Figure 1 As shown, a terminal power-on test method provided by an embodiment of the present invention includes:

[0041] receiving registration messages sent by each controller in real time, and assigning source device ID numbers to each controller according to the registration messages, so that each controller can communicate;

[0042] Bind each controller with the corresponding terminal under test, and send information to each controller to enable it to test the corresponding terminal under test.

[0043] Specifically, for the host to communicate with the controller, the controller must first be registered with the host; the first step of controller registration is to send a registration message to the host. After receiving the registration message, the host will assign a source device ID to the controller; when the controller obtains the source device ID, it can communicate with the host and enter a normal communication state.

[0044] Furthermore, before the power-on test is performed, the controller needs to be bound to the terminal under test. The binding process first requires the host to notify the controller to power on the terminal under test. After the terminal under test is powered on, a terminal ID will be sent to the host through the CAN bus. The terminal ID is globally unique. After receiving the terminal ID, the host will detect the terminal ID to determine whether the terminal under test has been registered. If the terminal is not registered, it is determined that the terminal is a terminal that has just been powered on, thereby achieving the binding between the terminal under test and the controller. After the binding is completed, the terminal under test will be powered on according to the host's instructions.

[0045] As an embodiment of the present invention, the allocating source device ID numbers to the controllers according to the registration message so that the controllers can communicate specifically includes:

[0046] According to the received registration message, it is determined that the controller is not registered, and a source device ID number is allocated to the unregistered controller to enable the controller to communicate.

[0047] Specifically, the controller must first register with the host to communicate with the host. The host determines whether the controller is a registered controller based on the registration message sent by the controller. If it is a registered controller, there is no need to assign a source device ID number to the controller. If it is an unregistered controller, a unique source device ID number is assigned to the unregistered controller so that the unregistered controller can register and communicate with the host.

[0048] As an embodiment of the present invention, binding the controller with the terminal under test specifically includes:

[0049] Send information to the controller to enable it to power on the terminal under test, and receive a registration message with a terminal ID sent by the terminal under test;

[0050] It is determined according to the registration message that the terminal ID is unregistered, and the controller and the terminal under test are bound.

[0051] Specifically, before the test, the controller needs to be bound to the terminal under test. The binding process first requires the host to notify the controller to power on the terminal under test. After the terminal under test is powered on, it will send a terminal ID to the host through the CAN bus. The terminal ID is globally unique. After receiving the terminal ID, the host will detect the terminal ID to determine whether the terminal under test has been registered and send information to the controller. If the terminal is not registered, it is determined that the terminal is a terminal that has just been powered on, thereby realizing the binding between the terminal under test and the controller. After the binding is completed, the terminal under test will be powered on according to the host's instructions.

[0052] As an embodiment of the present invention, the sending of information to the controller so that it tests the terminal under test specifically includes:

[0053] Information is sent to the controller to enable it to power on the terminal under test, and the test result is determined according to whether a registration message sent by the terminal under test is received.

[0054] Specifically, after the terminal under test is bound to the controller, the power-on test can be performed. The power-on test first requires the host to send a power-on test command to the controller. After the controller receives the power-on test command, it Figure 3The electronic switch of the controller completes the power-on test for the terminal under test. The test results include successful startup and failed startup. The controller cuts off the power to the terminal under test or sends an audible and visual signal through an audible and visual device according to the host's judgment result on the terminal under test, i.e. successful startup or failed startup. When the startup is successful, the host will notify the controller to cut off the power. When the startup fails, the host will notify the controller to continue to power on and notify the tester through an audible and visual signal.

[0055] As an embodiment of the present invention, determining the test result according to whether the registration message sent by the tested terminal is received specifically includes:

[0056] If a registration message sent by the terminal under test is received, it is determined that the startup is successful, and the controller is notified to power off the terminal under test; or

[0057] If the registration message sent by the terminal under test is not received, it is determined that the startup fails, and the tester is reminded through sound and light signals.

[0058] Specifically, after the controller receives the power-on test instruction, it will complete the power-on test for the terminal under test. After the test is completed, the test results are either successful startup or failed startup. The controller will power off the terminal under test or send an audible and visual signal through an audible and visual device based on the host's judgment result on the terminal under test, i.e., successful startup or failed startup. When the startup is successful, the host will notify the controller to power off. When the startup fails, the host will notify the controller to continue powering on and notify the tester through an audible and visual signal.

[0059] like Figure 2 As shown, a terminal power-on test system provided by an embodiment of the present invention includes:

[0060] A host, at least one controller and a terminal under test, wherein the host, at least one controller and the terminal under test are connected via a CAN bus;

[0061] The controller is used to send a registration message to the host in real time for registration, obtain the source device ID number assigned by the host for communication; determine in real time whether the binding with the terminal under test is completed, and if the binding is completed, perform real-time testing on the terminal under test according to the instructions sent by the host;

[0062] The host is used to receive the registration message sent by each controller in real time, and assign the source device ID number to the controller according to the registration message so that the controller can communicate; bind the controller with the terminal under test, and send information to the controller so that it can test the terminal under test;

[0063] The terminal under test is used to determine whether binding with the controller is completed, and if binding is completed, send a registration message to the host according to the instruction of the controller.

[0064] Specifically, the terminal power-on test system includes a host, at least one controller and a terminal under test; wherein the host is used to process information and send instructions to the controller and the terminal under test, the controller is used to communicate with the host, receive instructions sent by the host and complete binding with the terminal under test to perform a power-on test on the terminal under test; the terminal under test is a terminal product used for power-on testing. The terminal under test is connected to the controller and the host through a CAN bus, and the number of controllers is at least one, usually set at around 200, and the number of terminals under test corresponds to or is less than the number of controllers.

[0065] Before testing, the controller needs to be bound to the terminal under test. The binding process first requires the host to notify the controller to power on the terminal under test. After the terminal under test is powered on, it will send a terminal ID to the host through the CAN bus. The terminal ID is globally unique. After receiving the terminal ID, the host will detect the terminal ID to determine whether the terminal under test has been registered and send information to the controller. If the terminal is not registered, it is determined that the terminal is a terminal that has just been powered on, thereby realizing the binding between the terminal under test and the controller. After the binding is completed, the terminal under test will be powered on according to the host's instructions.

[0066] After the terminal under test is bound to the controller, a power-on test can be performed. The power-on test first requires the host to send a power-on test command to the controller. After receiving the power-on test command, the controller completes the power-on test for the terminal under test. The test results include successful startup and failed startup. The controller cuts off the power to the terminal under test or sends an audio-visual signal through an audio-visual device based on the host's judgment result on the terminal under test, i.e., successful startup or failed startup; when the startup is successful, the host will notify the controller to cut off the power. When the startup fails, the host will notify the controller to continue to power on, and notify the tester through an audio-visual signal. This system controls the binding and testing between the terminal under test and the controller through the host. Through no less than one controller, the corresponding number of terminals under test can be powered on at the same time, realizing efficient testing of a large number of terminals under test at the same time, reducing testing costs and improving testing efficiency.

[0067] As an embodiment of the present invention, allocating a source device ID number to the controller according to the registration message so that the controller can communicate specifically includes:

[0068] It is determined that the controller is not registered according to the received registration message, and a source device ID number is allocated to the unregistered controller to enable the controller to communicate.

[0069] Specifically, the controller must first register with the host to communicate with the host. The host determines whether the controller is a registered controller based on the registration message sent by the controller. If it is a registered controller, there is no need to assign a source device ID number to the controller. If it is an unregistered controller, a unique source device ID number is assigned to the unregistered controller so that the unregistered controller can register and communicate with the host.

[0070] As an embodiment of the present invention, binding the controller with the terminal under test specifically includes:

[0071] Send information to the controller to enable it to power on the terminal under test, and receive a registration message with a terminal ID sent by the terminal under test;

[0072] It is determined according to the registration message that the terminal ID is not registered, and the controller and the terminal under test are bound.

[0073] Specifically, before the test, the controller needs to be bound to the terminal under test. The binding process first requires the host to notify the controller to power on the terminal under test. After the terminal under test is powered on, it will send a terminal ID to the host through the CAN bus. The terminal ID is globally unique. After receiving the terminal ID, the host will detect the terminal ID to determine whether the terminal under test has been registered and send information to the controller. If the terminal is not registered, it is determined that the terminal is a terminal that has just been powered on, thereby realizing the binding between the terminal under test and the controller. After the binding is completed, the terminal under test will be powered on according to the host's instructions.

[0074] As an embodiment of the present invention, the sending of information to the controller so that it tests the terminal under test specifically includes:

[0075] Information is sent to the controller to enable it to power on the terminal under test, and the test result is determined according to whether a registration message sent by the terminal under test is received.

[0076] Specifically, after the terminal under test is bound to the controller, a power-on test can be performed. The power-on test first requires the host to send a power-on test instruction to the controller. After receiving the power-on test instruction, the controller completes the power-on test for the terminal under test. The test results include successful startup and failed startup. The controller cuts off the power to the terminal under test or sends an audio-visual signal through an audio-visual device based on the host's judgment result on the terminal under test, i.e., successful startup or failed startup; when the startup is successful, the host will notify the controller to cut off the power. When the startup fails, the host will notify the controller to continue to power on, and notify the tester through an audio-visual signal.

[0077] As an embodiment of the present invention, determining the test result according to whether the registration message sent by the tested terminal is received specifically includes:

[0078] If a registration message sent by the terminal under test is received, it is determined that the startup is successful, and the controller is notified to power off the terminal under test; or

[0079] If the registration message sent by the terminal under test is not received, it is determined that the startup fails, and the tester is reminded through sound and light signals.

[0080] Specifically, after the controller receives the power-on test instruction, it will complete the power-on test for the terminal under test. After the test is completed, the test results are either successful startup or failed startup. The controller will power off the terminal under test or send an audible and visual signal through an audible and visual device based on the host's judgment result on the terminal under test, i.e., successful startup or failed startup. When the startup is successful, the host will notify the controller to power off. When the startup fails, the host will notify the controller to continue powering on and notify the tester through an audible and visual signal.

[0081] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0082] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0083] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A terminal power-on test method, characterized in that: include: receiving registration messages sent by each controller in real time, and assigning source device ID numbers to each controller according to the registration messages, so that each controller can communicate; Binding each controller with a corresponding terminal under test, and sending information to each controller to enable it to test the corresponding terminal under test; The allocating source device ID numbers to the controllers according to the registration message so that the controllers can communicate specifically includes: determining, based on the received registration message, that the controller is not registered, and assigning a source device ID number to the unregistered controller to enable the controller to communicate; The binding of the controller to the terminal under test specifically includes: Send information to the controller to enable it to power on the terminal under test, and receive a registration message with a terminal ID sent by the terminal under test; Determining that the terminal ID is unregistered according to the registration message, and binding the controller and the terminal under test; The sending of information to the controller so that the controller performs a test on the terminal under test specifically includes: Information is sent to the controller to enable it to power on the terminal under test, and the test result is determined according to whether a registration message sent by the terminal under test is received.

2. The method according to claim 1, characterized in that The determining of the test result according to whether the registration message sent by the tested terminal is received specifically includes: If a registration message sent by the terminal under test is received, it is determined that the startup is successful, and the controller is notified to power off the terminal under test; or If the registration message sent by the terminal under test is not received, it is determined that the startup has failed, and the tester is reminded through sound and light signals.

3. A terminal power-on test system, characterized in that: include: A host, at least one controller and a terminal under test, wherein the host, at least one controller and the terminal under test are connected via a CAN bus; The controller is used to send a registration message to the host in real time for registration, obtain the source device ID number assigned by the host for communication; determine in real time whether the binding with the terminal under test is completed, and if the binding is completed, perform real-time testing on the terminal under test according to the instructions sent by the host; The host is used to receive the registration message sent by each controller in real time, and allocate a source device ID number to the controller according to the registration message so that the controller can communicate; Binding the controller to the terminal under test, and sending information to the controller to enable it to test the terminal under test; The terminal under test is used to determine whether binding with the controller is completed, and if binding is completed, send a registration message to the host according to the instruction of the controller; The allocating a source device ID number to the controller according to the registration message so that the controller can communicate specifically includes: determining that the controller is not registered according to the received registration message, and assigning a source device ID number to the unregistered controller to enable the controller to communicate; The binding of the controller to the terminal under test specifically includes: Send information to the controller to enable it to power on the terminal under test, and receive a registration message with a terminal ID sent by the terminal under test; Determining, according to the registration message, that the terminal ID is not registered, and binding the controller and the terminal under test; The sending of information to the controller so that the controller performs a test on the terminal under test specifically includes: Information is sent to the controller to enable it to power on the terminal under test, and the test result is determined according to whether a registration message sent by the terminal under test is received.

4. The system according to claim 3, characterized in that The determining of the test result according to whether the registration message sent by the tested terminal is received specifically includes: If a registration message sent by the terminal under test is received, it is determined that the startup is successful, and the controller is notified to power off the terminal under test; or If the registration message sent by the terminal under test is not received, it is determined that the startup has failed, and the tester is reminded through sound and light signals.

Images