Signaling of IDC Problems

Abstract

The present disclosure provides methods, devices, and systems for signaling of In-Device Coexistence (IDC) problems in uplink (UL) Carrier Aggregation (CA). Embodiments of a method in a User Equipment (UE) in communication with an Evolved Node B (eNB) are disclosed. In some embodiments, the method in the UE comprises sending an IDC indication to the eNB including information of problematic UL CA combinations. In this manner, the eNB is provided an indication from which the eNB can deduce which frequencies need to be avoided for UL CA.

Claims

1-16. (canceled)

17. A method performed by a User Equipment (UE), the method comprising: generating a message that indicates a combination of uplink carrier frequencies, where the uplink carrier frequencies in combination cause or are expected to cause In-Device Coexistence (IDC) problems at the UE; and transmitting the message to a base station serving the UE.

18. The method of claim 17, wherein the message comprises IDC assistance information.

19. The method of claim 18, wherein the IDC assistance information indicates a problematic Uplink (UL) Carrier Aggregation (CA) combination comprising the combination of uplink carrier frequencies.

20. The method of claim 17, wherein transmitting the message to the base station comprises the UE transmitting the message to the base station in response to experiencing IDC problems involving the combination of uplink carrier frequencies that the UE by itself cannot resolve.

21. The method of claim 17, wherein transmitting the message to the base station comprises transmitting a Radio Resource Control (RRC) message.

22. The method of claim 17, wherein the indication comprises an index identifying an Uplink (UL) Carrier Aggregation (CA) frequency band combination.

23. The method of claim 22, wherein the method includes transmitting the message to the base station only if measurement objects are configured for Downlink (DL) carriers corresponding to the UL CA frequency band combination.

24. The method of claim 17, wherein generating the message comprises generating the message to indicate one or more Uplink (UL) Carrier Aggregation (CA) frequency band combinations included among UL carriers that are candidates for CA.

25. The method of claim 17, wherein generating the message comprises indicating one or more Uplink Carrier Aggregation (CA) frequency combinations among UL CA frequency combinations included in capability information of the UE.

26. A User Equipment (UE) comprising: a transceiver; and processing circuitry configured to: generate a message that indicates a combination of uplink carrier frequencies, where the uplink carrier frequencies in combination cause or are expected to cause In-Device Coexistence (IDC) problems at the UE; and transmit, via the transceiver, the message to a base station serving the UE.

27. The UE of claim 26, wherein the message comprises IDC assistance information.

28. The UE of claim 27, wherein the IDC assistance information indicates a problematic Uplink (UL) Carrier Aggregation (CA) combination comprising the combination of uplink carrier frequencies.

29. The UE of claim 26, wherein the processing circuitry is configured to transmit the message to the base station in response to the UE experiencing IDC problems involving the combination of uplink carrier frequencies that the UE by itself cannot resolve.

30. The UE of claim 26, wherein the processing circuitry is configured to transmit the message to the base station as a Radio Resource Control (RRC) message.

31. The UE of claim 26, wherein the indication comprises an index identifying an Uplink (UL) Carrier Aggregation (CA) frequency band combination.

32. The UE of claim 31, wherein the processing circuitry is configured to transmit the message to the base station only if measurement objects are configured for Downlink (DL) carriers corresponding to the UL CA frequency band combination.

33. The UE of claim 26, wherein the indication indicates one or more Uplink (UL) Carrier Aggregation (CA) frequency band combinations included among UL carriers that are candidates for CA.

34. The UE of claim 26, wherein the indication indicates one or more Uplink Carrier Aggregation (CA) frequency combinations among UL CA frequency combinations included in capability information of the UE.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0056] FIG. 1 illustrates aggregated bandwidth of 100 megahertz (MHz) in Carrier Aggregation (CA);

[0057] FIG. 2 shows an ASN.1 example of a first embodiment of the present disclosure for a bit map indicating problematic band combinations;

[0058] FIG. 3 shows an ASN.1 example of a second embodiment of the present disclosure for a list of indexes to problematic band combinations;

[0059] FIG. 4 illustrates a cellular communications network according to some embodiments of the present disclosure;

[0060] FIGS. 5-9 illustrate operation of wireless devices/user equipments and network nodes according to different embodiments of the present disclosure;

[0061] FIGS. 10 and 11 are block diagrams that illustrate a wireless device according to some embodiments of the present disclosure; and

[0062] FIGS. 12 and 13 are block diagrams that illustrate a network node according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

[0063] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

[0064] Many mobile devices (e.g., smartphones, etc.) are or will be equipped with multiple radio transceivers in order to access various networks. For example, a UE may be equipped with a 3GPP LTE transceiver, an IEEE 802.11 (i.e., WiFi) transceiver, a Bluetooth transceiver, and a Global Navigation Satellites System (GNSS) receiver. The radio transceivers within the same UE are spatially close to one another (i.e., are co-located). As such, when the radio transceivers within the same UE operate on adjacent frequencies or sub-harmonic frequencies, transmissions associated with the transmitter of one radio transceiver may interfere with the receiver of another radio transceiver. This interference situation is referred to as an In-Device Coexistence (IDC) interference scenario, or IDC interference situation.

[0065] Recently, a problem has been identified where two or more simultaneous uplink (UL) inter-band transmissions, such as those transmitted by a UE operating according to a UL CA scheme, cause Inter-Modulation (IM) products that result in potential interference to a co-located GNSS receiver. Almost half of the two UL Component Carrier (CC) (2UL) inter-band Carrier Aggregation (CA) configurations that are currently being specified for 3GPP LTE generate IM products of up to 5th order that fall onto GNSS receive bands, thus causing an IDC problem. Even the impact of 5th order IM due to 2UL inter-band CA on a GNSS receiver is non-negligible. In addition, it has been identified that other systems (Bluetooth, Wireless Local Area Network (WLAN), etc.) may suffer from IM products from UL CA.

[0066] An IDC mechanism (i.e., a mechanism that avoids IDC interference) was introduced in 3GPP LTE Release (Rel) 11). This IDC mechanism addressed problem scenarios in which the UE suffers from interference between the LTE and Industrial. Scientific, and Medical (ISM) /GNSS signals. Both the case in which LTE is the victim and the case in which LTE is the aggressor were considered. However. UL CA problems were not considered for the 3GPP LTE Rel-11 IDC avoidance mechanism.

[0067] In the 3GPP LTE Rel-11 IDC mechanism, the UE indicates a problematic LTE frequency (as it indicates a Measurement Object (MO)) and then the UE indicates if this LTE frequency is a victim or aggressor with parameter interferenceDirection. In 3GPP LTE Rel-11, a problematic LTE frequency/carrier is one on which the UE is experiencing an IDC problem (i.e., IDC interference is at a level that cannot be solved by the UE itself). If the direction is “eutra.” then the eNB can avoid problematic transmissions on the LTE downlink; and, if the direction is “other.” then the eNB can avoid problematic transmissions on the LTE UL. If the direction is “both,” then both UL and DL transmissions/receptions need to be taken into account.

[0068] When using the signaling for the current IDC mechanism specified in 3GPP LTE Rel-11, the network cannot deduce that an IM product of a CA combination of multiple frequencies is a problem as the signaling for the current IDC mechanism lists only single frequencies. Instead, the eNB may deduce incorrectly that the carriers cannot be used even as Primary Cells (PCells). Thus, some additional information is needed.

[0069] One option for addressing this problem is that information of which UL CA combinations are problematic is included in the IDC indication. In this way, the eNB (i.e., the network) can directly deduce which LTE frequencies need to be avoided for UL CA.

[0070] A second option to address this problem is to include GNSS type of the GNSS receiver implemented at the UE. From this information, the eNB can derive which UL CA combinations are problematic. However, there are two problems with this approach, namely: 1) this approach is not applicable to the Bluetooth and WLAN (e.g., WiFi) case and 2) depending on UE implementation, the interference problems due to different modulation orders may vary.

[0071] A third option to address this problem is for the UE to signal victim frequency (ISM or GNSS frequency) and bandwidth together with the victim technology to the eNB. However, this approach has similar problems as the current IDC mechanism; namely, for the eNB, it would still be difficult to determine which LTE frequencies/carriers to limit.

[0072] Embodiments of the present disclosure provide a mechanism for how a UE can indicate problematic UL carrier frequencies in such a way that signaling load remains limited. Based on this indication, the eNB can reduce UL transmissions on the LTE carrier frequencies and thus avoid interference.

[0073] In some embodiments, a solution to solve the IDC problem in case of UL CA is to signal problematic UL CA combinations on the LTE side. This would be sufficient information for the eNB to solve the problem.

[0074] IDC Signaling Utilizing UE Capability Signaling

[0075] In principle, the UE could signal all possible UL CA combinations that are problematic in the IDC indication. Signaling would include frequency information (e.g., center frequency and bandwidth) for each carrier to be a candidate for aggregation in a carrier combination. However, as there are many combinations, the signaling overhead would be quite large.

[0076] Embodiments disclosed herein utilize a UE's capability signaling where frequency information is already given. In some embodiments, the UE signals an index referring to a band combination entry in the UE capability signaling to indicate which UL CA combinations suffer from IDC interference. UE capability signaling may include a list of all band combinations over which the UE supports CA. Each band entry includes information of the band frequency, bandwidth, class, etc.

[0077] In LTE Rel-10, there are 128 potential combinations (maxBandComb-r10) and in Rel-11 there are 256 potential combinations (maxBandComb-r11).

[0078] In a first embodiment, the signaling includes a bit map indicating if the corresponding band combination is problematic. Here, the bit is “1” if the corresponding band combination in the capability list is suffering from IDC interference and otherwise “0.” The length of the bit map corresponds to the number of band combinations in the capability signaling. FIG. 2 shows an ASN.1 example of the first embodiment.

[0079] In a second embodiment, the UE can indicate the list of indexes to the problematic band combinations. As such, the UE would signal, e.g., that the 5th band combination in the band combination list in the UE capability signaling is suffering from an IDC problem. FIG. 3 shows an ASN.1 example of the second embodiment.

[0080] The first embodiment is good if most of the band combinations suffer from interference. The second embodiment is better if only few combinations suffer from interference.

[0081] IDC Signaling Utilizing Measurement Object Identities (IDs)

[0082] In LTE Rel-11, the UE was only allowed to report IDC issues occurring or expected to occur on/by a carrier for which a measurement object is configured (from 3GPP TS 36.331 (version 11.1.0, September 2012), section 5.6.9.3: “include the IE affectedCarrierFreqList with an entry for each affected E-UTRA carrier frequency for which a measurement object is configured”). This was based on the assumption that the network would typically configure a RRM measurement on a carrier before configuring it as serving cell. As soon as the measurement object is configured the UE should report (expected) IDC problems.

[0083] Following the same principle, the UE would only indicate IDC problems for a supported combination of UL carriers if measurement objects are configured for all corresponding DL carriers of that combination.

a) measurement objects are configured for all the (corresponding DL) carriers; and
b) the UE supports UL CA among those carriers; and
c) the UE experiences or expects to experience IDC problems due to that carrier combination.

[0084] In this embodiment, a carrier combination is identified by a set of the corresponding MeasObjectId's (i.e., Measurement Object IDs). Assuming LTE Rel-10 CA as baseline up to 5 CCs, for each combination, there can be up to 5 measurementObjects indicated. For LTE Rel-13, there can be more objects in the combination.

[0085] Here is an example of this solution:

UE supports bands 1, 2, 3, 4. Each of the bands has two possible carriers, called a and b. UE supports UL CA of 1+2 and 1+3
Step 1: The UE has its PCell on carrier a of band 1 (called 1a). It has a measObject (ID=0) for 1a but no IDC issues.
=>No IDC report
Step 2: The eNB configures a measObject (ID=1) for carrier 3b. The UE has no UL or DL IDC problems
=>No IDC report
Step 3: The eNB configures a measObject (ID=2) for carrier 2a. The UE has no immediate IDC problems but knows that it would have problems if the eNB decides to configure UL CA between carrier 1a and 2a.
=>The UE sends an IDC indication “idcCombinations=[[0,2]]” (list with only one combination which comprises two carriers)
=>The eNB knows that the carriers corresponding to measurement object IDs 0 and 2 (carrier 1a and 2a) would cause an UL IDC issue.
Step 4: The UE no longer needs WLAN and hence the UL combination of 1a and 2a would no longer cause problems
Step 5: The UE sends an IDC indication “idcCombinations=[ ]”
=>The eNB configures UL CA.

[0086] Combination of Different Solutions

[0087] In the combined embodiment solution, the UE signals the index related to the band combination in the UE's capability signaling to indicate the problematic CA configuration as discussed above and presented below with respect to in FIG. 5. However, in some embodiments, the UE is allowed to signal such index only if the measurements (that is, measurement objects) are configured for the corresponding carriers.

[0088] In addition, in some embodiments, the eNB may configure which solution to use with the Radio Resource Control (RRC) signaling. If the eNB typically configures measurements before configuring CA, then the solution as described above in the section “IDC Signaling Utilizing Measurement Object IDs” and presented below with respect to FIGS. 6 and 7 can be configured. On the other hand, if the eNB is interested in IDC problems even when measurements are not configured, then it configures the mechanism as described above with respect to the first and second embodiments, as described above in the section “IDC Signaling Utilizing UE Capability Signaling” and presented below with respect to FIG. 5.

[0089] Example System Architecture and Operation Thereof According to Embodiments Above

[0090] FIG. 4 illustrates a cellular communications network 10 according to some embodiments of the present disclosure. In some embodiments, the cellular communications network 10 is a LTE (i.e., LTE or LTE-Advanced) cellular communications network. As such. LTE terminology is oftentimes used throughout this disclosure. However, the concepts and embodiments disclosed herein are not limited to LTE and may be utilized in any suitable type of cellular or wireless network.

[0091] As illustrated, the cellular communications network 10 includes a Radio Access Network (RAN) 12 including a number of base stations 14-1 and 14-2 (generally referred to herein collectively as base stations 14 and individually as base station 14). The base stations 14 provide wireless access to wireless devices 16-1 through 16-3 (generally referred to herein collectively as wireless devices 16 and individually as wireless device 16) within coverage areas (e.g., cells) of the base stations 14. The base stations 14 are connected to a core network 18. Note that while only two base stations 14 and three wireless devices 16 are illustrated in this example for clarity and ease of discussion, the cellular communications network 10 may include many base stations 14 serving many wireless devices 16. In LTE terminology, the wireless devices 16 are referred to as UEs and, as such, the wireless devices 16 are sometimes referred to herein as UEs 16. Likewise, in LTE terminology, the base stations 14 are referred to as Evolved, or Enhanced, Node Bs (eNBs) and, as such, the base stations 14 are sometimes referred to herein as eNBs 14. While in this embodiment the base stations 14 are macro base stations, the RAN 12 may include a mixture of macro base stations and lower power base stations (i.e., pico base stations, femto base stations, home eNBs, etc.). Some of the wireless devices 16 may be MTC devices that perform Machine-to-Machine (M2M) communication. Some examples of MTC devices are smart meters, signboards, cameras, remote sensors, laptops, and appliances. In this example, the wireless device 16-2 is a MTC device.

[0092] FIGS. 5 through 8 are illustrations of at least some of the embodiments described above. FIG. 5 illustrates IDC signaling utilizing UE capability signaling including the first and second embodiments detailed above in the section “IDC Signaling Utilizing UE Capability Signaling.” Notably, the network node that receives the capability information may be the same or different than the network node that receives an indicator of the problematic UL CA frequency band combinations.

[0093] The process of FIG. 5 will now be described with respect to the UE 16 and a network node(s) 20. The network node(s) 20 may be, for example, the base station 14 (e.g., an eNB), multiple base stations 14 (e.g., multiple eNBs), or some other network node(s). As illustrated, the UE 16 sends capability information to the network node(s) 20 (step 100). As described above, in some embodiments, the capability information includes a list of all band combinations over which the wireless device 16 supports CA. In other words, the capability information includes a list of all UL CA combinations (i.e., a list of all UL CA combinations) supported by the UE 16.

[0094] The UE 16 determines one or more problematic UL CA frequency band combinations (step 102). The one or more problematic UL CA frequency band combinations are one or more UL CA frequency band combinations for which the UE 16 is experiencing IDC problems or, in some embodiments, is expected to experience IDC problems. An IDC problem occurs when the level of IDC interference is at a level that cannot be resolved by the UE 16 itself.

[0095] The UE 16 sends at least one indicator of the one or more problematic UL CA frequency band combinations to the network node(s) 20 (step 104). As discussed above, in some embodiments, the at least one indicator is a bit map that includes a separate bit for each combination indicated in the capability information sent to the network node(s) 20 in step 100. The value of a particular bit indicates whether or not there is an IDC problem for the corresponding combination (e.g., “1” indicates an IDC problem and “0” indicates no IDC problem). As also described above, in some other embodiments, the at least one indicator is at least one index, where an index identifies a corresponding entry in the list of combinations supported by the UE 16 provided to the network node(s) 20 in step 100. Note that the network node 20 to which the at least one indicator is sent may or may not be the same as the network node 20 to which the capability information is sent in step 100. Optionally, the network node(s) 20 take one or more actions based on the received indicator(s) (step 106). The one or more actions may be, for example, one or more actions to avoid the IDC problem(s).

[0096] FIG. 6 illustrates IDC signaling utilizing measurementObjectsIDs including the third embodiment detailed above in the section “IDC Signaling Utilizing Measurement Object IDs.” Notably, the network node 20 that sends the configuration to measure on a plurality of frequency bands may be the same or different than the network node 20 that receives an indicator of the problematic UL CA frequency band combinations. Further, the measurement configuration illustrated in FIG. 6 may be via, for example, one or more measurement objects.

[0097] The process of FIG. 6 will now be described with respect to the UE 16 and a network node(s) 20. The network node(s) 20 may be, for example, the base station 14 (e.g., an eNB), multiple base stations 14 (e.g., multiple eNBs), or some other network node(s). As illustrated, the network node(s) 20 configure the UE 16 to measure on a plurality of (i.e., multiple) frequency bands (step 200). As discussed above, in some embodiments, the network node(s) 20 configure the UE 16 with Measurement Objects for carriers on which the UE 16 is to perform measurements. The Measurement Objects have corresponding Measurement Object IDs.

[0098] The UE 16 determines one or more problematic UL CA frequency band combinations from the frequency bands on which the UE 16 is configured to perform measurements (step 202). More specifically, as discussed above, the UE 16 determines that a particular UL CA frequency band combination is problematic if: (a) Measurement Objects are configured for all of the (corresponding DL) carriers, (b) the UE 16 supports UL CA among those carriers, and (c) the UE 16 experiences or expects to experience IDC problems due to that carrier combination.

[0099] The UE 16 sends at least one indicator of the one or more problematic UL CA frequency band combinations to the network node(s) 20 (step 204). As discussed above, in some embodiments, for each problematic UL CA frequency band combination, the at least one indicator includes the Measurement Object IDs of the Measurement Objects configured for the UE 16 for the corresponding (DL) carriers. Note that the network node 20 to which the at least one indicator is sent may or may not be the same as the network node 20 from which the configuration was received by the UE 16 in step 200. Optionally, the network node(s) 20 take one or more actions based on the received indicator(s) (step 206). The one or more actions may be, for example, one or more actions to avoid the IDC problem(s).

[0100] FIG. 7 illustrates one particular example of the embodiment of FIG. 6. In this example, FIG. 7 illustrates that the configuration is a configuration of Measurement Objects and that the IDC indication includes Measurement Object IDs, as described above. Otherwise, the process is the same as described above with respect to FIG. 6. Notably, the process of FIG. 7 is illustrated with respect to a UE 16 and an eNB(s) 14; however, the process is more generally applicable to a wireless device 16 and a network node(s) 20. As illustrated, the eNB(s) 14 configure the UE 16 with Measurement Objects for multiple downlink carriers (step 300). The UE 16 determines one or more problematic UL CA frequency band combinations (step 302). More specifically, as discussed above, the UE 16 determines that a particular UL CA frequency band combination is problematic if: (a) Measurement Objects are configured for all of the (corresponding DL) carriers, (b) the UE 16 supports UL CA among those carriers, and (c) the UE 16 experiences or expects to experience IDC problems due to that carrier combination.

[0101] The UE 16 sends an IDC indication including information of problematic UL CA combinations to the eNB(s) 14 (step 304). In general, the IDC indication includes Measurement Object IDs indicating the one or more problematic UL CA combinations to the eNB(s) 14. More specifically, as described above, for each problematic UL CA combination, the IDC indication includes a set of Measurement Object IDs for all corresponding DL carriers for the problematic UL CA combination. Note that the eNB 14 to which the at least one indicator is sent may or may not be the same as the eNB 14 from which the configuration was received by the UE 16 in step 300. Optionally, the eNB(s) 14 take one or more actions based on the received indicator(s) (step 306). The one or more actions may be, for example, one or more actions to avoid the IDC problem(s).

[0102] FIG. 8 illustrates IDC signaling according to embodiments detailed above in the section “Combination of Different Solutions.” Notably, the process of FIG. 8 is illustrated with respect to a UE 16 and an eNB(s) 14; however, the process is more generally applicable to a wireless device 16 and a network node(s) 20 (e.g., the base station 14 (e.g., an eNB), multiple base stations 14 (e.g., multiple eNBs), or some other network node(s)). As illustrated, the UE 16 sends capability information to the eNB(s) 14 (step 400). As described above, in some embodiments, the capability information includes a list of all band combinations over which the UE 16 supports CA. In other words, the capability information includes a list of all UL CA combinations (i.e., a list of all UL CA combinations) supported by the UE 16. In addition, the eNB(s) 14 configures the UE 16 to measure on a plurality of (i.e., multiple) frequency bands (step 402). As discussed above, in some embodiments, the eNB(s) 14 configures the UE 16 with Measurement Objects for carriers on which the UE 16 is to perform measurements. The Measurement Objects have corresponding Measurement Object IDs.

[0103] The UE 16 determines one or more problematic UL CA frequency band combinations from the frequency bands on which the UE 16 is configured to perform measurements (step 404). More specifically, as discussed above, the UE 16 determines that a particular UL CA frequency band combination is problematic if: (a) Measurement Objects are configured for all of the (corresponding DL) carriers, (b) the UE 16 supports UL CA among those carriers, and (c) the UE 16 experiences or expects to experience IDC problems due to that carrier combination.

[0104] The UE 16 sends at least one indicator of the one or more problematic UL CA frequency band combinations to the eNB(s) 14 (step 406). As discussed above, in some embodiments, the at least one indicator is a bit map that includes a separate bit for each combination indicated in the capability information sent to the eNB(s) 14 in step 400. The value of a particular bit indicates whether or not there is an IDC problem for the corresponding combination (e.g., “1” indicates an IDC problem and “0” indicates no IDC problem). As also described above, in some other embodiments, the at least one indicator is at least one index, where an index identifies a corresponding entry in the list of combinations supported by the UE 16 provided to the eNB(s) 14 in step 400. Note that the eNB 14 to which the at least one indicator is sent may or may not be the same as the eNB 14 to which the capability information is sent in step 400. Optionally, the eNB(s) 14 take one or more actions based on the received indicator(s) (step 408). The one or more actions may be, for example, one or more actions to avoid the IDC problem(s).

[0105] FIG. 9 illustrates an embodiment detailed above in the section “Combination of Different Solutions” in which an eNB 14 configures the UE 16 with the solution, or technique, to use for IDC signaling. Notably, the process of FIG. 9 is illustrated with respect to a UE 16 and an eNB(s) 14; however, the process is more generally applicable to a wireless device 16 and a network node(s) 20 (e.g., the base station 14 (e.g., an eNB), multiple base stations 14 (e.g., multiple eNBs), or some other network node(s)). As illustrated, the eNB 14 sends a solution indication to the UE 16 (step 500). As described above, the solution indication may be sent via RRC signaling (i.e., which solution to use may be configured via RRC signaling). For example, if measurements are configured before configuring CA, then the eNB 14 may configure the UE 16 to use the solution described above with respect to FIGS. 6 and 7. On the other hand, if the network is interested in IDC problems even if measurements are not configured, then the eNB 14 may configure the UE 16 to use the solution described above with respect to FIG. 5. The UE 16 then uses the indicated solution to perform IDC signaling (step 502).

[0106] FIG. 10 is a block diagram of a wireless device 16 according to some embodiments of the present disclosure. As illustrated, the wireless device 16 includes circuitry that operates to cause the wireless device 16 to implement the methods and functionality described herein. In one example, the circuitry can be in the form of processing means, which may include one or more processors 22 (e.g., one or more Central Processing Units (CPUs), one or more Application Specific Integrated Circuits (ASICs), and/or one or more Field Programmable Gate Arrays (FPGAs)) and memory 24 containing instructions executable by the one or more processors 22 whereby the wireless device 16 operates according to any of the embodiments described herein. The wireless device 16 also includes multiple radio transceivers 26 (e.g., LTE, WiFi, Bluetooth, GNSS, etc.) and at least one antenna 32 for each transceiver 26. Each transceiver 26 includes one or more transmitters 28 and/or one or more receivers 30. The transceiver 26 includes various types of circuitry such as, for example, filters, mixers, amplifiers, etc.

[0107] In some embodiments, a computer program is provided including instructions which, when executed by the at least one processor 22, cause the at least one processor 22 to carry out the functionality of the wireless device 16 according to any one of the embodiments described herein is provided. In some embodiments, a carrier containing the aforementioned computer program product. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as the memory 24).

[0108] FIG. 11 is a block diagram of a wireless device 16 according to some embodiments of the present disclosure. The wireless device 16 includes a problematic combinations module 34, which is implemented in software that is stored in a computer readable medium (e.g., memory) and executed by a processor of the wireless device 16. The problematic combinations module 34 is operative to send at least one indicator of at least one problematic uplink carrier aggregation frequency band combination to a network node.

[0109] FIG. 12 is a block diagram of a network node 20 according to some embodiments of the present disclosure. The network node 20 may be any type of network node (e.g., a base station (e.g., an eNB), a Mobility Management Entity (MME), a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), etc.). As illustrated, the network node 20 includes circuitry that operates to cause the network node 20 to implement the methods and functionality described herein. In one example, the network node 20 includes a baseband unit 36 that includes circuitry in the form of processing means which may include one or more processors 38 (e.g., one or more CPUs, one or more ASICs, and/or one or more FPGAs) and memory 40 containing instructions executable by the one or more processors 38 whereby the network node 20 operates according to any of the embodiments described herein. As illustrated, the network node 20 also includes a network interface 42, which allows the network node 20 to communicate with one or more additional network nodes in a wireless communications network. The network interface 42 may include one or more components (e.g., network interface card(s)) that connect the network node 20 to other systems.

[0110] If the network node 20 is a radio network node (e.g., a base station 14), the network node 20 also includes one or more radio units 44, including one or more transmitters 46 and one or more receivers 48 coupled to one or more antennas 50. In some embodiments, the functionality of the network node 20 is implemented in software stored in the memory 40 for execution by the one or more processors 48. In some embodiments, the network node 20 may include additional components responsible for providing additional functionality, including any of the functionality identified above and/or any functionality necessary to support the solutions described above.

[0111] FIG. 13 is a block diagram of a network node 20 according to some embodiments of the present disclosure. The network node 20 includes a transmit module 52 and a receive module 54, each of which is implemented in software that is stored in a computer readable medium (e.g., memory) and executed by a processor of the network node 20. The transmit module 52 is operative to provide a configuration to measure on a plurality of frequency bands. The receive module 54 is operative to receive compatibility information sent to the network node 20, the compatibility information indicating a plurality of uplink carrier aggregation frequency band combinations supported by the user equipment, and receive at least one indicator of at least one problematic uplink carrier aggregation frequency band combination. Notably, the transmit module 52 and the receive module 54 may correspond to features of the same or different network nodes.

[0112] Some exemplary, non-limiting examples of embodiments of the present disclosure are provided below.

[0113] Embodiments of a method in a User Equipment (UE) in communication with an evolved Node B (eNB) are disclosed. In some embodiments, the method in the UE comprises sending an IDC indication to the eNB including information of problematic UL CA combinations. In this manner, the eNB is provided an indication from which the eNB can deduce which frequencies need to be avoided for UL CA.

[0114] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. Further, in some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0115] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0116] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0117] Embodiments of a method in an eNB in communication with a UE are also disclosed. In some embodiments, the method in the eNB comprises receiving an IDC indication from the UE including information of problematic UL CA combinations. In some embodiments, the eNB deduces frequencies to avoid UL CA from the received information of problematic UL CA combinations.

[0118] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. Further, in some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0119] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0120] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0121] Embodiments of a UE for communication with an eNB are also disclosed. In some embodiments, the UE is adapted to send an IDC indication to the eNB including information of problematic UL CA combinations.

[0122] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination.

[0123] In some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0124] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0125] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0126] Embodiments of an eNB for communication with a UE are also disclosed. In some embodiments, the eNB is adapted to receive an IDC indication from the UE including information of problematic UL CA combinations. In some embodiments, the eNB is adapted to deduce frequencies to avoid for uplink carrier aggregation from the received information of problematic UL CA combinations.

[0127] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. Further, in some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0128] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0129] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0130] In some embodiments, a UE for communication with an eNB comprises at least one transceiver, at least one processor, and memory storing instructions executable by the at least one processor whereby the UE is operable to send, via the at least one transceiver, an IDC indication to the eNB including information of problematic UL CA combinations.

[0131] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. Further, in some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0132] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0133] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0134] In some embodiments, an eNB for communication with a UE comprises at least one communication interface, at least one processor, and memory storing instructions executable by the at least one processor whereby the eNB is operable to receive, via the at least one communication interface, an IDC indication from the UE including information of problematic UL CA combinations. In some embodiments, the eNB is adapted to deduce frequencies to avoid UL CA from the received information of problematic UL CA combinations.

[0135] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. In some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0136] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0137] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0138] In some embodiments, a UE for communication with an eNB comprises a problematic combinations module operable to send an IDC indication to the eNB including information of problematic UL CA combinations.

[0139] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. In some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0140] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0141] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0142] In some embodiments, an eNB for communication with a UE comprises a receive module operable to receive an IDC indication from the UE including information of problematic UL CA combinations. In some embodiments, the eNB further comprises a deduce module operable to deduce frequencies to avoid for UL CA from the received information of problematic UL CA combinations.

[0143] In some embodiments, the UE only indicates a UL CA combination as problematic if the UL CA combination is a combination of uplink carriers supported by the UE, measurement objects are configured for all corresponding downlink carriers, and the UE experiences or expects to experience IDC problems due to the UL CA combination. In some embodiments, the problematic UL CA combination is a UL CA combination for which the UE experiences IDC problems.

[0144] In some embodiments, the problematic UL CA combination is identified by a set of measurement object identities for all of the corresponding downlink carriers for the UL CA combination.

[0145] In some embodiments, the IDC indication comprises, for each problematic UL CA combination, a set of measurement object identities for all of the corresponding downlink carriers for the problematic UL CA combination.

[0146] The problematic combinations module, the receive module and the deduce module recited above, may in some embodiments be implemented as computer programs running on one or more processor similar to what is discussed in connection with FIGS. 11 and 13.

[0147] Some further embodiments include a user equipment, comprising: [0148] one or more transceivers; [0149] at least one processor; and [0150] memory storing instructions executable by the at least one processor whereby the user equipment is operable to: [0151] send at least one indicator of at least one problematic uplink carrier aggregation frequency band combination to a network node.

[0152] In some embodiments, the user equipment is further operable to: [0153] send compatibility information to a network node, the compatibility information indicating a plurality of uplink carrier aggregation frequency band combinations supported by the user equipment; [0154] wherein sending the at least one indicator comprises sending a bit map for the plurality of supported band combinations that indicates, for each combination, whether the combination is problematic.

[0155] According to some other embodiments, the user equipment is further operable to: [0156] send compatibility information to a network node, the compatibility information indicating a plurality of uplink carrier aggregation frequency band combinations supported by the user equipment; [0157] wherein sending the at least one indicator comprises sending a list of indexes comprising problematic uplink carrier aggregation frequency band combinations.

[0158] According to still other embodiments, the user equipment is further operable to: [0159] receive a configuration from a network node to measure on a plurality of frequency bands; [0160] wherein the at least one problematic uplink carrier aggregation frequency band combination is at least one combination of the plurality of frequency bands that the user equipment is configured to measure on and that the user equipment has determined is problematic.

[0161] The following acronyms are used throughout this disclosure.

[0162] 2UL Two Uplink Component Carrier

[0163] 3GPP Third Generation Partnership Project

[0164] 5G Fifth Generation

[0165] ASIC Application Specific Integrated Circuit

[0166] CA Carrier Aggregation

[0167] CC Component Carrier

[0168] CIF Carrier Indicator Field

[0169] CPU Central Processing Unit

[0170] CSI Channel State Information

[0171] DL Downlink

[0172] DRX Discontinuous Reception

[0173] eNB Evolved Node B

[0174] EPDCCH Enhanced or Evolved Physical Downlink Control Channel

[0175] E-UTRA Evolved Universal Terrestrial Radio Access

[0176] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0177] FDM Frequency Division Multiplexing

[0178] FPGA Field Programmable Gate Array

[0179] GNSS Global Navigation Satellite System

[0180] ID Identity

[0181] IDC In-Device Coexistence

[0182] IE Information Element

[0183] IM Inter-Modulation

[0184] ISM Industrial, Scientific, and Medical

[0185] LTE Long Term Evolution

[0186] M2M Machine-to-Machine

[0187] MHz Megahertz

[0188] MIMO Multiple Input Multiple Output

[0189] MME Mobility Management Entity

[0190] MO Measurement Object

[0191] MTC Machine Type Communication

[0192] PCell Primary Cell

[0193] PDCCH Physical Downlink Control Channel

[0194] PDN Packet Data Network

[0195] PDSCH Physical Downlink Shared Channel

[0196] P-GW Packet Data Network Gateway

[0197] RAN Radio Access Network

[0198] RAN4 Radio Access Network Working Group 4

[0199] Rel Release

[0200] RRC Radio Resource Control

[0201] RRM Radio Resource Management

[0202] SCEF Service Capability Exposure Function

[0203] SCell Secondary Cell

[0204] S-GW Serving Gateway

[0205] TDM Time Division Multiplexing

[0206] TS Technical Specification

[0207] UE User Equipment

[0208] UL Uplink

[0209] WCDMA Wideband Code Division Multiple Access

[0210] WLAN Wireless Local Area Network

[0211] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.