Testing method, apparatus, testing device, storage medium, and computer program product

Abstract

The present application discloses a testing method, an apparatus, a testing device, a storage medium, and a computer program product. The method comprises: performing an in-device co-existence (IDC) auxiliary configuration and a first configuration on a terminal, and determining whether the terminal can detect an IDC issue under the first configuration; if the terminal can detect the IDC issue under the first configuration, performing an IDC mechanism testing process on the terminal, and / or generating a first test result for the terminal; or if the terminal fails to detect the IDC issue under the first configuration, not performing an IDC mechanism testing process on the terminal, and / or generating a second test result for the terminal.

Description

Test method, device, test equipment, storage medium and computer program product

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 202410178002.3 and application date of February 8, 2024, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The present application relates to the field of terminal technology, and in particular to a testing method, apparatus, testing equipment, storage medium, and computer program product. Background Art

[0004] In the related art, the Minimization of Drive Test (MDT) function of the wireless network (i.e., Radio Access Network (RAN)) is defined. The measurement report (i.e., MDT measurement report) used by the terminal (also referred to as User Equipment (UE)) for MDT can be transmitted through the control plane. The terminal can output the MDT measurement report according to the definition of the related art. By analyzing the signaling process and measurement results in the MDT measurement report to analyze the quality of the wireless network, the workload of the drive test (which can be expressed as Drive Test in English, abbreviated as DT) can be minimized. Among them, the MDT data defined in the related art (such as the data in the above-mentioned MDT measurement report) can be collected in two different modes: immediate mode and logged mode. With respect to the logged mode, the related art introduces an In-Device Co-existence (IDC) mechanism (the mechanism can also be called a method, which can be expressed as a mechanism in English) in MDT. In order to verify whether the MDT function of the terminal has an IDC mechanism that meets relevant technical requirements, a test mechanism for the IDC mechanism is also defined in the relevant technology.

[0005] However, the test mechanism in the related art may not accurately determine whether the terminal correctly supports the relevant functions of the IDC problem (which can be expressed as IDC problem in English), that is, it is impossible to accurately evaluate whether the MDT function of the terminal has an IDC mechanism that meets the relevant technical requirements. Summary of the Invention

[0006] To solve related technical problems, embodiments of the present application provide a testing method, apparatus, testing equipment, storage medium, and computer program product.

[0007] The technical solution of the embodiment of the present application is implemented as follows:

[0008] The present invention provides a testing method, including:

[0009] Configuring the terminal with the IDC auxiliary configuration and the first configuration, and confirming whether the terminal can detect the IDC problem under the first configuration;

[0010] In a case where the terminal is capable of detecting an IDC problem under the first configuration, performing an IDC mechanism test process on the terminal and / or generating a first test result for the terminal; or

[0011] In a case where the terminal cannot detect the IDC problem under the first configuration, the IDC mechanism test process is not performed on the terminal, and / or a second test result is generated for the terminal.

[0012] In the above solution, under the first configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest.

[0013] In the above solution, confirming whether the terminal can detect the IDC problem under the first configuration includes:

[0014] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the first configuration when the terminal is in a connected state, and that the IDC problem can be detected under the first configuration when the terminal is in an idle state;

[0015] or,

[0016] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the first configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the first configuration, or it cannot be confirmed that the IDC problem is detected under the first configuration.

[0017] In the above solution, the method further includes:

[0018] confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0019] If the terminal is capable of detecting an IDC problem under the second configuration, executing the first sub-process of the IDC mechanism test process on the terminal and not executing the second sub-process of the IDC mechanism test process on the terminal, and / or generating a third test result for the terminal; or

[0020] In the case that the terminal cannot detect the IDC problem under the second configuration, the first sub-process and / or the second sub-process of the IDC mechanism test process are executed on the terminal, and / or a fourth test result for the terminal is generated; wherein,

[0021] The first sub-process is at least used to check that when an IDC problem is detected, measurement logging is suspended and an IDC detection flag is used in a measurement information table of the measurement log to mark an MDT report;

[0022] The second sub-process is at least used to check that the measurement record is restored when the IDC problem is resolved.

[0023] In the above solution, under the second configuration, the first channel and the second channel of the terminal are configured as at least one of the following:

[0024] The first channel and the second channel of the terminal are configured as a maximum distance;

[0025] The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest;

[0026] No information is transmitted on the first channel and / or the second channel of the terminal;

[0027] The first channel and / or the second channel of the terminal is closed.

[0028] In the above solution, the confirming whether the terminal cannot detect the IDC problem under the second configuration includes:

[0029] performing the second configuration on the terminal;

[0030] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the terminal can detect the IDC problem under the second configuration when in a connected state, and can detect the IDC problem under the second configuration when the terminal is in an idle state; or

[0031] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the second configuration when the terminal is in a connected state, or it cannot be confirmed that the IDC problem can be detected under the second configuration when the terminal is in a connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the second configuration, or it cannot be confirmed that the IDC problem is detected under the second configuration, or the IDC problem has been resolved under the second configuration.

[0032] In the above solution, the confirming whether the terminal cannot detect the IDC problem under the second configuration includes:

[0033] Before confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0034] If the terminal cannot detect the IDC problem under the second configuration, confirm whether the terminal can detect the IDC problem under the first configuration, and if the terminal can detect the IDC problem under the first configuration, perform the first sub-process and / or the second sub-process on the terminal to generate the first test result; or

[0035] If the terminal is able to detect the IDC problem under the second configuration, confirm whether the terminal is able to detect the IDC problem under the first configuration, and if the terminal is able to detect the IDC problem under the first configuration, execute the first sub-process on the terminal and do not execute the second sub-process on the terminal, to generate the first test result.

[0036] In the above solution, the confirming whether the terminal cannot detect the IDC problem under the second configuration includes:

[0037] After confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration.

[0038] In the above solution, confirming whether the terminal can detect the IDC problem under the first configuration includes:

[0039] confirming whether the terminal can detect the IDC problem in the first configuration by confirming whether the terminal cannot detect the IDC problem in the second configuration;

[0040] In a case where the terminal is capable of detecting the IDC problem under the second configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the first configuration.

[0041] In the above solution, under the first configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest;

[0042] In the second configuration, the first channel and the second channel of the terminal are configured as at least one of the following:

[0043] The first channel and the second channel of the terminal are configured as a maximum distance;

[0044] The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest;

[0045] No information is transmitted on the first channel and / or the second channel of the terminal;

[0046] The first channel and / or the second channel of the terminal is closed.

[0047] In the above solution, in executing the IDC mechanism test process on the terminal, the configuration performed on the terminal includes the first configuration.

[0048] The present application also provides a testing method, including:

[0049] Execute the IDC mechanism test process on the terminal;

[0050] If no fifth test result is obtained, configuring the terminal with the IDC auxiliary configuration and the third configuration, and confirming whether the terminal can detect the IDC problem under the third configuration, the fifth test result including suspending measurement recording;

[0051] A sixth test result for the terminal is generated according to whether the terminal is able to detect the IDC problem under the third configuration.

[0052] In the above solution, under the third configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest.

[0053] In the above solution, confirming whether the terminal can detect the IDC problem under the third configuration includes:

[0054] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the third configuration when the terminal is in a connected state, and that the IDC problem can be detected under the third configuration when the terminal is in an idle state;

[0055] or,

[0056] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the third configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the third configuration, or it cannot be confirmed that the IDC problem is detected under the third configuration.

[0057] In the above solution, confirming whether the terminal can detect the IDC problem under the third configuration includes:

[0058] confirming whether the terminal can detect the IDC problem under the third configuration by confirming whether the terminal cannot detect the IDC problem under the fourth configuration;

[0059] In a case where the terminal is able to detect the IDC problem under the fourth configuration, it is confirmed that the terminal is able to detect the IDC problem under the third configuration.

[0060] In the above solution, under the third configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest;

[0061] In the fourth configuration, the first channel and the second channel of the terminal are configured as at least one of the following:

[0062] The first channel and the second channel of the terminal are configured as a maximum distance;

[0063] The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest;

[0064] No information is transmitted on the first channel and / or the second channel of the terminal;

[0065] The first channel and / or the second channel of the terminal is closed.

[0066] In the above solution, the confirming whether the terminal cannot detect the IDC problem under the fourth configuration includes:

[0067] performing the fourth configuration on the terminal;

[0068] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the fourth configuration when the terminal is in a connected state, and that the IDC problem can be detected under the fourth configuration when the terminal is in an idle state; or

[0069] In the case that the terminal does not send IDC auxiliary information, and / or in the case that the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the fourth configuration when the terminal is in the connected state, or it cannot be confirmed that the IDC problem can be detected under the fourth configuration when the terminal is in the connected state; and when the terminal is in the idle state, the IDC problem cannot be detected under the fourth configuration, or it cannot be confirmed that the IDC problem is detected under the fourth configuration, or the IDC problem has been resolved under the fourth configuration.

[0070] In the above solution, in executing the IDC mechanism test process on the terminal, the configuration performed on the terminal includes the third configuration.

[0071] The present application also provides a testing device, including:

[0072] a first testing unit configured to configure the terminal with the IDC auxiliary configuration and the first configuration, and confirm whether the terminal can detect the IDC problem under the first configuration;

[0073] The second test unit is configured to, when the terminal can detect the IDC problem under the first configuration, execute the IDC mechanism test process on the terminal and / or generate a first test result for the terminal; or, when the terminal cannot detect the IDC problem under the first configuration, not execute the IDC mechanism test process on the terminal and / or generate a second test result for the terminal.

[0074] The present application also provides a testing device, including:

[0075] A third testing unit is configured to execute an IDC mechanism testing process on the terminal;

[0076] The fourth test unit is configured to, if the fifth test result is not obtained, configure the IDC auxiliary configuration and the third configuration of the terminal, and confirm whether the terminal can detect the IDC problem under the third configuration, and the fifth test result includes suspending measurement records; based on the confirmation of whether the terminal can detect the IDC problem under the third configuration, generate a sixth test result for the terminal.

[0077] The embodiment of the present application further provides a testing device, comprising: a communication interface and a processor; wherein,

[0078] The processor is configured to: configure the IDC auxiliary configuration and the first configuration on the terminal, and confirm whether the terminal can detect the IDC problem under the first configuration; if the terminal can detect the IDC problem under the first configuration, perform an IDC mechanism test process on the terminal and / or generate a first test result for the terminal; or, if the terminal cannot detect the IDC problem under the first configuration, not perform the IDC mechanism test process on the terminal and / or generate a second test result for the terminal;

[0079] or,

[0080] The processor is configured to: execute an IDC mechanism test process on the terminal; if no fifth test result is obtained, configure the terminal with an IDC auxiliary configuration and a third configuration, and confirm whether the terminal can detect an IDC problem under the third configuration, wherein the fifth test result includes suspending measurement recording; and generate a sixth test result for the terminal based on the confirmation of whether the terminal can detect the IDC problem under the third configuration.

[0081] The present application also provides a testing device, comprising: a processor and a memory configured to store a computer program that can be run on the processor.

[0082] The processor is configured to execute the steps of any of the above methods when running the computer program.

[0083] An embodiment of the present application further provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0084] An embodiment of the present application further provides a computer program product, comprising a computer program, which implements the steps of any of the above methods when executed by a processor.

[0085] The test method, apparatus, test equipment, storage medium, and computer program product provided in the embodiments of the present application configure an IDC auxiliary configuration and a first configuration on a terminal, and confirm whether the terminal can detect an IDC problem under the first configuration; if the terminal can detect an IDC problem under the first configuration, perform an IDC mechanism test process on the terminal, and / or generate a first test result for the terminal; or, if the terminal cannot detect an IDC problem under the first configuration, do not perform an IDC mechanism test process on the terminal, and / or generate a second test result for the terminal. Alternatively, perform an IDC mechanism test process on the terminal; if no fifth test result is obtained, perform an IDC auxiliary configuration and a third configuration on the terminal, and confirm whether the terminal can detect an IDC problem under the third configuration, the fifth test result including suspending measurement records; and generate a sixth test result for the terminal based on the confirmation of whether the terminal can detect an IDC problem under the third configuration. The solution provided by the embodiment of the present application is to first configure the IDC auxiliary configuration and the specific channel configuration (i.e., the above-mentioned first configuration) on the terminal before executing the IDC mechanism test process on the terminal, and confirm whether the terminal can detect the IDC problem under the specific channel configuration, and then execute the IDC mechanism test process on the terminal if the IDC problem can be detected; or, after executing the IDC mechanism test process on the terminal, if the terminal fails the test, that is, if the test result including the suspension measurement record is not obtained, configure the IDC auxiliary configuration and the specific channel configuration (i.e., the above-mentioned third configuration) on the terminal, and confirm whether the terminal can detect the IDC problem under the specific channel configuration. It can detect IDC problems and then generate the final test results for the terminal based on the confirmed results. In this way, it can avoid the situation where "IDC problems do not occur during the execution of the IDC mechanism test process on the terminal due to excellent terminal design (which can be understood as the terminal being able to support the IDC mechanism and improve the IDC problem)" is mistakenly judged as the terminal failing the test. In other words, it can avoid the problem of qualified terminals that can support the IDC mechanism being mistakenly judged as unqualified terminals that cannot support the IDC mechanism, so that it can accurately determine whether the terminal correctly supports the relevant functions of the IDC problem, that is, it can accurately evaluate whether the MDT function of the terminal has an IDC mechanism that meets the relevant technical requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] FIG1 is a schematic diagram of a flow chart of a testing method according to an embodiment of the present application;

[0087] FIG2 is a schematic diagram of a test process according to an embodiment of the present application;

[0088] FIG3 is a schematic diagram of another test process according to an embodiment of the present application;

[0089] FIG4 is a schematic diagram of a third test flow in accordance with an embodiment of the present application;

[0090] FIG5 is a schematic diagram of a fourth test flow in accordance with an embodiment of the present application;

[0091] FIG6 is a flow chart of another testing method according to an embodiment of the present application;

[0092] FIG7 is a schematic diagram of the fifth test flow of an embodiment of the present application;

[0093] FIG8 is a schematic diagram of the structure of a testing device according to an embodiment of the present application;

[0094] FIG9 is a schematic structural diagram of another testing device according to an embodiment of the present application;

[0095] FIG10 is a schematic diagram of the structure of the test equipment according to an embodiment of the present application. DETAILED DESCRIPTION

[0096] The present application will be described in further detail below with reference to the accompanying drawings and embodiments.

[0097] In related technologies, immediate-mode MDT data collection relies on measurement results provided by the wireless network and terminals. Terminal measurements are derived from Radio Resource Control (RRC) measurement reports. The wireless network can also include data such as power headroom reported by the Medium Access Control (MAC) layer, received interference power (RIP) measured by the cell antenna at the physical radio interface layer, data volume, Internet Protocol (IP) throughput, user-plane packet delay reports, and packet loss rate measured by the base station.

[0098] In logging mode, the terminal stores information related to accessibility issues in idle mode, RRC establishment failures, random access during handovers, and radio link failures (which may include connection loss). The terminal's MDT event log (i.e., the MDT measurement report mentioned above, also referred to as an MDT report, can be expressed in English as MDT report) is sent to the network upon request. If the radio connection is lost (i.e., a link is disconnected), the terminal sends an MDT logging mode report (i.e., an MDT measurement report) after the next successful radio connection is established.

[0099] Definitions and explanations of the IDC problem include: To enable ubiquitous access to a variety of networks and services, more and more terminals are equipped with multiple radio transceivers; for example, terminals may be equipped with Long Term Evolution (LTE), Wireless Fidelity (WiFi), Bluetooth transceivers, and Global Navigation Satellite System (GNSS) receivers. Because multiple radio transceivers in the same terminal operate on adjacent frequencies or sub-harmonic frequencies, the interference power from collocated radio transmitters can be much higher than the actual received power of the desired signal at the receiver. This situation causes IDC interference, known as the IDC problem. Because current state-of-the-art filter technology may not provide sufficient interference suppression capabilities in some cases, avoiding or minimizing IDC interference between these collocated radio transceivers is a challenge. When a terminal (intends to) use a wireless local area network (WLAN) on an overlapping carrier / band or adjacent carrier / band of an unlicensed carrier used for licensed spectrum assisted access (LAA, Licensed-Assisted Access or License Assisted Access) operation, for example, when relevant terminal hardware components (such as antennas, etc.) are shared between LAA and WLAN operations, an IDC problem may occur. If there is an unavoidable risk of IDC problems (such as those affected by regulatory levels, etc.), the base station (such as eNB, etc.) should configure the terminal's IDC function when the terminal is configured for LAA operation, that is, configure the terminal's IDC mechanism.

[0100] The IDC mechanism introduced in MDT for logging mode includes the following: once an IDC problem is detected, the terminal suspends recording measurement reports and reports an IDC detection flag (InDeviceCoexDetected-r17 in English) through the measurement report (this flag can also be understood as a sign or mark, which can be expressed as flag in English). In other words, when the terminal detects an IDC problem, the terminal suspends measurement logging and marks the MDT report with the IDC detection flag in the measurement information table of the measurement record. Once the IDC problem is resolved, the terminal resumes measurement logging (which can be expressed as resume the measurement logging in English). In other words, when the IDC problem detected by the terminal is resolved during the previous logging interval, the terminal resumes measurement logging.

[0101] The test mechanism (also referred to as a test case or test process, etc.) for the IDC mechanism defined to verify whether the MDT function of the terminal has an IDC mechanism that meets relevant technical requirements includes: introducing 2.4 GHz WiFi as an interference source to interfere with the 2300-2400 MHz frequency band (i.e., Band n40) of the New Radio (NR), constructing an IDC condition, and then verifying whether the terminal will suspend recording and report the IDC detection (InDeviceCoexDetected-r17) identification (also understood as a sign or mark, expressed as flag in English) through the measurement report; and whether the terminal will resume measurement recording after the IDC problem is resolved.

[0102] However, some well-designed terminals may have certain solutions to improve IDC issues, such as using software strategies to prevent 2.4GHz WiFi and Band n40 from operating simultaneously. For example, when interference risks are detected, WiFi can be adjusted to a channel away from the cellular network operating frequency, or the cellular network operating frequency can be adjusted to a channel away from the WiFi operating frequency. Therefore, even if the test environment is set to 2.4GHz WiFi and the 2300-2400MHz frequency band (i.e., Band n40), the terminal may not necessarily experience IDC issues. According to the IDC mechanism test mechanism defined in the relevant technology, if a well-designed terminal does not exhibit the expected pause recording state due to the absence of an IDC issue, it will be mistakenly judged as not correctly supporting the relevant functions of the IDC issue. In other words, using the test mechanism in the relevant technology may not accurately determine whether the terminal correctly supports the relevant functions of the IDC issue, that is, it is impossible to accurately evaluate whether the terminal's MDT function has an IDC mechanism that meets the relevant technical requirements.

[0103] Therefore, the embodiment of the present application considers combining the IDC auxiliary configuration (which can be expressed as idc-AssistanceConfig-r16 in English) and the IDC mechanism test process to comprehensively determine whether the terminal correctly supports the relevant functions of the IDC problem. Among them, in the related technology, when the terminal is in a connected state (which can be expressed as connected mode and / or RRC_CONNECTED in English), as long as the network configures the terminal with IDC assistance information (which can be expressed as IDC assistance information in English, or can also be expressed as idc-AssistanceConfig-r16), that is, when the network configures the terminal with IDC assistance configuration, once the terminal detects an IDC problem (which can be expressed as detecting IDC problem in English), the terminal can initiate a signaling process and provide (which can be expressed as provide in English) IDC assistance information in the RRC connected state (which can be expressed as RRC_CONNECTED in English).

[0104] Based on this, in various embodiments of the present application, before executing the IDC mechanism test process on the terminal, the terminal is first configured with the IDC auxiliary configuration and the specific channel configuration, and it is confirmed whether the terminal can detect the IDC problem under the specific channel configuration, and the IDC mechanism test process is executed on the terminal if the IDC problem can be detected; or, after executing the IDC mechanism test process on the terminal, if the terminal fails the test, that is, if the test result including the suspension measurement record is not obtained, the terminal is configured with the IDC auxiliary configuration and the specific channel configuration, and it is confirmed whether the terminal can detect the IDC under the specific channel configuration. problem, and then generate the final test result for the terminal based on the confirmed result; in this way, it can avoid the situation where "the IDC problem does not occur during the execution of the IDC mechanism test process on the terminal due to the excellent terminal design (which can be understood as the terminal being able to support the IDC mechanism and improving the IDC problem)" is mistakenly judged as the terminal failing the test. In other words, it can avoid the problem of a qualified terminal that can support the IDC mechanism being mistakenly judged as an unqualified terminal that cannot support the IDC mechanism, so that it can accurately judge whether the terminal correctly supports the relevant functions of the IDC problem, that is, it can accurately evaluate whether the MDT function of the terminal has an IDC mechanism that meets the relevant technical requirements.

[0105] In addition, in various embodiments of the present application, before executing the test method provided in the embodiment of the present application, it can be determined whether the terminal is applicable to the test method provided in the embodiment of the present application. Specifically, if the following conditions are met, it can be determined that the terminal is applicable to the test method provided in the embodiment of the present application, and the test method provided in the embodiment of the present application can be executed for the terminal: the terminal supports the fifth generation mobile communication technology (5G) core, performs measurement recording (logged measurements) in idle state (RRC_IDLE) and inactive state (RRC_INACTIVE), IDC mechanism, frequency range 1 (FR1, Frequency Range 1), Band n40, WLAN, reports the affected NR carrier frequency in IDC assistance information, and sends a terminal assistance information (UEAssistanceInformation) message including IDC assistance information (IDC-Assistance-r16) in the connected state when an IDC problem is detected in the idle state.

[0106] Specifically, an embodiment of the present application provides a testing method, which is applied to a testing device. As shown in FIG1 , the method includes:

[0107] Step 101: configuring the terminal with IDC auxiliary configuration and a first configuration (which may be expressed as "configuration" in English), and confirming (which may be expressed as "confirm" in English) whether the terminal can detect the IDC problem under the first configuration, i.e., checking (which may be expressed as "check" in English) whether the terminal can detect the IDC problem under the first configuration;

[0108] Step 102: When the terminal is able to detect the IDC problem under the first configuration, perform an IDC mechanism test process on the terminal and / or generate a first test result for the terminal; or, when the terminal cannot detect the IDC problem under the first configuration, do not perform the IDC mechanism test process on the terminal and / or generate a second test result for the terminal.

[0109] Here, it can be seen from the above steps 101 and 102 that the test method shown in Figure 1 is a technical solution that first confirms and / or checks the IDC problem and then performs the IDC mechanism test. That is, before the IDC mechanism test process, an IDC problem confirmation and / or inspection process can be set up. The IDC problem confirmation and / or inspection process is used to confirm and / or inspect whether the terminal can detect (in English, it can be expressed as "detect") the IDC problem under the first configuration. In addition, it can be understood that the "IDC problem confirmation process" and the "IDC problem inspection process" refer to the same process.

[0110] In actual application, the terminal may also be referred to as a UE, or as a device or a terminal to be tested, etc. The test device may also be referred to as an instrument, a test instrument, a test system, or a system simulator (which can be expressed as a System Simulator in English, abbreviated as SS), etc. The embodiments of the present application do not limit the names of the terminal and the test device, as long as their functions are implemented. In addition, it can be understood that the test device has the ability to exchange information with the terminal. When the test device exchanges information with the terminal, it can be assumed that the test device is a network (which can be expressed as a Network in English, abbreviated as NW), that is, it is assumed that the test device is a network device, such as a base station, etc., or the test device can be implemented through a network device.

[0111] In actual application, the first configuration can also be understood as the test condition (which can be expressed as test condition or Pre-test condition in English) constructed by the test equipment, or can be understood as a network test environment virtualized by the test equipment, or can be understood as a simulated network test state; the first configuration can specifically include a specific channel configuration that is expected or anticipated to enable qualified terminals to detect IDC problems. Specifically, the terminal is internally provided with at least one receiver (i.e., one or more receivers) and at least one transmitter (i.e., one or more transmitters), and an IDC problem may exist between a receiver (which may be referred to as a first receiver in the subsequent description) and a transmitter (which may be referred to as a first transmitter in the subsequent description), and the first transmitter is the interference source of the IDC problem. Through the first configuration, the working channel of the first receiver and the working channel of the first transmitter can be passively (which can be understood as being configured to) present a state corresponding to the first configuration, and the test equipment can confirm whether the terminal can detect the IDC problem in this state.

[0112] Based on this, in one embodiment, under the first configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest.

[0113] The first channel may include the working channel of the first receiver, and the second channel may include the working channel of the first transmitter. In this case, the transmission channel is the second channel; or the first channel may include the working channel of the first transmitter, and the second channel may include the working channel of the first receiver. In this case, the transmission channel is the first channel.

[0114] In actual application, the first channel and the second channel are configured to be at a minimum distance, which can also be understood as the first channel and the second channel being configured to be at a minimum interval state or a minimum isolation state, that is, the distance between the first channel and the second channel is the minimum under the first configuration. In addition, the minimum distance may refer to the theoretical minimum distance between the first channel and the second channel (that is, the minimum distance in a physical sense). Alternatively, the minimum distance may refer to the smallest possible distance between the first channel and the second channel, that is, the minimum distance that can actually be configured between the first channel and the second channel; in other words, in some specific cases where the terminal cannot support the theoretical minimum distance between the first channel and the second channel, the disturber of the IDC problem (that is, the working channel of the first transmitter) and the disturbed party (that is, the working channel of the first receiver) can be made as close to each other as possible, that is, when the test equipment configures the first configuration of the terminal, the minimum distance can be selected from the currently available (available in English) distance between the first channel and the second channel for configuration. For example, assuming that the test environment is 2.4GHz WiFi and the 2300-2400MHz frequency band (i.e., Band n40) (i.e., Band n40 is interfered with by 2.4GHz WiFi), assuming that the first channel includes the working channel of the first receiver (i.e., the working channel of Band n40), and the second channel includes the working channel of the first transmitter (i.e., the working channel of 2.4GHz WiFi), and assuming that the first receiver is the NR cell 1 (Cell 1) receiver (which may be referred to as NR Cell 1 in the subsequent description), and the first transmitter is the WLAN access point 1 (Cell 27) (Cell 27) transmitter (which may be referred to as WLAN AP 1 (Cell 27) in the subsequent description); when the test device configures the first configuration on the terminal, Band n40 can select the highest available frequency channel as the working channel, for example, NR Cell 1 is configured to be as close to 2400MHz as possible; and 2.4GHz WiFi can select the lowest available frequency channel as the working channel, for example, channel 1 (2401-2423MHz) is configured to WLAN AP 1 (Cell 27).

[0115] In actual application, the transmission power of the transmission channel is the highest, which may refer to configuring the theoretical maximum transmission power for the transmission channel (that is, the highest transmission power in the physical sense); or it may refer to configuring the actually configurable maximum transmission power for the transmission channel, that is, configuring the maximum transmission power among the currently available transmission powers for the transmission channel.

[0116] In one embodiment, confirming whether the terminal can detect the IDC problem under the first configuration may include:

[0117] When the terminal sends IDC auxiliary information, and / or when the terminal receives IDC auxiliary information, it is confirmed that the IDC problem can be detected under the first configuration when the terminal is in a connected state, and when the terminal is in an idle state (which can be expressed as idle mode and / or RRC_IDLE in English), the IDC problem can be detected under the first configuration.

[0118] Here, the confirmation that the terminal is capable of detecting the IDC problem under the first configuration when in the connected state refers to confirmation that the terminal in the connected state is capable of detecting the IDC problem under the first configuration, that is, confirmation that the terminal in the connected state and having the first configuration is capable of detecting the IDC problem, that is, confirmation that the terminal is capable of detecting the IDC problem in the RRC connected state and under the first configuration. The confirmation that the terminal is capable of detecting the IDC problem under the first configuration when in the idle state refers to confirmation that the terminal in the idle state is capable of detecting the IDC problem under the first configuration, that is, confirmation that the terminal in the idle state and having the first configuration is capable of detecting the IDC problem.

[0119] The terminal transmitting the IDC auxiliary information can also be understood as the terminal providing the IDC auxiliary information to the test device. Furthermore, it can be understood that the IDC auxiliary information is used to notify the test device of an IDC problem.

[0120] In actual application, the test device can determine whether the terminal sends and / or provides the IDC assistance information to the test device when the terminal is in a connected state by determining whether the test device receives the IDC assistance information sent by the terminal, thereby checking and / or confirming whether the terminal can detect the IDC problem under the first configuration. Specifically, under the first configuration, the network (i.e., the test device) can configure the IDC assistance (which can be expressed as IDC Assistance) configuration for the terminal through an RRC reconfiguration (which can be expressed as RRC Reconfiguration in English), and can observe whether the system simulator (i.e., the test device) can detect the IDC assistance information in the terminal assistance information (which can be expressed as UEAssistanceInformation in English). If the system simulator can detect the IDC assistance information reported by the terminal in the connected state, it can be determined that the terminal can detect the IDC problem under the first configuration when it is in the connected state; further, the system simulator can determine (which can be understood as determining or assuming) that the terminal can also detect the IDC problem under the first configuration when it is in the idle state. In this way, the network can check the IDC interference status of the terminal in the idle state through the IDC interference status of the terminal in the connected state, thereby at least solving the problem that the network cannot know the IDC interference status of the terminal in the idle state.

[0121] In one embodiment, confirming whether the terminal can detect the IDC problem under the first configuration may include:

[0122] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the first configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the first configuration, or it cannot be confirmed that the IDC problem is detected under the first configuration.

[0123] Among them, the inability to confirm that the terminal can detect the IDC problem in the connected state means that the terminal may be able to detect the IDC problem in the connected state, but the test device cannot confirm this situation, that is, the test device cannot obtain the conclusion that "the terminal can detect the IDC problem in the connected state" (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)). The inability to confirm that the IDC problem is detected in the first configuration means that the terminal in the idle state may be able to detect the IDC problem in the first configuration, but the test device cannot confirm this situation, that is, the test device cannot obtain the conclusion that "the IDC problem can be detected in the first configuration when the terminal is in the idle state."

[0124] Specifically, in actual application, under the first configuration, the network (i.e., the test device) can configure the IDC assistance (which can be expressed as IDC Assistance) configuration for the terminal through the RRC reconfiguration (which can be expressed as RRC Reconfiguration in English), and can observe whether the system simulator (i.e., the test device) can detect the IDC assistance information in the terminal assistance information (which can be expressed as UEAssistanceInformation in English). If the system simulator fails to detect the IDC assistance information reported by the terminal in the connected state, it can be determined that the IDC problem cannot be detected under the first configuration when the terminal is in the connected state; further, the system simulator can determine (which can be understood as determining or assuming) that the IDC problem cannot be detected under the first configuration when the terminal is in the idle state, or it can be considered that the system simulator cannot make a judgment or determination that "the IDC problem can be detected under the first configuration when the terminal is in the idle state."

[0125] In actual application, the first test result may indicate that the terminal can detect the IDC problem under the first configuration, and / or, the first test result may include the test conclusion of the IDC mechanism test process (the conclusion may also be called a judgment (expressed as judgment in English) or a verdict (expressed as Verdict in English)); the test conclusion of the IDC mechanism test process may include a conclusion that the test passed (expressed as Pass in English, abbreviated as P), a conclusion that the test failed (expressed as Fail in English, abbreviated as F), or a conclusion that the test result is uncertain (also understood as no test result, expressed as Inconclusive in English). Exemplarily, when the terminal can detect the IDC problem under the first configuration, the test device may enter the subsequent IDC mechanism test process and not generate the first test result; or, the test device may enter the subsequent IDC mechanism test process and generate the first test result. At this time, the first test result may indicate that the terminal can detect the IDC problem under the first configuration, and the first test result may include the test conclusion of the IDC mechanism test process; or, the test device may not enter the subsequent IDC mechanism test process and only generate the first test result. At this time, the first test result may indicate that the terminal can detect the IDC problem under the first configuration.

[0126] In actual application, the second test result may indicate that the terminal cannot detect the IDC problem under the first configuration, and / or the second test result may include a conclusion of test failure (a conclusion may also be referred to as a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)) or a conclusion of an uncertain test result (which can also be understood as no test result, which can be expressed as inconclusive in English). The conclusion of the uncertain test result means that the test device cannot determine whether the terminal can detect the IDC problem under the first configuration. Exemplarily, if the terminal cannot detect the IDC problem under the first configuration, the test device may not continue the subsequent IDC mechanism test process and not generate the second test result, that is, not perform any processing; or, the test device may not continue the subsequent IDC mechanism test process and, at the same time, terminate the test process, that is, generate the second test result. In this case, the second test result may include the conclusion of the uncertain test result; or, the test device may directly terminate the test process, that is, generate the second test result. In this case, the second test result may indicate that the terminal cannot detect the IDC problem under the first configuration, and the second test result may include a conclusion of test failure. In this way, by first confirming and / or checking the IDC problem, terminals that are not suitable for testing (i.e., terminals that cannot detect IDC problems under the first configuration) can be excluded in advance when the IDC mechanism testing process is required, thereby improving the judgment accuracy of the terminal test while reducing the waste of test resources.

[0127] In actual application, during the execution of the IDC mechanism test process on the terminal, the test device may construct at least one test condition (i.e., one or more test conditions) that is expected or anticipated to enable a qualified terminal to detect an IDC problem, i.e., configure the terminal with at least one specific channel configuration (i.e., one or more specific channel configurations) that is expected or anticipated to enable a qualified terminal to detect an IDC problem. Thereafter, the test device may obtain the MDT report of the terminal. If it is determined according to the MDT report that the terminal has both of the following behaviors or only one of the following two behaviors (i.e., if it is determined according to the MDT report that the terminal has the following behavior 1 and / or behavior 2), the test device may determine that the terminal has passed the IDC mechanism test (i.e., generate a conclusion (a conclusion may also be referred to as a judgment) that the test has passed (expressed as Pass in English, abbreviated as P)):

[0128] Behavior 1: When the terminal detects an IDC problem, the terminal suspends measurement recording and uses an IDC detection flag in a measurement information table of the measurement record to mark an MDT report;

[0129] Behavior 2: When the IDC problem detected by the terminal is resolved during the previous recording interval, the terminal resumes measurement recording.

[0130] Among them, the above-mentioned behavior 1 and behavior 2 can also be understood as the two test purposes (TP, Test Purpose) of the IDC mechanism test process. The above-mentioned behavior 1 can correspond to TP1. When the test device determines that the terminal has the above-mentioned behavior 1, it can generate a conclusion that the TP1 test passed (which can be expressed as TP1 Pass in English) (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)); when the test device determines that the terminal does not have the above-mentioned behavior 1, it can generate a conclusion that the TP1 test failed (which can be expressed as TP1 Fail in English). The above-mentioned behavior 2 can correspond to TP2. When the test device determines that the terminal has the above-mentioned behavior 2, it can generate a conclusion that the TP2 test passed (which can be expressed as TP2 Pass in English); when the test device determines that the terminal does not have the above-mentioned behavior 2, it can generate a conclusion that the TP2 test failed (which can be expressed as TP2 Fail in English).

[0131] In actual application, it can be seen from the above description that, for the same channel configuration (i.e., the first configuration), the test device can check the IDC interference status in the terminal in the idle state through the IDC interference status in the terminal in the connected state. Considering that the test device confirms whether the terminal can detect the IDC problem under the first configuration when the terminal is in the connected state, and the terminal may have the above-mentioned behavior 1 and / or 2 when it is in the idle state, in order to ensure that the terminal confirmed by the test device whether it can detect the IDC problem under the first configuration can have a reference significance for the IDC interference status of the terminal in the IDC mechanism test process, the configuration performed on the terminal by the test device during the execution of the IDC mechanism test process on the terminal can at least include the first configuration. In this way, the test device can use the test conditions equivalent to those of the connected state terminal (i.e., the first configuration) when checking the IDC interference status in the terminal in the idle state, thereby at least solving the problem of consistency of test conditions between the terminal in the idle state and the terminal in the connected state, and reducing the waste of test resources while improving the judgment accuracy of the terminal test.

[0132] In actual application, when the test device performs the IDC mechanism test process on the terminal, the configuration of the terminal may further include a second configuration. Under the second configuration, the first channel and the second channel may be configured as at least one of the following:

[0133] The first channel and the second channel of the terminal are configured as a maximum distance;

[0134] The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest;

[0135] No information is transmitted on the first channel and / or the second channel of the terminal;

[0136] The first channel and / or the second channel of the terminal is closed.

[0137] In actual application, the first channel and the second channel are configured to be at a maximum distance, which can also be understood as the first channel and the second channel being configured to be in a maximum interval state or a maximum isolation state, that is, the distance between the first channel and the second channel is the largest under the second configuration. In addition, the maximum distance may refer to the theoretical maximum distance between the first channel and the second channel (that is, the maximum distance in a physical sense). Alternatively, the maximum distance may refer to the largest possible distance between the first channel and the second channel, that is, the maximum distance that can actually be configured between the first channel and the second channel; in other words, in some specific cases where the terminal cannot support the theoretical maximum distance between the first channel and the second channel, the disturber (that is, the working channel of the first transmitter) and the disturbed party (that is, the working channel of the first receiver) of the IDC problem can be kept as far away from each other as possible, or even the disturber can be turned off, that is, when the test equipment configures the second configuration of the terminal, the maximum distance can be selected for configuration from the currently available (available in English) distance between the first channel and the second channel. For example, assuming that the test environment is 2.4GHz WiFi and the 2300-2400MHz frequency band (i.e., Band n40) (i.e., Band n40 is interfered with by 2.4GHz WiFi), assuming that the first channel includes the working channel of the first receiver (i.e., the working channel of Band n40), and the second channel includes the working channel of the first transmitter (i.e., the working channel of 2.4GHz WiFi), and assuming that the first receiver is NR Cell 1 and the first transmitter is WLAN AP 1 (Cell 27); then when the test device configures the second configuration for the terminal, Band n40 can select the lowest available frequency channel as the working channel, for example, NR Cell 1 is configured as close to 2300MHz as possible; for another example, NR Cell 1 is configured as far away from 2400MHz as possible. 2.4GHz WiFi can select the highest available frequency channel as the working channel, or 2.4GHz WiFi can be turned off.

[0138] In actual application, the transmission power of the transmission channel is the lowest, which may refer to configuring the theoretical minimum transmission power for the transmission channel (that is, the minimum transmission power in the physical sense); or it may refer to configuring the actually configurable minimum transmission power for the transmission channel, that is, configuring the minimum transmission power among the currently available transmission powers for the transmission channel.

[0139] In actual application, in the above-mentioned IDC problem confirmation (which can be expressed as confirm in English) and / or inspection (which can be expressed as check in English) process, the test device can also add confirmation and / or inspection whether the terminal cannot detect IDC problems (which can be expressed as can not detect IDC problem(s) in English) under the second configuration.

[0140] Based on this, in one embodiment, the method may further include:

[0141] confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0142] If the terminal is capable of detecting an IDC problem under the second configuration, executing the first sub-process of the IDC mechanism test process on the terminal and not executing the second sub-process of the IDC mechanism test process on the terminal, and / or generating a third test result for the terminal; or

[0143] In the case that the terminal cannot detect the IDC problem under the second configuration, the first sub-process and / or the second sub-process of the IDC mechanism test process are executed on the terminal, and / or a fourth test result for the terminal is generated; wherein,

[0144] The first sub-process is at least used to check (which can be expressed as "check" in English) to suspend measurement recording when an IDC problem is detected and mark the MDT report with an IDC detection flag in a measurement information table of the measurement record;

[0145] The second sub-process is at least used to check that the measurement record is restored when the IDC problem is resolved.

[0146] In actual application, it can be understood that the first sub-process can be used to test the above-mentioned TP1, that is, to test whether the terminal has the above-mentioned behavior 1, that is, to test whether the terminal suspends measurement recording and uses the IDC detection identifier in the measurement information table of the measurement record to mark the MDT report when the terminal detects an IDC problem, and to check whether the terminal suspends measurement recording and uses the IDC detection identifier in the measurement information table of the measurement record to mark the MDT report when the terminal detects an IDC problem. The second sub-process can be used to test the above-mentioned TP2, that is, to test whether the terminal has the above-mentioned behavior 2, that is, to test whether the measurement recording is resumed when the IDC problem detected by the terminal is resolved during the previous recording interval, and to check whether the terminal resumes measurement recording when the IDC problem is resolved.

[0147] In one embodiment, the confirming whether the terminal cannot detect the IDC problem under the second configuration may include:

[0148] performing the second configuration on the terminal;

[0149] In the case where the terminal sends IDC auxiliary information, and / or in the case where the IDC auxiliary information is received, it is confirmed that the IDC problem can be detected under the second configuration when the terminal is in a connected state, and that the IDC problem can be detected under the second configuration when the terminal is in an idle state.

[0150] Here, the confirmation that the terminal is capable of detecting the IDC problem under the second configuration when in the connected state refers to confirmation that the terminal in the connected state is capable of detecting the IDC problem under the second configuration, that is, confirmation that the terminal in the connected state and having the second configuration is capable of detecting the IDC problem, that is, confirmation that the terminal is capable of detecting the IDC problem in the RRC connected state and under the second configuration. The confirmation that the terminal is capable of detecting the IDC problem under the second configuration when in the idle state refers to confirmation that the terminal in the idle state is capable of detecting the IDC problem under the second configuration, that is, confirmation that the terminal in the idle state and having the second configuration is capable of detecting the IDC problem.

[0151] The terminal sending the IDC auxiliary information can also be understood as the terminal providing (in English, it can be expressed as providing) the IDC auxiliary information to the test device. In addition, it can be understood that the IDC auxiliary information is used to notify the IDC problem.

[0152] In actual application, the test device may configure the second configuration for the terminal when the terminal is in a connected state, and determine whether the terminal has sent and / or provided the IDC assistance information to the test device by determining whether the test device has received the IDC assistance information sent by the terminal, thereby confirming whether the terminal cannot detect the IDC problem under the second configuration. Specifically, under the second configuration, the network (i.e., the test device) may configure the IDC assistance (which may be expressed as IDC Assistance) configuration for the terminal through an RRC reconfiguration (which may be expressed as RRC Reconfiguration in English), and may observe whether the system simulator (i.e., the test device) can detect the IDC assistance information in the terminal assistance information (which may be expressed as UEAssistanceInformation in English). If the system simulator can detect the IDC assistance information reported by the terminal in the connected state, it may be determined that the terminal can detect the IDC problem under the second configuration when in the connected state; further, the system simulator may determine (which may be understood as determining or assuming) that the terminal can also detect the IDC problem under the second configuration when in the idle state. In this way, the network can check the IDC interference status of the terminal in the idle state through the IDC interference status of the terminal in the connected state, thereby at least solving the problem that the network cannot know the IDC interference status of the terminal in the idle state.

[0153] In one embodiment, the confirming whether the terminal cannot detect the IDC problem under the second configuration may include:

[0154] performing the second configuration on the terminal;

[0155] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the second configuration when the terminal is in a connected state, or it cannot be confirmed that the IDC problem can be detected under the second configuration when the terminal is in a connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the second configuration, or it cannot be confirmed that the IDC problem is detected under the second configuration, or the IDC problem has been resolved under the second configuration.

[0156] Among them, the inability to confirm that the terminal can detect the IDC problem under the second configuration when it is in the connected state means that the terminal may be able to detect the IDC problem under the second configuration when it is in the connected state, but the test device cannot confirm this situation, that is, the test device cannot obtain the conclusion that "the terminal can detect the IDC problem under the second configuration when it is in the connected state" (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)). The inability to confirm that the IDC problem is detected under the second configuration means that the terminal in the idle state may be able to detect the IDC problem under the second configuration, but the test device cannot confirm this situation, that is, the test device cannot obtain the conclusion that "the IDC problem can be detected under the second configuration when the terminal is in the idle state".

[0157] Specifically, in actual application, under the second configuration, the network (i.e., the test device) may configure the IDC assistance (which may be expressed as IDC Assistance) configuration for the terminal through an RRC reconfiguration (which may be expressed as RRC Reconfiguration in English), and may observe whether the system simulator (i.e., the test device) can detect the IDC assistance information in the terminal assistance information (which may be expressed as UEAssistanceInformation in English). If the system simulator fails to detect the IDC assistance information reported by the terminal in the connected state, it may be determined that the IDC problem cannot be detected under the second configuration when the terminal is in the connected state; further, the system simulator may determine (which may be understood as determining or assuming) that the IDC problem cannot be detected under the second configuration when the terminal is in the idle state, or it may be considered that the system simulator cannot make a judgment or determination that "the IDC problem can be detected under the second configuration when the terminal is in the idle state", or it may be considered that the IDC problem has been resolved under the second configuration.

[0158] In actual application, the third test result can indicate that the terminal can detect the IDC problem under the second configuration, and / or the third test result can at least include the conclusion that the above-mentioned TP2 test fails (which can be expressed as TP2 Fail in English) (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)); in addition, the third test result can also include the conclusion that the above-mentioned TP1 test passes (which can be expressed as TP1 Pass in English), the conclusion that the above-mentioned TP1 test fails, or the conclusion that the above-mentioned TP1 test result is uncertain (which can also be understood as no test result, which can be expressed as Inconclusive in English). Exemplarily, when the terminal is able to detect the IDC problem under the second configuration, the test device may only execute the first sub-process on the terminal and skip the second sub-process, that is, not execute the second sub-process on the terminal; or, the test device may only generate the third test result. In this case, the third test result may indicate that the terminal is able to detect the IDC problem under the second configuration, and the third test result may include the conclusion that the above-mentioned TP2 test fails and the conclusion that the above-mentioned TP1 test result is uncertain; or, the test device may execute the first sub-process on the terminal and not execute the second sub-process on the terminal, and also generate the third test result. In this case, the third test result may include the conclusion that the above-mentioned TP2 test fails and the conclusion that the above-mentioned TP1 test result passes or fails.

[0159] In actual application, the fourth test result may indicate that the terminal cannot detect the IDC problem under the second configuration, and / or the fourth test result may include the test conclusion of the first sub-process and / or the second sub-process (the conclusion may also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)); wherein, the test conclusion of the first sub-process may include the conclusion that the above-mentioned TP1 test passed, the conclusion that the above-mentioned TP1 test failed, or the conclusion that the above-mentioned TP1 test result is uncertain (which can also be understood as no test result, which can be expressed as Inconclusive in English), and the test conclusion of the second sub-process may include the conclusion that the above-mentioned TP2 test passed, the conclusion that the above-mentioned TP2 test failed, or the conclusion that the above-mentioned TP2 test result is uncertain. Exemplarily, when the terminal cannot detect the IDC problem under the second configuration, the test device may execute the first sub-process and the second sub-process on the terminal and generate the fourth test result. At this time, the fourth test result may characterize that the terminal cannot detect the IDC problem under the second configuration, and the fourth test result may include the test conclusions of the first sub-process and the second sub-process; or, the test device may only execute the first sub-process or the second sub-process on the terminal and generate the fourth test result. At this time, the fourth test result may include the test conclusions of the first sub-process or the second sub-process; or, the test device may only generate the fourth test result. At this time, the fourth test result may characterize that the terminal cannot detect the IDC problem under the second configuration, and the fourth test result may include the uncertain conclusion of the above-mentioned TP1 test result and the uncertain conclusion of the above-mentioned TP2 test result.

[0160] In actual application, the test device can first confirm (confirm in English) and / or check (check in English) whether the terminal cannot detect the IDC problem under the second configuration, and then confirm whether the terminal can detect the IDC problem under the first configuration.

[0161] Based on this, in one embodiment, confirming whether the terminal cannot detect the IDC problem under the second configuration may include:

[0162] Before confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0163] If the terminal cannot detect the IDC problem under the second configuration, confirm whether the terminal can detect the IDC problem under the first configuration, and if the terminal can detect the IDC problem under the first configuration, perform the first sub-process and / or the second sub-process on the terminal to generate the first test result; or

[0164] If the terminal is able to detect the IDC problem under the second configuration, confirm whether the terminal is able to detect the IDC problem under the first configuration, and if the terminal is able to detect the IDC problem under the first configuration, execute the first sub-process on the terminal and do not execute the second sub-process on the terminal, to generate the first test result.

[0165] Among them, the first test result may include the test conclusion of the first sub-process and / or the second sub-process (the conclusion may also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)); the test conclusion of the first sub-process may include the conclusion that the above-mentioned TP1 test passed, the conclusion that the above-mentioned TP1 test failed, or the conclusion that the above-mentioned TP1 test result is uncertain (which can also be understood as no test result, which can be expressed as Inconclusive in English), and the test conclusion of the second sub-process may include the conclusion that the above-mentioned TP2 test passed, the conclusion that the above-mentioned TP2 test failed, or the conclusion that the above-mentioned TP2 test result is uncertain.

[0166] In actual application, it can be seen from the above description that for the above-mentioned IDC problem confirmation and / or inspection process, the test equipment needs to configure the IDC auxiliary configuration (which can be expressed as idc-AssistanceConfig-r16 in English) for the terminal; for the IDC mechanism test process, the test equipment needs to configure the measurement record configuration (which can be expressed as LoggedMeasurementConfiguration in English) for the terminal. Specifically, when the test equipment needs to perform an IDC mechanism test on the terminal, it can first confirm and / or check the IDC problem, specifically, it can first configure the measurement record configuration for the terminal (i.e., configure LoggedMeasurementConfiguration first), and then perform IDC auxiliary configuration on the terminal (i.e., configure idc-AssistanceConfig-r16 again), and can also add a check for the IDC problem under the first configuration. Exemplarily, assuming that the test environment is 2.4GHz WiFi and the 2300-2400MHz frequency band (ie, Band n40) (ie, Band n40 is interfered with by 2.4GHz WiFi), assuming that the first channel includes the working channel of the first receiver (ie, the working channel of Band n40), and the second channel includes the working channel of the first transmitter (ie, the working channel of 2.4GHz WiFi), and assuming that the first receiver is NR Cell 1 and the first transmitter is WLAN AP 1 (Cell 27); then the channel configuration performed by the network / system simulator (which can be expressed as NW / SS, that is, the test equipment) on the terminal can be as shown in Table 1, and the test process performed by the network / system simulator on the terminal can be as shown in Figure 2. The specific test steps (also referred to as main behaviors, which can be expressed as Main behavior in English) corresponding to the test process shown in Figure 2 can be shown in Table 2.

[0167] Table 1 illustrates the time instances of cell power levels and parameter changes in Frequency Range 1 (FR1) during the process shown in Figure 2 and Table 2, and includes the downlink power and other changing parameters applied to the cell at different times during the test execution. In Table 1, "T0" represents the initial test condition, "T1," "T2," "T3," and "T4" represent the configurations corresponding to the subsequent main behavior descriptions; furthermore, "T2" and "T0" are substantially the same test conditions, "T3" and "T1" are substantially the same test conditions, and "T4" and "T2" are substantially the same test conditions.

[0168] Accordingly, as shown in FIG2 , when the terminal is tested, under initial test conditions, the terminal in the connected state and having the “T0” configuration (non-IDC configuration) is configured with a measurement record configuration in the RRC connected state; the terminal in the connected state is reconfigured to the IDC auxiliary configuration and the “T1” configuration (IDC configuration, i.e., the first configuration mentioned above) in the RRC connected state to trigger the IDC problem; it is checked whether the terminal in the connected state sends a terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information) message to notify the IDC problem; if the terminal does not send the terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information), the network / system simulator can generate at least one of the test conclusions (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as TP1&TP2 Inconclusive and / or TP1&TP2) of TP1 test result uncertainty (which can also be understood as no test result, which can be expressed as Inconclusive in English), TP2 test result uncertainty, TP1 test failure, and TP2 test failure (which can be expressed as judgment in English or Verdict in English)). FAIL) (ie, the second test result may include at least one of the test conclusions of TP1 test result being uncertain, TP2 test result being uncertain, TP1 test failure, and TP2 test failure).If the terminal sends terminal auxiliary information for notifying the IDC problem, the network / system simulator sends an RRC release message to the terminal; thereafter, the terminal in the idle state and with the "T2" configuration (non-IDC configuration and the same as the "T0" configuration) activates logging; the terminal in the idle state is reconfigured to the "T3" configuration (IDC configuration and the same as the "T1" configuration) to trigger the suspension of logging; 10 seconds (s) later, the terminal in the idle state is reconfigured to the "T4" configuration (non-IDC configuration and the same as the "T0" configuration) to resume logging; the network / system simulator sends a terminal information request to the terminal in the RRC connected state; check: when reconfigured to the "T3" configuration, whether the terminal suspends logging for about 10 seconds and sends a terminal information response message marked with the IDC detection identifier when returning to the connected state; if so, the network / system simulator can generate a test conclusion of TP1 test passed and / or TP2 test passed (which can be expressed in English as TP1 PASS and / or TP2 PASS) (that is, the above-mentioned first test result may include the test conclusions of TP1 test passing and / or TP2 test passing); if not, the network / system simulator may generate at least one of the test conclusions of TP1 test result being uncertain (which can also be understood as no test result, which can be expressed in English as Inconclusive), TP2 test result being uncertain, TP1 test failure, and TP2 test failure (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (that is, the above-mentioned first test result may include at least one of the test conclusions of TP1 test result being uncertain, TP2 test result being uncertain, TP1 test failure, and TP2 test failure).

[0169] In addition, in Table 2, in step 1a, the system simulator (i.e., the test device) configures the terminal with IDC auxiliary configuration; in step 1c, the system simulator configures the terminal with the first configuration (i.e., the "T1" configuration in Table 1); in step 1d, the system simulator confirms whether the terminal can detect the IDC problem under the first configuration. If the terminal cannot detect the IDC problem under the first configuration, the terminal will perform measurement recording without pausing; if the terminal can detect the IDC problem under the first configuration, the system simulator should execute the subsequent process, i.e., execute the IDC mechanism test process on the terminal (i.e., step 1e to step 22), and the first test result may include the judgment obtained in step 22 (such as P).

[0170] Table 1

[0171] Table 2

[0172] In actual application, when the test equipment needs to perform an IDC mechanism test on the terminal, it can first confirm and / or check the IDC problem. Specifically, it can first perform IDC auxiliary configuration on the terminal (i.e., first configure idc-AssistanceConfig-r16), and then configure the measurement record configuration of the terminal (i.e., then configure LoggedMeasurementConfiguration), and it can add a check for the IDC problem under the first configuration, or it can add a check for the IDC problem under the first and second configurations. Exemplarily, assuming that the test environment is 2.4 GHz WiFi and the 2300-2400 MHz frequency band (ie, Band n40) (ie, Band n40 is interfered with by 2.4 GHz WiFi), assuming that the first channel includes the working channel of the first receiver (ie, the working channel of Band n40), and the second channel includes the working channel of the first transmitter (ie, the working channel of 2.4 GHz WiFi), and assuming that the first receiver is NR Cell 1 and the first transmitter is WLAN AP 1 (Cell 27); then the channel configuration performed by the network / system simulator (which can be expressed as NW / SS, that is, the test equipment) on the terminal can be as shown in Table 3, and the test process performed by the network / system simulator on the terminal can be as shown in Figure 3. The specific test steps (also referred to as main behaviors, which can be expressed as Main behavior in English) corresponding to the test process shown in Figure 3 can be shown in Table 4 or Table 5.

[0173] Table 3 illustrates the time instances of cell power levels and parameter changes in FR1 during the processes shown in Figure 3 and Tables 4 and 5, and includes the downlink power and other parameter changes applied to the cell at different times during the test execution. In Table 3, "T0" represents the initial test condition, "T1," "T2," "T3," and "T4" represent the configurations corresponding to the subsequent main behavior descriptions. Furthermore, "T2" and "T0" are essentially the same test conditions, "T3" and "T1" are essentially the same test conditions, and "T4" and "T2" are essentially the same test conditions.

[0174] Accordingly, as shown in FIG3 , when the terminal is tested, under initial test conditions, the terminal in the connected state and having the “T0” configuration (non-IDC configuration) is configured with the IDC auxiliary configuration in the RRC connected state; the terminal in the connected state is reconfigured to the “T1” configuration (IDC configuration, i.e., the first configuration mentioned above) in the RRC connected state to trigger the IDC problem; check: whether the terminal in the connected state sends a terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information) message to notify the IDC problem; if the terminal does not send the terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information), the network / system simulator can generate at least one of the test conclusions (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)) of TP1 test result uncertainty (which can also be understood as no test result, which can be expressed as Inconclusive in English), TP2 test result uncertainty, TP1 test failure, and TP2 test failure (which can be expressed as TP1&TP2 Inconclusive and / or TP1&TP2 in English). FAIL) (ie, the second test result may include at least one of the test conclusions of TP1 test result being uncertain, TP2 test result being uncertain, TP1 test failure, and TP2 test failure).If the terminal sends terminal assistance information for notifying an IDC problem, the terminal in the connected state and with the "T2" configuration (non-IDC configuration) is reconfigured with the measurement logging configuration in the RRC connected state; thereafter, the network / system simulator sends an RRC release message to the terminal; the terminal in the idle state and with the "T2" configuration (non-IDC configuration) activates logging; the terminal in the idle state is reconfigured to the "T3" configuration (IDC configuration, which is the same as the "T1" configuration) to trigger the suspension of logging; after 10 seconds, the terminal in the idle state The terminal is reconfigured to the "T4" configuration (non-IDC configuration and the same as the "T0" configuration) to resume logging; the network / system simulator sends a terminal information request to the terminal in the RRC connected state; check: when reconfigured to the "T3" configuration, whether the terminal pauses logging for about 10 seconds and sends a terminal information response message marked with the IDC detection flag when returning to the connected state; if so, the network / system simulator can generate a test conclusion of TP1 test passed and / or TP2 test passed (in English, it can be expressed as TP1 PASS and / or TP2 PASS) (that is, the above-mentioned first test result may include the test conclusions of TP1 test passed and / or TP2 test passed); if not, the network / system simulator may generate at least one of the test conclusions of TP1 test result uncertain, TP2 test result uncertain, TP1 test failed, and TP2 test failed (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (that is, the above-mentioned first test result may include at least one of the test conclusions of TP1 test result uncertain, TP2 test result uncertain, TP1 test failed, and TP2 test failed).

[0175] In addition, in Table 4, in step 0a, the system simulator (i.e., the test device) configures the terminal with IDC auxiliary configuration; in step 0c, the system simulator configures the terminal with the first configuration (i.e., the "T1" configuration in Table 3); step 0d is used to confirm whether the terminal can detect the IDC problem under the first configuration. If the system simulator receives a terminal auxiliary information message including IDC auxiliary information, it confirms that the terminal can detect the IDC problem in the RRC connected state, and the problem will be recorded as a reference to the test result, that is, the system simulator can generate a first test result indicating that the terminal can detect the IDC problem under the first configuration; the IDC mechanism test process may include steps 0e to 22, and the first test result may also include the judgment obtained in step 22 (such as P).

[0176] In Table 5, in step 0a, the system simulator (i.e., the test device) configures the terminal with the IDC auxiliary configuration; in step 0c, the system simulator configures the terminal with the first configuration (i.e., the "T1" configuration in Table 3); in step 0d, the system simulator confirms whether the terminal can detect the IDC problem under the first configuration. If the terminal cannot detect the IDC problem under the first configuration, the terminal will perform measurement recording without pausing; if the terminal can detect the IDC problem under the first configuration, the system simulator should execute the subsequent process, i.e., execute the IDC mechanism test process (i.e., steps 0e to 22) on the terminal, and the first test result may include the judgment obtained in step 22 (such as P).

[0177] Table 3

[0178] Table 4

[0179] Table 5

[0180] In actual application, when the test equipment needs to perform an IDC mechanism test on the terminal, it can first confirm and / or check the IDC problem. Specifically, the IDC auxiliary configuration can be performed on the terminal first (i.e., configure idc-AssistanceConfig-r16 first), and then the measurement record configuration can be configured on the terminal (i.e., configure LoggedMeasurementConfiguration again), and the IDC problem under the first configuration can be added for checking, or the IDC problem under the second configuration and the first configuration can be added for checking; wherein, the IDC problem under the first configuration can be checked by checking the IDC problem under the second configuration; in addition, if the IDC problem occurs in both the connected terminals under the second configuration and the first configuration, then the terminal will be in a state of suspended measurement recording (which can be expressed as logging in English). If the test result is in the suspended state, TP2 cannot be implemented, that is, the conclusion that the TP2 test fails (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)) and / or the conclusion that the TP2 test result is uncertain (which can also be understood as no test result, which can be expressed as inconclusive in English) can be directly obtained (that is, the above-mentioned second test result / fourth test result may include the conclusion that the TP2 test fails and / or the conclusion that the TP2 test result is uncertain). Exemplarily, assuming that the test environment is 2.4 GHz WiFi and the 2300-2400 MHz frequency band (ie, Band n40) (ie, Band n40 is interfered with by 2.4 GHz WiFi), assuming that the first channel includes the working channel of the first receiver (ie, the working channel of Band n40), and the second channel includes the working channel of the first transmitter (ie, the working channel of 2.4 GHz WiFi), and assuming that the first receiver is NR Cell 1 and the first transmitter is WLAN AP 1 (Cell 27); then the channel configuration performed by the network / system simulator (which can be expressed as NW / SS, that is, the test equipment) on the terminal can be as shown in Table 6, and the test process performed by the network / system simulator on the terminal can be as shown in Figure 4, and the specific test steps (also referred to as main behaviors, which can be expressed as Main behavior in English) corresponding to the test process shown in Figure 4 can be shown in Table 7.

[0181] Table 6 shows the time instances of cell power levels and parameter changes in FR1 during the process shown in Figure 4, and includes the downlink power and other parameter changes applied to the cell at different times during the test execution. In Table 6, "T0" represents the initial test condition, "T1," "T2," "T3," and "T4" represent the configurations corresponding to the subsequent main behavior descriptions; "T2" and "T0" are essentially the same test conditions, "T3" and "T1" are essentially the same test conditions, and "T4" and "T2" are essentially the same test conditions.

[0182] Accordingly, as shown in FIG4 , when the terminal is tested, under the initial test conditions, the terminal in the connected state and having the “T0” configuration (non-IDC configuration, i.e., the second configuration mentioned above) is configured with the IDC auxiliary configuration in the RRC connected state; a check is performed on whether the terminal in the connected state and having the “T0” configuration sends a terminal auxiliary information (i.e., the IDC auxiliary information) message to notify the IDC problem; if the terminal sends the terminal auxiliary information (i.e., the IDC auxiliary information) for notifying the IDC problem, the network / system simulator can generate a conclusion (the conclusion can also be called a judgment (which can be expressed as judgment) or a verdict (which can be expressed as Verdict)) that the TP2 test result is uncertain (which can also be understood as no test result, which can be expressed as Inconclusive in English) and / or a conclusion that the TP2 test fails (which can be expressed as TP2 Inconclusive and / or TP2 FAIL), that is, the above-mentioned third test result / first test result may include the conclusion of TP2 test failure and / or the conclusion of TP2 test result uncertainty (here, the reason why the above-mentioned first test result may include the conclusion of TP2 test failure and / or the conclusion of TP2 test result uncertainty is: if the terminal can detect the IDC problem under the second configuration, then the terminal always has the IDC problem, so it can be inferred / assumed that the terminal can also detect the IDC problem under the first configuration, that is, by confirming whether the terminal can detect the IDC problem under the second configuration, it is possible to confirm whether the terminal can detect the IDC problem under the first configuration, thereby obtaining the above-mentioned first test result). If the terminal does not send terminal assistance information, the terminal in the connected state is reconfigured to the "T1" configuration (IDC configuration, i.e., the first configuration mentioned above) in the RRC connected state to trigger the IDC problem; check: whether the terminal in the connected state sends a terminal assistance information (i.e., the above-mentioned IDC assistance information) message to notify the IDC problem; if the terminal does not send terminal assistance information (i.e., the above-mentioned IDC assistance information), the network / system simulator can generate at least one of the test conclusions of TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (i.e., the above-mentioned second test result / fourth test result can include at least one of the test conclusions of TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure).If the terminal sends terminal assistance information for notifying an IDC problem, the terminal in the connected state and with the "T2" configuration (non-IDC configuration) is reconfigured with the measurement logging configuration in the RRC connected state; thereafter, the network / system simulator sends an RRC release message to the terminal; the terminal in the idle state and with the "T2" configuration (non-IDC configuration) activates logging; the terminal in the idle state is reconfigured to the "T3" configuration (IDC configuration, which is the same as the "T1" configuration) to trigger the suspension of logging; after 10 seconds, the terminal in the idle state The terminal is reconfigured to the "T4" configuration (non-IDC configuration and the same as the "T0" configuration) to resume logging; the network / system simulator sends a terminal information request to the terminal in the RRC connected state; check: when reconfigured to the "T3" configuration, whether the terminal pauses logging for about 10 seconds and sends a terminal information response message marked with the IDC detection flag when returning to the connected state; if so, the network / system simulator can generate a test conclusion of TP1 test passed and / or TP2 test passed (in English, it can be expressed as TP1 PASS and / or TP2 PASS) (that is, the above-mentioned first test result / fourth test result may include the test conclusions of TP1 test passed and / or TP2 test passed); if not, the network / system simulator may generate at least one of the test conclusions of TP1 test result uncertain, TP2 test result uncertain, TP1 test failed, and TP2 test failed (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (that is, the above-mentioned first test result / fourth test result may include at least one of the test conclusions of TP1 test result uncertain, TP2 test result uncertain, TP1 test failed, and TP2 test failed).

[0183] In addition, in Table 7, in step 0a, the system simulator (i.e., the test device) configures the terminal with an IDC auxiliary configuration; step 0c is used to test whether the terminal cannot detect the IDC problem under the second configuration (i.e., the "T0" configuration in Table 6); in step 0d, the system simulator configures the terminal with the first configuration (i.e., the "T1" configuration in Table 6); step 0e is used to confirm whether the terminal can detect the IDC problem under the first configuration; if the system simulator receives a terminal auxiliary information message including IDC auxiliary information, it confirms that the terminal can detect the IDC problem in the RRC connected state, and the problem will be recorded as a reference to the test result, that is, the system simulator can generate a first test result characterizing that the terminal can detect the IDC problem under the first configuration; the IDC mechanism test process may include steps 0e to step 22, and the above-mentioned first test result / fourth test result may also include the judgment obtained in step 22 (such as P).

[0184] Table 6

[0185] Table 7

[0186] In actual application, when the test equipment needs to perform an IDC mechanism test on the terminal, it can first confirm and / or check the IDC problem. Specifically, it can first perform IDC auxiliary configuration on the terminal (i.e., first configure idc-AssistanceConfig-r16), and then configure the measurement record configuration of the terminal (i.e., then configure LoggedMeasurementConfiguration), and can add checks on the IDC problems under the second configuration and the first configuration; if the IDC problem occurs in the connected terminal under the second configuration and the first configuration, then the terminal will be in a suspended measurement record state (which can be expressed as logging suspended in English), and TP1 can be verified at this time. For example, assuming that the test environment is 2.4GHz WiFi and the 2300-2400MHz frequency band (i.e., Band n40) (i.e., Band n40 is interfered with by 2.4GHz WiFi), assuming that the first channel includes the working channel of the first receiver (i.e., the working channel of Band n40), and the second channel includes the working channel of the first transmitter (i.e., the working channel of 2.4GHz WiFi), and assuming that the first receiver is NR Cell 1 and the first transmitter is WLAN AP 1 (Cell 27); then the channel configuration performed by the network / system simulator (which can be expressed as NW / SS, i.e., the test equipment) on the terminal can be as shown in Table 6, and the test process performed by the network / system simulator on the terminal can be as shown in Figure 5.

[0187] Specifically, as shown in Figure 5, when the terminal is tested, under the initial test conditions, the terminal in the connected state and with the "T0" configuration (non-IDC configuration, i.e., the second configuration mentioned above) is configured with the IDC auxiliary configuration in the RRC connected state; check: whether the terminal in the connected state and with the "T0" configuration sends a terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information) message to notify the IDC problem. Afterwards, if the terminal does not send terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information), the terminal in the connected state is reconfigured to the "T1" configuration (IDC configuration, i.e., the above-mentioned first configuration) in the RRC connected state to trigger the IDC problem; check: whether the terminal in the connected state sends a terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information) message to notify the IDC problem; if the terminal does not send terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information), the network / system simulator can generate at least one of the test conclusions (the conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)) of TP1 test result uncertainty (which can also be understood as no test result, which can be expressed as Inconclusive in English), TP2 test result uncertainty, TP1 test failure, and TP2 test failure (which can be expressed as TP1&TP2 Inconclusive and / or TP1&TP2 in English). FAIL) (i.e., the above-mentioned second test result / fourth test result may include at least one of the test conclusions of TP1 test result uncertainty, TP2 test result uncertainty, TP1 test failure, and TP2 test failure); if the terminal sends terminal auxiliary information for notifying the IDC problem, the terminal in the connected state and with the "T2" configuration (non-IDC configuration) is reconfigured with the measurement logging configuration in the RRC connected state; thereafter, the network / system simulator sends an RRC release message to the terminal; the terminal in the idle state and with the "T2" configuration (non-IDC configuration) activates logging; the terminal in the idle state is reconfigured to the "T3" configuration The terminal is configured as T4 (non-IDC configuration and the same as T0) to trigger the suspension of logging; 10 seconds later, the terminal in the idle state is reconfigured to the T4 configuration (non-IDC configuration and the same as T0) to resume logging; the network / system simulator sends a terminal information request to the terminal in the RRC connected state; checks: when reconfigured to the T3 configuration, whether the terminal suspends logging for approximately 10 seconds and sends a terminal information response message marked with an IDC detection identifier when returning to the connected state; if so, the network / system simulator can generate a test conclusion of TP1 test passed and / or TP2 test passed (which can be expressed as TP1 PASS and / or TP2 PASS in English) (that is, the above-mentioned first test result / fourth test result can include the test conclusion of TP1 test passed and / or TP2 test passed);If not, the network / system simulator may generate at least one of the test conclusions of TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure (which may be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (i.e., the first test result / fourth test result may include at least one of the test conclusions of TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure).

[0188] As shown in FIG5 , after checking whether a terminal in a connected state and having a “T0” configuration sends a terminal assistance information (i.e., the above-mentioned IDC assistance information) message to notify an IDC problem, if the terminal sends the terminal assistance information for notifying the IDC problem, the terminal in the connected state is reconfigured to a “T1” configuration (IDC configuration, i.e., the above-mentioned first configuration) in the RRC connected state to trigger the IDC problem; checking: whether the terminal in the connected state sends a terminal assistance information (i.e., the above-mentioned IDC assistance information) message to notify the IDC problem; if the terminal does not send the terminal assistance information (i.e., the above-mentioned IDC assistance information), the network / system simulator may generate at least one of the test conclusions of TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (i.e., the above-mentioned second test result / third test result may include at least one of the test conclusions of TP1 test result uncertainty, TP2 test result uncertainty, TP1 test failure, and TP2 test failure); if the terminal sends terminal auxiliary information for notifying the IDC problem, the terminal in the connected state and with the "T1" configuration (IDC configuration) is reconfigured with the measurement recording configuration in the RRC connected state; thereafter, the network / system simulator sends an RRC release message to the terminal; thereafter, the terminal is in the idle state, with the "T1" configuration (IDC configuration), and waits for at least 10s; thereafter, the network / system simulator sends a terminal information request to the terminal in the RRC connected state; check: when reconfigured to the "T3" configuration, whether the terminal suspends logging for about 10s and sends a terminal information response message marked with the IDC detection identifier when returning to the connected state; if so, the network / system simulator can generate a test conclusion that the TP1 test passed (which can be expressed in English as TP1 PASS) (i.e., the above-mentioned first test result / third test result may include the test conclusion that the TP1 test passed); if not, the network / system simulator may generate at least one of the test conclusions of TP1 test result being uncertain, TP2 test result being uncertain, TP1 test failure, and TP2 test failure (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL) (i.e., the above-mentioned first test result / third test result may include at least one of the test conclusions of TP1 test result being uncertain, TP2 test result being uncertain, TP1 test failure, and TP2 test failure).

[0189] In actual application, it can be seen from the above description that the test device can confirm whether the terminal can detect the IDC problem under the first configuration by confirming whether the terminal can detect the IDC problem under the second configuration; if the terminal can detect the IDC problem under the second configuration, it means that the terminal has always had an IDC problem, which means that the terminal can also detect the IDC problem under the first configuration.

[0190] Based on this, in one embodiment, confirming whether the terminal can detect the IDC problem under the first configuration may include:

[0191] confirming whether the terminal can detect the IDC problem in the first configuration by confirming whether the terminal cannot detect the IDC problem in the second configuration;

[0192] In a case where the terminal is capable of detecting the IDC problem under the second configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the first configuration.

[0193] In actual application, the testing device may first confirm whether the terminal can detect the IDC problem under the first configuration, and then confirm whether the terminal can detect the IDC problem under the second configuration.

[0194] Based on this, in one embodiment, confirming whether the terminal cannot detect the IDC problem under the second configuration may include:

[0195] After confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration.

[0196] Here, it should be noted that the specific process of the test device first confirming whether the terminal can detect the IDC problem under the first configuration and then confirming whether the terminal cannot detect the IDC problem under the second configuration can be understood with reference to any process shown in Figures 2 to 5, and the steps shown in Table 2 / Table 4 / Table 5 / Table 7, and the embodiments of the present application will not go into details about this.

[0197] In actual application, in addition to the above channel configuration and test steps, other channel configurations and test steps can also be used to test the terminal. For example, Table 8 provides a configuration for testing the IDC mechanism, and is applicable only when the terminal supports IDC reporting. Among them, for NR operating band n40, NR cell 14 / NRf4 (2390-2400MHz) can be selected because it is the available frequency closest to 2401MHz, and channel 1 (2401~2423MHz) can be configured to WLAN AP 1 (Cell 27). For NR operating band n41, NR cell 1 / NRf1 (2496-2556MHz) can be selected because it is the available frequency closest to 2483MHz, and channel 13 (2461-2483MHz) can be configured to WLAN AP2 (Cell 27b). In addition, when configuration "C1" is applied, the terminal does not send a terminal assistance information message including IDC assistance information because the terminal cannot detect IDC problems under the "C1" configuration. When configuration "C2" is applied, the terminal sends a terminal assistance information message including IDC assistance information because the terminal is able to detect IDC problems under configuration "C2" when IDC assistance information is configured. Based on the configuration shown in Table 8, the terminal can be tested using the configuration shown in Table 9 and the test steps shown in Table 10. In Table 9, configuration "C1" at "T0" represents the initial condition, and subsequent configurations marked "T1" and "T2" are applied at the points shown in the main behavior description in Table 10.

[0198] Table 8

[0199] Table 9

[0200] Table 10

[0201] The present application also provides a testing method for testing equipment, as shown in FIG6 , including:

[0202] Step 601: Execute the IDC mechanism test process on the terminal;

[0203] Step 602: If no fifth test result is obtained, configure the terminal with the IDC auxiliary configuration and the third configuration, and confirm whether the terminal can detect the IDC problem under the third configuration (i.e., check whether the terminal can detect the IDC problem under the third configuration). The fifth test result includes suspending measurement recording.

[0204] Step 603: Generate a sixth test result for the terminal based on whether the terminal is able to detect the IDC problem under the third configuration.

[0205] In the third configuration, the first and second channels of the terminal are configured to have a minimum distance, and / or the transmit channel of the first and second channels of the terminal has the highest transmit power. It is understood that the third configuration has the same meaning as the first configuration, and its specific meaning can be understood with reference to the first configuration. This embodiment of the present application will not be further described.

[0206] In actual application, it can be seen from the above steps 601 and 602 that the test method shown in Figure 6 is a technical solution that first performs an IDC mechanism test and then checks for IDC problems. That is, after the IDC mechanism test process, for terminals that do not suspend measurement logging (which can be expressed as measurement logging in English), that is, terminals that do not obtain the fifth test result, the IDC problem check process is then performed to check whether the terminal has detected an IDC problem. If the terminal is checked and / or confirmed to be able to detect the IDC problem under the third configuration, it can be determined that the terminal test result is inconclusive (which can also be understood as no test result, which can be expressed as inconclusive in English) and / or the test fails (which can be expressed as Fail in English, abbreviated as F), that is, the sixth test result can include a conclusion that the test result is inconclusive (a conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)) and / or a conclusion that the test fails. If the terminal is checked and / or confirmed to be unable to detect the IDC problem under the third configuration, it can be determined that the terminal has passed the test (which can be expressed as Pass in English, abbreviated as P), that is, the sixth test result can include a conclusion that the test has passed.

[0207] In one embodiment, confirming whether the terminal can detect the IDC problem under the third configuration may include:

[0208] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the third configuration when the terminal is in a connected state, and that the IDC problem can be detected under the third configuration when the terminal is in an idle state;

[0209] or,

[0210] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the third configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the third configuration, or it cannot be confirmed that the IDC problem is detected under the third configuration.

[0211] The IDC auxiliary information is used to notify IDC problems.

[0212] In one embodiment, confirming whether the terminal can detect the IDC problem under the third configuration may include:

[0213] confirming whether the terminal can detect the IDC problem under the third configuration by confirming whether the terminal cannot detect the IDC problem under the fourth configuration;

[0214] In a case where the terminal is capable of detecting the IDC problem under the fourth configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the third configuration.

[0215] In the fourth configuration, the first channel and the second channel of the terminal are configured as at least one of the following:

[0216] The first channel and the second channel of the terminal are configured as a maximum distance;

[0217] The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest;

[0218] No information is transmitted on the first channel and / or the second channel of the terminal;

[0219] The first channel and / or the second channel of the terminal is closed.

[0220] Here, it can be understood that the meaning of the fourth configuration is the same as that of the above-mentioned second configuration. It can be specifically understood by referring to the above-mentioned second configuration, and the embodiments of the present application will not be repeated here.

[0221] In one embodiment, confirming whether the terminal cannot detect the IDC problem under the fourth configuration may include:

[0222] performing the fourth configuration on the terminal;

[0223] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the fourth configuration when the terminal is in a connected state, and that the IDC problem can be detected under the fourth configuration when the terminal is in an idle state; or

[0224] In the case that the terminal does not send IDC auxiliary information, and / or in the case that the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the fourth configuration when the terminal is in the connected state, or it cannot be confirmed that the IDC problem can be detected under the fourth configuration when the terminal is in the connected state; and when the terminal is in the idle state, the IDC problem cannot be detected under the fourth configuration, or it cannot be confirmed that the IDC problem is detected under the fourth configuration, or the IDC problem has been resolved under the fourth configuration.

[0225] In actual application, when the test device executes the IDC mechanism test process on the terminal, the configuration performed on the terminal includes the third configuration.

[0226] In actual application, for the technical solution of the post-check IDC problem shown in Figure 6, it is assumed that the test environment configured by the test equipment is 2.4GHz WiFi and the 2300-2400MHz frequency band (ie, Band n40) (ie, Band n40 is interfered with by 2.4GHz WiFi), and it is assumed that the first channel includes the working channel of the first receiver (ie, the working channel of Band n40), and the second channel includes the working channel of the first transmitter (ie, the working channel of 2.4GHz WiFi), and it is assumed that the first receiver is NR Cell 1 and the first transmitter is WLAN AP 1 (Cell 27); then the channel configuration performed by the network / system simulator (which can be expressed as NW / SS, that is, the test equipment) on the terminal can be as shown in Table 11, and the test process executed by the network / system simulator on the terminal can be as shown in Figure 7. The specific test steps (also referred to as main behaviors, which can be expressed as Main behavior in English) corresponding to the test process shown in Figure 7 can be shown in Table 12.

[0227] Table 11 shows the time instances of cell power levels and parameter changes in FR1 during the processes shown in Figures 7 and Table 12, and includes the downlink power and other parameter changes applied to the cell at different times during the test execution. In Table 1, "T0" represents the initial test condition, "T1," "T2," and "T3" represent the configurations corresponding to the subsequent main behavior descriptions; "T2" and "T0" are essentially the same test conditions, and "T3" and "T1" are essentially the same test conditions.

[0228] Accordingly, as shown in FIG7 , when the terminal is tested, the terminal in the idle state and having the “T0” configuration (non-IDC configuration) activates logging; the terminal in the idle state is reconfigured to the “T1” configuration (IDC configuration) to trigger the suspension of logging; 10 seconds later, the terminal in the idle state is reconfigured to the “T2” configuration (non-IDC configuration and the same as the “T0” configuration) to resume logging; the network / system simulator sends a terminal information request to the terminal in the RRC connected state; checks: when reconfigured to the “T3” configuration, whether the terminal suspends logging for approximately 10 seconds and sends a terminal information response message marked with an IDC detection identifier when returning to the connected state; if so, the network / system simulator can generate a test conclusion (a conclusion can also be called a judgment (which can be expressed as judgment in English) or a verdict (which can be expressed as Verdict in English)) that the TP1 test passes and / or the TP2 test passes. PASS); if not, that is, the above-mentioned fifth test result is not obtained, the terminal in the connected state is reconfigured to the IDC auxiliary configuration and the "T3" configuration (IDC configuration, and the same as the "T1" configuration, that is, the above-mentioned third configuration) in the RRC connected state; check: whether the terminal sends a terminal auxiliary information (that is, the above-mentioned IDC auxiliary information) message to notify the IDC problem; if the terminal does not send terminal auxiliary information (that is, the above-mentioned IDC auxiliary information), the network / system simulator can generate a test conclusion that the TP1 test passed and / or the TP2 test passed (which can be expressed in English as TP1 PASS and / or TP2 PASS), that is, the sixth test result can include the test conclusion that the TP1 test passed and / or the TP2 test passed; if the terminal sends terminal auxiliary information for notifying the IDC problem, the network / system simulator can generate at least one of the test conclusions of TP1 test result uncertainty (which can also be understood as no test result, which can be expressed in English as Inconclusive), TP2 test result uncertainty, TP1 test failure, and TP2 test failure (which can be expressed in English as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL), that is, the sixth test result may include at least one of the test conclusions of TP1 test result being uncertain, TP2 test result being uncertain, TP1 test failure, and TP2 test failure.

[0229] In addition, in Table 12, the IDC mechanism test process includes steps 1 to 22; in step 23, the system simulator (i.e., the test device) configures the terminal with the IDC auxiliary configuration; in step 25, the system simulator configures the terminal with the third configuration (i.e., the "T3" configuration in Table 11); in step 26, the system simulator confirms whether the terminal can detect the IDC problem under the third configuration, and the sixth test result may include the judgment obtained in step 26 (such as F).

[0230] Table 11

[0231] Table 12

[0232] The test method provided in the embodiment of the present application is to configure the terminal with an IDC auxiliary configuration and a first configuration, and confirm whether the terminal can detect an IDC problem under the first configuration; if the terminal can detect an IDC problem under the first configuration, perform an IDC mechanism test process on the terminal, and / or generate a first test result for the terminal; or, if the terminal cannot detect an IDC problem under the first configuration, do not perform the IDC mechanism test process on the terminal, and / or generate a second test result for the terminal. Alternatively, perform an IDC mechanism test process on the terminal; if no fifth test result is obtained, configure the terminal with an IDC auxiliary configuration and a third configuration, and confirm whether the terminal can detect an IDC problem under the third configuration, the fifth test result including suspending measurement records; and generate a sixth test result for the terminal based on the confirmation of whether the terminal can detect an IDC problem under the third configuration. The solution provided by the embodiment of the present application is to first configure the IDC auxiliary configuration and the specific channel configuration (i.e., the above-mentioned first configuration) on the terminal before executing the IDC mechanism test process on the terminal, and confirm whether the terminal can detect the IDC problem under the specific channel configuration, and then execute the IDC mechanism test process on the terminal if the IDC problem can be detected; or, after executing the IDC mechanism test process on the terminal, if the terminal fails the test, that is, if the test result including the suspension measurement record is not obtained, configure the IDC auxiliary configuration and the specific channel configuration (i.e., the above-mentioned third configuration) on the terminal, and confirm whether the terminal can detect the IDC problem under the specific channel configuration. It can detect IDC problems and then generate the final test results for the terminal based on the confirmed results. In this way, it can avoid the situation where "IDC problems do not occur during the execution of the IDC mechanism test process on the terminal due to excellent terminal design (which can be understood as the terminal being able to support the IDC mechanism and improve the IDC problem)" is mistakenly judged as the terminal failing the test. In other words, it can avoid the problem of qualified terminals that can support the IDC mechanism being mistakenly judged as unqualified terminals that cannot support the IDC mechanism, so that it can accurately determine whether the terminal correctly supports the relevant functions of the IDC problem, that is, it can accurately evaluate whether the MDT function of the terminal has an IDC mechanism that meets the relevant technical requirements.

[0233] In addition, according to the solution provided in the embodiment of the present application, the network / system simulator (i.e., the test equipment) can check the IDC interference status in the terminal in the idle state through the IDC interference status in the terminal in the connected state, thereby at least solving the problem that the network cannot know the IDC interference status of the idle terminal.

[0234] In addition, the solution provided in the embodiment of the present application, by first confirming and / or checking the IDC problem, can exclude terminals that are not suitable for testing (i.e., terminals that cannot detect IDC problems under the first configuration) in advance when the IDC mechanism test process needs to be performed, thereby improving the judgment accuracy of the terminal test while reducing the waste of test resources.

[0235] In addition, the solution provided in the embodiment of the present application is that the test equipment can adopt test conditions equivalent to those of the connected state terminal (i.e., the first configuration) when checking the IDC interference status in the terminal in the idle state, thereby at least solving the problem of consistency of test conditions between the terminal in the idle state and the terminal in the connected state, and can reduce the waste of test resources while improving the judgment accuracy of the terminal test.

[0236] In addition, the solution provided in the embodiment of the present application can screen out terminals in which no IDC problems are detected from terminals that have not passed the first checkpoint (i.e., terminals that have not obtained the fifth test result) by checking IDC problems after executing the IDC mechanism test process on the terminal, thereby optimizing the terminal test pass rate and improving the judgment accuracy of the terminal test.

[0237] It should be noted that in various embodiments of the present application, the dotted lines in the test flow diagram (i.e., Figures 2 to 5, and Figure 7) represent optionality, that is, the corresponding branches (which can also be understood as situations) may exist or not; in other words, the dotted lines in the above test flow diagram refer to branch situations that may or may not exist.

[0238] In order to implement the method of the embodiment of the present application, the embodiment of the present application further provides a testing device, which is provided on the testing equipment, as shown in FIG8 , and includes:

[0239] The first testing unit 801 is configured to configure the terminal with the IDC auxiliary configuration and the first configuration, and confirm whether the terminal can detect the IDC problem under the first configuration;

[0240] The second testing unit 802 is configured to, when the terminal is able to detect the IDC problem under the first configuration, execute the IDC mechanism testing process on the terminal and / or generate a first test result for the terminal; or, when the terminal is unable to detect the IDC problem under the first configuration, not execute the IDC mechanism testing process on the terminal and / or generate a second test result for the terminal.

[0241] In one embodiment, the first testing unit 801 is further configured to:

[0242] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the first configuration when the terminal is in a connected state, and that the IDC problem can be detected under the first configuration when the terminal is in an idle state;

[0243] or,

[0244] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the first configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the first configuration, or it cannot be confirmed that the IDC problem is detected under the first configuration.

[0245] In one embodiment, the first testing unit 801 is further configured to confirm whether the terminal cannot detect the IDC problem under the second configuration;

[0246] Accordingly, the second testing unit 802 is further configured to:

[0247] If the terminal is capable of detecting an IDC problem under the second configuration, executing the first sub-process of the IDC mechanism test process on the terminal and not executing the second sub-process of the IDC mechanism test process on the terminal, and / or generating a third test result for the terminal; or

[0248] In the case that the terminal cannot detect the IDC problem under the second configuration, the first sub-process and / or the second sub-process of the IDC mechanism test process are executed on the terminal, and / or a fourth test result for the terminal is generated; wherein,

[0249] The first sub-process is at least used to check that when an IDC problem is detected, measurement logging is suspended and an IDC detection flag is used in a measurement information table of the measurement log to mark an MDT report;

[0250] The second sub-process is at least used to check that the measurement record is restored when the IDC problem is resolved.

[0251] In one embodiment, the first testing unit 801 is further configured to:

[0252] performing the second configuration on the terminal;

[0253] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the terminal can detect the IDC problem under the second configuration when in a connected state, and can detect the IDC problem under the second configuration when the terminal is in an idle state; or

[0254] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the second configuration when the terminal is in a connected state, or it cannot be confirmed that the IDC problem can be detected under the second configuration when the terminal is in a connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the second configuration, or it cannot be confirmed that the IDC problem is detected under the second configuration, or the IDC problem has been resolved under the second configuration.

[0255] In one embodiment, the first testing unit 801 is further configured to:

[0256] Before confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0257] If the terminal cannot detect the IDC problem under the second configuration, or if the terminal can detect the IDC problem under the second configuration, confirming whether the terminal can detect the IDC problem under the first configuration;

[0258] Accordingly, the second testing unit 802 is further configured to:

[0259] If the terminal cannot detect the IDC problem under the second configuration, and the terminal can detect the IDC problem under the first configuration, executing the first sub-process and / or the second sub-process on the terminal to generate the first test result; or

[0260] If the terminal can detect the IDC problem under the second configuration and the terminal can detect the IDC problem under the first configuration, the first sub-process is executed on the terminal and the second sub-process is not executed on the terminal to generate the first test result.

[0261] In one embodiment, the first testing unit 801 is further configured to, after confirming whether the terminal can detect the IDC problem under the first configuration, confirm whether the terminal cannot detect the IDC problem under the second configuration.

[0262] In one embodiment, the first testing unit 801 is further configured to:

[0263] confirming whether the terminal can detect the IDC problem in the first configuration by confirming whether the terminal cannot detect the IDC problem in the second configuration;

[0264] In a case where the terminal is capable of detecting the IDC problem under the second configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the first configuration.

[0265] In actual application, the first test unit 801 and the second test unit 802 can be implemented by a processor in the test device in combination with a communication interface.

[0266] In order to implement the method of the embodiment of the present application, the embodiment of the present application further provides a testing device, which is provided on the testing equipment, as shown in FIG9 , and includes:

[0267] The third testing unit 901 is configured to execute an IDC mechanism testing process on the terminal;

[0268] The fourth test unit 902 is configured to configure the IDC auxiliary configuration and the third configuration of the terminal when the fifth test result is not obtained, and confirm whether the terminal can detect the IDC problem under the third configuration, and the fifth test result includes suspending measurement records; based on the confirmation of whether the terminal can detect the IDC problem under the third configuration, generate a sixth test result for the terminal.

[0269] In one embodiment, the fourth testing unit 902 is further configured to:

[0270] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the third configuration when the terminal is in a connected state, and that the IDC problem can be detected under the third configuration when the terminal is in an idle state;

[0271] or,

[0272] In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the third configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the third configuration, or it cannot be confirmed that the IDC problem is detected under the third configuration.

[0273] In one embodiment, the fourth testing unit 902 is further configured to:

[0274] confirming whether the terminal can detect the IDC problem under the third configuration by confirming whether the terminal cannot detect the IDC problem under the fourth configuration;

[0275] In a case where the terminal is able to detect the IDC problem under the fourth configuration, it is confirmed that the terminal is able to detect the IDC problem under the third configuration.

[0276] In one embodiment, the fourth testing unit 902 is further configured to:

[0277] performing the fourth configuration on the terminal;

[0278] In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the fourth configuration when the terminal is in a connected state, and that the IDC problem can be detected under the fourth configuration when the terminal is in an idle state; or

[0279] In the case that the terminal does not send IDC auxiliary information, and / or in the case that the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the fourth configuration when the terminal is in the connected state, or it cannot be confirmed that the IDC problem can be detected under the fourth configuration when the terminal is in the connected state; and when the terminal is in the idle state, the IDC problem cannot be detected under the fourth configuration, or it cannot be confirmed that the IDC problem is detected under the fourth configuration, or the IDC problem has been resolved under the fourth configuration.

[0280] In actual application, the third test unit 901 and the fourth test unit 902 can be implemented by a processor in the test device in combination with a communication interface.

[0281] It should be noted that the test device provided in the above embodiment is merely illustrated by the division of the aforementioned program modules during testing. In actual application, the aforementioned processing can be distributed among different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the aforementioned processing. Furthermore, the test device provided in the above embodiment and the test method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0282] Based on the hardware implementation of the above program modules and in order to implement the method of the embodiment of the present application, the embodiment of the present application further provides a testing device, as shown in FIG10 , the testing device 1000 includes:

[0283] Communication interface 1001, capable of exchanging information with the terminal;

[0284] A processor 1002, connected to the communication interface 1001 to implement information interaction with the terminal, and configured to execute the methods provided by one or more of the above technical solutions when running a computer program;

[0285] The computer program is stored in the memory 1003 .

[0286] Specifically, when implementing a testing method according to an embodiment of the present application, the processor 1002 is configured to:

[0287] Configuring the terminal with the IDC auxiliary configuration and the first configuration, and confirming whether the terminal can detect the IDC problem under the first configuration;

[0288] In a case where the terminal is capable of detecting an IDC problem under the first configuration, performing an IDC mechanism test process on the terminal and / or generating a first test result for the terminal; or

[0289] In a case where the terminal cannot detect the IDC problem under the first configuration, the IDC mechanism test process is not performed on the terminal, and / or a second test result is generated for the terminal.

[0290] In one embodiment, the processor 1002 is further configured to:

[0291] In a case where the terminal sends IDC auxiliary information and / or in a case where the IDC auxiliary information is received through the communication interface 1001, confirming that the IDC problem can be detected under the first configuration when the terminal is in a connected state, and that the IDC problem can be detected under the first configuration when the terminal is in an idle state;

[0292] or,

[0293] In the case that the terminal does not send IDC auxiliary information, and / or in the case that IDC auxiliary information is not received through the communication interface 1001, it is confirmed that the IDC problem cannot be detected under the first configuration when the terminal is in the connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in the idle state, the IDC problem cannot be detected under the first configuration, or it cannot be confirmed that the IDC problem is detected under the first configuration.

[0294] In one embodiment, the processor 1002 is further configured to:

[0295] confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0296] If the terminal is capable of detecting an IDC problem under the second configuration, executing the first sub-process of the IDC mechanism test process on the terminal and not executing the second sub-process of the IDC mechanism test process on the terminal, and / or generating a third test result for the terminal; or

[0297] In the case that the terminal cannot detect the IDC problem under the second configuration, the first sub-process and / or the second sub-process of the IDC mechanism test process are executed on the terminal, and / or a fourth test result for the terminal is generated; wherein,

[0298] The first sub-process is at least used to check that when an IDC problem is detected, measurement logging is suspended and an IDC detection flag is used in a measurement information table of the measurement log to mark an MDT report;

[0299] The second sub-process is at least used to check that the measurement record is restored when the IDC problem is resolved.

[0300] In one embodiment, the processor 1002 is further configured to:

[0301] performing the second configuration on the terminal;

[0302] In a case where the terminal sends IDC auxiliary information, and / or in a case where the IDC auxiliary information is received through the communication interface 1001, confirming that the IDC problem can be detected under the second configuration when the terminal is in a connected state, and that the IDC problem can be detected under the second configuration when the terminal is in an idle state; or

[0303] In the case that the terminal does not send IDC auxiliary information, and / or in the case that IDC auxiliary information is not received through the communication interface 1001, it is confirmed that the IDC problem cannot be detected under the second configuration when the terminal is in the connected state, or it cannot be confirmed that the IDC problem can be detected under the second configuration when the terminal is in the connected state; and when the terminal is in the idle state, the IDC problem cannot be detected under the second configuration, or it cannot be confirmed that the IDC problem is detected under the second configuration, or the IDC problem has been resolved under the second configuration.

[0304] In one embodiment, the processor 1002 is further configured to:

[0305] Before confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration;

[0306] If the terminal cannot detect the IDC problem under the second configuration, confirm whether the terminal can detect the IDC problem under the first configuration, and if the terminal can detect the IDC problem under the first configuration, perform the first sub-process and / or the second sub-process on the terminal to generate the first test result; or

[0307] If the terminal is able to detect the IDC problem under the second configuration, confirm whether the terminal is able to detect the IDC problem under the first configuration, and if the terminal is able to detect the IDC problem under the first configuration, execute the first sub-process on the terminal and do not execute the second sub-process on the terminal, to generate the first test result.

[0308] In one embodiment, the processor 1002 is further configured to:

[0309] After confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration.

[0310] In one embodiment, the processor 1002 is further configured to:

[0311] confirming whether the terminal can detect the IDC problem in the first configuration by confirming whether the terminal cannot detect the IDC problem in the second configuration;

[0312] In a case where the terminal is capable of detecting the IDC problem under the second configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the first configuration.

[0313] Accordingly, when implementing another testing method according to an embodiment of the present application, the processor 1002 is configured to:

[0314] Execute the IDC mechanism test process on the terminal;

[0315] If no fifth test result is obtained, configuring the terminal with the IDC auxiliary configuration and the third configuration, and confirming whether the terminal can detect the IDC problem under the third configuration, the fifth test result including suspending measurement recording;

[0316] A sixth test result for the terminal is generated according to whether the terminal is able to detect the IDC problem under the third configuration.

[0317] In one embodiment, the processor 1002 is further configured to:

[0318] In a case where the terminal sends IDC auxiliary information and / or in a case where the IDC auxiliary information is received through the communication interface 1001, confirming that the IDC problem can be detected under the third configuration when the terminal is in a connected state, and that the IDC problem can be detected under the third configuration when the terminal is in an idle state;

[0319] or,

[0320] In the case that the terminal does not send IDC auxiliary information, and / or in the case that IDC auxiliary information is not received through the communication interface 1001, it is confirmed that the IDC problem cannot be detected under the third configuration when the terminal is in the connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in the idle state, the IDC problem cannot be detected under the third configuration, or it cannot be confirmed that the IDC problem is detected under the third configuration.

[0321] In one embodiment, the processor 1002 is further configured to:

[0322] confirming whether the terminal can detect the IDC problem under the third configuration by confirming whether the terminal cannot detect the IDC problem under the fourth configuration;

[0323] In a case where the terminal is capable of detecting the IDC problem under the fourth configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the third configuration.

[0324] In one embodiment, the processor 1002 is further configured to:

[0325] performing the fourth configuration on the terminal;

[0326] In a case where the terminal sends IDC auxiliary information, and / or in a case where IDC auxiliary information is received through the communication interface 1001, confirming that the IDC problem can be detected under the fourth configuration when the terminal is in a connected state, and that the IDC problem can be detected under the fourth configuration when the terminal is in an idle state; or

[0327] In the case that the terminal does not send IDC auxiliary information, and / or in the case that IDC auxiliary information is not received through the communication interface 1001, it is confirmed that the IDC problem cannot be detected under the fourth configuration when the terminal is in the connected state, or it cannot be confirmed that the IDC problem can be detected under the fourth configuration when the terminal is in the connected state; and when the terminal is in the idle state, the IDC problem cannot be detected under the fourth configuration, or it cannot be confirmed that the IDC problem is detected under the fourth configuration, or the IDC problem has been resolved under the fourth configuration.

[0328] It should be noted that the specific processing process of the processor 1002 can be understood by referring to the above method and will not be repeated here.

[0329] Of course, in actual use, the various components in test device 1000 are coupled together via bus system 1004. It will be appreciated that bus system 1004 is used to enable communication between these components. In addition to a data bus, bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in FIG10 , all of these buses are labeled as bus system 1004.

[0330] The memory 1003 in the embodiment of the present application is used to store various types of data to support the operation of the test device 1000. Examples of such data include: any computer program used to operate on the test device 1000.

[0331] The methods disclosed in the above embodiments of the present application can be applied to the processor 1002 or implemented by the processor 1002. The processor 1002 may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above methods can be completed by hardware integrated logic circuits or software instructions in the processor 1002. The processor 1002 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 1002 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 1003. The processor 1002 reads the information in the memory 1003 and completes the steps of the above methods in combination with its hardware.

[0332] In an exemplary embodiment, the test device 1000 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0333] It is understood that the memory 1003 of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0334] In an exemplary embodiment, the present application also provides a storage medium, namely, a computer storage medium, specifically, a computer-readable storage medium, including, for example, a memory 1003 storing a computer program. The computer program can be executed by the processor 1002 of the test device 1000 to perform the steps of any of the aforementioned methods. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface mount storage, optical disk, or CD-ROM.

[0335] In an exemplary embodiment, the present application further provides a computer program product, including a computer program, which can be executed by the processor 1002 of the test device 1000 to complete the steps of any of the aforementioned methods.

[0336] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0337] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

[0338] The above description is merely a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application.

Claims

1. A testing method comprising: Configuring the terminal with the in-device coexistence IDC auxiliary configuration and the first configuration, and confirming whether the terminal can detect the IDC problem under the first configuration; In a case where the terminal is capable of detecting an IDC problem under the first configuration, performing an IDC mechanism test process on the terminal, and / or generating a first test result for the terminal; or, In a case where the terminal cannot detect the IDC problem under the first configuration, the IDC mechanism test process is not performed on the terminal, and / or a second test result is generated for the terminal.

2. The method according to claim 1, wherein In the first configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest.

3. The method according to claim 1, wherein The confirming whether the terminal can detect the IDC problem under the first configuration includes: In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the first configuration when the terminal is in a connected state, and that the IDC problem can be detected under the first configuration when the terminal is in an idle state; or, In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the first configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the first configuration, or it cannot be confirmed that the IDC problem is detected under the first configuration.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: confirming whether the terminal cannot detect the IDC problem under the second configuration; If the terminal is capable of detecting an IDC problem under the second configuration, executing the first sub-process of the IDC mechanism test process on the terminal and not executing the second sub-process of the IDC mechanism test process on the terminal, and / or generating a third test result for the terminal; or In the case that the terminal cannot detect the IDC problem under the second configuration, the first sub-process and / or the second sub-process of the IDC mechanism test process are executed on the terminal, and / or a fourth test result for the terminal is generated; wherein, The first sub-process is at least used to check that when an IDC problem is detected, measurement recording is suspended and an IDC detection flag is used in a measurement information table of the measurement record to mark a minimization of drive tests (MDT) report; The second sub-process is at least used to check that the measurement record is restored when the IDC problem is resolved.

5. The method according to claim 4, wherein In the second configuration, the first channel and the second channel of the terminal are configured as at least one of the following: The first channel and the second channel of the terminal are configured as a maximum distance; The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest; No information is transmitted on the first channel and / or the second channel of the terminal; The first channel and / or the second channel of the terminal is closed.

6. The method according to claim 4, wherein: The confirming whether the terminal cannot detect the IDC problem under the second configuration includes: performing the second configuration on the terminal; In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the terminal can detect the IDC problem under the second configuration when in a connected state, and can detect the IDC problem under the second configuration when the terminal is in an idle state; or In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the second configuration when the terminal is in a connected state, or it cannot be confirmed that the IDC problem can be detected under the second configuration when the terminal is in a connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the second configuration, or it cannot be confirmed that the IDC problem is detected under the second configuration, or the IDC problem has been resolved under the second configuration.

7. The method according to claim 4, wherein: The confirming whether the terminal cannot detect the IDC problem under the second configuration includes: Before confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration; If the terminal cannot detect the IDC problem under the second configuration, confirm whether the terminal can detect the IDC problem under the first configuration, and if the terminal can detect the IDC problem under the first configuration, perform the first sub-process and / or the second sub-process on the terminal to generate the first test result; or If the terminal is able to detect the IDC problem under the second configuration, confirm whether the terminal is able to detect the IDC problem under the first configuration, and if the terminal is able to detect the IDC problem under the first configuration, execute the first sub-process on the terminal and do not execute the second sub-process on the terminal, to generate the first test result.

8. The method according to claim 4, wherein: The confirming whether the terminal cannot detect the IDC problem under the second configuration includes: After confirming whether the terminal can detect the IDC problem under the first configuration, confirming whether the terminal cannot detect the IDC problem under the second configuration.

9. The method according to claim 1, wherein The confirming whether the terminal can detect the IDC problem under the first configuration includes: confirming whether the terminal can detect the IDC problem in the first configuration by confirming whether the terminal cannot detect the IDC problem in the second configuration; In a case where the terminal is capable of detecting the IDC problem under the second configuration, it is confirmed that the terminal is capable of detecting the IDC problem under the first configuration.

10. The method according to claim 9, wherein: Under the first configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest; In the second configuration, the first channel and the second channel of the terminal are configured as at least one of the following: The first channel and the second channel of the terminal are configured as a maximum distance; The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest; No information is transmitted on the first channel and / or the second channel of the terminal; The first channel and / or the second channel of the terminal is closed.

11. The method according to claim 1, wherein In executing the IDC mechanism test process on the terminal, the configuration performed on the terminal includes the first configuration.

12. A testing method comprising: Execute the IDC mechanism test process on the terminal; If no fifth test result is obtained, configuring the terminal with the IDC auxiliary configuration and the third configuration, and confirming whether the terminal can detect the IDC problem under the third configuration, the fifth test result including suspending measurement recording; A sixth test result for the terminal is generated according to whether the terminal is able to detect the IDC problem under the third configuration.

13. The method according to claim 12, wherein: Under the third configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest.

14. The method according to claim 12, wherein: The confirming whether the terminal can detect the IDC problem under the third configuration includes: In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the third configuration when the terminal is in a connected state, and that the IDC problem can be detected under the third configuration when the terminal is in an idle state; or, In a case where the terminal does not send IDC auxiliary information, and / or in a case where the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the third configuration when the terminal is in a connected state, or it cannot be confirmed that the terminal can detect the IDC problem in the connected state; and, when the terminal is in an idle state, the IDC problem cannot be detected under the third configuration, or it cannot be confirmed that the IDC problem is detected under the third configuration.

15. The method according to claim 12, wherein: The confirming whether the terminal can detect the IDC problem under the third configuration includes: confirming whether the terminal can detect the IDC problem under the third configuration by confirming whether the terminal cannot detect the IDC problem under the fourth configuration; In a case where the terminal is able to detect the IDC problem under the fourth configuration, it is confirmed that the terminal is able to detect the IDC problem under the third configuration.

16. The method according to claim 15, wherein Under the third configuration, the first channel and the second channel of the terminal are configured to have a minimum distance, and / or the transmission power of the transmission channel of the first channel and the second channel of the terminal is the highest; In the fourth configuration, the first channel and the second channel of the terminal are configured as at least one of the following: The first channel and the second channel of the terminal are configured as a maximum distance; The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest; No information is transmitted on the first channel and / or the second channel of the terminal; The first channel and / or the second channel of the terminal is closed.

17. The method according to claim 15, wherein: The confirming whether the terminal cannot detect the IDC problem under the fourth configuration includes: performing the fourth configuration on the terminal; In a case where the terminal sends IDC auxiliary information, and / or in a case where the terminal receives IDC auxiliary information, confirming that the IDC problem can be detected under the fourth configuration when the terminal is in a connected state, and that the IDC problem can be detected under the fourth configuration when the terminal is in an idle state; or In the case that the terminal does not send IDC auxiliary information, and / or in the case that the IDC auxiliary information is not received, it is confirmed that the IDC problem cannot be detected under the fourth configuration when the terminal is in the connected state, or it cannot be confirmed that the IDC problem can be detected under the fourth configuration when the terminal is in the connected state; and when the terminal is in the idle state, the IDC problem cannot be detected under the fourth configuration, or it cannot be confirmed that the IDC problem is detected under the fourth configuration, or the IDC problem has been resolved under the fourth configuration.

18. The method according to claim 12, wherein: In executing the IDC mechanism test process on the terminal, the configuration performed on the terminal includes the third configuration.

19. A testing device comprising: a first testing unit configured to configure the terminal with the IDC auxiliary configuration and the first configuration, and confirm whether the terminal can detect the IDC problem under the first configuration; The second test unit is configured to, when the terminal can detect the IDC problem under the first configuration, execute the IDC mechanism test process on the terminal and / or generate a first test result for the terminal; or, when the terminal cannot detect the IDC problem under the first configuration, not execute the IDC mechanism test process on the terminal and / or generate a second test result for the terminal.

20. A testing device comprising: A third testing unit is configured to execute an IDC mechanism testing process on the terminal; The fourth test unit is configured to, if the fifth test result is not obtained, configure the IDC auxiliary configuration and the third configuration of the terminal, and confirm whether the terminal can detect the IDC problem under the third configuration, and the fifth test result includes suspending measurement records; based on the confirmation of whether the terminal can detect the IDC problem under the third configuration, generate a sixth test result for the terminal.

21. A testing device comprising: a communication interface and a processor; wherein, The processor is configured to: configure the IDC auxiliary configuration and the first configuration on the terminal, and confirm whether the terminal can detect the IDC problem under the first configuration; if the terminal can detect the IDC problem under the first configuration, perform an IDC mechanism test process on the terminal and / or generate a first test result for the terminal; or, if the terminal cannot detect the IDC problem under the first configuration, not perform the IDC mechanism test process on the terminal and / or generate a second test result for the terminal; or, The processor is configured to: execute an IDC mechanism test process on the terminal; if no fifth test result is obtained, configure the terminal with an IDC auxiliary configuration and a third configuration, and confirm whether the terminal can detect an IDC problem under the third configuration, wherein the fifth test result includes suspending measurement recording; and generate a sixth test result for the terminal based on the confirmation of whether the terminal can detect the IDC problem under the third configuration.

22. A testing device comprising: a processor and a memory configured to store a computer program capable of being executed on the processor, Wherein, when the processor is configured to run the computer program, it executes the steps of the method described in any one of claims 1 to 11, or executes the steps of the method described in any one of claims 12 to 18.

23. A storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 11, or the steps of the method according to any one of claims 12 to 18.

24. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 11, or the steps of the method according to any one of claims 12 to 18.

Images