In-device coexistence procedure enhancements

Abstract

Systems, apparatuses, and methods for enhancing in-device coexistence (IDC) interference reporting are described herein. A UE may receive configuration information indicating a target frequency for wireless communications by the UE. The UE may determine one or more affected frequency ranges relative to the target frequency, wherein IDC interference is detected or expected to occur in the one or more affected frequency ranges; and reporting the one or more affected frequency ranges.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems including affected frequencies that provide greater granularity for in-device coexistence (IDC) procedures. Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs) (commonly referred to within industry groups as Wi-Fi). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to facilitate communication between RAN base stations (which may also be often referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices, known as user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more radio access technologies (RATs) to perform communications between base stations and UEs. For example, GERAN implements GSM and / or EDGE RATs, UTRAN implements Universal Mobile Telecommunications System (UMTS) RATs or other 3GPP RATs, E-UTRAN implements LTE RATs (sometimes referred to herein as LTE), and NG-RAN implements NR RATs (sometimes referred to herein as 5G RATs, 5G NR RATs, or simply NR). In some deployments, E-UTRAN may also implement NR RATs. In some deployments, NG-RAN may also implement LTE RATs.

[0005] The base stations used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (often also referred to as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as a gNode B or gNB).

[0006] The RAN provides communication services together with external entities through its connection to the Core Network (CN). For example, E-UTRAN can utilize the Evolved Packet Core (EPC), while NG-RAN can utilize the 5G Core Network (5GC).

[0007] 5G NR frequency bands can be divided into two or more distinct frequency ranges. For example, Frequency Range 1 (FR1) may include frequency bands operating below 6 GHz, some of which may be used by previous standards and potentially expanded to cover new spectrum products from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Note that in some systems, FR2 may also include frequency bands from 52.6 GHz to 71 GHz (or higher). Frequency bands in the millimeter wave (mmWave) range of FR2 may have less coverage than those in FR1 but potentially higher available bandwidth. Those skilled in the art will recognize that these frequency ranges, provided by way of example, may change over time or from region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] To easily identify the discussion of any particular element or action, the most significant digit(s) in a reference number refers to the drawing number that first introduces that element.

[0009] Figure 1 A diagram illustrating coexistence interference within a wireless device according to some embodiments.

[0010] Figure 2 Graphs illustrating examples of coexistence interference according to some embodiments.

[0011] Figure 3 Illustrated is a frequency range of interest around a target frequency as configured by a network node according to some embodiments.

[0012] Figure 4 A flow chart illustrating a method for a UE according to some embodiments is illustrated.

[0013] Figure 5 A flow chart illustrating a method for a base station according to some embodiments is illustrated.

[0014] Figure 6 A flow chart illustrating a method for a SN in a wireless network configured for MR-DC according to some embodiments is illustrated.

[0015] Figure 7 A flow chart illustrating a method for a MN in a wireless network configured for MR-DC according to some embodiments is illustrated.

[0016] Figure 8An example architecture of a wireless communication system according to embodiments disclosed herein is illustrated.

[0017] Figure 9 A system for performing signaling between a wireless device and a network device according to embodiments disclosed herein is illustrated. DETAILED DESCRIPTION

[0018] Various embodiments are described with respect to a UE. However, reference to a UE is provided for illustrative purposes only. The example embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, a UE as described herein is used to represent any suitable electronic component.

[0019] One problem facing wireless communication systems is interference with wireless signals. In some cases, interference can originate from external devices. Furthermore, multiple radio access technologies (RATs) within a wireless system can also generate interference. This type of interference is referred to as inter-RAT interference. Two types of inter-RAT interference include inter-RAT harmonic interference and inter-RAT intermodulation distortion (IMD). Interference can degrade signal quality. Therefore, it is desirable to reduce the effects of interference on signals. Some embodiments herein provide systems, devices, and methods for reducing inter-RAT interference.

[0020] Figure 1 A diagram illustrates coexistence interference within a wireless device 100. As shown, the wireless device 100 may include multiple RATs. The RATs may include cellular 102, GPS 104, and Bluetooth / Wi-Fi (BT / WIFI 106). Inter-RAT harmonics (IMD) interference may occur between transmissions from one RAT and receptions from another RAT.

[0021] For example, LTE or NR transmissions may interfere with industrial, scientific, and medical (ISM) technologies (such as Bluetooth and / or WLAN) and / or the Global Navigation Satellite System (GNSS). Similarly, ISM and / or GNSS transmissions may interfere with cellular reception. Interference may include LTE uplink (UL) carrier aggregation (CA) IMD interference with wireless local area networks (WLAN), Bluetooth, and GNSS. Additionally, interference may include NR harmonics or LTE+NR dual connectivity (EN-DC) UL IMD interference with WLAN, Bluetooth, and GNSS in EN-DC.

[0022] Figure 2A diagram 200 illustrates an example of coexistence interference from an in-device ISM transmitter to an Evolved Universal Terrestrial Radio Access (E-UTRA) receiver. As shown, coexistence interference (i.e., inter-RAT interference) can result in unacceptable interference levels 202 for an LTE receiver. Embodiments herein provide mechanisms by which wireless communication systems can avoid inter-RAT interference. Specifically, some embodiments herein introduce an in-device coexistence (IDC) procedure, in which a UE can identify frequencies that may be experiencing interference due to coexisting RATs within the UE.

[0023] Some IDC solutions simply have the network configure the UE with an IDC Information Element (IE). The IDC IE configures the UE to report carrier frequencies affected by IDC interference. However, this reporting lacks the details that would allow the network to better mitigate interference, as the UE only reports the exact frequency, not the affected frequency range. Such IDC solutions can be limited by poor interference reporting. For example, the affected frequencies may not be adequately indicated.

[0024] The embodiments herein define a reporting mechanism that allows the UE to report the affected frequency range. When the UE transmits an IDC report, the network node may perform mitigation procedures. For example, the network node may perform a handover from the affected frequency range to another frequency range or release the affected frequency range.

[0025] In some embodiments, the UE detects the possibility of internal problems that the UE itself cannot resolve or internal problems caused by coexistence related to the use of certain radio resources. The UE provides information to the network node to assist the network node, which can limit the use of radio resources to avoid UE internal problems (or potential problems) caused by coexistence. Such IDC procedures can be used to resolve interference between 3GPP (including various multi-radio dual connectivity (MR-DC) architectures, namely NR-DC and EN-DC) and non-3GPP RATs (such as WiFi). Enhancements to frequency division multiplexing (FDM) solutions can allow for more granular indication of the affected frequencies (for example, at the bandwidth part (BWP) or physical resource block (PRB) level granularity).

[0026] For the FDM solution for IDC, three candidate options can be considered. In the first option, the center frequency of the actual affected frequency range plus the bandwidth can be reported. In the second option, the start frequency plus the end frequency of the actual affected frequency range can be reported. In the third option, the start frequency plus the bandwidth of the actual affected frequency range can be reported.

[0027] Some embodiments herein introduce a framework for IDC configuration and reporting. In some embodiments, a network node may provide an IDC configuration to a UE. The IDC configuration includes configuration information regarding a frequency range of interest (e.g., a frequency range in which the network wants to know if there is any inter-RAT interference). The network may provide the Absolute Radio Frequency Channel Number - New Radio (AFCN-NR) in the configuration information. The AFCN-NR is the center frequency of the frequency range of interest. In some embodiments, the configuration information may include a reference subcarrier spacing (SCS). The reference SCS may be used by the UE to report the frequency range in units of PRBs or Common Reference Blocks (CRBs). In some embodiments, the SCS may be specified as a default value (e.g., 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2). In some embodiments, the configuration information may include a frequency range of interest around the center frequency of the ARFCN-NR. In some embodiments, the frequency range of interest may be specified as a default value (e.g., 100 MHz for FR1 and 200 MHz for FR2).

[0028] Based on this configuration information, the UE may report one or more affected frequency ranges within the frequency range of interest of the network node. The UE may report affected frequency ranges within the frequency range of interest as indicated by the network (NW). If the affected frequency range is outside the frequency range of interest, the UE may not report it. The UE may indicate multiple problematic frequency ranges relative to a configured candidate frequency. The UE may report absolute frequencies.

[0029] For example, Figure 3 The figure illustrates a frequency range of interest 306 around a target frequency 308, as configured by a network node, according to some embodiments. The UE may report a candidate frequency index from the configured list (e.g., target frequency 308), an offset, and a direction bit to indicate whether the candidate frequency index is lower (left) or higher (right). The offset may indicate the distance from the target frequency 308 to the start, center, or end of the affected frequency range (e.g., possible affected frequency range 302, possible affected frequency range 304). The direction bit indicates whether the affected frequency range is above or below the target frequency 308. In some embodiments, the UE may report the absolute ARFCN for one or more affected frequency ranges.

[0030] In some embodiments, the UE may report the bandwidth of the affected frequency range as the number of PRBs or CRBs relative to the reference SCS as configured by the network node (e.g., 12*15kHz). In some embodiments, the UE may report the bandwidth of the affected frequency range as an integer value in MHz or KHz.

[0031] For example, in some embodiments, the UE may provide a report to the network node that includes a target frequency 308 index, a left / right indication (to indicate whether the affected frequency range is to the left / right of the target frequency 308), an offset of the center frequency of the affected frequency range (from the target frequency 308), and a number of PRBs relative to a reference SCS.

[0032] In some embodiments, the UE may provide a report to the network node that includes the target frequency 308 index, the positive / negative offset of the center frequency of the affected frequency range (to indicate left / right of the target frequency 308), and the number of PRBs relative to the reference SCS.

[0033] In some embodiments, the UE may report, for each affected frequency range, the ARFCN-NR of the center frequency of the affected frequency range and the number of PRBs relative to the reference SCS.

[0034] In some embodiments, the UE may report, for each affected frequency range, a target frequency 308 index, a left / right indication, and an offset (from the target frequency 308) of a near edge (e.g., edge 310) of the affected frequency range, and an offset of a far edge (e.g., edge 312) of the affected frequency range.

[0035] In some embodiments, the UE may report, for each affected frequency range, a target frequency 308 index, a positive / negative offset of a near edge (e.g., edge 310) of the affected frequency range (to indicate left / right of the target frequency), and a positive / negative offset of a far edge (e.g., edge 312) of the affected frequency range (to indicate left / right of the target frequency).

[0036] In some embodiments, the UE may report, for each affected frequency range, the ARFCN-NRs of both edges of the affected frequency range (eg, edge 310 and edge 312 of the possible affected frequency range 302).

[0037] In some embodiments, the UE may report, for each affected frequency range, the starting frequency of the frequency range and the number of PRBs relative to the reference SCS. In some embodiments, the starting frequency may be the target frequency 308 index, a left / right indication, and an offset from the near (or far) edge of the affected frequency range to the target frequency. In some embodiments, the starting frequency may be the target frequency 308 index and a positive or negative offset from the near (or far) edge of the affected frequency range to the target frequency.

[0038] In some embodiments, the UE may report the starting frequency in the absolute ARFCN-NR (e.g., the absolute ARFCN-NR of the lowest edge) and the number of PRBs relative to the reference SCS for each affected frequency range.

[0039] In some implementations, the UE may use a resource indication value (RIV) formula designed for BWP. The UE may report the starting frequency using the absolute ARFCN-NR or target frequency index of the lowest edge of the affected frequency range, and use the RIV formula to calculate the offset and number of PRBs / CRBs for each affected frequency block.

[0040] For MR-DC support, the secondary node (SN) may indicate the frequency range of interest for each target frequency to the master node (MN). The SN may indicate the reference SCS for each target frequency to the MN. The MN may send the affected frequency combination, including the frequency range for each affected frequency, to the SN.

[0041] Figure 4 A flow chart illustrating a method 400 for a UE according to embodiments herein is provided. The method 400 includes receiving 402, at a UE, configuration information from a base station, the configuration information indicating a target frequency for wireless communications by the UE. The method 400 includes determining 404, at the UE, one or more affected frequency ranges relative to the target frequency, in which IDC interference is detected or expected. The method 400 includes sending 406, from the UE to the base station, a message reporting the one or more affected frequency ranges.

[0042] In some embodiments of method 400, the configuration information indicating the target frequency includes an ARFCN-NR value.

[0043] In some embodiments of method 400, the configuration information further indicates a frequency range of interest relative to a target frequency for wireless communications by the UE, and the one or more affected frequency ranges are within the frequency range of interest indicated in the configuration information.

[0044] In some embodiments, method 400 further comprises determining a frequency range of interest relative to a target frequency for wireless communication by the UE based on a first default value in FR1 and a second default value in FR2, wherein one or more affected frequency ranges are within the frequency range of interest.

[0045] In some embodiments of method 400, the configuration information further indicates a reference SCS, and the message reports one or more affected frequency ranges in units of RBs based on the reference SCS.

[0046] In some embodiments, method 400 further includes determining a reference SCS based on a first default value in FR1 and a second default value in FR2, wherein the message reports the one or more affected frequency ranges in units of RBs based on the reference SCS.

[0047] In some embodiments of method 400, for each of the one or more affected frequency ranges, the message includes: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to the affected center frequency; and a number of RBs relative to a reference SCS to indicate the bandwidth relative to the affected center frequency. In some such embodiments, the message also includes a bit to indicate the direction from the target frequency to the affected center frequency. In some embodiments, the offset value is selected from a positive value and a negative value to indicate the direction from the target frequency to the affected center frequency.

[0048] In some embodiments of method 400, for each of the one or more affected frequency ranges, the message includes: an ARFCN of the affected center frequency; and a number of RBs relative to a reference SCS to indicate a bandwidth relative to the center frequency.

[0049] In some embodiments of method 400, for each of the one or more affected frequency ranges, the message includes: a target frequency index value corresponding to the target frequency; a first offset value from the target frequency to the near edge of the selected one of the one or more affected frequency ranges; and a second offset value from the target frequency to the far edge of the selected one of the one or more affected frequency ranges. In some such embodiments, the message also includes bits for indicating the direction from the target frequency toward the near edge and the far edge. In some embodiments, the first offset value and the second offset value are selected from positive and negative values ​​to indicate the direction from the target frequency toward the near edge and the far edge.

[0050] In some embodiments of method 400, for each of the one or more affected frequency ranges, the message includes: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to an edge of a selected one of the one or more affected frequency ranges; and a number of RBs relative to a reference SCS to indicate a bandwidth relative to the edge. In some such embodiments, the edge includes a starting frequency or an ending frequency of the selected one of the one or more affected frequency ranges. In certain embodiments, the message also includes a bit to indicate a direction from the target frequency to the edge. In certain embodiments, the offset value is selected from a positive value and a negative value to indicate a direction from the target frequency to the edge.

[0051] In some embodiments of method 400, for each of the one or more affected frequency ranges, the message includes: the ARFCN of the starting frequency of a selected one of the one or more affected frequency ranges; and the number of RBs relative to a reference SCS to indicate the bandwidth relative to the starting frequency.

[0052] In some embodiments of method 400, for each of the one or more affected frequency ranges, the message includes: an ARFCN of a starting frequency of a selected one of the one or more affected frequency ranges; and a RIV, wherein the offset and number of RBs of the one or more affected frequency blocks are capable of being derived from a formula based on the RIV.

[0053]

[0066] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 400. The apparatus may be, for example, an apparatus of a UE, such as wireless device 902 (UE), as described herein.

[0054] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 400. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 906 of wireless device 902 (UE), as described herein).

[0055] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuits operable to perform one or more elements of method 400. The apparatus may be, for example, an apparatus of a UE, such as wireless device 902 (UE), as described herein.

[0056] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 400. The apparatus may be, for example, a UE, such as wireless device 902 (UE), as described herein.

[0057] Implementations contemplated herein include signals as described in or associated with one or more elements of method 400 .

[0058] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 400. The processor may be a processor of a UE (such as the processor 904 of the wireless device 902 (UE), as described herein). The instructions may be located, for example, in the processor and / or in a memory of the UE (such as the memory 906 of the wireless device 902 (UE), as described herein).

[0059] Figure 5 A flow chart illustrating a method 500 for a base station according to embodiments herein is provided. The method 500 includes sending 502 configuration information from the base station to a UE, the configuration information indicating a target frequency for wireless communications by the UE. The method 500 includes receiving 504 a message at the base station from the UE reporting one or more affected frequency ranges relative to the target frequency, in which IDC interference is detected or expected at the UE. The method 500 includes generating 506 a response for coordinating radio resource usage of the UE to avoid or reduce IDC interference. The method 500 includes sending 508 the response from the base station to the UE.

[0060] In some embodiments of method 500, the configuration information indicating the target frequency includes an ARFCN-NR value.

[0061] In some embodiments of method 500, the configuration information further indicates a frequency range of interest relative to a target frequency for wireless communications by the UE, and the one or more affected frequency ranges are within the frequency range of interest indicated in the configuration information.

[0062] In some embodiments of method 500, the configuration information further indicates a reference SCS, and the message reports one or more affected frequency ranges in units of RBs based on the reference SCS.

[0063] In some embodiments of method 500, for each of the one or more affected frequency ranges, the message includes: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to the affected center frequency; and a number relative to the reference SCS indicating the bandwidth relative to the affected center frequency. In some such embodiments, the message also includes a bit indicating the direction from the target frequency to the affected center frequency. In certain embodiments, the offset value includes a positive or negative value to indicate the direction from the target frequency to the affected center frequency.

[0064] In some embodiments of method 500, for each of the one or more affected frequency ranges, the message includes: an ARFCN of the affected center frequency; and a number of RBs relative to a reference SCS to indicate a bandwidth relative to the center frequency.

[0065] In some embodiments of method 500, for each of the one or more affected frequency ranges, the message includes: a target frequency index value corresponding to the target frequency; a first offset value from the target frequency to the near edge of a selected one of the one or more affected frequency ranges; and a second offset value from the target frequency to the far edge of the selected one of the one or more affected frequency ranges. In some such embodiments, the message also includes bits for indicating the direction from the target frequency toward the near edge and the far edge. In some embodiments, the first offset value and the second offset value include positive or negative values ​​to indicate the direction from the target frequency toward the near edge and the far edge.

[0066] In some embodiments of method 500, for each of the one or more affected frequency ranges, the message includes: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to the edge of a selected one of the one or more affected frequency ranges; and a number of RBs relative to a reference SCS to indicate the bandwidth relative to the edge. In some such embodiments, the edge includes a starting frequency or an ending frequency of the selected one of the one or more affected frequency ranges. In certain embodiments, the message also includes a bit to indicate the direction from the target frequency to the edge. In certain embodiments, the offset value includes a positive or negative value to indicate the direction from the target frequency to the edge.

[0067] In some embodiments of method 500, for each of the one or more affected frequency ranges, the message includes: the ARFCN of the starting frequency of a selected one of the one or more affected frequency ranges; and the number of RBs relative to a reference SCS to indicate the bandwidth relative to the starting frequency.

[0068] In some embodiments of method 500, for each of the one or more affected frequency ranges, the message includes: an ARFCN of a start frequency of a selected one of the one or more affected frequency ranges; and a RIV. In some such embodiments, the embodiment further includes: determining an offset and a number of RBs of the one or more affected frequency blocks using a formula based on the RIV.

[0069] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 500. The apparatus may be, for example, an apparatus of a base station, such as network device 918 (base station), as described herein.

[0070] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 500. The non-transitory computer-readable medium may be, for example, a memory of a base station (such as memory 922 of network device 918 (base station), as described herein).

[0071] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuits operable to perform one or more elements of method 500. The apparatus may be, for example, a base station, such as network device 918 (base station), as described herein.

[0072] Embodiments contemplated herein include an apparatus comprising one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 500. The apparatus may be, for example, a base station, such as network device 918 (base station), as described herein.

[0073] Implementations contemplated herein include signals as described in or associated with one or more elements of method 500 .

[0074] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element causes the processing element to perform one or more elements of method 500. The processor may be a processor of a base station (such as processor 920 of network device 918 (base station), as described herein). These instructions may be located, for example, in the processor and / or in a memory of the base station (such as memory 922 of network device 918 (base station), as described herein).

[0075] Figure 6A flow chart illustrates a method 600 for a SN in a wireless network configured for MR-DC. The method 600 includes sending 602, from the SN to the MN, a first indication of a frequency range of interest for one or more target frequencies. The method 600 also includes sending 604, from the SN to the MN, a second indication of a reference subcarrier spacing (SCS) for the one or more target frequencies. The method 600 also includes receiving 606, at the SN, from the MN, a message indicating an affected frequency range for the one or more target frequencies, in which in-device coexistence (IDC) interference is detected or expected.

[0076] Additionally, according to some embodiments, reference Figure 5 Elements and embodiments described for method 500 may be included in method 600 .

[0077] Figure 7 A flow chart illustrating a method 700 for a mobile station (MN) in a wireless network configured for MR-DC is provided. The method 700 includes receiving 702 at the MN from a network service provider (SN) a first indication of a frequency range of interest for one or more target frequencies. The method 700 includes receiving 704 at the MN from the SN a second indication of a reference subcarrier spacing (SCS) for the one or more target frequencies. The method 700 includes sending 706 from the MN to the SN a message indicating an affected frequency range for the one or more target frequencies in which IDC interference is detected or expected.

[0078] Additionally, according to some embodiments, reference Figure 5 Elements and embodiments described for method 500 may be included in method 700 .

[0079] Figure 8 An example architecture of a wireless communication system 800 according to the embodiments disclosed herein is illustrated. The following description is provided for an example wireless communication system 800 operating in conjunction with the LTE system standard and / or the 5G or NR system standard provided in the 3GPP technical specifications.

[0080] like Figure 8 As shown, wireless communication system 800 includes UE 802 and UE 804 (although any number of UEs may be used). In this example, UE 802 and UE 804 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing device configured for wireless communication.

[0081] UE 802 and UE 804 can be configured to be communicatively coupled to RAN 806. In an embodiment, RAN 806 can be an NG-RAN, E-UTRAN, etc. UE 802 and UE 804 utilize connections (or channels) (shown as connection 808 and connection 810, respectively) with RAN 806, where each connection (or channel) includes a physical communication interface. RAN 806 may include one or more base stations (such as base station 812 and base station 814) that implement connection 808 and connection 810.

[0082] In this example, connection 808 and connection 810 are the air interfaces that enable such communicative coupling and may conform to the RAT used by RAN 806 , such as, for example, LTE and / or NR.

[0083] In some embodiments, UE 802 and UE 804 may also directly exchange communication data via side link interface 816. UE 804 is shown as being configured to access an access point (shown as AP 818) via connection 820. For example, connection 820 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, wherein AP 818 may include a Wi-Fi ® In this example, AP 818 may not be connected to another network (eg, the Internet) through CN 824.

[0084] In an embodiment, UE 802 and UE 804 may be configured to communicate with each other or with base station 812 and / or base station 814 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communication) or a single-carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this respect. An OFDM signal may include multiple orthogonal subcarriers.

[0085] In some embodiments, all or part of base station 812 or base station 814 may be implemented as one or more software entities running on a server computer as part of a virtual network. Additionally, or in other embodiments, base station 812 or base station 814 may be configured to communicate with each other via interface 822. In embodiments where wireless communication system 800 is an LTE system (e.g., when CN 824 is an EPC), interface 822 may be an X2 interface. This X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to an EPC and / or between two eNBs connected to an EPC. In embodiments where wireless communication system 800 is an NR system (e.g., when CN 824 is a 5GC), interface 822 may be an Xn interface. This Xn interface may be defined between two or more base stations (e.g., two or more gNBs, etc.) connected to a 5GC, between base station 812 (e.g., a gNB) and an eNB connected to a 5GC, and / or between two eNBs connected to a 5GC (e.g., CN 824).

[0086] RAN 806 is shown as being communicatively coupled to CN 824. CN 824 may include one or more network elements 826 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 802 and users of UE 804) connected to CN 824 via RAN 806. The components of CN 824 may be implemented in one physical device or separate physical devices that include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0087] In an embodiment, CN 824 may be an EPC, and RAN 806 may be connected to CN 824 via an S1 interface 828. In an embodiment, S1 interface 828 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between base station 812 or base station 814 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between base station 812 or base station 814 and a mobility management entity (MME).

[0088] In an embodiment, CN 824 may be a 5GC, and RAN 806 may be connected to CN 824 via an NG interface 828. In an embodiment, NG interface 828 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between base station 812 or base station 814 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between base station 812 or base station 814 and an access and mobility management function (AMF).

[0089] Generally speaking, application server 830 may be an element that provides applications (e.g., packet-switched data services) that utilize Internet Protocol (IP) bearer resources with CN 824. Application server 830 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 802 and UE 804 via CN 824. Application server 830 may communicate with CN 824 via IP communication interface 832.

[0090] Figure 9 A system 900 is illustrated for performing signaling 934 between a wireless device 902 and a network device 918 according to embodiments disclosed herein. System 900 can be part of a wireless communication system as described herein. Wireless device 902 can be, for example, a UE of the wireless communication system. Network device 918 can be, for example, a base station (e.g., an eNB or gNB) of the wireless communication system.

[0091] The wireless device 902 may include one or more processors 904. The processor 904 may execute instructions to perform various operations for the wireless device 902, as described herein. The processor 904 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof, configured to perform the operations described herein.

[0092] The wireless device 902 may include a memory 906. The memory 906 may be a non-transitory computer-readable storage medium that stores instructions 908, which may include, for example, instructions to be executed by the processor 904. The instructions 908 may also be referred to as program code or a computer program. The memory 906 may also store data used by the processor 904 and results computed by the processor.

[0093] The wireless device 902 may include one or more transceivers 910, which may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 912 of the wireless device 902 to facilitate signaling (e.g., signaling 934) to and / or from the wireless device 902 and other devices (e.g., network device 918) in accordance with a corresponding RAT.

[0094] The wireless device 902 may include one or more antennas 912 (e.g., one, two, four, or more). For implementations with multiple antennas 912, the wireless device 902 may leverage the spatial diversity of such multiple antennas 912 to transmit and / or receive multiple different data streams over the same time-frequency resources. This behavior may be referred to as, for example, multiple-input, multiple-output (MIMO) behavior (referring to the multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by the wireless device 902 may be achieved based on precoding (or digital beamforming) applied to the wireless device 902, which multiplexes the data streams across the antennas 912 based on known or assumed channel characteristics, such that each data stream is received at an appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Certain implementations may utilize single-user MIMO (SU-MIMO) methods (where data streams are all directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to separate (or different) receivers at different locations in the spatial domain).

[0095] In certain embodiments with multiple antennas, the wireless device 902 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 912 are adjusted relative to each other so that the (joint) transmissions of the antennas 912 can be steered (this is sometimes referred to as beam steering).

[0096] The wireless device 902 may include one or more interfaces 914. The interfaces 914 may be used to provide input to or output from the wireless device 902. For example, the wireless device 902 (UE) may include interfaces 914, such as a microphone, a speaker, a touch screen, and buttons, to allow a user of the UE to provide input and / or output to the UE. Other interfaces of such a UE may consist of transmitters, receivers, and other circuits (e.g., in addition to the transceiver 910 / antenna 912 already described) that allow the UE to communicate with other devices, and may be based on known protocols (e.g., Wi-Fi). ® and Bluetooth ® etc.) to perform the operation.

[0097] The wireless device 902 may include an IDC interference module 916. The IDC interference module 916 may be implemented via hardware, software, or a combination thereof. For example, the IDC interference module 916 may be implemented as a processor, circuitry, and / or instructions 908 stored in the memory 906 and executed by the processor 904. In some examples, the IDC interference module 916 may be integrated within the processor 904 and / or the transceiver 910. For example, the IDC interference module 916 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 904 or the transceiver 910.

[0098] The IDC interference module 916 may be used in various aspects of the present disclosure, for example, Figures 3 and 4 The IDC interference module 916 is configured to determine and report one or more affected frequency ranges relative to a target frequency in which in-device coexistence (IDC) interference is detected or expected to occur.

[0099] The network device 918 may include one or more processors 920. The processor 920 may execute instructions to perform various operations for the network device 918, as described herein. The processor 920 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0100] The network device 918 may include a memory 922. The memory 922 may be a non-transitory computer-readable storage medium that stores instructions 924 (which may include, for example, instructions to be executed by the processor 920). The instructions 924 may also be referred to as program code or a computer program. The memory 922 may also store data used by the processor 920 and results computed by the processor.

[0101] The network device 918 may include one or more transceivers 926, which may include RF transmitter and / or receiver circuitry that uses an antenna 928 of the network device 918 to facilitate signaling (e.g., signaling 934) to and / or from the network device 918 and other devices (e.g., wireless device 902) according to a corresponding RAT.

[0102] The network device 918 may include one or more antennas 928 (eg, one, two, four, or more). In embodiments with multiple antennas 928, the network device 918 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as described.

[0103] The network device 918 may include one or more interfaces 930. The interfaces 930 may be used to provide input to or output from the network device 918. For example, the network device 918 (base station) may include an interface 930 comprised of a transmitter, a receiver, and other circuitry (e.g., in addition to the transceiver 926 / antenna 928 already described). These interfaces enable the base station to communicate with other equipment in the core network and / or enable the base station to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining the base station or other equipment operatively connected to the base station.

[0104] The network device 918 may include an IDC configuration module 932. The IDC configuration module 932 may be implemented via hardware, software, or a combination thereof. For example, the IDC configuration module 932 may be implemented as a processor, circuitry, and / or instructions 924 stored in the memory 922 and executed by the processor 920. In some examples, the IDC configuration module 932 may be integrated within the processor 920 and / or the transceiver 926. For example, the IDC configuration module 932 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 920 or the transceiver 926.

[0105] The IDC configuration module 932 may be used in various aspects of the present disclosure, such as Figure 3 and Figure 5 The IDC configuration module 932 is configured to receive a message reporting one or more affected frequency ranges relative to a target frequency, in which IDC interference is detected or expected to occur at a UE, and generate a response to coordinate radio resource usage of the UE to avoid or reduce the IDC interference.

[0106] For one or more embodiments, at least one component of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the preceding figures may be configured to operate according to one or more of the examples described herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more of the examples described herein.

[0107] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0108] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0109] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in conjunction with another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in relation to one or more embodiments, and it should be appreciated that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless expressly stated otherwise herein.

[0110] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0111] Although the foregoing has been described in considerable detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. The embodiments of the present invention are therefore to be considered illustrative and not restrictive, and the specification is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a wireless network, the method comprising: receiving, at the UE, configuration information from a base station, the configuration information indicating a target frequency for wireless communication by the UE; determining, at the UE, one or more affected frequency ranges relative to the target frequency, wherein in-device coexistence (IDC) interference is detected or expected to occur in the one or more affected frequency ranges; as well as A message is sent from the UE to the base station to report the one or more affected frequency ranges. 2 . The method of claim 1 , wherein the configuration information indicating the target frequency comprises an Absolute Radio Frequency Channel Number (ARFCN)-New Radio (NR) value.

3. The method of claim 1 , wherein the configuration information further indicates a frequency range of interest relative to the target frequency for the wireless communication by the UE, and The one or more affected frequency ranges are within the frequency range of interest indicated in the configuration information.

4. The method according to claim 1, further comprising: determining a frequency range of interest relative to the target frequency for the wireless communication by the UE based on a first default value in a first frequency range (FR1) and a second default value in a second frequency range (FR2), The one or more affected frequency ranges are within the frequency range of interest.

5. The method according to claim 1, wherein the configuration information further indicates a reference subcarrier spacing (SCS), and The message reports the one or more affected frequency ranges in resource block (RB) units based on the reference SCS.

6. The method according to claim 1, further comprising: determining a reference subcarrier spacing (SCS) based on a first default value in a first frequency range (FR1) and a second default value in a second frequency range (FR2), The message reports the one or more affected frequency ranges in resource block (RB) units based on the reference SCS.

7. The method according to any one of claims 1 to 6, wherein for each of the one or more affected frequency ranges, the message comprises: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to the affected center frequency; and The number of resource blocks (RBs) relative to a reference subcarrier spacing (SCS) to indicate the bandwidth relative to the affected center frequency.

8. The method of claim 7, wherein the message further includes a bit to indicate a direction from the target frequency to the affected center frequency.

9. The method of claim 7, wherein the offset value is selected from positive and negative values ​​to indicate a direction from the target frequency to the affected center frequency.

10. The method according to any one of claims 1 to 6, wherein for each of the one or more affected frequency ranges, the message comprises: The Absolute Radio Frequency Channel Number (ARFCN) of the affected centre frequency; and The number of resource blocks (RBs) relative to the reference subcarrier spacing (SCS) to indicate the bandwidth relative to the center frequency.

11. The method according to any one of claims 1 to 6, wherein for each of the one or more affected frequency ranges, the message comprises: a target frequency index value corresponding to the target frequency; a first offset value from the target frequency to a near edge of a selected one of the one or more affected frequency ranges; and A second offset value from the target frequency to a far edge of the selected one of the one or more affected frequency ranges.

12. The method of claim 11, wherein the message further includes bits to indicate a direction from the target frequency toward the near edge and the far edge. 13 . The method of claim 11 , wherein the first offset value and the second offset value are selected from positive values ​​and negative values ​​to indicate directions from the target frequency toward the near edge and the far edge.

14. The method according to any one of claims 1 to 6, wherein for each of the one or more affected frequency ranges, the message comprises: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to an edge of a selected one of the one or more affected frequency ranges; and The number of resource blocks (RBs) relative to the reference subcarrier spacing (SCS) to indicate the bandwidth relative to the edge. 15 . The method of claim 14 , wherein the edge comprises a start frequency or an end frequency of a selected one of the one or more affected frequency ranges.

16. The method of claim 14, wherein the message further includes a bit to indicate a direction from the target frequency to the edge. 17 . The method of claim 14 , wherein the offset value is selected from positive and negative values ​​to indicate a direction from the target frequency to the edge.

18. The method according to any one of claims 1 to 6, wherein for each of the one or more affected frequency ranges, the message comprises: an absolute radio frequency channel number (ARFCN) of a start frequency of a selected one of the one or more affected frequency ranges; and The number of resource blocks (RBs) relative to the reference subcarrier spacing (SCS) to indicate the bandwidth relative to the starting frequency.

19. The method according to any one of claims 1 to 6, wherein for each of the one or more affected frequency ranges, the message comprises: an absolute radio frequency channel number (ARFCN) of a start frequency of a selected one of the one or more affected frequency ranges; and Resource Indicator Value (RIV), The offset and the number of resource blocks (RBs) of the one or more affected frequency blocks can be derived from a formula based on the RIV.

20. A method for a base station in a wireless network, the method comprising: sending configuration information from the base station to a user equipment (UE), the configuration information indicating a target frequency for wireless communications by the UE; receiving, at the base station, from the UE a message reporting one or more affected frequency ranges relative to the target frequency, wherein in-device coexistence (IDC) interference is detected or expected to occur at the UE in the one or more affected frequency ranges; generating a response for coordinating radio resource usage of the UE to avoid or reduce the IDC interference; as well as The response is sent from the base station to the UE. 21 . The method of claim 20 , wherein the configuration information indicating the target frequency comprises an Absolute Radio Frequency Channel Number (ARFCN)-New Radio (NR) value.

22. The method of claim 20, wherein the configuration information further indicates a frequency range of interest relative to the target frequency for the wireless communication by the UE, and The one or more affected frequency ranges are within the frequency range of interest indicated in the configuration information.

23. The method of claim 20, wherein the configuration information further indicates a reference subcarrier spacing (SCS), and The message reports the one or more affected frequency ranges in resource block (RB) units based on the reference SCS.

24. The method of any one of claims 20 to 23, wherein for each of the one or more affected frequency ranges, the message comprises: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to the affected center frequency; as well as The number of resource blocks (RBs) relative to a reference subcarrier spacing (SCS) to indicate the bandwidth relative to the affected center frequency.

25. The method of claim 24, wherein the message further includes a bit to indicate a direction from the target frequency to the affected center frequency.

26. The method of claim 24, wherein the offset value comprises a positive value or a negative value to indicate a direction from the target frequency to the affected center frequency.

27. The method of any one of claims 20 to 23, wherein for each of the one or more affected frequency ranges, the message comprises: The Absolute Radio Frequency Channel Number (ARFCN) of the affected centre frequency; and The number of resource blocks (RBs) relative to the reference subcarrier spacing (SCS) to indicate the bandwidth relative to the center frequency.

28. The method of any one of claims 20 to 23, wherein for each of the one or more affected frequency ranges, the message comprises: a target frequency index value corresponding to the target frequency; a first offset value from the target frequency to a near edge of a selected one of the one or more affected frequency ranges; and A second offset value from the target frequency to a far edge of the selected one of the one or more affected frequency ranges.

29. The method of claim 28, wherein the message further includes bits to indicate a direction from the target frequency toward the near edge and the far edge.

30. The method of claim 28, wherein the first offset value and the second offset value comprise positive or negative values ​​to indicate a direction from the target frequency toward the near edge and the far edge.

31. The method of any one of claims 20 to 23, wherein for each of the one or more affected frequency ranges, the message comprises: a target frequency index value corresponding to the target frequency; an offset value from the target frequency to an edge of a selected one of the one or more affected frequency ranges; and The number of resource blocks (RBs) relative to the reference subcarrier spacing (SCS) to indicate the bandwidth relative to the edge.

32. The method of claim 31 , wherein the edge comprises a start frequency or an end frequency of the selected one of the one or more affected frequency ranges.

33. The method of claim 31 , wherein the message further includes a bit to indicate a direction from the target frequency to the edge.

34. The method of claim 31, wherein the offset value comprises a positive value or a negative value to indicate a direction from the target frequency to the edge.

35. The method of any one of claims 20 to 23, wherein for each of the one or more affected frequency ranges, the message comprises: an absolute radio frequency channel number (ARFCN) of a start frequency of a selected one of the one or more affected frequency ranges; and The number of resource blocks (RBs) relative to the reference subcarrier spacing (SCS) to indicate the bandwidth relative to the starting frequency.

36. The method of any one of claims 20 to 23, wherein for each of the one or more affected frequency ranges, the message comprises: an absolute radio frequency channel number (ARFCN) of a start frequency of a selected one of the one or more affected frequency ranges; and Resource Indicator Value (RIV).

37. The method of claim 36, further comprising: A formula is used based on the RIV to determine an offset and a number of resource blocks (RBs) for one or more affected frequency blocks.

38. A method for a secondary node (SN) configured for multi-radio access technology (MR)-dual connectivity (DC) in a wireless network, the method comprising: sending, from the SN to a master node (MN), a first indication of a frequency range of interest for one or more target frequencies; sending, from the SN to the MN, a second indication of a reference subcarrier spacing (SCS) for the one or more target frequencies; as well as A message is received at the SN from the MN indicating an affected frequency range of the one or more target frequencies, wherein in-device coexistence (IDC) interference is detected or expected to occur in the affected frequency range.

39. A method for a master node (MN) configured for multi-radio access technology (MR)-dual connectivity (DC) in a wireless network, the method comprising: receiving, at the MN, from a secondary node (SN), a first indication of a frequency range of interest for one or more target frequencies; receiving, at the MN from the SN, a second indication of a reference subcarrier spacing (SCS) for the one or more target frequencies; as well as A message is sent from the MN to the SN indicating an affected frequency range of the one or more target frequencies, wherein in-device coexistence (IDC) interference is detected or expected to occur in the affected frequency range.

40. An apparatus comprising means for performing the method according to any one of claims 1 to 39.

41. A computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 1 to 39.

42. An apparatus comprising logic components, modules or circuits for performing the method according to any one of claims 1 to 39.

Images