JP2023000532A - Mobile terminal test system and mobile terminal test method - Google Patents

Abstract

To provide a mobile terminal test system and a mobile terminal test method that make it possible to obtain a useful test result in a short period of time before tests of all test cases are completed.SOLUTION: A mobile terminal test system 1 for serially executing tests of a plurality of test cases stipulated in a 3GPP standard on a mobile terminal 100, comprises: an operation unit 30 for setting a test principle; a test execution control unit 12 for making a measurement device 10 execute measurement of the tests of the plurality of test cases; and a priority order decision unit 16 that, depending on the test principle set by the operation unit 30 and a test result of an already executed test case of the plurality of test cases, determines priority order of test cases having not been executed of the plurality of test cases. The test execution control unit 12 makes the measurement device 10 execute measurement of the test cases having not been executed among the plurality of test cases in the order decided by the priority order decision unit 16.SELECTED DRAWING: Figure 1

Description

The present invention relates to a mobile terminal testing system and a mobile terminal testing method, and more particularly to a mobile terminal testing system and a mobile terminal testing method for executing a conformance test of mobile terminals conforming to the 3GPP standards.

In recent years, 5G services that operate millimeter waveband frequencies have started in various countries, and the production of 5G mobile terminals such as 5G smartphones is in full swing. A 5G mobile terminal design and development company or its manufacturing factory measures the output level and reception sensitivity of transmission radio waves through the wireless communication antenna provided in the 5G mobile terminal, and the 5G mobile terminal meets a predetermined standard. A performance test is performed to determine whether the requirements are met.

Among such performance tests, there is a conformance test for confirming whether mobile terminals and base station apparatuses conform to the 3GPP (3rd Generation Partnership Project) standard. In the conformance test, a test case (Test Case: TC) is executed, which defines a test purpose, pass/fail criteria, test conditions, a plurality of test items identified by Test ID, and a test procedure.

Patent Literature 1 describes a test system that automatically executes a plurality of test cases, with operation settings including replacement of software for each test device set as a set of test cases.

JP 2011-199719 A

As described in TS 38.522 of the 3GPP standard, the test cases to be executed are specified, but the test system can execute arbitrary test cases and the order of execution is not specified. For this reason, depending on the execution order of the test cases, the test time set for each test case may be unnecessarily spent.

Under similar test conditions, the modulation/demodulation circuit, RF circuit, and filter circuit used in the mobile terminal, and the settings of these circuits are the same. In such a case, there may be a series of successes (hereinafter also referred to as "PASS"), or conversely, a series of failures (hereinafter also referred to as "FAIL").

On the other hand, for example, a request to preferentially execute test cases that are likely to pass, or conversely, to preferentially execute test cases that are likely to fail and investigate the cause of failure. There is a request. However, the conventional test system has a problem that it is not possible to improve the efficiency of the test order and meet the demand for preferentially obtaining the test result according to the test purpose.

The present invention has been made to solve such conventional problems, and is a mobile terminal test system capable of obtaining useful test results in a short time before testing of all test cases is completed. and to provide a mobile terminal test method.

In order to solve the above problems, a mobile terminal test system according to the present invention is a mobile terminal test system that sequentially executes tests of a plurality of test cases defined by the 3GPP standards on a mobile terminal, wherein the test policy is a test policy setting unit for setting a test policy, a test execution control unit that causes a measuring device to measure the tests of the plurality of test cases, the test policy set by the test policy setting unit, and the plurality of test cases a priority determining unit that determines the priority of test cases whose execution has not been completed among the plurality of test cases according to the test results of the executed test cases, wherein the test execution control The unit is configured to cause the measuring device to measure a test case, among the plurality of test cases, which has not been executed, in the order of priority determined by the priority determining unit.

With this configuration, the mobile terminal testing system according to the present invention determines the priority order of test cases that have not been executed according to the test policy and the test results of the executed test cases, and according to this priority order, The measurement device is adapted to measure the tests of the test cases whose execution has not been completed. As a result, the mobile terminal testing system according to the present invention can obtain useful test results in a short period of time before testing of all test cases is completed.

Also, in the mobile terminal testing system according to the present invention, when the test policy set by the test policy setting part is the first policy, the priority determination unit may perform one of the plurality of test cases. The priority of test cases including test conditions or combinations of test conditions that have passed the test results of already completed test cases may be increased.

With this configuration, the mobile terminal testing system according to the present invention can provide test cases including test conditions or combinations of test conditions that have resulted in PASS in the test results of already-executed test cases when the test policy is the first policy. priority. As a result, the mobile terminal testing system according to the present invention classifies unexecuted test cases into those with a high possibility of passing and those with a high possibility of failing, and gives priority to the test cases with a high possibility of passing. can be run to verify compliance with the 3GPP standards.

Further, the mobile terminal testing system according to the present invention specifies a test condition or a combination of test conditions that causes the test result to fail when the test policy set by the test policy setting unit is the second policy. The priority determination unit may be configured to lower the priority of test cases including the test conditions or combinations of test conditions specified by the failure factor identification unit.

With this configuration, the mobile terminal testing system according to the present invention specifies a test condition or a combination of test conditions in which the test result is FAIL when the test policy is the second policy, and the specified test condition or test condition It is designed to lower the priority of test cases that include combinations of As a result, the mobile terminal testing system according to the present invention classifies unexecuted test cases into those with a high possibility of PASS and those with a high possibility of failing, and executes the test cases with a high possibility of failing. By lowering the priority of and deferring it, it is possible to shorten the test time until useful test results are obtained.

Further, in the mobile terminal testing system according to the present invention, when the test policy set by the test policy setting unit is the second policy, the test result of the executed test case among the plurality of test cases is further comprising a similar test case generation unit that generates a test case including a test condition or a combination of test conditions similar to the test condition or combination of test conditions that failed in The priority of the test cases generated by the similar test case generation unit may be increased when the identification unit has not identified the test conditions or the combination of test conditions that cause the test result to fail.

With this configuration, when the test policy is the second policy, the mobile terminal test system according to the present invention can be applied to test conditions or combinations of test conditions that result in FAIL in the test results of the executed test cases. A similar test case containing a similar test condition or a combination of test conditions is generated, and the priority of this similar test case is increased. As a result, the mobile terminal testing system according to the present invention classifies unexecuted test cases into those with a high possibility of passing and those with a high possibility of failing, and classifies similar test cases with a high possibility of failing. It can be executed preferentially to verify the cause of FAIL.

Further, a mobile terminal testing method according to the present invention is a mobile terminal testing method for sequentially executing a plurality of test cases defined by the 3GPP standard on a mobile terminal, and is a test policy for setting a test policy. a setting step, a test execution control step of causing a measuring device to measure tests of the plurality of test cases, a test policy set by the test policy setting step, and an executed test among the plurality of test cases and a priority determining step of determining a priority of test cases whose execution has not been completed among the plurality of test cases according to test results of the cases, wherein the test execution control step determines the priority. In the configuration, the measuring device is caused to measure a test of a test case that has not been completed among the plurality of test cases in the order of priority determined by the determining step.

Further, in the mobile terminal testing method according to the present invention, the priority determining step includes executing one of the plurality of test cases when the test policy set by the test policy setting step is a first policy. The priority of test cases including test conditions or combinations of test conditions that have passed the test results of already completed test cases may be increased.

Further, the mobile terminal testing method according to the present invention specifies a test condition or a combination of test conditions that causes the test result to fail when the test policy set by the test policy setting step is the second policy. and the priority determining step lowers the priority of test cases including the test conditions or combinations of test conditions identified by the failure factor identifying step.

Further, in the mobile terminal testing method according to the present invention, when the test policy set by the test policy setting step is the second policy, the test result of the executed test case among the plurality of test cases is further comprising a similar test case generation step of generating a test case including test conditions or a combination of test conditions similar to the test conditions or combination of test conditions that failed in The priority of the test cases generated by the similar test case generation step may be increased when the identification step does not identify the test conditions or the combination of test conditions that cause the test result to fail.

The present invention provides a mobile terminal testing system and a mobile terminal testing method that can obtain useful test results in a short period of time before testing of all test cases is completed.

1 is a block diagram showing the configuration of a mobile terminal testing system according to an embodiment of the present invention; FIG. FIG. 4 is a diagram showing an example combination of test frequencies, BWP bandwidths, and SSB constellations; FIG. 4 is a conceptual diagram showing a test case execution procedure; 4 is a flow chart showing processing of a mobile terminal testing method using the mobile terminal testing system according to the embodiment of the present invention; 5 is a flowchart showing details of processing in the flowchart of FIG. 4; 4 is a table showing a display example of test results for each test item in a certain combination of test conditions. FIG. 5 is a flow chart showing processing when an affirmative determination is made in step S3 of the flow chart of FIG. 4; FIG. 7 is a table showing a display example of test results for each test case;

Hereinafter, embodiments of a mobile terminal testing system and a mobile terminal testing method according to the present invention will be described with reference to the drawings.

A mobile terminal testing system 1 according to this embodiment shown in FIG. The mobile terminal test system 1 includes a measurement device 10 , a control device 20 , an operation section 30 and a display section 31 .

The measuring device 10 establishes a wireless communication connection or wired communication connection with the mobile terminal 100 to measure the transmission/reception characteristics of the mobile terminal 100 . The measuring apparatus 10 can measure, for example, transmission power, error vector amplitude (EVM), IQ constellation, spectrum, etc., as transmission characteristics of the mobile terminal 100 . Also, the measuring device 10 can measure, for example, packet error rate (PER), frame reception rate (FRR), etc., as reception characteristics of the mobile terminal 100 .

The control device 20 is composed of, for example, a microcomputer or a personal computer including a CPU, ROM, RAM, HDD, etc., and controls the operations of the above-described components that make up the mobile terminal testing system 1 . In addition, the control device 20 transfers a predetermined program stored in the ROM or the like to the RAM and executes it by the CPU, so that the test case storage unit 11, the test execution control unit 12, the pass/fail judgment unit 13, the failure factors, and the like, which will be described later. At least part of the identification unit 14, the similar test case generation unit 15, the priority determination unit 16, and the tendency storage unit 17 can be configured by software. At least part of the test case storage unit 11, the test execution control unit 12, the pass/fail determination unit 13, the failure factor identification unit 14, the similar test case generation unit 15, the priority order determination unit 16, and the trend storage unit 17 It is also possible to configure with a digital circuit such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). Alternatively, at least part of the test case storage unit 11, the test execution control unit 12, the pass/fail determination unit 13, the failure factor identification unit 14, the similar test case generation unit 15, the priority order determination unit 16, and the trend storage unit 17, It is also possible to combine hardware processing by digital circuits and software processing by a predetermined program as appropriate.

The test case storage unit 11 stores information on test cases for conformance tests conforming to the 3GPP standards. The test case storage unit 11 can also store information on test cases (hereinafter also referred to as “similar test cases”) generated by a similar test case generation unit 15, which will be described later.

The test execution control unit 12 controls the measurement device 10 to perform test measurement of the test cases read from the test case storage unit 11 . In addition, the test execution control unit 12 performs testing of test cases whose execution has not been completed among the plurality of test cases stored in the test case storage unit 11, according to the priority determined by the priority determination unit 16, which will be described later. It controls the measuring device 10 to perform the measurement of .

The pass/fail judgment unit 13 judges whether the test result of the test case is pass (PASS) or fail (FAIL) based on the result of measurement by the measuring device 10 and the pass/fail judgment criteria. Furthermore, the pass/fail determination unit 13 stores in the tendency storage unit 17 whether the test results for each test condition or combination of test conditions of the executed test cases are PASS or FAIL.

The test conditions are conditions set in the measuring device 10 in order to test the frequency, strength, and phase of signals transmitted and received by the mobile terminal 100 . Test conditions include, for example, test frequency [Low/Mid/High Range], BWP arrangement [Low/Mid/High test channel bandwidth], BWP bandwidth, SCS (Subcarrier Spacing) [Lowest, Mid, Highest], RB (Resource Block) arrangement, modulation scheme, SNR (Signal-to-Noise Ratio) limit, TCI (Transmission Configuration Indicator) QCL (Quasi Co-Location) setting [SSB (Synchronization Signal / PBCH block) / CSI-RS (Channel State Information Reference Signal)].

The operation unit 30 selects either the first policy (hereinafter also referred to as "similar PASS investigation") or the second policy (hereinafter also referred to as "similar FAIL investigation") as the test policy of the mobile terminal test system 1. Configure the test policy setting part for setting. A similar PASS search is a test strategy that identifies test conditions or combinations of test conditions that result in a PASS test result. Further, the similar FAIL investigation is a test policy that identifies test conditions or combinations of test conditions that result in a FAIL test result.

The failure factor specifying unit 14 specifies a test condition or a combination of test conditions that will result in a FAIL test result when the test policy set by the operation unit 30 is a similar FAIL investigation. Further, the failure factor identifying unit 14 may analyze the cause of FAIL in the test item including the identified test condition or combination of test conditions, and display the analysis result on the display unit 31 .

When the test policy set by the operation unit 30 is the similar FAIL investigation, the similar test case generation unit 15 generates tests similar to the test conditions or combinations of test conditions that have failed in the test results of the executed test cases. It is designed to generate similar test cases containing combinations of conditions or test conditions. For example, the similar test case generation unit 15 can generate similar test cases by changing the parameters of each test condition for which the test result is FAIL according to the user's operation input to the operation unit 30. be. A similar test case is used in the failure factor identification unit 14 to identify the cause of FAIL, and does not necessarily conform to the 3GPP standards.

Analysis of the cause of FAIL by the failure factor identification unit 14 will be described below. FIG. 2 is a diagram showing an example combination of test frequencies, BWP bandwidths, and SSB placements. Here, DC_1A_n78A represents the dual connectivity of the combination of LTE band 1 and 5G band n78. Also, DC_3A_n41A represents dual connectivity of a combination of LTE band 3 and 5G band n41.

For example, assume that the test result of a test item including a combination of DC_3A_n41A as the test frequency, 100 MHz as the BWP bandwidth, and High Range as the SSB allocation is FAIL. Among these combinations, if the test result of the test item of the test case (or similar test case) in which the test frequency is changed to DC_1A_n78A is PASS, the cause of FAIL is highly likely to be intermodulation distortion. In this case, the failure factor identification unit 14 displays on the display unit 31 that there is a possibility that the test result is FAIL due to intermodulation distortion.

Also, for example, it is assumed that the test result of the test item including the combination of DC_3A_n41A for the test frequency, 100 MHz for the BWP bandwidth, and High Range for the SSB allocation is FAIL. Among these combinations, if the test result of the test item of the test case (or similar test case) where the BWP bandwidth is changed to 20MHz is PASS, the cause of FAIL is the frequency characteristics and modulation/demodulation performance within the band. Very likely. In this case, the failure factor identification unit 14 displays on the display unit 31 that the test result may have been FAIL due to the frequency characteristics and modulation/demodulation performance within the band.

Also, for example, it is assumed that the test result of the test item including the combination of DC_3A_n41A for the test frequency, 100 MHz for the BWP bandwidth, and High Range for the SSB allocation is FAIL. Among these combinations, if the test result of the test item of the test case (or similar test case) where the SSB arrangement is changed to Low Range is PASS, the cause of FAIL may be the phase synchronization problem. expensive. In this case, the failure factor identifying unit 14 displays on the display unit 31 that the test result may have been FAIL due to phase synchronization failure.

The priority determining unit 16 stores test cases according to the test policy set by the operation unit 30 and the test results of executed test cases among the plurality of test cases stored in the test case storage unit 11. A priority order is determined for all test cases whose execution has not been completed among the plurality of test cases stored in the unit 11 . Further, the priority determining unit 16 may display a list of test cases scheduled to be executed on the display unit 31 in the order of execution schedule.

For example, when the test policy set by the operation unit 30 is a similar PASS investigation, the priority order determination unit 16 determines whether the test conditions or combinations of test conditions that have become PASS in the test results of the executed test cases. Increase case priority.

Further, for example, when the test policy set by the operation unit 30 is the similar FAIL investigation, the priority determination unit 16 determines whether the test case including the test condition or combination of test conditions specified by the failure factor specifying unit 14 lower the priority of

Further, for example, when the test policy set by the operation unit 30 is a similar FAIL investigation, the priority determination unit 16 determines that the failure factor identification unit 14 determines that the test condition or combination of test conditions that causes the test result to be FAIL. If not specified, increase the priority of existing test cases containing test conditions or combinations of test conditions similar to the test conditions or combinations of test conditions that failed in the test results of the executed test cases.

Further, for example, when the test policy set by the operation unit 30 is a similar FAIL investigation, the priority determination unit 16 determines that the failure factor identification unit 14 determines that the test condition or combination of test conditions that causes the test result to be FAIL. If not specified, the priority of the similar test case generated by the similar test case generation unit 15 is increased.

The test execution control section 12 includes a frequency control section 12a, an intensity control section 12b, a phase control section 12c, and a resource control section 12d.

The frequency control unit 12 a sets test conditions for the frequency used by the mobile terminal 100 in the measuring device 10 . The test conditions related to frequency are the test frequency, BWP arrangement, BWP bandwidth, etc., and correspond to the combination of filters in mobile terminal 100, filter performance, and the like. The test frequency is an LTE band, a 5G band, a combination of the LTE band and the 5G band (Band combo), or the like.

For example, as shown in FIG. 3, when the test frequency is DC_1A_n78A, the operating conditions of the mobile terminal 100 are: the band setting of the modulation/demodulation circuit is DC_1A_n78A; the internal oscillation setting of the RF circuit is 2.1 GHz and 3.5 GHz; Internally selected settings are 2-3 GHz and 3-4 GHz, and so on. After these operating conditions are set in the mobile terminal 100 by the measuring device 10, the test cases are repeatedly executed for each test frequency.

The strength control unit 12b sets test conditions for the strength of the signal transmitted from the mobile terminal 100 in the measuring device 10. FIG. Test conditions related to strength include SNR limits. The strength test conditions correspond to the performance of filters in the mobile terminal 100, the demodulation performance, and the like.

The phase controller 12 c sets test conditions for the phase of the signal transmitted from the mobile terminal 100 to the measuring device 10 . The phase-related test conditions include TCI QCL settings. The phase-related test conditions correspond to the demodulation performance within the mobile terminal 100 and the like.

The resource control unit 12 d sets test conditions for resources of signals transmitted from the mobile terminal 100 to the measuring device 10 . The test conditions for modulation/demodulation performance include the modulation scheme, RB allocation, and the like. The test conditions for the modulation/demodulation performance correspond to the modulation/demodulation performance of the mobile terminal 100 and the like.

The test execution control unit 12 performs control to execute either the similarity PASS investigation or the similarity FAIL investigation according to the user's operation input to the operation unit 30 . The outline of the similar PASS investigation and the similar FAIL investigation is as follows. Here, to simplify the explanation, it is assumed that the mobile terminal test system 1 is scheduled to execute four test cases TC1 to TC4 in the order of TC1, TC2, TC3, and TC4 in the initial settings.

For example, in the similar PASS survey, if the test frequency of test case TC1 has a PASS tendency in the Low/Mid Range of 5G band n78 and a FAIL tendency in the High Range, the priority determining unit 16 determines the remaining test case TC2 From among TC4, select a test case having a test condition where the test frequency is Low/Mid Range. If test case TC3 is a test case with only High Range conditions, the priority is given to Low/Mid Range of Test Case TC2, Low/Mid Range of Test Case TC4, High Range of Test Case TC2, and Test Case TC2. The high range of case TC3 and the high range of test case TC4 are lowered in this order.

In this way, the mobile terminal test system 1 preferentially executes test cases with a high PASS tendency, and thereby, before the test of all the test cases is completed, the test conditions or test conditions under which the test result becomes PASS are completed. can be specified.

Also, for example, in the similar FAIL investigation, the test frequency of test case TC1 has a PASS tendency in the Low/Mid Range of the 5G band n78, and a FAIL tendency in the High Range, and the level of the transmission signal of the mobile terminal 100 is no problem. However, it is assumed that the analysis by the failure factor identification unit 14 has revealed that the signal quality may be poor. In this case, the priority determining unit 16 selects the priority of test cases for measuring signal quality from the remaining test cases TC2 to TC4. If test case TC3 is a test case for signal quality measurement with only High Range conditions, the priority is given to High Range of test case TC3, High Range of test case TC2, High Range of test case TC4, and Test case TC3. The low/mid range of case TC2 and the low/mid range of test case TC4 are lowered in this order. Then, when High Range of test case TC3 is also FAIL, the failure factor identification unit 14 displays on the display unit 31 that the test result may have been FAIL due to poor signal quality of the mobile terminal 100. .

In this way, the mobile terminal test system 1 preferentially executes test cases with a high FAIL tendency, and thereby, before the test of all test cases is completed, the test conditions or test conditions where the test result becomes FAIL. and the cause of FAIL can be specified.

The operation unit 30 is for receiving an operation input by the user, and is configured by a touch panel including a touch sensor for detecting a contact position by a touch operation on an input surface corresponding to the display screen of the display unit 31, for example. . When the user touches the position of a specific item displayed on the display screen with a finger, stylus, or the like, the operation unit 30 recognizes the match between the position detected by the touch sensor on the display screen and the position of the item. As a result, a signal for executing the function assigned to each item is output to the control device 20 . The operation unit 30 may be operably displayed on the display unit 31, or may include an input device such as a keyboard or mouse.

By the user's operation input to the operation unit 30, it is possible to set the test strategy, specifications of the mobile terminal 100, parameters of various test conditions, and the like.

The display unit 31 is composed of a display device such as a liquid crystal display or a CRT, and displays various display contents such as setting screens and test results related to measurement of transmission/reception characteristics of the mobile terminal 100 by the measuring device 10 based on display control by the control device 20. is displayed on the display screen. The display contents include, for example, the test case execution order schedule, the measurement result of the transmission/reception characteristics of the mobile terminal 100 by the measurement device 10, and the like. Furthermore, the display unit 31 displays operation targets such as buttons, soft keys, pull-down menus, and text boxes for setting various conditions.

A mobile terminal testing method using the mobile terminal testing system 1 will be described below with reference to the flowchart of FIG.

First, the test execution control unit 12 sets various information such as the test policy and the specifications of the mobile terminal 100 according to the user's operation on the operation unit 30 (test policy setting step S1).

Next, the test execution control unit 12 causes the measuring device 10 to measure one test case that has not been executed or has not been executed among the plurality of test cases scheduled to be executed ( Test execution control step S2).

Next, the test execution control unit 12 determines whether or not a test strategy has been set by the operation unit 30 (step S3). When the test strategy has been set by the operation unit 30, the test execution control unit 12 executes the process of step S21, which will be described later. On the other hand, if the test strategy has not been set by the operation unit 30, the test execution control unit 12 executes the process of step S4.

In step S4, the test execution control unit 12 determines whether there are test cases that have not been executed or whose execution has not been completed (step S4). If test cases to be executed remain, the processes from step S2 onward are executed again. On the other hand, if there are no test cases left to be executed, the process of step S5 is executed.

In step S5, the test execution control unit 12 controls display of the test results of all the test cases executed in step S2 and the like on the display screen of the display unit 31 (step S5).

An example of the processing of step S2 will be described below with reference to the flowchart of FIG. Here, for the 5G band n1, a case of executing a test case regarding the characteristics of the maximum transmission level of the mobile terminal 100 will be described as an example. In addition, each test condition is an example for description.

First, the frequency control unit 12a of the test execution control unit 12 sets one of the Low/Mid/High ranges of the 5G band n1 to the measuring device 10 (step S11).

Next, the frequency control unit 12a of the test execution control unit 12 sets any one of 10 MHz, 20 MHz, and 40 MHz as the BWP bandwidth in the measuring device 10 (step S12).

Next, the frequency control unit 12a of the test execution control unit 12 sets either 15 kHz or 30 kHz as the SCS to the measuring device 10 (step S13). The above steps S11 to S13 are steps for setting test conditions.

Next, the test execution control unit 12 causes the measuring device 10 to measure the test items with Test IDs 1 to 6 using the combination of test conditions set in steps S11 to S13 (step S14).

The pass/fail determination unit 13 determines whether the test results of the test items with Test IDs 1 to 6 are PASS or FAIL, based on the measurement result of the maximum transmission level by the measuring device 10 (step S15).

The test execution control unit 12 determines whether or not there are any unexecuted test items in the combination of test conditions set in steps S11 to S13 (step S16). If there are unexecuted tests for test items in the combination of test conditions set in steps S11 to S13, the processes from step S14 onward are executed again. On the other hand, when the tests for all test items have been completed in the combination of test conditions set in steps S11 to S13, the process of step S17 is executed.

As shown in FIG. 6, the test execution control unit 12 controls display of the test results of the test items under the combination of test conditions set in steps S11 to S13 on the display screen of the display unit 31 (step S17).

The test execution control unit 12 determines whether or not there remains a combination of test conditions that have not been set in steps S11 to S13 (step S18). If there remains a combination of test conditions that have not been set, the processing from step S11 onward is executed again. On the other hand, when all combinations of test conditions are set, a series of processing ends.

In this manner, the test execution control unit 12 executes the test for each test item while changing the combination of test conditions in steps S11 to S13.

Hereinafter, the processing when it is determined that the test policy has been set by the operation unit 30 in step S3 will be described with reference to the flowchart of FIG.

First, the pass/fail determination unit 13 causes the trend storage unit 17 to store the test results of the test cases executed in step S2 and the like in association with test conditions such as frequency, intensity, and phase (step S21). The trend storage unit 17 stores test results (PASS or FAIL) for each of these test conditions or combinations of test conditions.

Furthermore, in step S21, the pass/fail determination unit 13 stores the tendency of the test conditions or the combination of test conditions in the test items that have passed among the test items in the test cases executed in step S2 and the like to have a PASS tendency. be memorized. For example, in the test cases executed in step S2 or the like, when all test items including a specific modulation method (here, "Modulation1") pass, the pass/fail determination unit 13 performs a test including Modulation1 as a test condition. The tendency storage unit 17 stores that the item is the PASS tendency.

Similarly, in step S21, the pass/fail determination unit 13 stores in the trend storage unit that the test conditions or combinations of test conditions in the failed test items among the test items in the test cases executed in step S2 and the like have a tendency to fail. Store in 17. For example, in the test cases executed in step S2 or the like, when all test items including a specific modulation method (here, "Modulation1") fail, the pass/fail determination unit 13 performs a test including Modulation1 as a test condition. The tendency storage unit 17 is made to store that the item is the FAIL tendency.

Next, the test execution control unit 12 determines whether the test policy set in the test policy setting step S1 is a similar PASS investigation or a similar FAIL investigation (step S22). If the similar PASS survey is set, the process of step S23 is executed. On the other hand, when the similar FAIL investigation is set, the process of step S28 is executed.

In step S23, the test execution control unit 12 determines whether at least one of the test results of each test item of the test cases executed in step S2 or step S26 described later has a FAIL (step S23). . If there is no FAIL in the test results of the test cases of each test item executed in step S2 or step S26, which will be described later, the process of step S24 is executed. On the other hand, if even one of the test results of the test cases of each test item executed in step S2 or step S26, which will be described later, is FAIL, the process of step S27 is executed.

In step S24, the test execution control unit 12 determines whether execution of all test cases in which test items including test conditions or combinations of test conditions having a PASS tendency stored in step S21 are defined has been completed. to decide. For example, the test execution control unit 12 determines whether or not all test cases defined with test items including Modulation1 in the test conditions have been executed. If execution of all the test cases defined in step S21 with test conditions or test item combinations including test conditions having a PASS tendency or combination of test conditions has not been completed, the process of step S25 is executed. On the other hand, if execution of all test cases defined in step S21 and having test conditions or test item combinations that have a PASS tendency has been completed, the process of step S4 is executed.

In step S25, the priority determining unit 16 selects, among test cases defined as test items including test conditions or combinations of test conditions that have become PASS in the test results of executed test cases, tests that have not been executed. The priority of the case is set to the highest order, and the execution order of all test cases whose execution has not been completed is updated (priority determination step S25).

Next, the test execution control unit 12 causes the measuring device 10 to measure the test of the test case with the highest priority set in step S25 (test execution control step S26). For example, in the test case executed in step S2 or the like, if all the test items including Modulation1 in the test condition pass, the test execution control unit 12 determines that the test item including Modulation1, which is the test condition expected to pass, is defined as PASS. Prioritize execution of test cases. When the processing of step S26 is completed, the processing after step S21 is executed again.

In step S27, the priority determining unit 16 lowers the priority of the test cases defined as test items including test conditions or combinations of test conditions that are commonly included in the failed tests. update the execution order of all test cases that have not been executed (priority determination step S27). For example, for the test cases executed in step S2 or the like, if FAIL occurs only for a test item that includes a combination of Modulation 1 and a test frequency High Range condition, the priority order determination unit 16 Decrease the priority of test cases that contain combinations. As a result, in step S2 that is executed after step S27, test cases that define test items that include a combination of Modulation 1 and the test frequency Low/Mid Range conditions are preferentially executed. When the process of step S27 is completed, the process of step S4 is executed.

In step S28, the failure factor identifying unit 14 identifies, among the test results of each test item of the test cases executed in step S2 and the like, the test condition or combination of test conditions that causes the test result to be FAIL (failure Factor identification step S28).

Next, the test execution control unit 12 determines whether or not a test condition or a combination of test conditions that causes a test result of FAIL has been identified in the failure factor identification step S28 (step S29). The determination here is made, for example, based on whether or not the number of FAILs for each test condition or each combination of test conditions exceeds a predetermined threshold. If a test condition or a combination of test conditions that causes the test result to be FAIL can be specified by the failure factor specifying step S28, the process of step S30 is executed. On the other hand, if the failure factor identification step S28 fails to identify the test condition or the combination of the test conditions that causes the test result to be FAIL, the process of step S31 is executed.

In step S30, the priority determining unit 16 lowers the priority of the test cases in which test items including the test conditions or combinations of test conditions identified in the failure factor identification step S28 are lowered. Update the execution order of all test cases that have not been executed (priority determination step S30). When the process of step S30 is completed, the process of step S4 is executed.

In step S<b>31 , the test execution control unit 12 determines whether or not an instruction to generate a similar test case has been input by the user's operation input to the operation unit 30 . When an instruction to generate a similar test case is input to the operation unit 30, the process of step S32 is executed. On the other hand, if no instruction to generate a similar test case has been input to the operation unit 30, the process of step S35 is executed.

In step S32, the similar test case generation unit 15 generates a similar test case including a test condition or a combination of test conditions similar to the test condition or combination of test conditions that failed in the test results of the executed test cases. (Similar test case generation step S32).

Next, the priority determining unit 16 sets the highest priority to the similar test cases that have not been executed and generated in the similar test case generating step S32, and sets the execution order of all the test cases that have not been executed to the highest priority. is updated (priority determination step S33).

Next, the test execution control unit 12 causes the measuring device 10 to measure the test of the similar test case with the highest priority set in the priority determination step S33 (test execution control step S34). When the processing of step S34 is completed, the processing after step S21 is executed again.

In step S35, the priority determining unit 16 selects, among test cases defined as test items including test conditions or combinations of test conditions that have failed in the test results of executed test cases, tests that have not been executed. The priority of the case is set to the highest order, and the execution order of all test cases whose execution has not been completed is updated (priority determination step S35).

Next, the test execution control unit 12 causes the measuring device 10 to measure the test of the test case with the highest priority set in step S35 (test execution control step S36). When the processing of step S36 is completed, the processing after step S21 is executed again.

FIG. 8 shows an example of test results displayed on the display section 31 in step S5 of the flowchart of FIG. Here, it is assumed that the number of test cases is 4 for simplification of explanation. The test result of each test case TC1 to TC4 is PASS when all the test items defined for each test case TC1 to TC4 are PASS, and FAIL otherwise.

In the flowchart of FIG. 4, all the tests of one test case are executed in step S2. 1 may omit useless measurements, such as rounding up the test of a test case in which a test item with no PASS probability is defined. In that case, the mobile terminal testing system 1 executes the processing in which one test case in step S2 is read as one test item, and in step S2 and thereafter, the processing or determination in units of test cases is processed or determined in units of test items. A process that is read as a judgment is executed. As a result, for example, if a test item with a Test ID of 1 fails in a certain test case, it is possible to omit the execution of the test items with a Test ID of 2 or later, and proceed to the test of the next test case. Become.

As described above, the mobile terminal testing system 1 according to the present embodiment determines the priority order of test cases that have not been executed according to the test policy and the test results of the executed test cases, According to this priority, the measuring device 10 is made to measure the tests of the test cases whose execution has not been completed. As a result, the mobile terminal testing system 1 according to this embodiment can obtain useful test results in a short period of time before testing of all test cases is completed.

In addition, the mobile terminal testing system 1 according to the present embodiment, when the test policy is a similar PASS survey, is a test condition or a combination of test conditions that has become PASS in the test results of already-executed test cases. Priority is raised. As a result, the mobile terminal testing system 1 according to the present embodiment classifies unexecuted test cases into those with a high possibility of passing and those with a high possibility of failing, and classifies the test cases with a high possibility of passing. can be preferentially executed to check compliance with the 3GPP standards. It should be noted that the similar PASS investigation may be ended halfway and the similar FAIL investigation may be started based on the status of the intermediate results of the similar PASS investigation.

Further, the mobile terminal testing system 1 according to the present embodiment specifies a test condition or a combination of test conditions in which the test result is FAIL when the test policy is similar FAIL investigation, and the specified test condition or test condition combination The priority of test cases containing combinations is lowered. As a result, the mobile terminal testing system 1 according to the present embodiment classifies unexecuted test cases into those with a high possibility of passing and those with a high possibility of failing, and classifies the test cases with a high possibility of failing. By lowering the priority of the execution of and deferring it, it is possible to shorten the test time until useful test results are obtained.

In addition, when the test policy is the similar FAIL investigation, the mobile terminal testing system 1 according to the present embodiment provides a similar test condition or a combination of test conditions that has resulted in a FAIL test result in the test results of the executed test cases. A similar test case including test conditions or a combination of test conditions is generated, and the priority of this similar test case is raised. As a result, the mobile terminal testing system 1 according to this embodiment classifies unexecuted test cases into those with a high possibility of PASS and those with a high possibility of failing, and performs similar tests with a high possibility of failing. A case can be prioritized to verify the cause of FAIL.

1 mobile terminal test system 10 measuring device 11 test case storage unit 12 test execution control unit 12a frequency control unit 12b intensity control unit 12c phase control unit 12d resource control unit 13 pass/fail determination unit 14 failure factor identification unit 15 similar test case generation unit 16 Priority Order Determination Unit 17 Trend Storage Unit 20 Control Device 30 Operation Unit 31 Display Unit 100 Mobile Terminal

Also, in the mobile terminal testing system according to the present invention, the priority determination unit specifies the test conditions or the combination of test conditions under which the test policy set by the test policy setting unit passes the test result . 1 policy, the priority of a test case including a test condition or a combination of test conditions that has passed in the test results of the executed test cases among the plurality of test cases, wherein good too.

Further, in the mobile terminal testing system according to the present invention, when the test policy set by the test policy setting unit is a second policy that specifies a test condition or a combination of test conditions that causes the test result to fail , , a failure factor identification unit that identifies a test condition or a combination of test conditions that causes the test result to fail, wherein the priority determination unit determines the test conditions or the test conditions identified by the failure factor identification unit may be configured to lower the priority of test cases that include a combination of

Further, in the mobile terminal testing system according to the present invention, when the test policy set by the test policy setting unit is the second policy, the testing of executed test cases among the plurality of test cases is performed. A similar test case generation unit that generates a test case including test conditions or a combination of test conditions similar to the test condition or combination of test conditions that failed as a result, wherein the priority determining unit The priority of the test cases generated by the similar test case generation unit may be increased when the factor identification unit does not identify the test conditions or the combination of test conditions that cause the test result to fail. .

Further, in the mobile terminal testing method according to the present invention, the priority determination step includes the test policy set by the test policy setting step specifying a test condition or a combination of test conditions for which the test result passes . 1 policy, the priority of a test case including a test condition or a combination of test conditions that has passed in the test results of the executed test cases among the plurality of test cases, wherein good too.

Further, in the mobile terminal testing method according to the present invention, when the test policy set by the test policy setting step is a second policy that specifies a test condition or a combination of test conditions that causes the test result to fail , , further comprising a failure factor identification step of identifying a test condition or a combination of test conditions that causes the test result to fail, wherein the priority order determination step includes the test conditions or the test conditions identified by the failure factor identification step may be configured to lower the priority of test cases that include a combination of

Further, in the mobile terminal testing method according to the present invention, when the test policy set by the test policy setting step is the second policy, the testing of executed test cases among the plurality of test cases is performed. further comprising a similar test case generation step of generating test cases including test conditions or combinations of test conditions similar to the test conditions or combinations of test conditions that failed in the results, wherein the prioritization step includes: The priority of the test cases generated by the similar test case generation step may be increased when the factor identification step does not identify the test conditions or the combination of test conditions that cause the test result to fail. .

Claims (8)

A mobile terminal testing system (1) for sequentially executing a plurality of test case tests defined by the 3GPP standards for a mobile terminal (100),
a test policy setting unit (30) for setting a test policy;
a test execution control unit (12) that causes a measurement device (10) to measure the tests of the plurality of test cases;
A test case that has not been executed among the plurality of test cases according to the test policy set by the test policy setting unit and the test result of the executed test case among the plurality of test cases A priority determination unit (16) that determines the priority of
The test execution control unit causes the measurement device to measure the test of a test case that has not been completed among the plurality of test cases, in the order of priority determined by the priority determination unit. mobile terminal test system. When the test policy set by the test policy setting unit is a first policy, the priority order determination unit passes the test results of the executed test cases among the plurality of test cases. 2. The mobile terminal testing system according to claim 1, wherein a test case including a test condition or a combination of test conditions is prioritized. a failure factor identification unit (14) for identifying a test condition or a combination of test conditions that causes the test result to fail when the test policy set by the test policy setting unit is the second policy; ,
2. The mobile terminal testing system according to claim 1, wherein said priority determining section lowers the priority of a test case including the test condition or combination of test conditions identified by said failure factor identifying section. When the test policy set by the test policy setting unit is the second policy, the test condition or the test condition failed in the test result of the executed test case among the plurality of test cases Further comprising a similar test case generation unit (15) that generates a test condition containing a combination of similar test conditions or a combination of test conditions,
The priority determination unit determines whether the test cases generated by the similar test case generation unit are selected when the failure factor identification unit does not identify the test condition or the combination of test conditions that causes the test result to fail. 4. The mobile terminal testing system according to claim 3, wherein the priority is raised. A mobile terminal testing method for sequentially executing a plurality of test cases defined by the 3GPP standard for a mobile terminal (100),
a test policy setting step (S1) for setting a test policy;
a test execution control step (S2, S26, S34, S36) for causing a measuring device (10) to measure the tests of the plurality of test cases;
A test case that has not been executed among the plurality of test cases according to the test policy set by the test policy setting step and the test result of the executed test case among the plurality of test cases A priority order determination step (S25, S27, S30, S33, S35) for determining the priority order of
The test execution control step causes the measuring device to measure a test case that has not been executed among the plurality of test cases in the order of priority determined by the priority determination step. mobile terminal test method. In the priority determining step, when the test policy set by the test policy setting step is the first policy, the test results of the executed test cases among the plurality of test cases have passed. 6. A mobile terminal testing method according to claim 5, characterized in that the priority of test cases containing test conditions or combinations of test conditions is increased. further comprising a failure factor identification step (S28) for identifying a test condition or a combination of test conditions that causes the test result to fail when the test policy set in the test policy setting step is the second policy; ,
6. The mobile terminal testing method according to claim 5, wherein said priority determining step lowers the priority of a test case including the test condition or combination of test conditions specified by said failure factor specifying step. When the test policy set by the test policy setting step is the second policy, the test condition or the test condition failed in the test result of the executed test case among the plurality of test cases Further comprising a similar test case generation step (S32) for generating a test case including test conditions or a combination of test conditions similar to the combination,
The priority determining step determines the test cases generated by the similar test case generating step when the test condition or combination of test conditions that cause the test result to fail is not identified by the fail factor identifying step. 8. The mobile terminal testing method according to claim 7, wherein the priority is raised.

Images