In-device interference management method and device

Abstract

Methods, systems, apparatus, including a method of wireless communication, the method including receiving, by a network device from a wireless device, a report indicating availability of radio frequency (RF) resources configured for communication with the wireless device, and transmitting, by the network device, a reconfiguration command to the wireless device in accordance with the report.

Description

Technical Field

[0001] This document relates to systems, devices, and techniques for wireless communications. Background Art

[0002] Efforts are currently underway to define the next generation of wireless communication networks that will provide different technologies for greater deployment flexibility, support for a wide range of devices and services, and efficient bandwidth utilization. Summary of the invention

[0003] This document describes, among other things, techniques for managing in-device interference conflicts.

[0004] In one example aspect, a wireless communication method is disclosed. The method includes receiving, by a network device, a report from a wireless device indicating availability of radio frequency (RF) resources configured for communication with the wireless device; and transmitting, by the network device, a reconfiguration command to the wireless device based on the report.

[0005] In another example aspect, a wireless communication method is disclosed. The method includes generating, by a wireless device, a report indicating availability of radio frequency (RF) resources configured to be used by the wireless device to communicate with a network device; and transmitting, by the wireless device, the report to the network device.

[0006] In yet another example aspect, a wireless communication apparatus is disclosed that includes a processor configured to implement the methods described herein.

[0007] In another example aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

[0008] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example of a communication device exhibiting in-device coexistence (IDC) radio frequency (RF) interference is shown.

[0010] Figure 2 An example of a spectrum affected by IDC interference is shown.

[0011] Figure 3 An example signal exchange diagram for performing bandwidth part (BWP) reporting is shown.

[0012] Figure 4 An example of a spectrum not affected by IDC interference is shown.

[0013] Figure 5An example of the impact of IDC interference between two different protocols is shown.

[0014] Figure 6 An example of an IDC reporting process is shown.

[0015] Figure 7 is a flow chart of an example wireless communication method.

[0016] Figure 8 is a flow chart of an example wireless communication method.

[0017] Fig. 9 is a block diagram of an example of a wireless communication device.

[0018] Fig.10 An example wireless communication network is shown.

[0019] Fig.11 An example frequency division multiplexing (FDM) scenario is shown.

[0020] Fig.12 An example frequency division multiplexing (FDM) scenario is shown. DETAILED DESCRIPTION

[0021] Section headings are used in this document only to improve readability and do not limit the scope of the embodiments and techniques disclosed in each section to only that section. In addition, for ease of understanding, some embodiments are described with reference to the Third Generation Partnership Project (3GPP) New Radio (NR) standard ("5G"), and the described techniques may be implemented in different wireless systems that implement protocols other than the 5G protocol.

[0022] The current IDC (In-Device Coexistence) solutions in NR are carrier-based and therefore cannot adequately indicate the affected frequencies via the NR FDM (Frequency Division Multiplexing) solutions.

[0023] Since multiple radio transceivers within the same wireless device (sometimes referred to as user equipment UE) are in close proximity, Figure 1 As shown, the transmit power of one transmitter may be much higher than the receive power level of another receiver.

[0024] like Figure 1As shown in the embodiments of FIG, the UE may include multiple transmit / receive chains, each of which may have one or more corresponding antennas. Here, three transmit / receive chains are shown - the leftmost is an LTE (Long Term Evolution) transmit / receive chain, which includes an antenna 1 and an LTE baseband processor coupled to an LTE RF portion (e.g., an RF integrated circuit and other components). The middle transmit / receive chain includes a global positioning system (GPS) portion with a corresponding antenna 2 and a GPS RF and baseband processing module (typically an integrated circuit or a programmable processor). The rightmost transmit / receive chain includes a Bluetooth and / or Wi-Fi circuit (RF and baseband) with a corresponding antenna 3. During operation, interference may be of two types with respect to the 3GPP circuit system (LTE or possibly NR). Incoming interference or intrusive interference may affect LTE transmission / reception operations and may be generated by GPS or Bluetooth / Wi-Fi circuit systems. Another type of interference is interference caused by the LTE circuit system and affects GPS and Bluetooth or Wi-Fi operations.

[0025] To address these issues, IDC-related mechanisms were introduced in LTE. According to the LTE protocol, when the network instructs to report IDC auxiliary information, both the serving frequency and the non-serving frequency will trigger IDC. In addition, the frequency that is currently experiencing IDC problems and potential IDC problems on secondary frequencies and non-serving frequencies (where measurement objects are configured) should be reported. Then, with the development of 5G, similar IDC schemes were introduced for NR and dual connectivity (EN-DC) situations.

[0026] In addition, in wireless communication, the concept of bandwidth part (BWP) is introduced into the wireless communication system. BWP can represent a group of continuous physical resource blocks (PRBs) on a given carrier. For each cell, the network can configure multiple BWPs, but only one BWP can be activated. At the same time, the UE will report its capabilities according to the requirements of the network. For DC (dual connection) / CA (carrier aggregation) scenarios, the network will configure the BWP of each band entry according to the UE BC (band combination) capability. The network can switch BWP through radio resource control (RRC) signaling, downlink control information DCI, BWP inactivity timer or random access (RA) process. Generally, RRC signaling has the longest delay among all these methods. Through all these methods, each BWP is activated or deactivated separately through its corresponding control information. For example, in DCI, there is a bandwidth part indicator to indicate which BWP of the current serving cell will be activated / deactivated. An example is shown in Table 1.

[0027] Table 1 Values ​​of the BWP indicator field

[0028]

[0029] In 3GPP Rel 18, enhancements to the IDC frequency division multiplexing (FDM) solution were agreed to allow for a finer-grained indication of the affected frequencies (e.g., bandwidth part BWP or physical resource block PRB level granularity).

[0030] In traditional schemes (eg, LTE), for IDC reporting, the network would indicate a list of "center frequencies".

[0031] For NR, the network shall indicate candidateServingFreqList with ARFCN (Absolute Radio Frequency Channel Number) value. An example is shown in Table 2.

[0032] Table 2

[0033]

[0034] For E-UTRA (Evolved Universal Mobile Telecommunications System Terrestrial Radio Access), the UE shall consider the frequency of the configured measurement object.

[0035] The UE will then report the affected frequencies to the network with 2 different IDC interference types:

[0036] - IDC interference from or to a 3GPP single carrier (along with interference direction);

[0037] - IDC interference caused by 3GPP uplink (UL) CA or DC to Industrial Scientific Medical or Global Navigation Satellite System (ISM / GNSS) frequencies, together with the victim type.

[0038] On the network side, the network will determine how to move the 3GPP signal away from the ISM / GNSS band based on the center frequency reported by the UE together with the interference direction or victim type. The network can perform inter-frequency switching, remove SCells from the serving cell set or deactivate the affected SCells, or in the case of uplink CA operation, allocate uplink PRB resources on one or more component carriers CC whose intermodulation distortion and harmonics are not within the frequency range of the victim system receiver.

[0039] This document provides, among other things, solutions for IDC FDM enhancement methods that provide greater flexibility and granular control than existing solutions.Throughout this document, some example embodiments, technical problems raised by these embodiments, and technical solutions to address and overcome these problems are shown.

[0040] Example Introduction

[0041] For the scenario where the BWP is configured only for the serving cell, different enhancement methods may be used for the serving frequency (on which the serving cell exists) and the non-serving frequency.

[0042] For example, the UE may report BWP-level IDC for certain frequencies (eg, serving frequencies) and / or other frequencies (eg, non-serving frequencies) or other frequencies without enhanced PRB-level IDC.

[0043] In some embodiments, the UE makes the decision based on the network configuration.Alternatively or additionally, the UE may decide how to report the IDC.

[0044] For UE determination, the UE may determine based on whether there is a BWP that is not affected by IDC; if so, the UE may report the BWP level IDC for that frequency.

[0045] For embodiments using network configuration, the network may request the UE to report BWP level IDC for certain frequencies (eg, serving frequencies) and / or PRB level reports for other frequencies (eg, non-serving frequencies).

[0046] Problem 1: IDC interference solution based on BWP

[0047] Problem description: In the traditional solution, the UE can only indicate the carrier frequency to the network, and the network will use this auxiliary information to determine whether switching is required and the target frequency. When considering BWP, there is a situation where only part of the BWP will be affected by IDC interference. If the network obtains BWP-based or PRB-based information, the network can also use BWP switching or reconfiguration to resolve IDC interference.

[0048] Example solution:

[0049] - In some embodiments, the UE reports to the network the BWPs that are not affected by IDC interference or the BWP combinations that are not affected by IDC interference. Alternatively, this information is implicitly indicated by reporting the affected BWF and BWP combinations.

[0050] In some embodiments, the UE may also report the unaffected PRB range or unaffected PRB range information to the network.

[0051] In some embodiments, the network may configure whether to report affected BWP / PRBs or unaffected BWP / PRBs.

[0052] - In some embodiments, the network may perform BWP or BWP combination switching based on the information reported by the UE.

[0053] Example 1: Permitted BWP Report

[0054] like Figure 2 As shown, it is assumed that only dedicated BWP1 is affected by IDC interference, and BWP1 is activated and the UE detects IDC interference.

[0055] The UE may indicate BWP2 and BWP3 (which represent allowed BWPs since there is no IDC) to the network, and then the network may switch the UE from BWP1 to BWP2 or BWP3.

[0056] Example 2: Allowable BWP Reporting – General Process

[0057] Figure 3 An example process for reporting allowed BWP (or BWP not affected by IDC) is shown. The process may proceed as follows.

[0058] In step 1, the UE may report UE assistance information to a network device (eg, a base station). The UE assistance information may include IDC information at a BWP level.

[0059] In step 2, in response to the UE assistance information, the network may send a reconfiguration message to the UE. In the reconfiguration message, the network may specify that the BWP is to be switched or modified.

[0060] In step 3, based on the received reconfiguration message, the UE may perform the handover or reconfiguration indicated by the network. After completing the action, the UE may report back a reconfiguration complete message indicating that the reconfiguration has been completed. In some embodiments, Figure 3 The processes shown in may be implemented under network control, such as when initiated by the network.

[0061] Example 3: Allowed BWP reporting signal

[0062] Table 3 shows an example of the message content for reporting the allowed BWP from the UE to the network.

[0063] Table 3

[0064]

[0065] Example 4: Reporting signal for allowed BWP combinations (or BWP combinations not affected by IDC)

[0066] Table 4 shows an example of the message contents for reporting allowed BWP combinations from the UE to the network.

[0067] Table 4

[0068]

[0069]

[0070] Example 5: UE indicates PRB range not affected by IDC interference

[0071] Figure 4 An example of reporting the spectrum of the PRB range that is not affected by IDC interference is shown. Table 5 shows an example syntax of the allowed PRB list reported from the UE to the network.

[0072] Table 5

[0073]

[0074]

[0075] In some embodiments, when the network obtains one or more allowed PRB ranges, the network may decide to configure the UE in one or more allowed PRB ranges. In some embodiments, the UE may also indicate allowed PRB range combinations for UL CA / DC cases.

[0076] Question 2: IDC Interference Level Report

[0077] Problem description: For BWP / PRB level reporting, the UE can report the dedicated BWP / PRB affected by the IDC problem. According to the simulation results in Appendix A.2 of 36.816 (e.g., Figure 5 ), the IDC interference sensitivity is different for different frequency ranges. For example, Figure 5 In Figure 1, a two-dimensional grid of interfering frequencies (horizontal axis) and affected victim frequencies (vertical axis) is shown. The shading of the corresponding grid cells reflects the relative value of the interference. The report can include multiple levels of interference sensitivity. Figure 5 In the illustrated embodiment, three levels are indicated: a first level of desensitization greater than 50 dB, a second level of desensitization between 50 dB and 10 dB, and a third level of desensitization less than 10 dB. This particular case may correspond to interference from a wireless local area network (WLAN) network (e.g., Wi-Fi) to an LTE network.

[0078] From the network side, if the UE can indicate the IDC interference sensitivity level for each BWP / PRB range, the network can perform more precise resource control.

[0079] Example Solution

[0080] Solution 1: UE indicates the IDC interference level of the affected BWP / PRB range

[0081] - The network may configure thresholds for different sensitivity levels for UE reporting - for example, the number of levels and upper and / or lower thresholds for each level.

[0082] -When the IDC interference level information is different from the previously reported one, the UE triggers IDC interference assistance information reporting.

[0083] -The IDC interference level can then be expressed in terms of desensitization.

[0084] Solution 2: UE indicates the BWP / PRB range that is not affected by IDC interference

[0085] - The network configures the UE only within the allowed BWP / PRBs.

[0086] In the following examples, PRB range is used as an example, however, similar techniques can also be used for BWP level reporting method, where PRB range is replaced by BWP or BWP combination.

[0087] Example 6: UE reports affected PRB range with interference level information of affected frequencies Table 6 shows a configuration example of an interference level report message that may be used by an embodiment.

[0088] Table 6

[0089] PRB range of frequency Interference level PRB Range 1 high PRB Range 2 middle PRB Range 3 Low

[0090] The signaling syntax is shown in Table 7 below:

[0091] Table 7

[0092]

[0093]

[0094] Example 7: UE reports affected PRB range combinations with interference level information

[0095] For the case where the PRB range combination is reported for UL CA or DC case, the UE may also indicate the interference level for each PRB range combination. In Table 8, f1 and f2 represent the carrier frequencies used in CA or DC case.

[0096] Table 8

[0097]

[0098] The signaling may be as shown in Table 9 below:

[0099] Table 9

[0100]

[0101]

[0102] Example 8: The network configures one or more thresholds for interference level reporting

[0103] In this example, the network indicates a threshold for reconfiguration messages within "other configurations", which may require the UE to report IDC interference stronger than the threshold, or may require the UE to report IDC interference weaker than the threshold. Table 10 shows an example of a configuration provided by the network.

[0104] Table 10

[0105] PRB range of frequency Interference level PRB Range 1 Level 1: Stronger than Threshold PRB Range 2 Level 2: Lower than threshold

[0106] The network may also indicate more than one threshold, for example, threshold 1 and threshold 2. Table 11 shows an example of the content of such a message.

[0107] Table 11

[0108]

[0109]

[0110] Example 8: UE triggers IDC interference level report

[0111] Figure 6 An example of a process for reporting an IDC interference level report is shown. Figure 6 At step 1, the network may transmit a reconfiguration message and the UE may receive the reconfiguration message. The message includes an IDC interference level reporting indication, such as described in this document.

[0112] At step 2, the UE may provide a report of the IDC interference level. The report may be provided in a UE assistance information message. In some embodiments, optionally, upon noticing that the IDC interference level has changed, the UE may subsequently transmit another UE assistance information message including updated IDC interference level information. This optional step may be reported multiple times in response to changes in the IDC interference level.

[0113] In some embodiments, the UE may trigger an IDC interference level report when the network indicates reporting of the IDC interference level, or when the network indicates a threshold different from a previous threshold, or when the IDC interference level information on the UE side is updated.

[0114] In some embodiments, the interference level information may also include corresponding PRBs.

[0115] As mentioned above, for the BWP based scheme, if the UE reports the affected BWP for IDC interference (or the affected BWP combination for CA / DC case), the interference level may also be reported like the PRB based scheme described above.

[0116] Question 3: UE capability reporting and others

[0117] (1) For BWP-based or PRB-based reporting, the UE may indicate relevant capabilities to the network, including indicating the UE's capability to support BWP-based IDC reporting, indicating the capability to support PRB-based reporting, or indicating the UE's capability to support IDC interference level reporting.

[0118] (2) For BWP / PRB level IDC reporting, the UE may report the BWP combination index or the PRB combination index.

[0119] For reports based on BWP combination index, the BWP combination index can be set according to predefined rules. While PRB combination index can be set in 2 steps:

[0120] -Step 1: Give the index of each PRB range

[0121] - Step 2: Give an index to each PRB range combination according to a predefined rule.

[0122] Discuss the enhancements of FDM scenarios

[0123] This section discusses examples of enhancements provided to serving and non-serving frequencies as described previously in this document.

[0124] FDM enhancements for NR service frequencies

[0125] For BWP reporting, the UE can report which BWPs are (or are not) affected by IDC interference. The network can then further determine how to resolve the IDC issue, for example, handing the UE over to another BWP or handing the UE over to another cell, etc. According to traditional rules, ongoing and expected IDC interference should be reported, so for BWP-based reporting, the configured BWP is taken into account.

[0126] For PRB reporting, the UE can report which PRBs are (or are not) affected by IDC interference, and the network can then determine the next action based on this information.

[0127] PRB-based reporting can provide more IDC interference information than the BWP-based scheme, but at the cost of slightly higher signaling overhead.

[0128] First, the single carrier scenario is disclosed, followed by the CA / DC scenario. For the single carrier scenario, it can be further divided into two scenarios:

[0129] Scenario 1: Only some configured BWPs are affected.

[0130] Scenario 2: All configured BWPs are affected.

[0131] Previously about Figure 2 Scene 1 is disclosed.

[0132] Through BWP reporting, the UE can indicate to the network the affected BWP1 (or unaffected BWP2), and then the network can switch the UE from BWP1 to BWP2.

[0133] With PRB reporting, the network will need to determine which BWP is still available based on the PRB information, which will also increase the complexity of network implementation.

[0134] For scenario 2, Fig.11 As an example, here both dedicated BWP1 and BWP2 are affected by IDC interference.

[0135] With BWP reporting the UE will indicate 2 dedicated BWPs and the network will then have to handover the UE to another cell using the FDM solution.

[0136] With PRB reporting, the UE will report the dedicated affected PRBs, and then the network can resolve the IDC issue through BWP reconfiguration or switching. However, for the BWP reconfiguration method, the bandwidth may also be affected.

[0137] Therefore, for scenario 2, with dedicated PRB reporting, the network may not need to handover the UE to another cell by reconfiguring the BWP.

[0138] The above is about the single CC case. For CA / DC, it will be more complicated. Here we take CA as an example. Assume there are 2 CCs and 2 BWPs for each CC, as shown below:

[0139] 1. Cell 1: UL BWP 1 + Cell 2: UL BWP 1

[0140] 2. Cell 1: UL BWP 1 + Cell 2: UL BWP2 ---- IDC interference to non-3gpp RAT

[0141] 3. Cell 1: UL BWP2 + Cell 2: UL BWP 1 --- IDC interference to non-3gpp RAT

[0142] 4. Cell 1: UL BWP2 + Cell 2: UL BWP2

[0143] Through BWP reporting, the UE can indicate the affected BWP combinations (or unaffected BWP combinations) to the network, and then the network can switch the UE to an available BWP combination.

[0144] Through PRB reporting, different PRB range combinations may need to be indicated, and then at the network side, it will need to be determined which BWP combinations are not affected by the reported PRB-based IDC interference information.

[0145] For the CA / DC case, reporting the PRB range combinations from the UE side is more complicated. From the network side, it is also complicated to deduce the available BWP combinations based on the reported PRB information. Another difference compared to the BWP and PRB based scheme is that the UE may need to report BWP level IDC interference when the BWP configuration changes. However, this case can be considered as an extreme case because once the network reconfigures the BWP, the previously reported IDC information should be considered to avoid ongoing or potential IDC interference.

[0146] Therefore, in some embodiments, for IDC interference affecting NR serving frequencies, a BWP-based scheme may be used as a baseline.

[0147] As mentioned before, if BWP level IDC reporting is supported, the network can perform BWP switching / modification to resolve IDC interference. The general process can be as described in Figure 3 discussed.

[0148] For BWP level IDC reporting, there may be two possible implementation scenarios:

[0149] Option 1: BWP of the configuration affected by IDC interference.

[0150] Option 2: Configured BWP that is not affected by IDC interference.

[0151] For option 1, the network can determine the available BWP based on the reported information, while for option 2, the network only needs to select the available BWP from the reporting UEs.

[0152] FDM enhancement for other frequencies

[0153] Fig.12 A scenario related to this scenario is depicted. As mentioned earlier, in addition to the NR serving frequency, the UE can also report Eutra frequencies and NR non-serving frequencies. For these frequencies, no BWP is configured. Therefore, the FDM solution can be enhanced from the PRB aspect. For example, the affected PRBs (or unaffected PRBs) are reported. For the NR non-serving frequency, if it is affected by IDC interference, it will be reported with carrier information in the traditional signaling, and the network will avoid switching the UE to this carrier.

[0154] If the PRB level information of a non-serving frequency is reported, the network may select a cell on the non-serving frequency but avoid allocating PRBs affected by IDC interference.

[0155] However, it is for non-serving frequencies, so it may not even be used on the network side, especially for cases where the network can resolve existing IDC interference through BWP switching situations.

[0156] Here, there may be two different types of IDC interference:

[0157] IDC interference from or to a 3GPP single carrier (along with interference direction);

[0158] IDC interference caused by 3GPP UL CA or DC to ISM / GNSS (with victim type).

[0159] For type 1, if PRB level is supported, the UE will report the affected PRB range of the corresponding frequency. But for type 2, it means that the UE reports the PRB range combination, which will be more complicated.

[0160] Some preferred embodiments may combine the following solutions.

[0161] For example, a network node (eg, a base station) may implement the following solution.

[0162] 1. A wireless communication method (e.g., Figure 7 The method 700 shown in the figure includes: receiving (702) a report indicating the availability of radio frequency (RF) resources configured for communication with the wireless device by a network device from a wireless device; and transmitting (704) a reconfiguration command to the wireless device by the network device based on the report. Various examples of reports and reconfiguration commands are described throughout this document, including, for example, Tables 1 to 11.

[0163] 2. The method of solution 1, wherein the reporting is based on estimated in-device RF interference at the wireless device.

[0164] 3. A method according to any one of solutions 1-2, wherein the report provides the availability of RF resources based on frequency domain granularity.

[0165] 4. The method according to solution 4, wherein the frequency domain granularity is at a bandwidth part level or a bandwidth part combination level.

[0166] 5. The method according to solution 5, wherein the frequency domain granularity is at the physical resource block (PRB) level.

[0167] 6. The method according to solution 4-5, wherein BWP level granularity is used for serving cells or PRB level granularity is used for non-serving frequencies.

[0168] 7. The method of any one of solutions 1-6, wherein the report provides a list of available RF resources.

[0169] 8. The method of any one of solutions 1-7, wherein the report provides a list of unavailable RF resources.

[0170] 9. A method according to any one of solutions 1-8, wherein the reconfiguration command causes the wireless device to switch to another bandwidth part or another bandwidth part combination according to the reconfiguration command.

[0171] 10. The method of solution 9, wherein the reconfiguration command is included in a medium access control element (MAC CE).

[0172] 11. The method of solution 9, wherein the reconfiguration command is included in a radio resource control (RRC) message.

[0173] 12. A method according to any one of solutions 1-11, wherein the report is generated in response to a request from a network device.

[0174] 13. A method according to any one of solutions 1-12, wherein the report is formatted according to a report configuration transmitted by the network device.

[0175] 14. The method of solution 13, wherein the report is configured to provide threshold information for decisions regarding RF interference within the device.

[0176] 15. The method of solution 13, wherein the reporting configuration specifies interference levels to be reported in the report.

[0177] For example, a wireless device (eg, UE) may implement the following solution.

[0178] 16. A wireless communication method (e.g., Figure 8 The method 800 shown in the figure includes: generating (802) a report by a wireless device indicating the availability of radio frequency (RF) resources configured to be used by the wireless device to communicate with a network device; and transmitting (804) the report by the wireless device to the network device. Various examples of reports and reconfiguration commands are described throughout this document, including, for example, Tables 1 to 11.

[0179] 17. The method of solution 16, wherein the report is generated by estimating in-device RF interference of the wireless device.

[0180] 18. A method according to any of solutions 16-17, wherein the report includes bandwidth part (BWP) or physical resource block (PRB) interference level information.

[0181] 19. A method according to any of solutions 16-18, wherein the report is generated in response to a request from a network device.

[0182] 20. A method according to any of solutions 16-19, wherein the report is formatted according to a report configuration received from the network device.

[0183] 21. The method of solution 20, wherein the report is configured to provide threshold information for decisions regarding RF interference within the device.

[0184] 22. The method of solution 20, wherein the reporting configuration specifies interference levels to be reported in the report.

[0185] 23. The method of solution 18, wherein BWP level granularity is used for serving cells or PRB level granularity is used for non-serving frequencies.

[0186] 24. The method according to any of the above solutions, wherein the report provides a list of available RF resources.

[0187] 25. The method according to any of the above solutions, wherein the report provides a list of unavailable RF resources.

[0188] 26. A method according to any one of solutions 1-10, wherein the wireless device receives a reconfiguration command in response to the report, wherein the reconfiguration command causes the wireless device to switch to another bandwidth part or another bandwidth part combination according to the reconfiguration command.

[0189] 27. The method of solution 23, wherein the reconfiguration command is received as a medium access control element (MAC CE).

[0190] 28. The method of solution 23, wherein the reconfiguration command is received as a radio resource control (RRC) message.

[0191] 29. A wireless communication device, comprising a processor, wherein the processor is configured to implement the method according to any one of solutions 1-28.

[0192] 30. A computer-readable medium having stored thereon codes which, when executed, cause a processor to implement the method according to any one of solutions 1-28.

[0193] Fig. 9 is a block diagram of an example implementation of a wireless communication device 1200. Method 700 or 800 may be implemented by device 1200. In some embodiments, for example, when implementing method 700, device 1200 may be a base station or network device of a wireless network. In some embodiments, for example, when implementing method 800, device 1200 may be a user equipment. Device 1200 includes one or more processors, for example, processor electronics 1210, transceiver circuit system 1215, and one or more antennas 1220 for transmitting and receiving wireless signals. Device 1200 may include a memory 1205, which may be used to store data and instructions used by processor electronics 1210. Device 1200 may also include an additional network interface to additional equipment of one or more core networks or network operators. The additional network interface (not explicitly shown in the figure) may be wired (e.g., optical fiber or Ethernet) or wireless.

[0194] Fig.10 An example of a wireless communication system 1300 is depicted in which the various techniques described herein may be implemented. System 1300 includes a base station 1302 that may have a communication connection with a core network (1312) and a wireless communication medium 1304 to communicate with one or more user devices 1306. User device 1306 may be a smartphone, a tablet, a machine-to-machine communication device, an Internet of Things (IoT) device, or the like.

[0195] It should be understood that this document provides various techniques that can be implemented by embodiments of a UE or network, where IDC measurements and reporting can be controlled at the PRB or BWP level. In an advantageous aspect, the UE can provide interference level information to the network at the BWP, BWP combination or PRB level, allowing the network to make decisions about switching or reconfiguring the UE, thereby mitigating the adverse effects of IDC.

[0196] It should also be understood that this document provides several enhancements to existing IDC schemes. For example, in some embodiments, for BWP reporting, all configured BWPs (not just active BWPs) will be considered and used for IDC reporting. For PRB reporting, the UE will report which PRBs are (or are not) affected by IDC interference, and the network will then determine the next action based on this information. PRB-based reporting can provide more IDC interference information than BWP-based schemes, but at the cost of slightly higher signaling overhead.

[0197] The disclosed embodiments and other embodiments, modules and functional operations described in this document may be implemented in digital electronic circuit systems, or in computer software, firmware or hardware, including the structures disclosed in this document and their structural equivalents, or in a combination of one or more of them. The disclosed embodiments and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium, for execution by a data processing device or for controlling the operation of the data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition that affects a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" encompasses all devices, equipment and machines for processing data, such as a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program under consideration, such as code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagation signal is an artificially generated signal, such as a machine-generated electrical signal, an optical signal, or an electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0198] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program under consideration, or in multiple collaborative files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed to be executed on one computer or multiple computers located at one site or distributed across multiple sites and interconnected by a communications network.

[0199] The processes and logic flows described in this document may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by special purpose logic circuitry, and apparatus may also be implemented as special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0200] For example, processors suitable for executing computer programs include general-purpose microprocessors and special-purpose microprocessors, as well as any one or more processors of any kind of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Typically, a computer will also include or be operably coupled to one or more large-capacity storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data to receive data from or transfer data to, or both. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor storage devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM optical disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit system.

[0201] Although this document contains many details, these should not be interpreted as limitations on the scope of the claimed invention or the scope of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described in this document in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. In addition, although the above-mentioned features may be described as working in certain combinations and even initially claimed as such, in some cases, one or more features from the combination may be deleted from the combination, and the combination may involve sub-combinations or variations of sub-combinations. Similarly, although operations are described in a particular order in the accompanying drawings, this should not be understood as requiring that the operations be performed in the particular order or sequence shown, or that all the operations shown be performed to obtain the desired results.

[0202] Only some examples and implementations are disclosed. Variations, modifications and enhancements may be made to the described examples and implementations and other implementations based on what is disclosed.

Claims

1. A wireless communication method, comprising: receiving, by a network device, from a wireless device a report indicating availability of radio frequency (RF) resources configured for communicating with the wireless device; as well as A reconfiguration command is transmitted by the network device to the wireless device based on the report.

2. The method according to claim 1, wherein: The reporting is based on estimated in-device radio frequency interference at the wireless device.

3. The method according to any one of claims 1 to 2, wherein: The report provides the availability of RF resources based on frequency domain granularity.

4. The method according to claim 3, wherein: The frequency domain granularity is at a bandwidth portion level or a bandwidth portion combination level.

5. The method according to claim 3, wherein: The frequency domain granularity is at the physical resource block (PRB) level.

6. The method according to claims 4-5, wherein: BWP level granularity is used for serving cell or PRB level granularity is used for non-serving frequency.

7. The method according to any one of claims 1 to 6, wherein: The report provides a list of available RF resources.

8. The method according to any one of claims 1 to 7, wherein: The report provides a list of unavailable RF resources.

9. The method according to any one of claims 1 to 8, wherein: The reconfiguration command causes the wireless device to switch to another bandwidth portion or another combination of bandwidth portions according to the reconfiguration command.

10. The method according to claim 9, wherein: The reconfiguration command is included in a Medium Access Control Element (MAC CE).

11. The method according to claim 9, wherein: The reconfiguration command is included in a Radio Resource Control (RRC) message.

12. The method according to any one of claims 1 to 11, wherein: The report is generated in response to a request from the network device.

13. The method according to any one of claims 1 to 12, wherein: The report is formatted according to a report configuration transmitted by the network device.

14. The method according to claim 13, wherein: The reporting configuration provides threshold information for decisions regarding RF interference within the device.

15. The method according to claim 13, wherein: The reporting configuration specifies the interference levels to be reported in the report.

16. A wireless communication method, comprising: generating, by a wireless device, a report indicating availability of radio frequency (RF) resources configured to be used by the wireless device to communicate with a network device; as well as The report is transmitted by the wireless device to the network device.

17. The method according to claim 16, wherein: The report is generated by estimating in-device RF interference of the wireless device.

18. The method according to any one of claims 16-17, wherein: The report includes bandwidth part (BWP) or physical resource block (PRB) interference level information.

19. The method according to any one of claims 16 to 18, wherein: The report is generated in response to a request from the network device.

20. The method according to any one of claims 16 to 19, wherein: The report is formatted according to a report configuration received from the network device.

21. The method according to claim 20, wherein: The reporting configuration provides threshold information for decisions regarding RF interference within the device.

22. The method according to claim 20, wherein: The reporting configuration specifies the interference levels to be reported in the report.

23. The method according to claim 18, wherein: BWP level granularity is used for serving cell or PRB level granularity is used for non-serving frequency.

24. A method according to any one of the preceding claims, wherein: The report provides a list of available RF resources.

25. A method according to any one of the preceding claims, wherein: The report provides a list of unavailable RF resources.

26. The method according to any one of claims 1 to 10, wherein: The wireless device receives a reconfiguration command in response to the report, wherein the reconfiguration command causes the wireless device to switch to another bandwidth portion or another combination of bandwidth portions according to the reconfiguration command.

27. The method according to claim 23, wherein: The reconfiguration command is received as a Medium Access Control Element (MACCE).

28. The method of claim 23, wherein: The reconfiguration command is received as a Radio Resource Control (RRC) message.

29. A wireless communication device comprising a processor configured to implement the method according to any one of claims 1-28.

30. A computer readable medium having stored thereon codes which, when executed, cause a processor to implement the method of any one of claims 1-28.

Images