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

Abstract

The invention discloses a test method and device, test equipment, a storage medium and a computer program product. The method comprises the following steps: carrying out in-device coexistence (IDC) auxiliary configuration configuration and first configuration configuration on a terminal, and confirming whether the terminal can detect an IDC problem under the first configuration; under the condition that the terminal can detect an IDC problem under the first configuration, executing an IDC mechanism test process on the terminal, and / or generating a first test result for the terminal; or under the condition that the terminal cannot detect the IDC problem under the first configuration, the IDC mechanism test process is not executed on the terminal, and / or a second test result for the terminal is generated.

Description

Technical Field

[0001] 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

[0002] 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.

[0003] 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

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

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

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

[0007] 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;

[0008] 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

[0009] 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.

[0010] 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.

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

[0012] 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;

[0013] or,

[0014] 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.

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

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

[0017] 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

[0018] 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,

[0019] 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;

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

[0021] 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:

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

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

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

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

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

[0027] performing the second configuration on the terminal;

[0028] 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

[0029] 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.

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

[0031] 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;

[0032] 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

[0033] 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.

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

[0035] 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.

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

[0037] 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;

[0038] 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.

[0039] 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;

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

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

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

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

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

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

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

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

[0048] 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;

[0049] 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.

[0050] 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.

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

[0052] 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;

[0053] or,

[0054] 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.

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

[0056] 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;

[0057] 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.

[0058] 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;

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

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

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

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

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

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

[0065] performing the fourth configuration on the terminal;

[0066] 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

[0067] 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.

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

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

[0070] 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;

[0071] The second testing unit is configured to, when the terminal is capable of detecting an IDC problem under the first configuration, execute an 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 an 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.

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

[0073] The third testing unit is used to perform an IDC mechanism testing process on the terminal;

[0074] The fourth test unit is used 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.

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

[0076] 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;

[0077] or,

[0078] 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.

[0079] The present application also provides a testing device, comprising: a processor and a memory for storing a computer program that can be run on the processor.

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

[0081] 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.

[0082] 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.

[0083] 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

[0084] Figure 1 A flow chart of a testing method according to an embodiment of the present application;

[0085] Figure 2 This is a test flow diagram of an embodiment of the present application;

[0086] Figure 3 This is another test flow diagram of an embodiment of the present application;

[0087] Figure 4 This is a schematic diagram of the third test process of the embodiment of the present application;

[0088] Figure 5 This is a schematic diagram of the fourth test flow of the embodiment of the present application;

[0089] Figure 6 This is a flow chart of another testing method according to an embodiment of the present application;

[0090] Figure 7 This is a schematic diagram of the fifth test process of the embodiment of the present application;

[0091] Figure 8 This is a schematic diagram of the structure of a testing device according to an embodiment of the present application;

[0092] Figure 9 This is a schematic diagram of another test device structure according to an embodiment of the present application;

[0093] Figure 10 This is a schematic diagram of the test equipment structure of the embodiment of the present application. DETAILED DESCRIPTION

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

[0095] 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.

[0096] 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.

[0097] Definitions and explanations of the IDC problem include: To enable ubiquitous access to a variety of networks and services, an increasing number of 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, IDC problems may occur. If there is an unavoidable risk of IDC problems (such as being 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.

[0098] The IDC mechanism introduced in MDT for logging mode includes: upon detecting an IDC problem, the terminal suspends measurement logging and reports an IDC detection flag (InDeviceCoexDetected-r17) through the measurement report (this flag can also be understood as a sign or mark, which can be expressed as a flag in English). In other words, when the terminal detects an IDC problem, the terminal suspends measurement logging and tags the MDT report with the IDC detection flag in the measurement information table of the measurement record (which can be expressed as When UE detects IDC problem, UE suspends measurement logging and tags MDT report with inDeviceCoexDetected-r17 flag inlogMeasInfoList-r16 in VarLogMeasReport in English). 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 problems detected by the terminal are resolved during the last logging interval, the terminal resumes measurement logging (When the IDC problems detected by the UE is resolved during the last logging interval, UE resumes measurement logging in English).

[0099] 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.

[0100] 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.

[0101] 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 assistanceinformation in English, or 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 IDCproblem 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).

[0102] 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.

[0103] Specifically, the present invention provides a test method for testing a device such as Figure 1 As shown, the method includes:

[0104] 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;

[0105] 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.

[0106] Here, it can be seen from the above steps 101 and 102 that Figure 1The test method shown 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.

[0107] In actual application, the terminal may also be referred to as 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 SystemSimulator 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 realized. 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 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.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] 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. Exemplarily, 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 can 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 can 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 as close to 2400MHz as possible (which can be expressed in English as NR Cell 1is configured as close to 2400MHzas possible); and 2.4GHz WiFi can select the lowest available frequency channel as the operating channel. For example, channel 1 (2401-2423 MHz) is configured to WLAN AP 1 (Cell 27).

[0112] 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.

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

[0114] 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.

[0115] 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.

[0116] 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.

[0117] 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.

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

[0119] 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.

[0120] 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."

[0121] 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."

[0122] 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.

[0123] 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.

[0124] 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)):

[0125] Behavior 1: When the terminal detects an IDC problem, the terminal suspends measurement logging and tags the MDT report with an IDC detection flag in the measurement information table of the measurement log (which can be expressed in English as When UE detects IDCproblem, UE suspend measurement logging and tag MDT report withinDeviceCoexDetected-r17 flag in logMeasInfoList-r16 in VarLogMeasReport);

[0126] Behavior 2: When the IDC problems detected by the UE are resolved during the last logging interval, the UE resumes measurement logging (which can be expressed in English as When the IDC problems detected by the UE is resolved during the last logging interval, UE resumes measurement logging).

[0127] 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).

[0128] 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.

[0129] 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:

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

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

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

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

[0134] 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. Exemplarily, 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 of 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 (expressed in English as NR Cell 1is configured as close to 2300MHz as possible); for another example, NR Cell 1 is configured as far from 2400MHz as possible (expressed in English as NR Cell 1is configured as far from 2400MHz as possible). The 2.4 GHz WiFi can select the highest available frequency channel as the operating channel, or the 2.4 GHz WiFi can be turned off (expressed as WLAN AP 1 (Cell 27) is configured as being off).

[0135] 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.

[0136] 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.

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

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

[0139] 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

[0140] 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,

[0141] 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;

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

[0143] 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.

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

[0145] performing the second configuration on the terminal;

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

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

[0151] performing the second configuration on the terminal;

[0152] 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.

[0153] 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".

[0154] 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.

[0155] 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 (expressed as TP2Fail in English) (the conclusion can also be called a judgment (expressed as judgment in English) or a verdict (expressed as Verdict in English)); in addition, the third test result can also include the conclusion that the above-mentioned TP1 test passes (expressed as TP1Pass in English), the conclusion that the above-mentioned TP1 test fails, or the conclusion that the above-mentioned TP1 test result is uncertain (can also be understood as no test result, 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.

[0156] 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.

[0157] 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.

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

[0159] 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;

[0160] 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

[0161] 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.

[0162] 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.

[0163] 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. 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 1, and the test process performed by the network / system simulator on the terminal can be as shown in Table 1. Figure 2 As shown, Figure 2 The specific test steps (also called main behaviors) corresponding to the test process shown are shown in Table 2.

[0164] Table 1 shows the Figure 2Table 2 shows the time instances of cell powerlevel and parameter changes for Frequency Range 1 (FR1) in the process, and includes the downlink power and other changing parameters applied to the cell at different times of the test execution. In Table 1, "T0" represents the initial test condition, "T1", "T2", "T3" and "T4" are the configurations corresponding to the subsequent main behavior descriptions; and "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.

[0165] Accordingly, if Figure 2As shown, when the terminal is tested, under the initial test conditions, the terminal in the connected state and with the "T0" configuration (non-IDC configuration) is configured with a measurement logging configuration in the RRC connected state (which can be expressed in English as UE in connected mode with "T0" config (non-IDC config) to be configured with "LoggedMeasurementConfiguration" in RRC_CONNECTED); the terminal in the connected state is reconfigured in the RRC connected state to the IDC auxiliary configuration and the "T1" configuration (IDC configuration, that is, the above-mentioned first configuration) to trigger the IDC problem (which can be expressed in English as UE in connected mode to be reconfigured with "idc-AssistanceConfig-r16"and "T1" config (IDC config) to trigger IDC problem in RRC_CONNECTED); Check: whether the terminal in the connected state sends a terminal assistance information (that is, the above-mentioned IDC assistance information) message to notify the IDC problem (which can be expressed in English as Check: whether UE in connected mode sends an UEAssistanceInformation message to inform the IDC problems); if the terminal does not send terminal auxiliary information (that is, 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 judgment (which can be expressed as judgment in English) or 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&TP2Inconclusive and / or TP1&TP2FAIL in English) (that is, the above-mentioned second test result can 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 network / system simulator sends an RRC release message to the terminal (which can be expressed as NW / SS sends RRCRelease to UE in English);Afterwards, UE in idle mode with "T2" config (non-IDC config, the same as "T0") to activate logging; UE in idle mode to be reconfigured with "T3" config (IDC config, the same as "T1") to trigger logging suspension; After 10 seconds, UE in idle mode to be reconfigured with "T4" config (non-IDC config, the same as "T0") to resume logging. resumelogging); the network / system simulator sends a terminal information request to the terminal in the RRC connected state (which can be expressed as NW / SS sends "UEInformationRequest" to UE in RRC_CONNECTED); check: when reconfigured to the "T3" configuration, whether the terminal suspends logging for about 10 seconds and sends a terminal information response message tagged with the IDC detection identifier when returning to the connected state (which can be expressed as Check: whether UE suspended logging for about 10s when reconfigured with "T3" and transmits an UEInformationResponse message Tagged with inDeviceCoexDetected-r17 when back to connected mode); 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) (that is, the above-mentioned first test result may 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 following test conclusions: a TP1 test result is inconclusive (which may also be understood as no test result, which may be expressed as "inconclusive" in English), a TP2 test result is inconclusive, a TP1 test fails, and a TP2 test fails (which may be expressed as "TP1&TP2 inconclusive and / or TP1&TP2 FAIL" in English). (i.e., the first test result may include at least one of the following test conclusions: a TP1 test result is inconclusive, a TP2 test result is inconclusive, a TP1 test fails, and a TP2 test fails).

[0166] 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).

[0167] Table 1

[0168]

[0169]

[0170] Table 2

[0171]

[0172]

[0173]

[0174]

[0175]

[0176]

[0177]

[0178] 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. For example, assuming that the test environment is 2.4GHz WiFi and 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 Cell1 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 3, and the test process performed by the network / system simulator on the terminal can be as shown in Table 3. Figure 3 As shown, Figure 3 The specific test steps (also referred to as main behaviors) corresponding to the test flow shown may be shown in Table 4 or Table 5.

[0179] Table 3 shows the Figure 3 , and the time instances of cell power level and parameter changes for FR1 in the processes shown in Tables 4 and 5 (which can be expressed as Time instances of cell power level and parameter changes for FR1), and include the downlink power and other changing parameters applied to the cell at different times of test execution. In Table 3, "T0" represents the initial test condition, "T1", "T2", "T3", and "T4" are the configurations corresponding to the subsequent main behavior descriptions; and, "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.

[0180] Accordingly, if Figure 3As shown, when the terminal is tested, under the initial test conditions, the terminal in the connected state and with the "T0" configuration (non-IDC configuration) is configured with the IDC auxiliary configuration in the RRC connected state (which can be expressed in English as UE in connected mode with "T0" config (non-IDC config) to be configured with "idc-AssistanceConfig-r16" in RRC_CONNECTED); the terminal in the connected state is reconfigured to the "T1" configuration (IDC configuration, that is, the above-mentioned first configuration) in the RRC connected state to trigger the IDC problem (which can be expressed in English as UE inconnected mode to be reconfigured with "T1" config (IDC config) to trigger IDCproblem in RRC_CONNECTED); Check: whether the terminal in the connected state sends a terminal assistance information (that is, the above-mentioned IDC assistance information) message to inform the IDC problem (which can be expressed in English as Check: whether UE in connectedmode sends an UEAssistanceInformation message to inform the IDC problems); if the terminal does not send the terminal auxiliary information (that is, 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 (that is, it can be expressed as judgment in English) or a verdict (that is, it can be expressed as TP1&TP2Inconclusive and / or TP1&TP2FAIL 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) (that is, the above-mentioned second test result can 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 assistance information for notifying an IDC problem, the terminal in connected mode with "T2" config (non-IDC config) to be configured with "LoggedMeasurementConfiguration" in RRC_CONNECTED;Afterwards, the network / system simulator sends an RRC release message to the terminal (which can be expressed as NW / SS sends RRCRelease to UE in English); the terminal in idle mode with "T2" config (non-IDC config) to activate logging (which can be expressed as UE in idle mode with "T2" config (non-IDC config) to activate logging in English); the terminal in idle state is reconfigured to "T3" config (IDC config, the same as "T1") to trigger logging suspension (which can be expressed as UE in idle mode to be reconfigured with "T3" config (IDC config, the same as "T1") to trigger logging suspension); after 10 seconds, the terminal in idle state is reconfigured to "T4" config (non-IDC config, the same as "T0") to resume logging logging); the network / system simulator sends a terminal information request to the terminal in the RRC connected state (which can be expressed as NW / SS sends "UEInformationRequest" to UE in RRC_CONNECTED); check: when reconfigured to the "T3" configuration, whether the terminal suspends logging for about 10s and sends a terminal information response message tagged with the IDC detection identifier when returning to the connected state (which can be expressed as Check: whether UE suspended logging for about 10swhenreconfigured with "T3"and transmits an UEInformationResponse message Taggedwith inDeviceCoexDetected-r17 when back to connected mode); 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 PASSand / or TP2 PASS) (that is, the above-mentioned first test result may 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 following test conclusions: TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure (which may be expressed in English as TP1&TP2Inconclusive and / or TP1&TP2FAIL) (i.e., the first test result may include at least one of the following test conclusions: TP1 test result inconclusive, TP2 test result inconclusive, TP1 test failure, and TP2 test failure).

[0181] 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).

[0182] 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).

[0183] Table 3

[0184]

[0185] 2401703-I-CP-CMCC-BJ

[0186]

[0187] Table 4

[0188]

[0189]

[0190]

[0191]

[0192]

[0193]

[0194] 2401703-I-CP-CMCC-BJ

[0195]

[0196] Table 5

[0197]

[0198]

[0199]

[0200]

[0201]

[0202]

[0203]

[0204]

[0205] 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). 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 Table 6. Figure 4 As shown, Figure 4 The specific test steps (also called main behaviors) corresponding to the test process shown are shown in Table 7.

[0206] Among them, Table 6 shows the Figure 4The flow shown shows the time instances of cell power level and parameter changes for FR1, 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; 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.

[0207] Accordingly, if Figure 4As shown, when the terminal is tested, under the initial test conditions, the terminal in the connected state and with the "T0" configuration (non-IDC configuration, that is, the second configuration mentioned above) is configured with the IDC auxiliary configuration in the RRC connected state (which can be expressed in English as UE in connected mode with "T0" config (non-IDC config) to be configured with "idc-AssistanceConfig-r16" in RRC_CONNECTED); Check: whether the terminal in the connected state and with the "T0" configuration sends a terminal assistance information (that is, the above-mentioned IDC assistance information) message to notify the IDC problem (which can be expressed in English as Check: whether UE with T0" config in connected mode sends an UEAssistanceInformation message to inform the IDC problems); if the terminal sends terminal auxiliary information for notifying the IDC of problems (i.e., the above-mentioned IDC auxiliary information), the network / system simulator can generate a conclusion (a conclusion can also be called a judgment (can be expressed as judgment in English) or a verdict (can be expressed as Verdict in English) that the TP2 test result is inconclusive (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 (can be expressed as TP2 Inconclusive and / or TP2 FAIL), that is, the third test result / first test result may include a conclusion of TP2 test failure and / or a conclusion of TP2 test result uncertainty (herein, the reason why the first test result may include a conclusion of TP2 test failure and / or a 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 can be confirmed whether the terminal can detect the IDC problem under the first configuration, thereby obtaining the 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, that is, the first configuration) in the RRC connected state to trigger the IDC problem (which can be expressed in English as UE in connected mode to be reconfigured with "T1" config (IDC config) to trigger IDC problem in RRC_CONNECTED);Check: whether the terminal in the connected state sends a terminal assistance information (i.e., the above-mentioned IDC assistance information) message to inform the IDC problems (expressed in English as Check: whether UE in connected mode sends an UEAssistanceInformation message to inform the IDC problems); 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 uncertainty, TP2 test result uncertainty, TP1 test failure, and TP2 test failure (expressed in English as TP1&TP2 Inconclusive and / orTP1&TP2FAIL) (i.e., the above-mentioned second test result / fourth test result can 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 assistance information for notifying an IDC problem, the terminal in connected mode with "T2" config (non-IDC config) to be configured with "LoggedMeasurementConfiguration" in RRC_CONNECTED; thereafter, the network / system simulator sends an RRC release message to the terminal; the terminal in idle mode with "T2" config (non-IDC config) to activate logging; the terminal in idle mode to be reconfigured with "T3" config (IDC config, the same as "T1") to trigger loggingsuspension);After 10 seconds, UE in idle mode to be reconfigured with "T4" config (non-IDC config, the same as "T0") to resume logging. The network / system simulator sends a "UEInformationRequest" to the UE in RRC_CONNECTED. Check: whether the UE suspended logging for about 10 seconds when reconfigured with "T3" and transmits an UEInformationResponse message Tagged with inDeviceCoexDetected-r17 when back to connected. mode); if yes, the network / system simulator may generate a test conclusion that the TP1 test passed and / or the TP2 test passed (which may be expressed as TP1 PASS and / or TP2 PASS in English) (i.e., the first test result / fourth test result may include the test conclusions that the TP1 test passed and / or the TP2 test passed); if no, the network / system simulator may generate at least one of the test conclusions that the TP1 test result is inconclusive, the TP2 test result is inconclusive, the TP1 test fails, and the TP2 test fails (which may be expressed as TP1&TP2Inconclusive and / or TP1&TP2FAIL in English) (i.e., the first test result / fourth test result may include at least one of the test conclusions that the TP1 test result is inconclusive, the TP2 test result is inconclusive, the TP1 test fails, and the TP2 test fails).

[0208] 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).

[0209] Table 6

[0210]

[0211]

[0212]

[0213] Table 7

[0214]

[0215]

[0216]

[0217]

[0218]

[0219]

[0220]

[0221]

[0222]

[0223] 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 Table 6. Figure 5 shown.

[0224] Specifically, if Figure 5As shown, when the terminal is tested, under 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 (which can be expressed in English as UE in connected mode with "T0" config (non-IDC config) to be configured with "idc-AssistanceConfig-r16" in RRC_CONNECTED); Check: whether the terminal in the connected state and with the "T0" configuration sends a terminal assistance information (i.e., the above-mentioned IDC assistance information) message to inform the IDC problems (which can be expressed in English as Check: whether UE with T0" config in connected mode sends an UEAssistanceInformation message to inform the IDC problems). Afterwards, if the terminal does not send the terminal assistance information (i.e., the above-mentioned IDC 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 (which can be expressed in English as UE in connected mode to be reconfigured Check: whether the UE in connected mode sends an UEAssistanceInformation message to inform the IDC problems;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 (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)) 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 FAIL in English) (i.e., the above-mentioned second test result / fourth test result can 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 an IDC problem, a terminal in a connected state and having a "T2" configuration (non-IDC configuration) is reconfigured with a measurement logging configuration in an RRC connected state (which can be expressed as UE in connected mode with "T2" config (non-IDC config) to be configured with "LoggedMeasurementConfiguration" in English). RRC_CONNECTED); after that, the network / system simulator sends an RRC release message to the terminal (which can be expressed as NW / SS sends RRCRelease to UE); the terminal in idle mode with "T2" config (non-IDC config) to activate logging; the terminal in idle mode is reconfigured with "T3" config (IDC config, the same as "T1") to trigger logging suspension; after 10s, the terminal in idle mode is reconfigured with "T4" config (non-IDC config, the same as "T0") to resume logging resume logging);The network / system simulator sends a terminal information request to the UE in RRC_CONNECTED state (NW / SS sends "UEInformationRequest" to UE in RRC_CONNECTED); Check: whether UE suspended logging for about 10s when reconfigured with "T3" and transmits an UEInformationResponse message Tagged with inDeviceCoexDetected-r17 when back to connected mode); if so, the network / system simulator can generate a test conclusion of TP1 PASS and / or TP2 PASS. If the test result is negative, the network / system simulator may generate at least one of the following test conclusions: a TP1 test result is inconclusive, a TP2 test result is inconclusive, a TP1 test fails, and a TP2 test fails (which may be expressed in English as TP1&TP2Inconclusive and / or TP1&TP2FAIL).

[0225] like Figure 5As shown, 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 terminal assistance information for notifying an 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 an IDC problem (which can be expressed in English as UE in connected mode to be reconfigured with "T1" config (IDC config) to trigger IDC problem in RRC_CONNECTED); Check: whether the terminal in the connected state sends a terminal assistance information (i.e., the above-mentioned IDC assistance information) message to inform the IDC problem (which can be expressed in English as Check: whether UE in connected mode sends an UEAssistanceInformationmessage to inform the IDC problems); if the terminal does not send terminal auxiliary information (i.e., the above-mentioned IDC auxiliary information), the network / system simulator may generate at least one of the test conclusions of TP1 test result uncertainty, TP2 test result uncertainty, TP1 test failure, and TP2 test failure (which can be expressed in English as TP1&TP2 Inconclusiveand / or TP1&TP2FAIL) (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 IDC problems, the terminal in the connected state and with the "T1" configuration (IDC configuration) is reconfigured with the measurement logging configuration in the RRC connected state (which can be expressed in English as UE in connected modewith"T1"config(IDC config)to be configured with"LoggedMeasurementConfiguration"in RRC_CONNECTED); thereafter, the network / system simulator sends an RRC release message to the terminal (which can be expressed in English as NW / SS sends RRCRelease to UE); after that, the terminal is in idle mode with "T1" config (IDC config) and wait at least 10s (English can be expressed as UE in idle mode with "T1" config (IDC config) and wait at least 10s);Afterwards, the network / system simulator sends a UEInformationRequest to the UE in RRC_CONNECTED in the RRC connected state. Check: whether the UE suspended logging for about 10s when reconfigured with "T3" and transmits an UEInformationResponse message Tagged with inDeviceCoexDetected-r17 when back to connected mode); if yes, the network / system simulator may generate a test conclusion that the TP1 test passed (which may be expressed as TP1 PASS in English) (i.e., the first test result / third test result may include the test conclusion that the TP1 test passed); if no, the network / system simulator may generate at least one of the test conclusions that the TP1 test result is inconclusive, the TP2 test result is inconclusive, the TP1 test fails, and the TP2 test fails (which may be expressed as TP1&TP2 Inconclusive and / or TP1&TP2 FAIL in English) (i.e., the first test result / third test result may include at least one of the test conclusions that the TP1 test result is inconclusive, the TP2 test result is inconclusive, the TP1 test fails, and the TP2 test fails).

[0226] 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.

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

[0228] 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;

[0229] 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.

[0230] 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.

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

[0232] 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.

[0233] 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 referred to. Figures 2 to 5 Any of the processes shown and the steps shown in Table 2 / Table 4 / Table 5 / Table 7 are understood, and the embodiments of the present application will not be repeated here.

[0234] The present application also provides a testing method for testing equipment, such as Figure 6 As shown, the method includes:

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

[0236] 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.

[0237] 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.

[0238] 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.

[0239] In actual application, it can be seen from the above steps 601 and 602 that Figure 6 The test method shown is a technical solution of first performing an IDC mechanism test and then checking 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 uncertain (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 uncertain (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.

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

[0241] 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;

[0242] or,

[0243] 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.

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

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

[0246] 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;

[0247] 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.

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

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

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

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

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

[0253] 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.

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

[0255] performing the fourth configuration on the terminal;

[0256] 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

[0257] 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.

[0258] 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.

[0259] In practical application, Figure 6 The technical solution for post-checking the IDC problem shown in FIG5 is as follows: assuming that the test environment configured by the test equipment is 2.4 GHz WiFi and 2300-2400 MHz frequency band (i.e., Band n40) (i.e., Band n40 is interfered with by 2.4 GHz 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.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, i.e., the test equipment) on the terminal can be as shown in Table 8, and the test process performed by the network / system simulator on the terminal can be as shown in FIG5. Figure 7 As shown, Figure 7 The specific test steps (also referred to as main behaviors) corresponding to the test flow shown are shown in Table 9.

[0260] Among them, Table 8 shows the Figure 7 Table 9 shows the time instances of cell power level and parameter changes for FR1 in the process, 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," and "T3" are the configurations corresponding to the subsequent main behavior descriptions; and "T2" and "T0" are essentially the same test conditions, and "T3" and "T1" are essentially the same test conditions.

[0261] Accordingly, if Figure 7As shown, when the terminal is tested, the terminal in idle mode and with "T0" configuration (non-IDC configuration) activates logging (which can be expressed in English as UE in idle mode with "T0" config (non-IDC config) to activate logging); the terminal in idle state is reconfigured to "T1" configuration (IDC configuration) to trigger logging suspension (which can be expressed in English as UE in idle mode to be reconfigured with "T1" config (IDC config) to trigger logging suspension); after 10s, the terminal in idle state is reconfigured to "T2" configuration (non-IDC configuration, and the same as "T0") to resume logging (which can be expressed in English as After 10s, UE in idle mode to be reconfigured with "T2" config (non-IDC config, the same as "T0") to resume logging); the network / system simulator sends a terminal information request to the terminal in the RRC connected state (which can be expressed in English as NW / SS sends "UEInformationRequest" to UE in RRC_CONNECTED); Check: whether UE suspended logging for about 10s when reconfigured with "T3" and transmits an UEInformationResponse message Tagged with inDeviceCoexDetected-r17 when back to connected mode; If so, the network / system simulator can generate a test conclusion (a conclusion can also be called a judgment or a verdict) of TP1 test passed and / or TP2 test passed (TP1 PASS and / or TP2 PASS in English);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 (which can be expressed in English as UE in connected mode to bereconfigured with "idc-AssistanceConfig-r16"and"T3"(IDC config, the same as"T1")in RRC_CONNECTED); Check: whether the terminal sends a terminal assistance information (that is, the above-mentioned IDC assistance information) message to inform the IDC problems (which can be expressed in English as Check: whether UE sends anUEAssistanceInformation message to inform the IDC problems); if the terminal does not send terminal assistance information (that is, the above-mentioned IDC assistance 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 If the terminal sends terminal auxiliary information for notifying the IDC of a problem, the network / system simulator may generate at least one of the following test conclusions: an inconclusive TP1 test result (also understood as no test result, expressed as "inconclusive"), an inconclusive TP2 test result, a TP1 test failure, and a TP2 test failure (expressed as "TP1&TP2 Inconclusive and / or TP1&TP2FAIL" in English). Therefore, the sixth test result may include at least one of the following test conclusions: an inconclusive TP1 test result, an inconclusive TP2 test result, a TP1 test failure, and a TP2 test failure.

[0262] In addition, in Table 9, 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 8); 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 (for example, F).

[0263] Table 8

[0264]

[0265]

[0266] Table 9

[0267]

[0268]

[0269]

[0270]

[0271]

[0272]

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] 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.

[0278] It should be noted that in various embodiments of the present application, the test flow diagram (ie Figures 2 to 5 ,as well as Figure 7 ) represents optionality, that is, the corresponding branch (which can also be understood as a situation) may exist or not; in other words, the dotted line in the above test flow diagram refers to a branch situation that may or may not exist.

[0279] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a testing device, which is set on the testing equipment, such as Figure 8 As shown, the device includes:

[0280] 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;

[0281] The second testing unit 802 is configured to, when the terminal is capable of detecting an IDC problem under the first configuration, execute an 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 an 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.

[0282] In one embodiment, the first testing unit 801 is specifically configured to:

[0283] 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;

[0284] or,

[0285] 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.

[0286] 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;

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

[0288] 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

[0289] 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,

[0290] 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;

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

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

[0293] performing the second configuration on the terminal;

[0294] 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

[0295] 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.

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

[0297] 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;

[0298] 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;

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

[0300] 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

[0301] 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.

[0302] 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.

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

[0304] 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;

[0305] 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.

[0306] 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.

[0307] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a testing device, which is set on the testing equipment, such as Figure 9 As shown, the device includes:

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

[0309] The fourth test unit 902 is used 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.

[0310] In one embodiment, the fourth testing unit 902 is specifically configured to:

[0311] 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;

[0312] or,

[0313] 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.

[0314] In one embodiment, the fourth testing unit 902 is specifically configured to:

[0315] 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;

[0316] 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.

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

[0318] performing the fourth configuration on the terminal;

[0319] 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

[0320] 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.

[0321] 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.

[0322] 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.

[0323] 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 also provides a testing device, such as Figure 10 As shown, the test device 1000 includes:

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

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

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

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

[0328] 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;

[0329] 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

[0330] 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.

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

[0332] 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;

[0333] or,

[0334] 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.

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

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

[0337] 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

[0338] 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,

[0339] 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;

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

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

[0342] performing the second configuration on the terminal;

[0343] 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

[0344] 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.

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

[0346] 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;

[0347] 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

[0348] 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.

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

[0350] 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.

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

[0352] 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;

[0353] 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.

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

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

[0356] 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;

[0357] 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.

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

[0359] 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;

[0360] or,

[0361] 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.

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

[0363] 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;

[0364] 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.

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

[0366] performing the fourth configuration on the terminal;

[0367] 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

[0368] 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.

[0369] 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.

[0370] Of course, in actual application, the various components in the test device 1000 are coupled together through the bus system 1004. It can be understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 10 Various buses are labeled as bus system 1004.

[0371] 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.

[0372] 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 in the processor 1002 or instructions in software form. The processor 1002 can 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. The general-purpose processor can 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.

[0373] 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.

[0374] 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.

[0375] 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.

[0376] 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.

[0377] 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.

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

[0379] 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, characterized in that: include: 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, characterized in that 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.

3. The method according to claim 1, characterized in that 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, characterized in that 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, characterized in that 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 to have a maximum distance ； The transmission power of the transmission channel of the first channel and the second channel of the terminal is the lowest; The first channel and / or the second channel of the terminal has no information transmission ； The first channel and / or the second channel of the terminal is closed.

6. The method according to claim 4, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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 ； The first channel and / or the second channel of the terminal has no information transmission ； 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, characterized in that: include: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: include: 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 testing unit is configured to, when the terminal is capable of detecting an IDC problem under the first configuration, execute an 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 an 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.

20. A testing device, characterized in that: include: The third testing unit is used to perform an IDC mechanism testing process on the terminal; The fourth test unit is used 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.

21. A testing device, characterized in that: include: 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, characterized in that: include: a processor and a memory for storing a computer program capable of being executed on the processor, Wherein, when the processor is used 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, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented, or the steps of the method according to any one of claims 12 to 18 are implemented.

24. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented, or the steps of the method according to any one of claims 12 to 18 are implemented.

Images