WO2016192296A1

WO2016192296A1 - Method for testing terminal performance, terminal, and storage medium

Info

Publication number: WO2016192296A1
Application number: PCT/CN2015/093615
Authority: WO
Inventors: 兰凯
Original assignee: 深圳市中兴微电子技术有限公司
Priority date: 2015-05-29
Filing date: 2015-11-02
Publication date: 2016-12-08
Also published as: CN106294039A

Abstract

Disclosed are a method for testing a terminal performance, a terminal, and a storage medium. The method comprises: acquiring a test version and a test parameter from a host by using a Boot; storing the acquired test version and the test parameter in an internal storage; starting the test version in the internal storage by using the Boot, and reading the test parameter required for running the test version from the internal storage so as to complete testing of the terminal performance, wherein the test version comprises: a Boot, an operating system, a drive abstraction, and a radio frequency module.

Description

Method for testing terminal performance, terminal and storage medium

Technical field

The present invention relates to a communication terminal production test technology, and in particular, to a method for testing terminal performance, a terminal, and a storage medium.

Background technique

At present, the production test scheme of the traditional communication products basically adopts a dual system or a test mode of the same system dual mode. The dual system test scheme consists of a normally used version stored in the terminal memory and a version corresponding to the production test used therein; the same system dual mode scheme adopts a special instruction after the terminal is normally turned on. The terminal is put into the production test mode to complete the corresponding production test function. These two common production test methods need to start the official version at startup, but the current version of the smart machine is generally very large, and has a slow startup time.

Summary of the invention

To solve the above technical problem, an embodiment of the present invention provides a method for testing terminal performance, a terminal, and a storage medium.

The method for testing the performance of the terminal provided by the embodiment of the present invention includes:

Using the boot program (Boot) to obtain the test version and test parameters from the host;

Store the obtained test version and test parameters into memory;

Using Boot, starting the test version in the memory, and reading the test parameters required to run the test version from the memory to complete the test of the terminal performance;

The test version includes: Boot, operating system (OS, Operating System), driver abstraction (drv, drviver), and radio frequency module.

In the embodiment of the present invention, the booting machine is used to obtain the test version and the test parameters from the host, including:

Start Boot and perform synchronous handshake operation with the host.

After the synchronization handshake succeeds, the Boot interacts with the host to obtain the test version and test parameters from the host.

In the embodiment of the present invention, the method further includes:

Deleting the association relationship between the test version and the parameters in the flash memory, and establishing an association relationship between the test version and the in-memory parameter;

In the embodiment of the present invention, the method further includes:

The relationship between the parameters of the radio module and the Flash module is canceled.

In the embodiment of the present invention, the method further includes:

Start Boot and perform synchronous handshake operation with the host.

When the synchronization handshake fails, use Boot to start the normal version.

The terminal provided by the embodiment of the present invention includes:

The obtaining unit is configured to use the Boot to obtain a test version and test parameters from the host;

a storage unit configured to store the obtained test version and test parameters into the memory;

a test unit, configured to use Boot to start a test version in the memory, and read test parameters required to run the test version from the memory to complete testing of the terminal performance;

The test version includes: Boot, operating system, driver abstraction, and radio module.

In the embodiment of the present invention, the acquiring unit is further configured to start a boot and perform a synchronous handshake operation with the host. After the synchronous handshake is successful, the Boot uses the host to interact with the host to obtain a test version and test parameters from the host.

In the embodiment of the present invention, the terminal further includes: a setting unit configured to cancel the association relationship between the test version and the parameter in the flash memory, and establish the test version to the parameter in the memory connection relation.

In the embodiment of the present invention, the terminal further includes: a setting unit configured to cancel the association relationship between the radio module phy and the parameters in the Flash.

In the embodiment of the present invention, the terminal further includes: a startup unit configured to start the boot and perform a synchronous handshake operation with the host; when the synchronous handshake fails, the boot starts the normal version by using the boot.

A storage medium having stored therein a computer program configured to perform the method of testing the performance of the terminal.

In the technical solution of the embodiment of the present invention, the official version is tailored, and the module not required for the production test version is cut out, and at the same time, the terminal pair is stripped by changing the requirement of reading the flash in the production test version to the requirement of reading the memory. Flash dependencies. When the terminal system starts, it no longer reads the parameters from the Flash, but directly reads the parameters of the memory, so that the entire test version is completely no longer dependent on the data in the Flash. During the production test, the host (PC) interacts with the terminal's Boot, downloads the test version to the terminal's memory, and uses Boot to launch the test version just downloaded. After the test version is launched, you can complete the various functions during the test. By adopting the technical solution of the embodiment of the invention, the improvement of the test efficiency is greatly improved, the effect of reducing the startup time is achieved, and the startup time of the test process is saved.

DRAWINGS

1 is a schematic diagram of a test version according to an embodiment of the present invention;

2 is a schematic diagram of downloading a test version and test parameters according to an embodiment of the present invention;

3 is a schematic flowchart of a method for testing performance of a terminal according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.

detailed description

In order to understand the features and technical details of the embodiments of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings. It is not intended to limit the embodiments of the invention.

In the embodiment of the present invention, the version of the complete terminal is changed to the official version, and the version of the test terminal is referred to as the test version. Referring to FIG. 1, an embodiment of the present invention performs necessary cutting on a complete version of a terminal. The purpose of the production test of the terminal is mainly to check production performance indicators such as hardware performance, material batch quality, and patch quality, and the test version itself. It does not include the upper-level business modules, such as: phone book, web browser and other application functions, and does not need to perform business functions such as search network. Therefore, the test version can be tailored to include only the following functional modules: Boot, OS , driver abstraction (drv), radio module (phy).

The following describes the various functional modules of the test version:

Boot: Provides the special startup process required for the test version.

Operating system (OS): The OS is the minimum OS, providing basic thread scheduling functions; ensuring real-time testing.

Driver abstraction (drv): Contains board-level drivers, provides a unified abstract interface; guarantees terminal and host communication functions, such as Universal Serial Bus (USB); guarantees non-RF test functions, such as: Button, liquid crystal display (LCD, Liquid Crystal Display), etc.

Radio frequency module (phy): Contains RF test modules of various standards; ensures RF test functions such as Long Term Evolution (LTE) and Wideband Code Division Multiple Access (WCDMA).

Relative to the official version, at least the following functional modules are omitted: protocol stack (ps), AT command (at), network (net), and application (app).

In the embodiment of the present invention, the Boot of the terminal is different from the existing Boot, and a new startup mode is added to the existing Boot function, as follows:

After Boot starts, it synchronizes with the host within the specified time.

After a successful handshake, the Boot interacts with the host to complete the test version and the test version. Download the parameters. Here, the parameters required for the test version and the test version are downloaded to the memory of the terminal. For the case where the handshake is not completed after startup, Boot starts the normal version.

Boot is responsible for starting the production test version in the terminal memory.

In the embodiment of the present invention, the test version is out of dependence on the terminal Flash. After the test version is started in the memory, since there is no valid data in the flash of the terminal at this time, the test version can only use the downloaded one in the memory. part of data. This requires removing the Flash-dependent actions from the cropped test version. Specifically:

Remove the dependency of the test version on the parameters in the Flash during the startup process. The test version needs to read the configuration parameters from Flash more or less during the startup process. The read action here should be changed from the read parameter in Flash to the memory. Read the parameters in .

Remove the dependence of each function module on the parameters in Flash. Since the test version has been cropped, it is only necessary to consider the dependence of the RF part on Flash.

In the embodiment of the present invention, referring to FIG. 2, the terminal needs to separately download the following two parts of the file:

Test version: Provides the functionality required for testing.

Test parameters: A collection of multiple configuration parameter files, which are downloaded to the memory of the specified location.

In the technical solution of the embodiment of the present invention, during the production test, the test version and the test parameters are downloaded to the memory of the terminal through the Boot interaction between the host and the terminal, and the boot version that has just been downloaded is started by using the Boot. After the test version is launched, you can complete the various functions during the test.

The technical solutions of the present invention are further described in detail below in conjunction with specific embodiments.

FIG. 3 is a schematic flowchart of a method for testing performance of a terminal according to an embodiment of the present invention. The method for testing terminal performance in this example is applied to a terminal, and the terminal may be an electronic terminal of a communication type such as a mobile phone or a tablet computer; As shown, the method for testing terminal performance includes the following steps:

Step 301: Using Boot, obtain a test version and test parameters from the host.

In the embodiment of the present invention, the host may be a computer (PC). The device obtains the test version and the test parameters from the host by using the boot, and includes: starting the boot and performing a synchronous handshake operation with the host; after the synchronous handshake is successful, the Boot uses the host to interact with the host to obtain the test version and the test parameters from the host.

The following describes the various functional modules of the test version:

Boot: Provides the special startup process required for the test version.

Relative to the official version, at least the following functional modules are omitted: protocol stack (ps), AT command (at), Network (net), application (app).

In the embodiment of the present invention, the boot is started, and the host performs a synchronous handshake operation; when the synchronous handshake fails, the normal version is started by using the boot.

Step 302: Store the obtained test version and test parameters into the memory.

After Boot starts, it synchronizes with the host within the specified time.

After the successful handshake, the Boot interacts with the host to complete the download of the parameters required for the test version and the test version. Here, the parameters required for the test version and the test version are downloaded to the memory of the terminal. For the case where the handshake is not completed after startup, Boot starts the normal version.

In the embodiment of the present invention, the association relationship between the test version and the parameters in the flash memory is canceled, and the association relationship between the test version and the in-memory parameter is established.

In the embodiment of the present invention, the association relationship between the parameters of the radio frequency module and the Flash module is cancelled.

Step 303: Boot, start the test version in the memory, and read the test parameters required to run the test version from the memory to complete the test of the terminal performance.

Before adopting the technology of the embodiment of the present invention, it is necessary to start the normal version to enter the test state, which takes about 60 seconds. With the technical solution of the embodiment of the present invention, it takes only about 10 seconds to download the test version to the test version, and the test state can be entered, thereby greatly improving the startup time, improving the production efficiency, and achieving the expected effect.

FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention. As shown in FIG. 4, the terminal includes:

The obtaining unit 41 is configured to acquire a test version and test parameters from the host by using the Boot;

The storage unit 42 is configured to store the obtained test version and test parameters into the memory;

The testing unit 43 is configured to use a boot to start a test version in the memory, and read, from the memory, test parameters required to run the test version to complete testing of the terminal performance;

In the embodiment of the present invention, the obtaining unit 41 is further configured to start a boot and perform a synchronous handshake operation with the host. After the synchronous handshake is successful, the Boot and the host interact to obtain a test version and test parameters from the host.

In the embodiment of the present invention, the terminal further includes: a setting unit 44, configured to cancel the association relationship between the test version and the parameter in the flash memory, and establish an association relationship between the test version and the parameter in the memory.

In another embodiment of the present invention, the terminal further includes: a setting unit 44 configured to cancel the association relationship between the radio module phy and the parameters in the Flash.

In the embodiment of the present invention, the terminal further includes: a booting unit 45 configured to start a boot and perform a synchronous handshake operation with the host; when the synchronous handshake fails, the boot starts the normal version by using the boot.

In the technical solution of the embodiment of the present invention, the official version is tailored, and the module that is not required by the test version is cut out, and at the same time, the terminal is removed from the Flash by changing the requirement of reading the Flash in the test version to the requirement of reading the memory. rely. When the terminal system starts, it no longer reads from Flash The parameters, while directly reading the parameters of the memory, so that the entire test version is completely no longer dependent on the data in Flash. During the test, the host (PC) interacts with the terminal's Boot, downloads the test version to the terminal's memory, and uses Boot to launch the test version just downloaded. After the test version is launched, you can complete the various functions during the test. By adopting the technical solution of the embodiment of the invention, the improvement of the test efficiency is greatly improved, the effect of reducing the startup time is achieved, and the startup time of the test process is saved.

Embodiments of the present invention also describe a storage medium in which a computer program is stored, the computer program being configured to perform the method of testing terminal performance of the foregoing embodiments.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

The invention cuts the official version of the terminal, cuts out the modules that are not needed for the production test version, and strips the terminal's dependence on the Flash by changing the requirement of reading the Flash in the production test version to the requirement of reading the memory. When the terminal system starts, it no longer reads the parameters from the Flash, but directly reads the parameters of the memory, so that the entire test version is completely no longer dependent on the data in the Flash.

Claims

A method of testing terminal performance, the method comprising:

Use the startup program Boot to obtain the test version and test parameters from the host;

Store the obtained test version and test parameters into memory;

With Boot, the test version in the memory is started, and the test parameters required to run the test version are read from the memory to complete the test of the terminal performance.
The method for testing terminal performance according to claim 1, wherein the test version comprises: a Boot, an operating system, a driver abstraction, and a radio frequency module.
The method for testing the performance of a terminal according to claim 2, wherein the obtaining the test version and the test parameters from the host by using the boot program Boot includes:

Start Boot and perform synchronous handshake operation with the host.

After the synchronization handshake succeeds, the Boot interacts with the host to obtain the test version and test parameters from the host.
The method of testing terminal performance according to claim 3, wherein the method further comprises:

The association relationship between the test version and the parameters in the flash memory is canceled, and the association relationship between the test version and the in-memory parameter is established.
The method of testing terminal performance according to claim 2, wherein the method further comprises:

The relationship between the parameters of the radio module and the Flash module is canceled.
The method of testing the performance of a terminal according to any one of claims 2 to 5, wherein the method further comprises:

Start Boot and perform synchronous handshake operation with the host.

When the synchronization handshake fails, use Boot to start the normal version.
A terminal, the terminal comprising:

The obtaining unit is configured to use the Boot to obtain a test version and test parameters from the host;

a storage unit configured to store the obtained test version and test parameters into the memory;

The testing unit is configured to use Boot to start a test version in the memory, and read test parameters required to run the test version from the memory to complete testing of the terminal performance.
The terminal according to claim 7, wherein the test version comprises: a Boot, an operating system, a driver abstraction, and a radio frequency module.
The terminal according to claim 8, wherein the obtaining unit is further configured to start a boot and perform a synchronous handshake operation with the host. After the synchronous handshake is successful, the Boot uses the host to interact with the host to obtain a test version and test parameters from the host.
The terminal according to claim 9, wherein the terminal further comprises: a setting unit configured to cancel an association relationship between the test version and a parameter in the flash memory, and establish an association relationship between the test version and an in-memory parameter.
The terminal according to claim 8, wherein the terminal further comprises: a setting unit configured to cancel the association relationship of the radio frequency module with parameters in the Flash.
The terminal according to any one of claims 8 to 11, wherein the terminal further comprises: a booting unit configured to start a boot and perform a synchronous handshake operation with the host; and when the synchronous handshake fails, the boot is used to start the normal version.
A storage medium having stored therein a computer program configured to perform the method of testing terminal performance according to any one of claims 1 to 6.