WO2017077522A1

WO2017077522A1 - Handling in-device coexistence issues

Info

Publication number: WO2017077522A1
Application number: PCT/IB2016/056697
Authority: WO
Inventors: Mattias Tan Bergström; Torsten DUDDA; Riikka Susitaival
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2015-11-06
Filing date: 2016-11-07
Publication date: 2017-05-11

Abstract

In accordance with certain embodiments disclosed herein, a method for handling in-device coexistence issues comprises establishing a first wireless connection with a first network node (400). The method also comprises receiving a configuration message (410). The configuration message comprises configuration information for a second wireless connection with a second network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The method additionally comprises determining whether the first wireless connection or the second wireless connection is experiencing, or will experience, interference (415). The method further comprises determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message (425). The method also comprises, upon determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in- device coexistence issues upon being applied (430).

Description

HANDLING IN-DEVICE COEXISTENCE ISSUES

TECHNICAL FIELD

Embodiments presented herein relate to wireless communication, and in particular to systems, methods, apparatuses, wireless devices, network nodes, computer programs, and user equipment, for handling in-device coexistence issues.

BACKGROUND

In 3GPP Release 11 the In-Device Coexistence (IDC) feature was introduced in LTE. This feature was introduced to tackle situations when a wireless device (WD) or user equipment (UE) is operating multiple radio technologies (e.g., LTE, Bluetooth, near field communication (NFC), wireless local area network (WLAN) such as Wi-Fi, GPS, etc.) and the radios used for these different technologies cause interference with one another. For example, a transmission by an LTE transmitter may cause interference to a GPS receiver, a Bluetooth receiver and a WLAN receiver, as well as the WLAN transmitter may cause interference to the LTE receiver. Another, more specific example where IDC type interference is likely to be present is shown in FIGURE 3. FIGURE 3 shows a range of frequencies 300. When the WD uses an LTE carrier in band 40, such as frequency band 310, at the same time as it is using a WLAN channel in the 2.4 GHz band, such as frequency band 320, there may be IDC issues because these frequency bands are adjacent to one another.

Integration between WLAN and 3GPP has received more and more interest the last couple of years and 3GPP is working on different features to integrate LTE and Wi-Fi. For simplicity herein, a wireless connection based on 3GPP's LTE standard may be referred to as an LTE connection and a wireless connection based on Wi-Fi may be referred to as a WLAN connection. An LTE connection may of course be based on other wireless standards, such as 5G, 3G, Wi-Max, or any other wireless standard used for what may colloquially be called cellular telecommunication. Similarly, a WLAN connection may be based on other local wireless standards and should not be limited solely to Wi-Fi.

One difference in how a WD accesses the WLAN in an LTE-WLAN aggregation or integration scenario is that the WLAN use is initiated by the evolved NodeB (eNB) as opposed to the WD deciding to switch the WLAN on. In addition to the example integration features provided below, other features have been proposed. For example, a feature has been discussed where an IP- tunnel is established between a network node of the 3GPP network (e.g., the eNB) and the WD via a WLAN node. As with the examples below, this feature will rely, at least to some extent, on the eNB's control of the WLAN usage by the WD.

EXAMPLE l: LTE-WLAN AGGREGATION

LTE and WLAN aggregation is a feature where the WD may receive and transmit messages using wireless links to both an eNB and a Wireless Termination (WT) which is a logical node on WLAN side and can be implemented in an Access Point (AP), router, Access Controller (AC), or another physical WLAN network node. The WD may have separate data bearers configured for the WLAN link and the LTE link or a data bearer may be split between the LTE link and the WLAN link. In the split bearer architecture option of LTE/WLAN aggregation, the downlink data may be split on the Packet Data Convergence Protocol (PDCP) layer in the eNB. The eNB may route PDCP PDUs dynamically via eNB Radio Link Control (RLC) to the WD directly, or via a backhaul channel to the secondary eNB (SeNB) or WLAN MAC to the WD.

In the separate data bearer architecture, the lower layers of a bearer are switched to LTE or WLAN meaning all PDCP packets of that bearer are routed via either the LTE link or the WLAN link. From the eNB perspective, the separate bearer architecture (which has been called architecture option 2C) in dual connectivity, may be seen as a static routing decision. In case of the architecture option 2C, there would be either no eNB RLC below the PDCP of the user plane bearer, in case all packets are routed via WLAN to the WD; or there would be no WLAN, i.e. all packets would be routed via LTE to the WD.

Another option for LTE/WLAN aggregation (which has been called architecture option 3C) resembles the Rel-12 dual connectivity split bearer architecture, where the WLAN network node assumes the role of the secondary eNB. An adaptation layer is needed in order to adapt PDCP packets to be transported by WLAN. However, it is still not clear if this adaptation layer will be at the eNB or WLAN network node, or parts of it in each node.

Another feature in LTE and WLAN aggregation is that the eNB may configure the WD to obtain and report WLAN measurements (e.g. RSSI) to the eNB. These measurements can be used by the eNB to make a decision to configure or de-configure the WD with LTE WLAN aggregation. In a dedicated command, the eNB may provide the WD with a WLAN mobility set, which is a set of WLAN identifiers among which the WD shall connect and among which WD-specific WLAN mobility is allowed.

EXAMPLE 2: LTE-WLAN INTERWORKING

In this approach, which has been adopted for 3GPP release 12, the 3GPP The radio access network (RAN) provides assistance parameters that help the WD in performing access selection and traffic steering. The RAN assistance information is composed of threshold values and WLAN identifiers. The threshold values could be, for example for metrics such as 3GPP signal related metrics RSRP/RSRQ/RSCP/EcNo, WLAN signal related metrics such as RCPI/RSSI, WLAN load/utilization, WLAN backhaul load/capacity, etc. One example of a RAN rule that uses the threshold value could be that the WD should connect to a WLAN if the LTE connection level is below the signalled LTE connection signal level threshold while the WLAN connection has a signal level above the signalled WLAN signal level threshold (it has also been discussed that the RAN should provide thresholds for when the WD should steer traffic back from WLAN to 3GPP). This is illustrated below: if (3GPP signal < thresholdi) && (WLAN signal > threshold2) {

steerTrafficToWLANO;

} else if (3GPP signal > thresholds) 11 (WLAN signal < threshold^ { steerTrafficTo3gpp();

}

With the above mechanism it is likely not wanted, or maybe not even feasible, for the WD to consider other WLANs when deciding where to steer traffic. For example, it may not be feasible for the WD to use this mechanism to decide to steer traffic to a WLAN that does not belong to, or is not operated by, the operator of the LTE connection. Hence it has been proposed that the RAN should also indicate to the terminal which WLANs the mechanism should be applied for by sending WLAN identifiers. The RAN assistance parameters (e.g., thresholds, WLAN identifiers, etc.) provided by the RAN may be provided with dedicated signalling and/or broadcast signalling. Dedicated parameters can only be sent to the terminal when having a valid RRC connection to the 3GPP based wireless network. A terminal which has received dedicated parameters applies dedicated parameters; otherwise the terminal applies the broadcast parameters. If no RRC connection is established between the terminal and the 3GPP based wireless network, the terminal cannot receive the dedicated parameters.

In 3GPP Release 13, further enhancements to the interworking solution are currently being discussed. For example, one option being discussed is the use of WLAN measurements to help in the decision making. For example, a WD may be configured to obtain and report WLAN measurements (such as WLAN RSSI) to the eNB. Based on receiving the measurements, the eNB may indicate within a traffic steering command to the WD how to steer traffic between the LTE link and the WLAN link.

EXAMPLE 3: LTE-WLAN INTEGRATION BASED ON IP TUNNEL Another approach for LTE WLAN integration had been taken in 3GPP Release 13. A characteristic of this approach is that an IPsec tunnel is established between the eNB and the WD via the WLAN network. This way, no changes to the WLAN network need to be applied. The idea is that one EPS bearer may be switched between LTE and the IPSec tunnel to the WD. In this scenario, as in the other approaches above, WLAN measurements maybe used by the eNB for decision making. Furthermore, use of the WLAN mobility set, which the eNB configures to the WD, is envisaged.

Because the current LTE-WLAN integration features, and likely future wireless integration, rely to some extent on control from one network (e.g., the LTE network) when the WD uses an alternate network (e.g., the WLAN network), the controlling network may request the WD to use resources that cause the WD to experience IDC issues. Traditionally, the controlling network node would, more or less, have to solve the IDC issues for the WD by adjusting, and to some extent disturbing, the WD's use of the wireless link with the controlling network node. However, in some scenarios it would be more beneficial for the controlling network node to stop the WD 's usage of the secondary network in order to protect the WD 's link with the controlling network. However, despite the controlling network node having received WLAN measurements from the WD, the information that is reported to the controlling network node is insufficient to determine the cause of the interference.

SUMMARY

An object of embodiments herein is to provide systems, methods, apparatuses, wireless devices, network nodes, computer programs, and user equipment, for handling in-device coexistence (IDC) issues. In accordance with certain embodiments disclosed herein, a method for handling in-device coexistence issues comprises establishing a first wireless connection with a first network node. The method also comprises receiving a configuration message. The configuration message comprises configuration information for a second wireless connection with a second network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The method additionally comprises determining whether the first wireless connection or the second wireless connection is experiencing, or will experience, interference. The method further comprises determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message. The method also comprises, upon determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

In some embodiments of the method the indication is provided in a radio resource control (RRC) message. In certain embodiments of the method the indication is provided using media access control (MAC) signaling. In particular embodiments of the method the indication is part of a message, the message comprises information about a cause of the interference.

In some embodiments, the second network node provides a plurality of wireless signals. Each wireless signal is available for the second wireless connection. In these embodiments, where the method includes determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, the method comprises determining whether using each of the plurality of wireless signals causes, or will cause, interference for the first wireless connection or the second wireless connection. Upon determining that each of the plurality of wireless signals is causing or will cause interference, the method further includes providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

In certain embodiments, the second network node provides a plurality of wireless signals. Each wireless signal is available for the second wireless connection. In these embodiments, where the method includes determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, the method comprises determining whether using any of the plurality of wireless signals causes, or will cause, interference for the first wireless connection or the second wireless connection. Upon determining that any of the plurality of wireless signals is causing or will cause interference, the method further includes providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

In some embodiments, upon determining that the interference is not due to the configuration information in the configuration message, the method comprises implementing a first mitigation action. The first mitigation action attempts to remove or reduce the interference.

In accordance with particular embodiments, a method for handling in- device coexistence issues comprises establishing a first wireless connection with a wireless device. The method also comprises sending the wireless device a configuration message. The configuration message comprises configuration information for a second wireless connection with a remote network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The method also comprises receiving a message that the wireless device is encountering interference with at least one of the first or the second wireless connections. The method further comprises, upon the message comprising an indication that the interference is due to the configuration information in the configuration message, implementing a first mitigation action to reduce or eliminate the interference. The method additionally includes, upon the message not comprising an indication that the interference is due to the configuration information in the configuration message, implementing a second mitigation action to reduce or eliminate the interference, the second mitigation action different than the first mitigation action.

In certain embodiments of the method, the message is a radio resource control (RRC) message. In particular embodiments of the method the message is received via media access control (MAC) signalling. In some embodiments of the method the message comprises information about a cause of the interference.

In certain embodiments, where the method comprises implementing the first mitigation action, the method further comprises sending the wireless device a second configuration message. The second configuration message comprising updated configuration information for the second wireless connection.

In particular embodiments, where the method comprises implementing the second mitigation action, the method further comprises modifying the first wireless connection with the wireless device.

In accordance with particular embodiments, a wireless device for handling in-device coexistence issues comprises interface circuitry. The interface circuitry is configured to establish a first wireless connection with a first network node. The interface circuitry is further configured to receive a configuration message. The configuration message comprises configuration information for a second wireless connection with a second network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The wireless device also comprises processing circuitry. The processing circuitry is configured to determine whether the first wireless connection or the second wireless connection is experiencing, or will experience, interference. The processing circuitry is also configured to determine whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message. Upon the processing circuitry determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, the interface circuitry is further configured to provide the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied. The wireless device also comprises a power source configured to provide the interface circuitry and the processing circuitry with power.

In accordance with certain embodiments, a network node for handling in-device coexistence issues comprises interface circuitry. The interface circuitry is configured to establish a first wireless connection with a wireless device. The interface circuitry is also configured to send the wireless device a configuration message. The configuration message comprises configuration information for a second wireless connection with a remote network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The interface circuitry is further configured to receive a message that the wireless device is encountering interference with at least one of the first or the second wireless connections. The network node also comprises processing circuitry. The processing circuitry is configured to, upon the message comprising an indication the interference is due to the configuration information in the configuration message, implement a first mitigation action to reduce or eliminate the interference. The processing circuitry is also configured to, upon the message not comprising an indication the interference is due to the configuration information in the configuration message, implement a second mitigation action to reduce or eliminate the interference. The second mitigation action is different than the first mitigation action. The network node also comprises a power source configured to provide the interface circuitry and the processing circuitry with power.

In accordance with particular embodiments, a user equipment, UE, for handling in-device coexistence issues comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry. The radio front-end circuitry is configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to establish a first wireless connection with a first network node. The processing circuitry is also configured to receive a configuration message. The configuration message comprises configuration information for a second wireless connection with a second network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The processing circuitry is further configured to determine whether the first wireless connection or the second wireless connection is experiencing, or will experience, interference. The processing circuitry is additionally configured to whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message. Upon determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, the processing circuitry is further configured to provide the first network node with an indication that applying the configuration information in the configuration message is causing in- device coexistence issues as applied, or will cause in-device coexistence issues upon being applied. The UE also comprises an input interface connected to the processing circuitry. The input interface is configured to allow input of information into the UE to be processed by the processing circuitry. The UE further comprises an output interface connected to the processing circuitry. The output interface is configured to output information from the UE that has been processed by the processing circuitry. The UE additionally comprises a battery connected to the processing circuitry and configured to supply power to the UE.

In accordance with particular embodiments, a wireless device for handling in-device coexistence issues comprises a connection module configured to establish a first wireless connection with a first network node. The wireless device also comprises a receiver module configured to receive a configuration message. The configuration message comprises configuration information for a second wireless connection with a second network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The wireless device further comprises a first determine module configured to determine whether the first wireless connection or the second wireless connection is experiencing, or will experience, interference. The wireless device additionally includes a second determine module configured to determine whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message. The wireless device also includes a provider module configured to, upon determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, provide the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in- device coexistence issues upon being applied.

In accordance with particular embodiments, a network node for handling in-device coexistence issues comprises a connection module configured to establish a first wireless connection with a wireless device. The network node also comprises a transmitter module configured to send the wireless device a configuration message. The configuration message comprises configuration information for a second wireless connection with a remote network node. The second wireless connection comprises a different wireless technology than the first wireless connection. The network node additionally includes a receiver module configured to receive a message that the wireless device is encountering interference with at least one of the first or the second wireless connections. The network node further comprises a first implementation module configured to, upon the message comprising an indication the interference is due to the configuration information in the configuration message, implement a first mitigation action to reduce or eliminate the interference. The network node also comprises a second implementation module configured to, upon the message not comprising an indication the interference is due to the configuration information in the configuration message, implement a second mitigation action to reduce or eliminate the interference, the second mitigation action different than the first mitigation action. Advantageously, in certain embodiments, when a WD identifies that there is an IDC issue the WD may try to solve the problem internally. If this does not succeed, the WD may indicate to the network node that it is experiencing (or will experience) IDC issues caused by the requested use of the secondary wireless connection (e.g., WLAN connection). Advantageously one or more embodiments provide a wireless device with the ability to provide more accurate and helpful indications as to the interference being experienced by the wireless device. This may be used to better mitigate the interference being experienced by the wireless device. For example, if the network node receives a message indicating that the wireless connection that it requested the WD to use is causing problems, the network node can decide whether to modify this requested wireless connection or its own wireless connection with the WD.

It is to be noted that any feature of any of the above embodiments may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to the other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following detailed disclosure, attached claims, and drawings.

Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the element, apparatus, component, means, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

BRIEF DESCRIPTION OF THE DRAWINGS

Particular embodiments are now described, by way of example, with reference to the accompanying drawings, in which:

Figure 1 illustrates a wireless network comprising a more detailed view of a network node and a wireless device, in accordance with a particular embodiment;

Figure 2 illustrates a bock diagram of a User Equipment (UE), in accordance with a particular embodiment;

Figure 3 illustrates an allocation of frequencies, in accordance with a particular embodiment;

Figure 4 illustrates a flowchart for handling in-device coexistence problems, in accordance with a particular embodiment; and

Figure 5 illustrates a schematic block diagram illustrating the functional modules used in handling in-device coexistence issues, according to a particular embodiment.

DETAILED DESCRIPTION

Some of the embodiments contemplated by the claims will now be described more fully hereinafter with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the claims and the claims should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to help convey the scope of the inventive concept to those skilled in the art. Like numbers refer to like elements throughout the description.

Figure 1 illustrates a wireless network comprising a more detailed view of network node 120 and WD 110, in accordance with a particular embodiment. For simplicity, Figure 1 only depicts network 150, network nodes 120 and 120a, and WD 110. Network node 120 comprises processor 122, storage 123, interface 121, and antenna 121a. Similarly, WD 110 comprises processor 112, storage 113, interface 111 and antenna 111a. These components may work together in order to provide network node and/ or wireless device functionality, such as providing wireless connections in a wireless network and making decisions as to what data is to be sent via which wireless link. In certain embodiments, the components of Figure 1 may be configured to allow, for example, WD 110 to indicate to network node 120 that a configuration message provided by network node 120 is causing, or will cause, WD 110 to experience in-device coexistence issues.

In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

Network 150 may comprise one or more IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), backbone networks, wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices. Network node 120 comprises processor 122, storage 123, interface 121, and antenna 121a. These components are depicted as single boxes located within a single larger box. In practice however, a network node may comprise any number of additional components and multiple different physical components that make up a single illustrated component (e.g., interface 121 may comprise terminals for coupling wires for a wired connection and a radio transceiver for a wireless connection). As another example, network node 120 may be a virtual network node in which multiple different physically separate components interact to provide the functionality of network node 120 (e.g., processor 122 may comprise three separate processors located in three separate enclosures, where each processor is responsible for a different function for a particular instance of network node 120). Similarly, network node 120 may be composed of multiple physically separate components (e.g., a NodeB component and a radio network controller (RNC) component, a base transceiver station (BTS) component and a base station controller (BSC) component, etc.), which may each have their own respective processor, storage, and interface components. In certain scenarios in which network node 120 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and BSC pair, may be a separate network node. In some embodiments, network node 120 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate storage 123 for the different RATs) and some components may be reused (e.g., the same antenna 121a may be shared by the RATs).

Network node 120a may comprise similar components, although the actual components may, in practice, be different than those of network node 120. For example, network node 120 may be an eNB and network node 120a may be a WLAN access point. Both nodes may have processors, storage, and interfaces but the type of each of these components maybe different due to the different functions/roles of the respective network nodes. In certain embodiments, network node 120a may provide a plurality of wireless signals any one of which may be used for wireless connection 140.

Processor 122 may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 120 components, such as storage 123, network node 120 functionality. For example, processor 122 may execute instructions stored in storage 123. Such functionality may include providing various wireless features discussed herein to wireless devices, such as WD 110, including any of the steps or methods disclosed herein. In certain embodiments, processor 122 may be configured to implement different mitigation actions depending on the information contained in the indication received from WD 110 via wireless connection 130. For example, processor 122 may generate a second configuration message to be sent by interface 121 to WD 110 with updated configuration information for wireless connection 140. As another example, processor 122 may determine how to modify wireless connection 130 so as to reduce or eliminate the interference experienced by WD 110.

Storage 123 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory component. Storage 123 may store any suitable instructions, data or information, including software and encoded logic, utilized by network node 120. In some embodiments, storage 123 may store several different WLAN identifiers. The included WLAN identifiers may comprise WLANs operated, approved or otherwise affiliated with the same entity that operates network node 120. In some embodiments, the included WLANs may comprise WLANs operated by customers of the entity that operates network node 120. Network node 120 also comprises interface 121 which may be used in the wired or wireless communication of signalling and/or data between network node 120, network 150, and/or WD 110. For example, interface 121 may perform any formatting, coding, or translating that may be needed to allow network node 120 to send and receive data with network 150 over a wired connection and/ or with WD 110 over a wireless connection. Interface 121 may also include a radio transmitter and/or receiver that may be coupled to or a part of antenna 121a. The radio may receive digital data that is to be sent out to other network nodes or WDs. The radio may convert the digital data into a radio signal having the appropriate parameters (e.g., channel, frequency, bandwidth, timeslot, etc.). The radio signal may be transmitted via antenna 121a to the appropriate recipient (e.g., WD 110).

Antenna 121a may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 121a may comprise one or more (e.g., MIMO) omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.

In certain embodiments, interface 121 may be configured to establish wireless connection 130 with WD 110. Interface 121 may further be configured to use wireless connection 130 to send a configuration message to WD 110. The configuration message may comprise configuration information for wireless connection 140 with network node 120a. Wireless connections 130 and 140 may comprise different wireless technologies (e.g., Wi-Fi, LTE, etc.). Interface 121 may also be configured to receive a message that WD 110 is encountering interference with at least one wireless connection 130 or 140. The message may comprise an indication that WD 110 is experiencing IDC issues. The message may also comprise an indication that the IDC issues are due to the configuration information sent by network node 120. The message may further comprise information about the interference that is being experienced by WD no and/or the cause of the interference. In some embodiments, the indication is received in a radio resource control (RRC) message. In certain embodiments, the indication is received via media access control (MAC) signalling.

WD no may be any type of wireless endpoint, internet of things (IoT) device, mobile station, mobile phone, wireless local loop phone, smartphone, user equipment, desktop computer, PDA, cell phone, tablet, laptop, VoIP phone or handset, which is able to wirelessly send and receive data and/or signals to and from a network node, such as network node 120. WD 110 comprises processor 112, storage 113, interface 111, and antenna 111a. Like network node 120, the components of WD 110 are depicted as single boxes located within a single larger box, however in practice a wireless device may comprises multiple different physical components that make up a single illustrated component (e.g., storage 113 may comprise multiple discrete microchips, each microchip representing a portion of the total storage capacity).

Processor 112 may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in combination with other WD 110 components, such as storage 113, WD 110 functionality. Such functionality may include providing various wireless features discussed herein, including any of the steps or methods disclosed herein. For example, in some embodiments, processor 112 may determine the type and source of interferences experienced by WD 110 and how to mitigate such interferences. Processor 112 may further determine whether the interference is causing IDC issues and whether or not those IDC issues were caused by configuration information provided by network node 120.

In certain embodiments, processor 112 may be used to determine whether wireless connection 140 or wireless connection 130 is experiencing any interference. Processor 112 may also be used to determine whether the interference is due to the configuration information in a configuration message provided to WD no by network node 120. It is of course understood that the configuration information itself does not cause the interference but rather the configuration of interface 111 based on the configuration information which may cause the interference.

In certain embodiments, network node 120a may provide a plurality of wireless signals, any one of which may be used for establishing wireless connection 140. In some embodiments, processor 112 may determine that the interference is due to wireless connection 140 being configured based on the configuration information in the configuration message if each of the plurality of wireless signals provided by network node 120a causes, or will cause, interference for wireless connection 130, or vice-versa. In certain embodiments, processor 112 may determine that the interference is due to wireless connection 140 being configured based on the configuration information in the configuration message if any of the plurality of wireless signals provided by network node 120a causes, or will cause, interference for wireless connection 130, or vice-versa. Regardless of how it is determined, in certain embodiments, if processor 112 determines that the interference is based on the configuration information, interface 111 may transmit a message to network node 120, the message may comprise an indication that the requested configuration of wireless connection 140 is causing, or will cause, IDC issues for WD 110. Conversely, if processor is 112 determines that the requested configuration of wireless connection 140 did not, or does not, cause the interference experienced by either wireless connection, processor 112 may implement a mitigation action to remove or reduce the interference. This may involve turning off the cause of the interference (e.g., a Bluetooth transmitter), changing channels, etc. If the mitigation is unsuccessful, interface 111 may transmit a message to network node 120, the message may alert network node 120 of the interference, but may be devoid of an indication that the requested configuration of wireless connection 140 is causing, or will cause, IDC issues for WD 110.

Storage 113 may be any form of volatile or non-volatile memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory component. Storage 113 may store any suitable data, instructions, or information, including software and encoded logic, utilized by WD 110. In some embodiments storage 113 may maintain a list, database, or other organization of data (e.g. modulation scores) useful for identifying target network nodes to which it can establish a wireless connection (e.g., a secondary wireless connection).

Interface 111 may be used in the wireless communication of signalling and/or data between WD 110 and network node 120. For example, interface 111 may perform any formatting, coding, or translating that may be needed to allow WD 110 to send and receive data from network node 120 over wireless connection 130 and/or network node 120a over wireless connection 140. Interface 111 may also include a radio transmitter and/ or receiver that may be coupled to or a part of antenna 111a. The radio may receive digital data that is to be sent out to network node 121 via wireless connection 130 and/or to network node 120a via wireless connection 140. The radio may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 111a to corresponding network node i2o/i2oa.

Antenna 111a may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 111a may comprise one or more (e.g., MIMO) omni-directional, sector or panel antennas operable to transmit/receive radio signals. In some embodiments, the radio signals may be between 2 GHz and 66 GHz. For simplicity, antenna 111a may be considered a part of interface 111 to the extent that a wireless signal is being used.

In some embodiments, interface 111 may be configured to establish wireless connection 130 with network node 120. Wireless connection 130 may be used to send messages, signalling and/ or other types of data from network node 120 to wireless device 110. For example, interface 111 may be configured to receive a configuration message from network node 120 via wireless connection 130. The configuration message may comprise configuration information for wireless connection 140 with network node 120a. Wireless connections 130 and 140 may comprise different wireless technologies (e.g., Wi-Fi, LTE, Bluetooth, etc.). If processor 112 determines that the interference being experienced by WD 110 is due to the configuration information in the configuration message, interface 111 may be configured to provide network node 120 with a message comprising an indication that the interference is due to the configuration information in the configuration message. In some instances, where processor 112 does not determine that the interference is due to the configuration message, interface 111 may be configured to provide network node 120 with a message comprising an indication that it is experiencing interference without an indication that the interference is due to the configuration message. Depending on the scenario and embodiment, interface 111 may be configured to provide the message in a variety of different ways. For example, the massage may be provided in a radio resource control (RRC) message or via media access control (MAC) signalling. In addition to the indication that the interference is due to the configuration message, the message may also comprise information about the determined cause of the interference (e.g., the frequency or channel, the severity of the interference, the source ID of the interference, etc.)

Figure 2 illustrates a bock diagram of a User Equipment (UE), in accordance with a particular embodiment. As shown in Figure 2, UE 200 is an example wireless device. UE 200 includes an antenna 205, radio front-end circuitry 210, processing circuitry 215, input interface 220, output interface 225, computer-readable storage medium 230 and power source 235. Antenna 205 may include one or more antennas or antenna arrays, and is configured to send and/ or receive wireless signals. Antenna 205 is connected to radio front- end circuitry 210. In certain alternative embodiments, wireless device 200 may not include antenna 205, and antenna 205 may instead be separate from wireless device 200 and be connectable to wireless device 200 through an interface or port.

The radio front-end circuitry 210 may comprise various filters and amplifiers, is connected to antenna 205 and processing circuitry 215, and is configured to condition signals communicated between antenna 205 and processing circuitry 215. In certain alternative embodiments, wireless device 200 may not include radio front-end circuitry 210, and processing circuitry 215 may instead be connected to antenna 205 without radio front-end circuitry 210. Although not depicted, in some embodiments UE 200 may comprise one or more ports for a wired connection.

Processing circuitry 215 may include one or more of radio frequency (RF) transceiver circuitry, baseband processing circuitry, and application processing circuitry. In some embodiments, the RF transceiver circuitry, baseband processing circuitry, and application processing circuitry may be on separate chipsets. In alternative embodiments, part or all of the baseband processing circuitry and application processing circuitry maybe combined into one chipset, and the RF transceiver circuitry may be on a separate chipset. In still alternative embodiments, part or all of the RF transceiver circuitry and baseband processing circuitry may be on the same chipset, and the application processing circuitry may be on a separate chipset. In yet other alternative embodiments, part or all of the RF transceiver circuitry, baseband processing circuitry, and application processing circuitry may be combined in the same chipset. Processing circuitry 215 may include, for example, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), and/or one or more field programmable gate arrays (FPGAs).

In particular embodiments, some or all of the functionality described herein as being provided by a wireless device may be provided by the processing circuitry 215 executing instructions stored on a computer-readable storage medium 230. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 215 without executing instructions stored on a computer-readable medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a computer-readable storage medium or not, the processing circuitry can be said to be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry 215 alone or to other components of UE 200, but are enjoyed by the wireless device as a whole, and/or by end users and the wireless network generally. Antenna 205, radio front-end circuitry 210, and/ or processing circuitry 215 may be configured to perform any receiving operations described herein as being performed by a wireless device. Any information, data and/or signals maybe received from a network node and/or another wireless device.

The processing circuitry 215 may be configured to perform any determining operations described herein as being performed by a wireless device. Determining as performed by processing circuitry 215 may include processing information obtained by the processing circuitry 215 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the wireless device, and/ or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Antenna 205, radio front-end circuitry 210, and/ or processing circuitry 215 may be configured to perform any transmitting operations described herein as being performed by a wireless device. Any information, data and/ or signals may be transmitted to a network node and/or another wireless device.

Computer-readable storage medium 230 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by a processor as well as data an information used by, or produced by processing circuitry 215. Examples of computer- readable storage medium 230 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory computer- readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 215. In some embodiments, processing circuitry 215 and computer-readable storage medium 230 may be considered to be integrated.

Alternative embodiments of UE 200 may include additional components beyond those shown in Figure 2 that may be responsible for providing certain aspects of the UE's functionality, including any of the functionality described herein and/or any functionality necessary to support the solution described herein. As just one example, UE 200 may include input interface 220 which may comprise interfaces, devices and circuits, and output interface 225 which may comprise output interfaces, devices and circuits. Input interface 220 is configured to allow input of information into UE 200, and is connected to processing circuitry 215 to allow processing circuitry 215 to process the input information. For example, input interface 220 may include a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input elements. Output interface 225 is configured to allow output of information from UE 200, and is connected to processing circuitry 215 to allow processing circuitry 215 to output information from UE 200. For example, output interface 225 may include a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output elements. Using one or more input interface 220 and/or output interface 225, UE 200 may communicate with end users and/ or the wireless network, and allow them to benefit from the functionality described herein.

UE 200 may include power source 235. Power source 235 may comprise power management circuitry. Power source 235 may receive power from a power supply, which may either be comprised in, or be external to, power source 235. For example, UE 200 may comprise a power supply in the form of a battery or battery pack which is connected to, or integrated in, power source 235. Other types of power sources, such as photovoltaic devices, may also be used. As a further example, UE 200 may be connectable to an external power supply (such as an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power supply supplies power to power source 235. Power source 235 may perform any conversion, transform, or adaptation needed to ensure that the power from the external power supply is safe for use with the components of UE 200. Power source 235 may be connected to all or some of the components of UE 200 and may be configured to supply UE 200, including processing circuitry 215, with power for performing the functionality described herein.

UE 200 may also include multiple sets of processing circuitry 215, computer- readable storage medium 230, radio circuitry 210, and/or antenna 205 for different wireless technologies integrated into wireless device 200, such as, for example, GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chipsets and other components within wireless device 200.

Figure 4 illustrates a flowchart for handling in-device coexistence problems, in accordance with particular embodiments. The embodiment depicted in Figure 4 involves three separate devices, a first network node, a second network node and a wireless device. The first network node is a controlling network node while the second network node is a secondary network node. The two network nodes may comprise different technologies, operate at different frequencies, and/or rely on different protocols and standards. For ease of explanation, it will be assumed that the wireless device is a UE, that the controlling network node is an eNB providing an LTE wireless connection, and that the secondary network node is a WLAN access point (AP) providing a Wi-Fi based WLAN wireless connection. The AP may provide a plurality of wireless signals, any one of which may be used by the UE for a WLAN connection. Although the flowchart will be described in terms of these specific devices, it should be apparent that the method is equally suited for use by any of a variety of different devices.

Traditionally, prior eNBs would not be made aware of the cause of the

UE's IDC issues. More specifically, the eNB would not know that IDC issues between the LTE connection and the WLAN connection were caused by the eNB requested WLAN usage. The eNB would simply assume that any interference issues were due to some wireless action or feature being performed by the UE (e.g., connecting to a WLAN because the end user wanted to download a movie that could only be downloaded over Wi-Fi). Based on this assumption, the eNB would adjust the LTE configuration in an attempt to reduce or eliminate the interference. However, this has the drawback that the LTE performance maybe degraded just to solve the IDC problem, when it may have been better to solve the IDC issues by stop the UE from using WLAN.

Unlike traditional systems, in particular embodiments, the eNB (or some other network node in communication with the eNB) is able to determine how to reconfigure the UE using an indication from the UE of whether or not the UE is experiencing IDC issues caused by the eNB's requested WLAN configuration. For example, if the UE indicates that there are IDC issues and these are caused by the UE operating a WLAN interworking feature which the network controls to some extent, then the eNB may decide to stop the WLAN interworking feature to solve the IDC issues rather than disturbing the LTE connection. Alternatively, the eNB may decide that in the current situation it is more beneficial to allow the UE to continue to use the WLAN interworking feature and instead adjust the UE 's LTE configuration to solve the IDC issues. For example, the eNB may change the UE's LTE carrier (e.g., change the PCell, or change the UE's LTE carrier aggregation or dual connectivity configuration (e.g., change or de-configure certain LTE carriers for the UE)).

The method begins at step 400 with establishing a first wireless connection between the UE and the eNB. In this embodiment, the first wireless connection may be established according the procedures and protocols of LTE and may be referred to as the LTE connection.

At step 405 the eNB sends the UE a configuration message. At step 410 the UE receives the configuration message from the eNB. The configuration message comprises configuration information for a second wireless connection with the AP. In this embodiment, the second wireless connection may be established according the procedures and protocols of Wi-Fi and may be referred to as the WLAN connection. Depending on the embodiment and/or scenario the configuration information may be for the UE to use the WLAN now or in the near future. This may allow, for example, the UE to perform WLAN measurements (e.g., the UE may receive WLAN measurement configuration), steer some or all traffic to the AP via the WLAN (e.g. UE receives WLAN mobility set), etc. In some embodiments, the configuration message sent at step 405 may comprise a request for the UE to make and/or report the WLAN measurements.

The way in which the eNB provides the UE with the configuration message may vary depending on the embodiment and/or scenario. For example, if the eNB and the UE are to use WLAN interworking/integration, the configuration message may comprise an RRC configuration message sent from the eNB requesting the UE to use the specified WLAN connection. At step 415 the UE determines whether the WLAN connection or the LTE connection is experiencing, or will experience, interference. The interference may arise from external sources (e.g., a running microwave oven, a neighbour's use of their own WLAN, etc.) or internal sources giving rise to IDC issues. For example, the wireless interface for the WLAN connection may cause interference for the wireless interface for the LTE connection. As another example, the UE's Bluetooth interface may be causing interference with either the WLAN connection or the LTE connection.

If there is no interference, the method may return to step 415 where the UE may operate as configured and may continue to check for interference. The interference checks may be done periodically (e.g., every 5 minutes), on a schedule (e.g., once every 100 TTIs), in response to an event (e.g., a change in signal quality that exceeds a threshold), when instructed (e.g., upon receipt of a request message from the eNB), or on any other suitable basis.

At step 420 the UE determines if there are any options available for the

UE to mitigate the interference on its own. For example, if the interference is due to an internal Bluetooth transceiver of the UE, the UE may determine whether it is possible to turn off the Bluetooth transceiver. As another example, the UE may determine if the UE can use a different wireless signal for the WLAN connection with the AP. If the UE determines that there are one or more options available to mitigate the interference, then the method may proceed to step 445 where the mitigation action is implemented.

In some embodiments, according to some WLAN integration mechanisms defined by 3GPP, the UE can be configured with a set of WLAN identifier(s). This set of WLAN identifiers may be referred to as a "mobility set." The UE is then able to connect to a WLAN matching those WLAN identifier(s) in the mobility set. Some of the WLAN identifiers may match several WLAN APs. In some scenarios, the IDC issues may arise from connecting to a subset of those WLAN APs that are currently available to the UE. For example, the eNB may request the UE to connect to a WLAN with SSID = X. And there may be one WLAN AP with SSID X in the 2.4 GHz band and another WLAN AP with SSID X in the 5 GHz band. As illustrated in the scenario of Figure 3, the IDC issues may only occur if the UE connects to a WLAN in the 2.4 GHz band. In such a scenario, in some embodiments, the WD may select the WLAN band that is free of the interference, such as the 5GHz band. Because each of the possible WLAN connections in the mobility set do not cause interference, the UE may determine there is no interference (step 415), that there are options (step 420) or that requested configuration does not cause interference (step 425). In some embodiments, the UE may determine that there are no options if any of the WLAN signals to which the UE may connect (based on the eNB-provided configuration information) would cause IDC issues. For example, even though the AP offers a WLAN connection in the 5 GHz band, because the WLAN connection in the 2.4 GHz band would cause IDC issues, the UE would, at step 430, send a message comprising an indication that it would experience, or is experiencing, IDC issues based on the eNB provided configuration message. In other embodiments, in the same scenario, the UE may determine there are no options if all of the possible WLANs with which the UE may connect to (based on the eNB-provided configuration). For example, with the AP providing WLAN connections in both the 2.4 GHz and 5 GHz band, the UE would not send the indication since the UE may, at step 445, connect to the WLAN in 5 GHz band and hence avoid IDC issues.

At step 425 the UE determines whether the interference is due to the configuration information in the configuration message. In some embodiments, such as where the AP provides the UE with an option to select from multiple possible wireless signals for the WLAN connection (e.g., the AP supports wireless connections in multiple frequency bands), the UE may determine that the configuration information is causing the IDC interference if each of the possible wireless signals provided by the AP cause, or will cause, the IDC issues. In other embodiments, in the same situation, the UE may determine that the configuration information is causing the IDC interference if any of the possible wireless signals provided by the AP cause the IDC issues. Regardless of how the UE makes the determination, once it is made, the method either proceeds to step 430 and an indication of the IDC issues is provided to the eNB or the method proceeds to step 450 and an indication of interference (without an indication of IDC issues) is provided to the eNB. The inclusion, or absence, of an indication of any IDC issues allows the eNB to consider whether to solve the interference the UE is experiencing by stopping or modifying the UE's use of the WLAN connection in order to protect the UE's LTE communication, or by adjusting the UE's LTE connection. In the embodiment depicted in Figure 4, IDC issues are mitigated by adjusting the WLAN connection and interference without IDC issues are mitigated by adjusting the LTE connection. Other embodiments and/or scenarios may take different mitigating actions (e.g., different steps 440 or 455) for different scenarios. These maybe based on other factors such as signal quality, network load of the AP and/or its associated network, network load of the eNB and/or it associated network, operator preference, user preference, etc.

At step 430, if the UE determines that the interference is due to the configuration information in the configuration message, and that the UE is unable to mitigate the interference on its own, the UE provides the eNB with an indication that the interference is due to the configuration information in the configuration message. This indication is received by the eNB in a message at step 435. The indication alerts the eNB that the UE is experiencing IDC issues based on the configuration information provided by the eNB. This indication can be used by the eNB to determine how to re-configure the UE such that the IDC issues are avoided or mitigated.

Depending on the embodiment, the indication maybe provided in a radio resource control (RRC) message or using media access control (MAC) signalling. MAC signalling may be slightly quicker that RRC signalling which may allow the eNB to be made aware of IDC issues quicker compared to RRC signalling. RRC signalling may be slightly more robust, dynamic and extensible compared to RRC signalling which may allow for improved information sharing, compared to MAC signalling. In some embodiments, the message sent by the UE may comprise information about a cause of the interference. The eNB may consider this information when assisting the UE in solving the IDC issues.

In some embodiments, the indication may be signalled in an IDC indication message (e.g., inDeviceCoexistencelndication). For example, the indication may be implemented as a bit flag-indicator which the UE sets to one value (e.g., 1 for true) if the UE wants to indicate that it is experiencing IDC issues due to the eNB's requested WLAN configuration and another value (e.g. o for false) otherwise. In certain embodiments, the indication may comprise an indicator which, if present indicates that the UE is experiencing IDC issues due to the eNB's requested WLAN configuration, and otherwise the indicator is not present. An example of how this can be done is provided in below.

In some embodiments, in addition to the IDC problem, the UE may indicate additional information in (or alongside) the indication. For example, the UE may indicate which WLAN channel(s) gave rise to the IDC issues. In another embodiment, the UE may indicate the WLAN band the UE was using which caused the IDC issues to arise (e.g., 2.4GHz or 5GHz band). In some embodiments, the UE may indicate one or more WLAN identifier(s) associated with the WLAN that is causing (or would cause) the IDC issues. This may be the WLAN's basic service set identifier (BSSID) and/or homogeneous extended service set identifier (HESSID) and/or service set identifier (SSID). This additional information may allow the eNB to configure the UE such that the UE does not connect to the problematic WLAN (e.g., remove that particular WLAN from the UE 's WLAN mobility set).

Below is an example implementation of providing an indication of the IDC issues experienced by the UE in the LTE RRC specification. In particular, the UE uses a flag to indicate that the UE is experiencing, or expects to experience, IDC issues based on the result of a configuration that the eNB has provided for the UE. In this example the flag named "eutran-CausedWLAN- IDC-problems" is included by the UE if the IDC issues are due to the eNB provided WLAN configuration for the UE.

Signalling radio bearer: SRBi

RLC-SAP: AM

Logical channel: DCCH

Direction: UE to E-UTRAN

InDeviceCoexIndication message

—ASNlSTART

InDeviceCoexIndication-rn ::= SEQUENCE {

criticalExtensions CHOICE {

ci CHOICE {

inDeviceCoexIndication-rii InDeviceCoexIndication-rn-IEs, spares NULL, spare2 NULL, sparei NULL

criticalExtensionsFuture SEQUENCE {}

}

InDeviceCoexIndication-rn-IEs ::= SEQUENCE {

ajfectedCarrierFreqList-rii AffectedCarrierFreqList-rii

OPTIONAL,

tdm-Assistancelnfo-ni TDM-Assistancelnfo-ni

OPTIONAL,

lateNonCriticalExtension OCTET STRING

OPTIONAL,

nonCriticalExtension InDeviceCoexIndication-ri3-IEs

OPTIONAL

}

InDeviceCoexIndication-ri3-IEs ::= SEQUENCE {

eutran-CausedWLAN-IDC-problems ENUMERATED {true}

OPTIONAL,

nonCriticalExtension SEQUENCE {}

OPTIONAL

}

AffectedCarrierFreqList-ru ::= SEQUENCE (SIZE (i..maxFreqIDC-rii)) OF AjfectedCarrierFreq-m

AffectedCarrierFreq-ru : : = SEQUENCE {

carrierFreq-m MeasObjectld,

interferenceDirection-ni ENUMERATED {eutra, other, both, spare}

}

TDM-Assistancelnfo-ru ::= CHOICE {

drx-Assistancelnfo-ru SEQUENCE { drx-CycleLeng th-ni ENUMERATED {sf40, sf64, sf8o,

sf256, spare2, sparei}, drx-Ojfset-ru INTEGER (0..255) OPTIONAL, drx-ActiveTime-m ENUMERATED {sf20, sf30, sf40, sf6o, sf8o,

sfioo, spare2, sparei} λ

idc-SubframePatternList-rii IDC-SubframePatternList-m,

}

IDC-SubframePatternList-ru : : = SEQUENCE (SIZE

(i..maxSubframePatternIDC-rn)) OF IDC-SubframePattern-rii

IDC-SubframePattern-ru ::= CHOICE {

subframePatternFDD-rii BIT STRING (SIZE (4)), subframePatternTDD-rii CHOICE {

subframeConfigo-rii BIT STRING (SIZE (70)), subframeConfigi-5-rii BIT STRING (SIZE (10)), subframeConfig6-rii BIT STRING (SIZE (60))

}

- ASNiSTOP

In addition to a one-bit indication, such as inDeviceCoexistencelndi cation the message may include additional information about the IDC issues the UE is experiencing. For example, the message may include the LTE frequencies that are suffering from the interference as well as additional TDM information that could solve the problem. In addition, in some embodiments, the UE may also include frequency information of the problematic WLAN frequencies. In some embodiments, the UE may provide measurement object IDs related to WLAN measurements to indicate problematic WLAN frequencies.

In certain embodiments, the indication may be signalled in a WLAN failure information message (or "WLAN association status indication" message). One benefit of signalling this indication in the WLAN failure message is that the UE may take additional actions when triggering the transmission of the WLAN failure message. These additional actions may include suspending traffic on the WLAN connection and continuing communication on the LTE connection. In particular embodiments, the indication of the IDC issues may be signalled in a WLAN measurement reporting message sent to the eNB. For example, if the eNB has configured the UE to perform WLAN measurement reporting and the UE triggers the transmission of a measurement report, the UE may include in the measurement report an indication whether the UE expects that a certain WLAN would cause IDC issues if used. This may allow the eNB to know which WLAN may cause IDC issues prior to requesting the UE to connect to a WLAN. The eNB may then select a WLAN that is least likely to cause IDC issues.

In some embodiments, how the indication is signalled to the eNB may depend on how the UE is configured to use WLAN. For example, when the UE is configured with WLAN measurement reporting, but not with operating LTE WLAN integration/interworking/aggregation, the UE may provide the IDC indication within an IDC indication message or WLAN measurement report. However, when the UE is configured using LTE WLAN integration/interworking/aggregation, the IDC indication may be included in a WLAN failure information message or a WLAN association status indication message, in which case the UE could also take additional actions such as suspending WLAN operation and continuing traffic on LTE.

In certain embodiments, the UE may determine how to signal the indication based on which messages the UE is configured to send. For example, if the UE is configured to send the IDC indication message (inDeviceCoexistencelndication) then the UE may include in this message the indication that the IDC problem is based on the WLAN configuration proposed by the eNB. If the UE is not configured to send the IDC indication message (inDeviceCoexistencelndication), then the UE may instead include it in the WLAN failure information message (or "WLAN association status indication" message). Other combinations of which messages to use in which scenarios are also possible.

Whether the UE sends the indication or not may be based on network configuration and/ or capabilities of the UE. This may allow a UE to work with a eNB that does not have this feature enabled (or that does not support this indication) and conversely for an eNB to work with a UE that does not have this feature enabled (or that does not support this indication). In some embodiments, it may be configured such that by default the UE does not include the indication that it is experiencing IDC issues. The UE will only send the indication if the eNB has configured the UE to do so (e.g., signalled the UE to provide this indication). In some embodiments, the request to send the indication may be explicit or implicit in the configuration message requesting the UE to use the WLAN.

In some embodiments, when the UE expects IDC issues to occur, the UE may send an indication of the IDC issues, with or without an indication that the IDC issues are based on the eNB provided WLAN configuration. For example, in the scenario depicted in Figure 3, where the LTE connection is on band 40, if the eNB has sent a configuration message instructing the UE to use a WLAN connection on a 2.4GHz band, the UE may first try to solve the problems internally (e.g., switch to a 5GHz WLAN connection from the same AP). If it cannot solve the problem internally, then the UE may indicate to the eNB that the serving cell on band 40 is having an IDC issue based on the 2.4GHz WLAN connection configured by the eNB. The eNB can then decide whether to handover the UE to another frequency, reconfigure the WLAN connection, or reconfigure the cell or LTE connection.

In particular embodiments, the UE may send the IDC indication when configured to obtain and report WLAN measurements. In some scenarios it may be that measurements for some of the WLANs indicated in the configuration can be obtained while other WLAN measurements cannot be obtained without causing IDC issues. In some embodiments, when the UE is configured to obtain WLAN measurements, and taking these measurements causes IDC problem(s) to arise, the UE may include information regarding the WLAN measurement configuration (e.g., pointer or index of the WLAN measurement configuration, WLAN Measurement object, WLAN measurement reporting configuration or WLAN Measurement ID). In certain embodiments, the UE may indicate the frequencies that are suffering from IDC issues. In some embodiments, the eNB may determine that those WLANs for which no measurements are reported are WLANS that are causing, or will cause, IDC issues for the UE. At step 440 the eNB sends the UE a second configuration message modifying either the LTE or the WLAN connection in order to reduce or eliminate the interference. The type of mitigation action employed may vary depending on a variety of factors such as signal quality, network load of the AP and/or its associated network, network load of the eNB and/or it associated network, operator preference, user preference, other circumstances observed by the eNB as well as by the information in the indication provided by the UE at step 435. The second configuration message is received by the UE at step 410 and the method proceeds again from there.

In certain embodiments, the eNB may also consider other parameters when deciding whether to reconfigure the LTE connection or the WLAN connection of the UE. For example, if the LTE network is heavily loaded, then it may be beneficial to let the UE continue to use the WLAN connection (or perhaps modify the WLAN connection as in step 440) so that the UE consumes less resources in LTE. However, if LTE is not heavily loaded it may be better to let the UE use LTE resources rather than use the WLAN resources that are causing the IDC issues. Other parameters which may be considered include, but are not limited to: UE subscription information, load in WLAN, type of traffic the UE uses, WLAN quality, LTE quality, the services be run by, or for, the UE (e.g., streaming, real-time communication, etc.) etc. Other options the eNB may consider are to handover the UE to the other frequencies, remove (in case of carrier aggregation (CA)) the problematic cell or configure the UE with a discontinuous reception (DRX) configuration which would solve the problem.

At step 445, if the UE has determined that it can reduce the interference on it is own, it may implement one or more mitigation actions. For example, if the UE determines the interference is caused by its Bluetooth transmitter, the UE may try turning off the Bluetooth transmitter. In some embodiments, if the UE determines that the IDC issues can be solved in a TDM-manner (e.g., by multiplexing the use of the interfering transceivers in time) the UE may indicate a bit-map or DRX cycles to the eNB which indicates which TTIs are affected by IDC interference. At step 450 if there is interference, and the interference cannot be mitigated by the UE, and the interference is not due to the configuration provided by the eNB, the UE provides the eNB with a message containing an indication that the UE is experiencing interference. This message does not include an indication of any IDC issues or includes an explicit indication that the interference is not based on the configuration information provided by the eNB.

At step 455 if the message from the UE does not include an indication that the interference is due to the configuration message, then the eNB may modify the LTE connection. Prior to the embodiments disclosed herein, this was the only option for an eNB. That is, the eNB would always attempt to cure interference, by adjusting the LTE connection because it would not know if the interference was caused by the WLAN configuration the eNB requested the WD to use.

The steps described above are merely illustrative of certain embodiments.

It is not required that all embodiments incorporate all the steps above nor that the steps be performed in the exact order depicted in Figure 4. For example, in some embodiments, in some scenarios, the eNB may, after receiving the indication that the interference is due to the configuration message at step 435, determine that the best way to mitigate the interference is to modify the LTE connection (step 455) instead of reconfiguring the WLAN connection by sending the second configuration message at 440. Furthermore, some embodiments may include steps not illustrated in Figure 4. For example, in the scenario described above, after step 435, there maybe a step where the eNB determines the best mitigation action to take based on the received indication.

The steps illustrated in Figure 4, and described above, maybe performed through a computer program product that may, for example, be executed by the components and equipment illustrated in Figures 1 or 2. For example, storage 123 may comprise computer readable means on which a computer program can be stored. The computer program may include instructions which cause processor 122 (and any operatively coupled entities and devices, such as interface 121 and storage 123) to execute methods according to embodiments described herein. Similarly, storage 113 may comprise computer readable means on which a computer program can be stored. The computer program may include instructions which cause processor 112 (and any operatively coupled entities and devices, such as interface 111 and storage 113) to execute methods according to embodiments described herein. The computer program and/or computer program product may thus provide means for performing any steps herein disclosed. Any appropriate steps, methods, or functions may be performed through one or more functional modules, such as those depicted in Figure 5.

Figure 5 is a schematic block diagram illustrating the functional modules used in handling in-device coexistence issues, according to particular embodiments. In particular, there is depicted the functional modules of a particular wireless device 500 and network node 550. Each functional module may comprise software, computer programs, sub-routines, libraries, source code, or any other form of executable instructions that are executed by, for example, a processor. Other embodiments may include more, fewer, or different functional modules. Moreover, a single depicted module may represent multiple similar modules. For example, determine module 504 may be configured to make all relevant determinations disclosed herein, or it may comprise multiple different determine modules each module configured to make a subset of the relevant determinations disclosed herein such that collectively they make all the relevant determinations. The illustrated modules may further be configured to perform other functions or steps not explicitly described with respect to the respective module, including providing any features or functions disclosed with respect to any of the other figures.

Each functional module may be implemented in hardware and/or in software. For example, one or more or all functional modules may be implemented by processors 112 and/or 122, possibly in cooperation with storage 113 and/or 123. Processors 112 and/or 122 and storage 113 and/or 123 may thus be arranged to allow processors 112 and/or 122 to fetch instructions from storage 113 and/or 123 and execute the fetched instructions to allow the respective functional module to perform any steps or functions disclosed herein. In this Figure 5, wireless device 500 comprises connection module 502, receiver module 504, determine module 506, implementation module 508, and provider module 510; and network node 550 comprises connection module 552, transmitter module 554, implementation module 556, and receiver module 558.

Starting with the functional modules of wireless device 500, connection module 502 is configured to establish wireless connection 560 with network node 550. For purposes of simplicity in describing the functional modules of Figure 5, it may be assumed that wireless connection 560 is an LTE connection. Of course, other embodiments may involve other radio access technology for wireless connection 560.

Receiver module 504 is configured to receive a configuration message from network node 550. Typically, although not always, the configuration message will be sent via wireless connection 560. In some embodiments, the configuration message may be received via other means (e.g., a WLAN connection). The configuration message may include configuration information for a second wireless connection with a second network node. The second wireless connection (not depicted) may comprise a different wireless technology than wireless connection 560. For purposes of simplicity in describing the functional modules of Figure 5, it may be assumed that the second wireless connection is a WLAN connection using Wi-Fi. Of course, other embodiments may involve other radio access technology for the second wireless connection.

Determine module 506 is configured to determine whether the second wireless connection is causing or will cause interference with wireless connection 560, or vice-versa. Determine module 506 may further be configured to determine whether the interference is due to the configuration information in the configuration message received from network node 550. In some embodiments, determine module 506 may determine information about a cause of the detected interference. For example, the frequency or frequency range in which the interference is detected.

Implementation module 508 is configured to implement a first mitigation action that attempts to remove or reduce the interference. Implementation module 508 may be invoked upon determine module 506 determining that the interference is not due to the configuration information in the configuration message. This may arise, for example, where WD 500 experiences IDC issues caused by a Bluetooth transmitter in wireless device 500.

Provider module 510 is configured to, upon determine module 506 determining that the interference is due to the configuration information in the configuration message, provide network node 550 with an indication that the interference is due to the configuration information in the configuration message. In some embodiments, provider module 510 may be configured to provide the indication in a radio resource control (RRC) message. In some embodiments, provider module 510 may be configured to provide the indication using media access control (MAC) signalling. In some embodiments, the indication may comprise information about a cause of the interference, in addition to an indication as to whether the interference is due to the configuration information.

In some embodiments, the second network node may provide a plurality of wireless signals that are each available for use for the second wireless connection. Determine module 506 may then, in certain embodiments, determine whether using each of the plurality of wireless signals causes, or will cause, interference for wireless connection 560 or the WLAN connection. If each of the plurality of wireless signals causes, or will cause, interference then provider module 510 may provide network node 550 with an indication that the interference is due to the configuration information in the configuration message. In particular embodiments, determine module 506 may be configured to determine whether any of the plurality of wireless signals causes or will cause interference. If any of the plurality of wireless signals is causing or will cause interference, provider module 510 may be configured to provide network node 550 with an indication that the interference is due to the configuration information in the configuration message.

Now discussing the functional modules of network node 550, including the same assumptions made above, connection module 552 is configured to establish wireless connection 560 with wireless device 500. Transmitter module 554 is configured to send wireless device 500 a configuration message. The configuration message comprises configuration information for a second wireless connection with a second network node. The second wireless connection comprising a different wireless technology than the wireless connection 560.

Implementation module 556 is configured to implement a first or a second mitigation action to reduce or eliminate the interference depending on whether or not the received message comprises an indication that WD 500 is experiencing interference or IDC issues due to the configuration information in the configuration message. The first and second mitigation actions may be different. For example, in some scenarios the first mitigation action may comprise implementation module 556 sending WD 500 a second configuration message comprising updated configuration information for the second wireless connection. As another example, in some scenarios, the second mitigation action may comprise implementation module 556 modifying wireless connection 560.

Receiver module 558 is configured to receive a message comprising an indication that the wireless device is encountering interference with at least one of the first or the second wireless connections. The message may also comprise an indication as to whether or not the interference is the result of the information in the configuration message sent by transmitter module 554. In particular embodiments, the message may comprise information about a cause of the interference. In some embodiments, the indication of the IDC issues may be received in a radio resource control (RRC) message. In certain embodiments, the indication is received via media access control (MAC) signalling.

Certain aspects of the inventive concept have mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, embodiments other than the ones disclosed above are equally possible and within the scope of the inventive concept. Similarly, while a number of different combinations have been discussed, all possible combinations have not been disclosed. One skilled in the art would appreciate that other combinations exist and are within the scope of the inventive concept. Moreover, as is understood by the skilled person, the herein disclosed embodiments are as such applicable also to other standards and communication systems and any feature from a particular figure disclosed in connection with other features may be applicable to any other figure and or combined with different features.

Claims

1. A method for handling in-device coexistence issues, the method comprising:

establishing a first wireless connection with a first network node (400); receiving a configuration message, the configuration message comprising configuration information for a second wireless connection with a second network node, the second wireless connection comprising a different wireless technology than the first wireless connection (410);

determining whether the first wireless connection or the second wireless connection is experiencing, or will experience, interference (415); determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message (425); and

upon determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied (430).

2. The method of Claim 1, wherein the indication is provided in a radio resource control (RRC) message.

3. The method of Claim 1, wherein the indication is provided using media access control (MAC) signaling.

4. The method of Claim 1, wherein the indication is part of a message, the message comprises information about a cause of the interference.

5. The method of Claim 1, wherein:

the second network node provides a plurality of wireless signals, each wireless signal available for the second wireless connection;

determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message comprises determining whether using each of the plurality of wireless signals causes, or will cause, interference for the first wireless connection or the second wireless connection; and

upon determining that each of the plurality of wireless signals is causing or will cause interference, providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

6. The method of Claim 1, wherein:

determining whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message comprises determining whether using any of the plurality of wireless signals causes, or will cause, interference for the first wireless connection or the second wireless connection; and

upon determining that any of the plurality of wireless signals is causing or will cause interference, providing the first network node with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

7. The method of Claim 1, wherein upon determining that the interference is not due to the configuration based the configuration message, implementing a first mitigation action, the first mitigation action attempting to remove or reduce the interference (445).

8. A method for handling in-device coexistence issues, the method comprising:

establishing a first wireless connection with a wireless device (400); sending the wireless device a configuration message, the configuration message comprising configuration information for a second wireless connection with a remote network node, the second wireless connection comprising a different wireless technology than the first wireless connection (405);

receiving a message that the wireless device is encountering interference with at least one of the first or the second wireless connections (435);

upon the message comprising an indication that the interference is due to the configuration information in the configuration message, implementing a first mitigation action to reduce or eliminate the interference (440); and upon the message not comprising an indication that the interference is due to the configuration information in the configuration message, implementing a second mitigation action to reduce or eliminate the interference, the second mitigation action different than the first mitigation action (455).

9. The method of Claim 8, wherein the message is a radio resource control (RRC) message.

10. The method of Claim 8, wherein the message is received via media access control (MAC) signaling.

11. The method of Claim 8, wherein the message further comprises information about a cause of the interference.

12. The method of Claim 8, wherein implementing the first mitigation action comprises sending the wireless device a second configuration message, the second configuration message comprising updated configuration information for the second wireless connection (440).

13. The method of Claim 8, wherein implementing the second mitigation action comprises modifying the first wireless connection with the wireless device (455).

14. A wireless device (110) for handling in-device coexistence issues, the wireless device comprising:

interface circuitry (111) configured to:

establish a first wireless connection (130) with a first network node (120); and

receive a configuration message, the configuration message comprising configuration information for a second wireless connection (140) with a second network node (120a), the second wireless connection (140) comprising a different wireless technology than the first wireless connection (130);

processing circuitry (112) configured to:

determine whether the first wireless connection (130) or the second wireless connection (140) is experiencing, or will experience, interference; and

determine whether the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message; and

a power source (235) configured to provide the interface circuitry (111) and the processing circuitry (112) with power;

wherein, upon the processing circuitry (112) determining that the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message, the interface circuitry (111) is further configured to provide the first network node (120) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

15. The wireless device (110) of Claim 14, wherein the indication is provided in a radio resource control (RRC) message.

16. The wireless device (110) of Claim 14, wherein the indication is provided using media access control (MAC) signaling.

17. The wireless device (110) of Claim 14, wherein the indication is part of a message, the message comprises information about a cause of the interference.

18. The wireless device (110) of Claim 14, wherein:

the second network node (120a) provides a plurality of wireless signals, each wireless signal available for the second wireless connection (140);

the processing circuitry (112) configured to determine whether the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message is further configured to determine whether using each of the plurality of wireless signals causes, or will cause, interference for the first wireless connection (130) or the second wireless connection (140); and

upon the processing circuitry (112) determining that each of the plurality of wireless signals is causing or will cause interference, the interface circuitry (111) is further configured to provide the first network node (120) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in- device coexistence issues upon being applied.

19. The wireless device (110) of Claim 14, wherein:

the processing circuitry (112) configured to determine whether the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message is further configured to determine whether using any of the plurality of wireless signals causes, or will cause, interference for the first wireless connection (130) or the second wireless connection (140); and

upon the processing circuitry (112) determining that any of the plurality of wireless signals is causing or will cause interference, the interface circuitry (111) is further configured to provide the first network node (120) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in- device coexistence issues upon being applied.

20. The wireless device (110) of Claim 14, wherein upon the processing circuitry (112) determining that the interference is not due to the configuration based on the configuration message, the processing circuitry (112) is further configured to implement a first mitigation action, the first mitigation action attempting to remove or reduce the interference.

21. A network node (120) for handling in-device coexistence issues, the network node comprising:

interface circuitry (121) configured to:

establish a first wireless connection (130) with a wireless device

(110);

send the wireless device (110) a configuration message, the configuration message comprising configuration information for a second wireless connection (140) with a remote network node (120a), the second wireless connection (140) comprising a different wireless technology than the first wireless connection (130); and

receive a message that the wireless device (110) is encountering interference with at least one of the first or the second wireless connections (130, 140);

processing circuitry (122) configured to:

upon the message comprising an indication that the interference is due to the configuration information in the configuration message, implement a first mitigation action to reduce or eliminate the interference; and

upon the message not comprising an indication that the interference is due to the configuration information in the configuration message, implement a second mitigation action to reduce or eliminate the interference, the second mitigation action different than the first mitigation action; and

a power source configured to provide the interface circuitry (121) and the processing circuitry (122) with power.

22. The network node (120) of Claim 21, wherein the message is a radio resource control (RRC) message.

23. The network node (120) of Claim 21, wherein the message is received via media access control (MAC) signaling.

24. The network node (120) of Claim 21, wherein the message further comprises information about a cause of the interference.

25. The network node (120) of Claim 21, wherein the processing circuitry (122) configured to implement the first mitigation action is further configured to generate a second configuration message to be sent by the interface circuitry (121) to the wireless device (110), the second configuration message comprising updated configuration information for the second wireless connection (140).

26. The network node (120) of Claim 21, wherein the processing circuitry (122) configured to implement the second mitigation action is further configured to modify the first wireless connection (130) with the wireless device.

27. A user equipment, UE, (200) for handling in-device coexistence issues, said UE (200) comprising:

an antenna (205) configured to send and receive wireless signals; radio front-end circuitry (210) connected to the antenna (205) and to processing circuitry (215), the radio front-end circuitry (210) configured to condition signals communicated between the antenna (205) and the processing circuitry (215);

the processing circuitry (215) configured to:

establish a first wireless connection (130) with a first network node (120);

determine whether the first wireless connection (130) or the second wireless connection (140) is experiencing, or will experience, interference; determine whether the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message; and

upon determining that the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message, provide the first network node (120) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in- device coexistence issues upon being applied;

an input interface (220) connected to the processing circuitry (215) and configured to allow input of information into the UE (200) to be processed by the processing circuitry (215);

an output interface (225) connected to the processing circuitry (215) and configured to output information from the UE that has been processed by the processing circuitry (215); and a battery (235) connected to the processing circuitry (215) and configured to supply power to the UE (200).

28. The UE (200) of Claim 27, wherein the indication is provided in a radio resource control (RRC) message.

29. The UE (200) of Claim 27, wherein the indication is provided using media access control (MAC) signaling.

30. The UE (200) of Claim 27, wherein the indication is part of a message, the message comprises information about a cause of the interference.

31. The UE (200) of Claim 27, wherein:

the processing circuitry (215) configured to determine whether the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message is further configured to determine whether using each of the plurality of wireless signals causes, or will cause, interference for the first wireless connection (130) or the second wireless connection (140); and

upon the processing circuitry (215) determining that each of the plurality of wireless signals is causing or will cause interference, the processing circuitry (215) is further configured to provide the first network node (120) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

32. The UE (200) of Claim 27, wherein:

the processing circuitry (215) configured to determine whether the interference is due to the second wireless connection (140) being configured based on the configuration information in the configuration message is further configured to determine whether using any of the plurality of wireless signals causes, or will cause, interference for the first wireless connection (130) or the second wireless connection (140); and

upon the processing circuitry (215) determining that any of the plurality of wireless signals is causing or will cause interference, the processing circuitry (215) is further configured to provide the first network node (120) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in- device coexistence issues upon being applied.

33. The UE (200) of Claim 27, wherein upon the processing circuitry (215) determining that the interference is not due to the configuration based on the configuration message, the processing circuitry (215) is further configured to implement a first mitigation action, the first mitigation action attempting to remove or reduce the interference.

34. A wireless device (500) for handling in-device coexistence issues, the wireless device (500) comprising:

a connection module (502) configured to establish a first wireless connection (560) with a first network node (550);

a receiver module (504) configured to receive a configuration message, the configuration message comprising configuration information for a second wireless connection with a second network node, the second wireless connection comprising a different wireless technology than the first wireless connection (560);

a first determine module (506) configured to determine whether the first wireless connection (560) or the second wireless connection is experiencing, or will experience, interference;

a second determine module (506) configured to determine whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message; and

a provider module (510) configured to, upon determining that the interference is due to the second wireless connection being configured based on the configuration information in the configuration message, provide the first network node (550) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

35. The wireless device (500) of Claim 34, wherein the indication is provided in a radio resource control (RRC) message.

36. The wireless device (500) of Claim 34, wherein the indication is provided using media access control (MAC) signaling.

37. The wireless device (500) of Claim 34, wherein the indication is part of a message, the message comprises information about a cause of the interference.

38. The wireless device (500) of Claim 34, wherein:

the first determine module (506) configured to determine whether the interference is due to the second wireless connection being configured based on the configuration information in the configuration message is further configured to determine whether using each of the plurality of wireless signals causes, or will cause, interference for the first wireless connection or the second wireless connection; and

upon determining that each of the plurality of wireless signals is causing or will cause interference, the provider module (510) is further configured to provide the first network node (550) with an indication that applying the configuration information in the configuration message is causing in-device coexistence issues as applied, or will cause in-device coexistence issues upon being applied.

39. The wireless device (500) of Claim 34, wherein:

the second network node provides a plurality of wireless signals, each wireless signal available for the second wireless connection; and

the first determine module (506) configured to determine whether the second wireless connection is causing or will cause interference with the first wireless connection (560) is further configured to determine whether any of the plurality of wireless signals causes or will cause interference with the first wireless connection (560); and

upon determining that any of the plurality of wireless signals is causing or will cause interference, the provider module (510) is configured to provide the first network node (550) with an indication that the interference is due to the configuration information in the configuration message.

40. The wireless device (500) of Claim 34, further comprising an implementation module (508), wherein upon the second determine module (506) determining that the interference is not due to the configuration based on the configuration message, the implementation module (508) is configured to implement a first mitigation action, the first mitigation action attempting to remove or reduce the interference.

41. A network node (550) for handling in-device coexistence issues, the network node (550) comprising:

a connection module (552) configured to establish a first wireless connection (560) with a wireless device (500);

a transmitter module (554) configured to send the wireless device (500) a configuration message, the configuration message comprising configuration information for a second wireless connection with a remote network node, the second wireless connection comprising a different wireless technology than the first wireless connection (560);

a receiver module (558) configured to receive a message that the wireless device (500) is encountering interference with at least one of the first or the second wireless connections (560);

a first implementation module (556) configured to, upon the message comprising an indication that the interference is due to the configuration information in the configuration message, implement a first mitigation action to reduce or eliminate the interference; and

a second implementation module (556) configured to, upon the message not comprising an indication that the interference is due to the configuration information in the configuration message, implement a second mitigation action to reduce or eliminate the interference, the second mitigation action different than the first mitigation action.

42. The network node (550) of Claim 41, wherein the message is a radio resource control (RRC) message.

43. The network node (550) of Claim 41, wherein the message is received via media access control (MAC) signaling.

44. The network node (550) of Claim 41, wherein the message further comprises information about a cause of the interference.

45. The network node (550) of Claim 41, wherein the first implementation module (556) configured to implement the first mitigation action is further configured to send the wireless device (500) a second configuration message, the second configuration message comprising updated configuration information for the second wireless connection.

46. The network node of Claim 41, wherein the second implementation module (556) configured to implement the second mitigation action is further configured to modify the first wireless connection (560) with the wireless device (500).