Enhanced in-device coexistence reporting in wireless communication system

Abstract

A user equipment (UE) may establish a radio resource control (RRC) connection with a network node and receive an RRC reconfiguration message from the network node. The UE may determine at least one of one or more clean resources or one or more non-clean resources based on the RRC reconfiguration message, wherein the one or more non-clean resources may correspond to at least one in-device coexistence (IDC) conflict. The UE may transmit uplink assistance information (UAI) to the network node, and the UAI may include information corresponding to one or more start points and one or more end points of at least one of the one or more clean resources or one or more non-clean resources.

Description

Technical Field

[0001] The present application relates to wireless devices, and more particularly, to apparatus, systems, and methods for enhanced in-device coexistence (IDC) reporting in wireless communication systems. Background Art

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these functions. In addition, there are many different wireless communication technologies and wireless communication standards. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), Bluetooth, and the like. TM wait.

[0003] The introduction of an ever-increasing number of features and functions in wireless communication devices also requires continuous improvements in wireless communications and improvements in wireless communication devices. In order to increase coverage and better serve the increased demand and range of intended uses of wireless communications, in addition to the above-mentioned communication standards, there are wireless communication technologies being developed, including fifth generation (5G) new radio (NR) communications. Therefore, there is a need for improvements in the field of supporting such development and design. Summary of the invention

[0004] Embodiments relate to apparatus, systems, and methods for enhanced in-device coexistence (IDC) reporting in a wireless communication system.

[0005] In some embodiments, a user equipment (UE) may establish a radio resource control (RRC) connection with a network node and receive an RRC reconfiguration message from the network node. The UE may determine at least one of one or more clean resources or one or more unclean resources based on the RRC reconfiguration message, wherein the one or more unclean resources may correspond to at least one in-device coexistence (IDC) conflict. The UE may send uplink assistance information (UAI) to the network node, and the UAI may include information corresponding to one or more start points and one or more end points of at least one of the one or more clean resources or one or more unclean resources.

[0006] According to some embodiments, the information may include one or more resource numbers of one or more clean resources and one or more unclean resources. In some embodiments, at least one of the one or more starting points or one or more end points may be reported by the UE with respect to at least one of the lower edge of the component carrier (CC) or the absolute radio frequency channel number (ARFCN). Additionally or alternatively, one or more clean resources and one or more unclean resources may be at least one of one or more bandwidth parts (BWP) or one or more physical resource blocks (PRB). According to another embodiment, the RRC reconfiguration message may include configuration information corresponding to at least one of the following: carrier aggregation, dual connectivity, one or more BWPs, or an absolute radio frequency channel number (ARFCN) configured by a network node.

[0007] In some embodiments, the network node may be a master node (MN) corresponding to a first radio access technology (RAT), wherein the UAI may be sent to at least one of: the MN or a secondary node (SN) corresponding to the first RAT.

[0008] According to further embodiments, the UE may receive configuration information corresponding to the IDC report prohibition timer from the network node. Additionally or alternatively, according to some embodiments, the UE may start the IDC report prohibition timer after sending the UAI, wherein when the IDC report prohibition timer is running, the UE may be prohibited from sending additional UAI.

[0009] In some embodiments, the network node may establish a radio resource control (RRC) connection with a user equipment (UE) and send an RRC reconfiguration message to the UE. The network node may then receive uplink assistance information (UAI) from the UE. Additionally or alternatively, the UAI may include information corresponding to at least one resource of one or more clean resources or one or more unclean resources associated with one or more component carriers (CCs). In addition, according to some embodiments, one or more unclean resources correspond to at least one in-device coexistence (IDC) conflict. The network node may then limit the use of one or more unclean resources based on the UAI.

[0010] According to some embodiments, limiting the use of one or more unclean resources may include releasing one or more unclean resources in the unclean resources. Additionally or alternatively, limiting the use of one or more unclean resources may include releasing a secondary cell (SCell) on one of the one or more CCs. In some embodiments, limiting the use of one or more unclean resources may include at least one of the following: performing scheduling based on a hybrid automatic repeat request mode, configuring the UE to utilize a time domain multiplexing (TDM) mode, or configuring the UE to utilize a discontinuous reception (DRX) configuration.

[0011] In some embodiments, the network node may receive a secondary cell group (SCG) configuration for carrier aggregation (CA) from a secondary node (SN) and forward the UAI to the SN. Additionally, according to some embodiments, the network node may be configured to send configuration information corresponding to an IDC report prohibit timer to the UE, wherein when the IDC report prohibit timer is running, the UE may be prohibited from sending additional UAI. In some embodiments, the UAI may be received via medium access control-control element (MAC-CE) signaling.

[0012] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of cellular telephones, tablet computers, wearable computing devices, portable media players, and a variety of other computing devices.

[0013] This summary is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects, and advantages of the topics described herein will become apparent through the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0015] Figure 1 An exemplary wireless communication system according to some embodiments is illustrated;

[0016] Figure 2 illustrates a base station (BS) in communication with a user equipment (UE) device according to some embodiments;

[0017] Figure 3 illustrates an example block diagram of a UE according to some embodiments;

[0018] Figure 4 illustrates an exemplary block diagram of a BS according to some embodiments;

[0019] Figure 5 illustrates an exemplary block diagram of a cellular communication circuit according to some embodiments;

[0020] Figure 6 is an exemplary block diagram illustrating aspects of uplink carrier aggregation by utilizing two carriers according to some embodiments;

[0021] Figure 7is a communication flow diagram illustrating aspects of an exemplary method for enhanced in-device coexistence reporting;

[0022] Figure 8A-8C illustrates aspects and methods for enhanced IDC reporting using frequency division multiplexing (FDM) according to some embodiments;

[0023] Figure 9A-9D Illustrate aspects and methods for enhanced IDC reporting using FDM in single carrier and carrier aggregation scenarios according to some embodiments;

[0024] Fig.10 illustrates aspects of enhanced IDC reporting for Multi-Radio Access Technology - Dual Connectivity (MR-DC) according to some embodiments; and

[0025] Figure 11-Figure 12 Aspects of enhanced IDC reporting using Medium Access Control - Control Element (MAC-CE) reporting are illustrated in accordance with some embodiments.

[0026] Although the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to be limited to the specific forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0027] Acronyms

[0028] Various acronyms are used throughout this disclosure. Definitions of the most commonly used acronyms that may appear throughout this disclosure are provided below:

[0029] 3GPP: Third Generation Partnership Project

[0030] TS: Technical Specification

[0031] RAN: Radio Access Network

[0032] RAT: Radio Access Technology

[0033] UE: User Equipment

[0034] RF: Radio Frequency

[0035] BS: Base Station

[0036] DL: Downlink

[0037] UL: Uplink

[0038] LTE: Long Term Evolution

[0039] NR: New Radio

[0040] 5GS: 5G system

[0041] 5GMM: 5GS Mobility Management

[0042] 5GC: 5G core network

[0043] CA: Carrier Aggregation

[0044] FR: Frequency range

[0045] PCC: Primary Component Carrier

[0046] SCC: Secondary Component Carrier

[0047] LB: Low frequency band

[0048] MB: Mid-band

[0049] HB: High frequency band

[0050] UHB: Ultra-high frequency band

[0051] TRP: Total Radiated Power

[0052] RSRP: Reference Signal Received Power

[0053] PUCCH: Physical Uplink Control Channel

[0054] RACH: Random Access Channel

[0055] BW: Bandwidth

[0056] TX: Send

[0057] RX: Receive

[0058] IDC: Coexistence within the device

[0059] IDM: Interleaved Division Multiplexing

[0060] LAA: License Assisted Access

[0061] ISM: Industrial, Scientific and Medical Radio Band GNSS: Global Navigation Satellite System

[0062] IMD: Intermodulation

[0063] WLAN: Wireless Local Area Network

[0064] FDM: Frequency Division Multiplexing

[0065] TDM: Time Division Multiplexing

[0066] RRC: Radio Resource Control

[0067] DRX: Discontinuous Reception

[0068] HARQ: Hybrid Automatic Repeat Request

[0069] PHR: Power Headroom

[0070] HO: Handover

[0071] BT: Bluetooth

[0072] E-UTRAN: Evolved Universal Terrestrial Radio Access Network

[0073] EN-DC: E-UTRAN New Radio – Dual Connectivity

[0074] MR-DC: Multi-RAT-Dual Connectivity

[0075] NR-DC: New Radio – Dual Connectivity

[0076] BWP: Bandwidth Part

[0077] PRB: Physical Resource Block

[0078] ARFCN: Absolute Radio Frequency Channel Number

[0079] UAI: Uplink Assistance Information

[0080] MN: Master Node

[0081] MCG: Master Cell Group

[0082] SN: Secondary Node

[0083] SCG: Secondary Cell Group

[0084] CG: Cell Group

[0085] CC: Component Carrier

[0086] SCell: Secondary cell

[0087] MAC-CE: Medium Access Control-Control Element

[0088] the term

[0089] The following is a glossary of terms used in this disclosure:

[0090] Memory medium—any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media, such as hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or combinations thereof. In addition, the memory medium may be located in a first computer system executing a program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter example, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media, which may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., embodied as a computer program) that may be executed by one or more processors.

[0091] Carrier medium—storage media as described above, as well as physical transmission media such as a bus, network, and / or other physical transmission media that convey signals such as electrical, electromagnetic, or digital signals.

[0092] Programmable hardware element - includes various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include field programmable gate arrays (FPGAs), programmable logic devices (PLDs), field programmable object arrays (FPOAs), and complex PLDs (CPLDs). Programmable function blocks can range from fine-grained (combinational logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic."

[0093] Computer System—Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0094] User Equipment (UE) (or "UE device") - any of various types of computer systems or devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile phones or smart phones (e.g., iPhone TM, based on Android TM phones), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) that can be easily transmitted by a user and capable of wireless communication.

[0095] Wireless Device—Any of various types of computer systems or devices that perform wireless communications. A wireless device may be portable (or mobile), or may be stationary or fixed at a location. A UE is an example of a wireless device.

[0096] Communication device - any of various types of computer systems or devices that perform communication, where the communication may be wired or wireless. A communication device may be portable (or mobile), or may be stationary or fixed at a location. A wireless device is an example of a communication device. A UE is another example of a communication device.

[0097] Base Station—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0098] Processing element (or processor) - refers to various elements or combinations of elements that are capable of performing functions in a device, such as user equipment or a cellular network device. A processing element may include, for example, a processor and associated memory, portions or circuits of a separate processor core, an entire processor core, a separate processor, an array of processors, circuits such as an application specific integrated circuit (ASIC), a programmable hardware element such as a field programmable gate array (FPGA), and any of the above various combinations.

[0099] Channel - a medium used to convey information from a transmitter (sender) to a receiver. It should be noted that, since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" as used herein may be considered to be used in a manner that conforms to the standards of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0100] Frequency band—The term “frequency band” has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0101] Automatically—refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the need for the action or operation to be directly specified or performed by a user input. Thus, the term "automatically" is in contrast to a user manually performing or specifying an action, wherein the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," wherein the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user action. The form may be automatically filled out by a computer system, wherein the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0102] Approximately - refers to a value that is close to a correct or exact value. For example, approximately can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, "approximately" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of a particular application.

[0103] Concurrency - refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be implemented using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism", where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0104] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having a structure” that performs one or more tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently performing the task (e.g., a collection of electrical conductors may be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, “configured to” may be a broad statement that generally means “having a circuit” that performs one or more tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently turned on. Typically, circuits that form a structure corresponding to “configured to” may include hardware circuits.

[0105] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Representing a component configured to perform one or more tasks expressly intends that the component does not invoke the interpretation of 35 U.S.C. §112(f).

[0106] Figure 1 and Figure 2 —Communications systems

[0107] Figure 1 A simplified example wireless communication system according to some embodiments is illustrated. Note that Figure 1 The system is merely one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0108] As shown, the example wireless communication system includes a base station 102A, which communicates with one or more user equipment 106A, user equipment 106B, etc. to user equipment 106N through a transmission medium. Each user equipment in the user equipment may be referred to as a "user equipment" (UE) in this article. Therefore, user equipment 106 is referred to as UE or UE device.

[0109] The base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware to enable wireless communications with the UEs 106A-106N.

[0110] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), which are also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. It should be noted that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". It should be noted that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0111] As shown, the base station 102A may also be configured to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, the base station 102A may facilitate communications between user devices and / or between user devices and the network 100. Specifically, the cellular base station 102A may provide the UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0112] Base station 102A and other similar base stations (such as base stations 102B, ..., 102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping service to UE 106A-106N and similar devices over a geographic area via one or more cellular communication standards.

[0113] Thus, although base station 102A may function as Figure 1106A-106N, each UE 106 may also be able to receive signals from (and possibly be within communication range of) one or more other cells (which may be provided by base stations 102B-102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be able to facilitate communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or any other variety of other granularity of cells providing service area sizes. For example, Figure 1 The illustrated base stations 102A-102B may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0114] In some embodiments, base station 102A may be a next generation base station, such as a 5G New Radio (5G NR) base station or "gNB". In some embodiments, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TR points). In addition, a UE capable of operating in accordance with 5G NR may be connected to one or more TR points within one or more gNBs. For example, base station 102A and one or more other base stations 102 may support joint transmissions such that UE 106 may be able to receive transmissions from multiple base stations (and / or multiple TR points provided by the same base station).

[0115] It should be noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). If desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0116] Figure 2A user equipment 106 (e.g., one of devices 106A-106N) is illustrated in accordance with some embodiments in communication with a base station 102. The UE 106 may be a device with cellular communication capabilities, such as a mobile phone, handheld device, computer, laptop, tablet, smart watch or other wearable device, or indeed any type of wireless device.

[0117] UE 106 may include a processor (processing element) configured to execute program instructions stored in a memory. UE 106 may perform any method implementation in the method implementation scheme described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA), an integrated circuit, and / or any of various other possible hardware components configured to (e.g., individually or in combination) perform any method implementation in the method implementation scheme described herein or any part of any method implementation in the method implementation scheme described herein.

[0118] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, NR or LTE using at least some shared radio components. As an additional possibility, the UE 106 may be configured to communicate using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio component may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Typically, the radio component may include any combination of a baseband processor, an analog RF signal processing circuit (e.g., including filters, mixers, oscillators, amplifiers, etc.) or a digital processing circuit (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of a receive chain and / or a transmit chain between multiple wireless communication technologies such as those discussed above.

[0119] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or, in various possibilities, either LTE or 1xRTT, or either LTE or GSM) and an independent radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0120] Figure 3 —UE block diagram

[0121] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is illustrated. Note that Figure 3 The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, in addition to other devices, the communication device 106 can be a user equipment (UE) device, a mobile device or a mobile station, a wireless device or a wireless station, a desktop computer or a computing device, a mobile computing device (e.g., a laptop, a notebook or a portable computing device), a tablet computer and / or a combination of devices. As shown in the figure, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components may be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 300 may be implemented as independent components or groups of components for various purposes. This group of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0122] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, camera, keyboard; output devices such as speakers; etc.), a display 360 that may be integrated with the communication device 106 or external to it, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, UMTS, GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0123] Wireless communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as one or more antennas 335 as shown. Wireless communication circuitry 330 may include cellular communication circuitry and / or short- to medium-range wireless communication circuitry, and may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0124] In some embodiments, as further described below, the cellular communication circuitry 330 may include one or more receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR) for multiple RATs. Moreover, in some embodiments, the cellular communication circuitry 330 may include a single transmit chain that may switch between radio components dedicated to specific RATs. For example, a first radio component may be dedicated to a first RAT (e.g., LTE) and may communicate with a dedicated receive chain and a transmit chain shared with a second radio component. A second radio component may be dedicated to a second RAT (e.g., 5G NR) and may communicate with a dedicated receive chain and a shared transmit chain.

[0125] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include various elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0126] The communication device 106 may also include one or more smart cards 345 , such as one or more Universal Integrated Circuit Cards (UICC) 345 , having Subscriber Identity Module (SIM) functionality.

[0127] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from the one or more processors 302 and convert those addresses to locations in a memory (e.g., a memory 306, a read-only memory (ROM) 350, a NAND flash memory 310)), and / or to other circuits or devices (such as the display circuit 304, the wireless communication circuit 330, the connector I / F 320, and / or the display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0128] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuits. As described herein, the communication device 106 may include hardware and software components for implementing any of the various features and techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transient computer-readable memory medium), the processor 302 of the communication device 106 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). Alternatively (or in addition), in combination with one or more components in other components 300, 304, 306, 310, 320, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement part or all of the features described herein.

[0129] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0130] In addition, as described herein, wireless communication circuit 330 may include one or more processing elements. In other words, one or more processing elements may be included in wireless communication circuit 330. Therefore, wireless communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of wireless communication circuit 330. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of wireless communication circuit 330.

[0131] Figure 4 —Block diagram of a base station

[0132] Figure 4 An example block diagram of a base station 102 according to some embodiments is illustrated. Note that Figure 4 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device, which may be configured to receive addresses from the processor 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0133] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the telephone network described above. Figure 1 and Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0134] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0135] In some embodiments, base station 102 may be a next generation base station, such as a 5G New Radio (5G NR) base station, or "gNB". In such embodiments, base station 102 may be connected to a legacy Evolved Packet Core (EPC) network and / or to an NR Core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TR points). Furthermore, a UE capable of operating in accordance with 5G NR may connect to one or more TR points within one or more gNBs.

[0136] The base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio component 430. The antenna 434 communicates with the radio component 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5GNR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0137] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, the base station 102 may include multiple radio components that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5GNR radio component for performing communications according to 5G NR. In this case, the base station 102 may be able to operate as both an LTE base station and a 5GNR base station. As another possibility, the base station 102 may include a multimode radio component that can perform communications according to any one of a plurality of wireless communication technologies (e.g., 5G NR and LTE, 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0138] As further described later herein, BS102 may include hardware and software components for implementing or supporting a specific implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support a specific implementation of part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as a field programmable gate array (FPGA), or as an application specific integrated circuit (ASIC) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS102 may be configured to implement or support a specific implementation of part or all of the features described herein.

[0139] Furthermore, as described herein, processor 404 may include one or more processing elements. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0140] Additionally, as described herein, radio 430 may include one or more processing elements. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Additionally, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0141] Figure 5 —Block diagram of cellular communication circuit

[0142] Figure 5 An example simplified block diagram of a cellular communication circuit according to some embodiments is illustrated. Note that Figure 5 The block diagram of cellular communication circuitry is only one example of possible cellular communication circuitry; other circuitry, such as circuitry that includes or is coupled to sufficient antennas for different RATs to perform uplink activities using separate antennas, or circuitry that includes or is coupled to fewer antennas, such as circuitry that may be shared between multiple RATs, is also possible. According to some embodiments, cellular communication circuitry 330 may be included in a communication device such as communication device 106 described above. As described above, communication device 106 may be a user equipment (UE) device, a mobile device or station, a wireless device or station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0143] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335a-335b and 336 as shown. In some embodiments, cellular communication circuitry 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, the cellular communication circuit 330 may include a first modem 510 and a second modem 520. The first modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the second modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0144] As shown, the first modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for sending and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some embodiments, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0145] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuits for sending and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

[0146] In some embodiments, the switch 570 may couple the transmit circuit 534 to an uplink (UL) front end 572. In addition, the switch 570 may couple the transmit circuit 544 to the UL front end 572. The UL front end 572 may include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuit 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572) supported by the first modem 510, the switch 570 may be switched to a first state that allows the first modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572) supported by the second modem 520, the switch 570 may be switched to a second state that allows the second modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572).

[0147] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processors 512, 522 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processors 512, 522 may be configured as programmable hardware elements, such as a field programmable gate array (FPGA) or as an application specific integrated circuit (ASIC). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336, the processors 512, 522 may be configured to implement part or all of the features described herein.

[0148] In addition, as described herein, the processors 512, 522 may include one or more processing elements. Therefore, the processors 512, 522 may include one or more integrated circuits (ICs) configured to perform the functions of the processors 512, 522. In addition, each integrated circuit may include circuits (e.g., first circuits, second circuits, etc.) configured to perform the functions of the processors 512, 522.

[0149] In some embodiments, the cellular communication circuit 330 may include only one transmit / receive chain. For example, the cellular communication circuit 330 may not include the modem 520, the RF front end 540, the DL front end 560, and / or the antenna 335b. As another example, the cellular communication circuit 330 may not include the modem 510, the RF front end 530, the DL front end 550, and / or the antenna 335a. In some embodiments, the cellular communication circuit 330 may also not include the switch 570, and the RF front end 530 or the RF front end 540 may communicate with the UL front end 572, for example, directly.

[0150] Figure 6 —Carrier aggregation

[0151] Figure 6 is an exemplary block diagram illustrating various aspects of carrier aggregation (CA) according to some embodiments. More specifically, Figure 6 The principle of uplink carrier aggregation (UL-CA) is illustrated, where a UE 610 may be configured to transmit simultaneously on two contiguous or non-contiguous carriers. In addition, a UE may transmit on multiple uplink carriers using the same antenna port or multiple antenna ports (eg, antennas).

[0152] For example, Figure 6Two carriers (e.g., X and Y) corresponding to specific channel bandwidths (e.g., bandwidth X 602 and bandwidth Y 604) associated with their respective frequency bands (e.g., band X and band Y) are illustrated. Figure 6 It is illustrated that UE 610 may be able to transmit simultaneously on two carriers using two different frequencies fX 606 and fY 608. In some embodiments, band X and band Y may be contiguous, such that their bands share a common or adjacent frequency boundary (e.g., the bands are adjacent to each other, such as long term evolution (LTE) band 13 and LTE band 14). Additionally or alternatively, the two bands may be non-contiguous (e.g., LTE band 2 and LTE band 13), corresponding to bands with one or more frequency gaps therebetween. Contiguous and non-contiguous new radio (NR) bands may similarly be used for uplink carrier aggregation.

[0153] In some embodiments, bandwidth X 602 and bandwidth Y 604 may be similar or identical bandwidths. For example, bandwidth X 602 and bandwidth Y 604 may each correspond to a bandwidth of 20 MHz. Additionally or alternatively, bandwidth X 602 and bandwidth Y 604 may be characterized by various different channel bandwidths. For example, according to some embodiments, bandwidth X 602 may be a bandwidth of 20 MHz, while bandwidth Y 604 may be characterized by a bandwidth of 10 MHz. According to other embodiments, UE 610 may communicate using bandwidth X 602 corresponding to frequency band X using frequency fX 606. Additionally or alternatively, UE 610 may also communicate using a channel bandwidth such as bandwidth Y 604 corresponding to frequency band Y using frequency fY 608. Although some of the above embodiments utilize examples of LTE frequency bands and their corresponding frequencies and bandwidths (and other characteristics), Figure 6 Scenarios for UL-CA utilizing various examples of New Radio (NR) bands and their corresponding frequencies and channel bandwidths (as well as other characteristics) may also be described.

[0154] In some legacy systems, a user equipment (UE) may not have been configured or designed to support transmit (Tx) operations on the same antenna port or multiple antenna ports to transmit on multiple uplink carriers for inter-band UL-CA. For example, the selection of antenna ports for inter-band UL-CA may be based on receive (Rx) monitoring of primary component carrier 1 (PCC1) and PCC2. More specifically, receive monitoring may involve monitoring two Rx antenna ports (e.g., antennas) for a low band (LB) and four Rx antenna ports for a mid band (MB), a high band (HB), or an ultra-high band (UHB). In some embodiments, LB may correspond to a frequency less than or equal to 1 GHz, MB may correspond to a frequency between 1 GHz and 2 GHz, HB may correspond to a frequency between 2 GHz and 3 GHz, and UHB may correspond to a frequency between 3 GHz and 6 GHz.

[0155] As an example, inter-band UL-CA of LTE Band 12 and LTE Band 2 may use two separate antenna ports (e.g., antennas) for Tx transmission. Furthermore, the two separate Tx ports may be selected based on downlink Rx measurements such as reference signal received power (RSRP). Additionally, although some of the above embodiments utilize examples of UL-CA, Figure 6 Various example downlink (DL-CA) (e.g., UE receiving transmissions from the network) scenarios utilizing NR or LTE bands and their corresponding frequencies and channel bandwidths (and other characteristics) may also be described. However, problems may arise due to the proximity of antennas or antenna ports to each other. More specifically, coexistence (e.g., in-device coexistence (IDC)) interference may occur on multiple antennas within the same UE.

[0156] For example, a UE may have three antennas (ANT#1, ANT#2, and ANT#3) corresponding to various frequencies, and ANT#1 may be associated with an LTE radio frequency (RF) and an LTE baseband frequency, ANT#2 may be associated with a GPS RF and a GPS baseband frequency, and ANT#3 may be associated with a Bluetooth (BT) or WiFi RF and a BT / WiFi baseband frequency. Therefore, transmission and reception of these antennas and various frequency bands may cause interference between the antennas. For example, ANT#1 may cause LTE interference to ANT#2 and ANT#3. Additionally or alternatively, according to some scenarios, ANT#3 may cause BT / WiFi interference to ANT#1. Therefore, due to reception on an LTE antenna and transmission on a BT / WiFi antenna, coexistence interference involving an LTE radio may be interfered with by an industrial, scientific, and medical (ISM) radio band. Additionally or alternatively, transmission on an LTE antenna and reception on a BT / WiFi antenna may cause coexistence interference involving an ISM radio being interfered with by LTE.

[0157] In another scenario, coexistence interference may occur between an in-device ISM transmitter and an Evolved Universal Terrestrial Radio Access (E-UTRA) receiver. For example, coexistence interference involves a Global Navigation Satellite System (GNSS) radio being interfered with by an LTE antenna due to transmission on the LTE antenna and reception on the GNSS antenna. Additionally or alternatively, if both the LTE and GNSS antennas are receiving rather than transmitting, there may not be an interference issue.

[0158] In other words, due to the Tx and Rx of different antennas, there may be various forms of interference, including inter-radio access technology (RAT) harmonics or interleaved division multiplexing (IDM) interference. For example, interference from LTE to ISM or from ISM to LTE and from LTE to GNSS. Additionally or alternatively, there may be interference, including LTE UL CA IMD interference to wireless local area networks (WLAN), BT, and GNSS. In addition, interference scenarios may include interference from only NR harmonics or LTE+NR (EN-DC) UL IMD to WLAN, Bluetooth, and GNSS in EN-DC. In some scenarios, hardware sharing between WiFi and Licensed Assisted Access (LAA) may also cause interference issues.

[0159] Therefore, these issues can lead to degraded cellular performance, especially in scenarios where transmit power is limited due to Tx backoff (e.g., backing off / reducing transmit power) or limited overhead / power headroom (PHR). For example, higher bands MB / HB / UHB may utilize higher Tx backoff values ​​compared to LB. These transmit power backoff values ​​may be characterized or utilized in this way to help mitigate distortion associated with transmission (e.g., intermodulation or harmonic distortion, etc.). Additionally or alternatively, the current network implementation signaling may be supported only on PCC1 for these two carriers. If the MB / HB / UHB carrier is assigned to PCC1 with high Tx backoff, signaling performance may also be degraded.

[0160] One goal that may be targeted in the development of cellular communication technologies (potentially included in 3GPP cellular technologies such as LTE and NR) may include reducing or mitigating interference in IDC scenarios. New cellular communication technologies are constantly being developed to increase coverage, better meet various needs and use cases, and for various other reasons. Therefore, it may be beneficial to provide enhanced UE IDC reporting methods to avoid potential interference issues. Therefore, improvements are desired in this area.

[0161] Enhanced in-device coexistence reporting in wireless communication systems

[0162] A technique for improving user experience may involve using frequency division multiplexing (FDM) technology in an IDC scenario to reduce or mitigate interference issues. For example, a UE may detect IDC issues related to the use of certain radio resources and provide this information to the network so that the network can adjust or limit the use of radio resources via FDM accordingly. FDM can be used in different ways to allocate resources more flexibly and efficiently, and effectively reduce or mitigate interference issues related to the UE's IDC. In other words, by reporting resources that are affected or may be problematic due to IDC, the UE can benefit from using this information with FDM to avoid the network of the resources. This can help avoid interference issues that may be caused by their use, and then provide a better user experience.

[0163] Based on network (NW) control and user equipment (UE) assistance information (e.g., uplink assistance information (UAI)), there may be different ways to perform enhanced IDC reporting. For example, according to some embodiments, FDM may be utilized based on the UE receiving a radio resource control (RRC) message, and in response to determining an IDC problem with radio resources, the UE may provide the network with UAI to notify it of the resources that may be problematic. In some embodiments, if the NW applies an FDM method using enhanced IDC reporting via UAI received from the UE, the NW may be able to instruct the UE to perform a handover (HO) process to another frequency. Additionally or alternatively, according to some embodiments, if the UE communicates with a secondary cell, the NW may be able to deconfigure or deactivate the indicated interfered SCell.

[0164] Additionally or alternatively, methods involving time division multiplexing (TDM) may further correspond to scenarios based on discontinuous reception (DRX) or hybrid automatic repeat request (HARQ) process reservation. For example, in some embodiments, the UE may report the interfered frequency and / or the recommended TDM mode to the NW. According to some embodiments, if the NW applies a TDM method based on an enhanced IDC report via a UAI received from the UE, the NW may be able to configure the UE so that it utilizes the recommended DRX configuration. Additionally or alternatively, according to some embodiments, the NW may be able to perform scheduling based on the HARQ reservation mode recommended by the UE.

[0165] In some embodiments, the enhanced IDC reporting method may be based on the UE performing autonomous rejection. For example, due to some critical short-term events corresponding to ISM frequencies (e.g., events during BT / WiFi connection establishment or other important signaling), the UE may be able to autonomously reject resources (NR or LTE).

[0166] In addition, existing NR IDC methods may need to be improved to adequately indicate interference reporting of affected frequencies. For example, enhancements related to FDM scenarios may allow for more granular indication of affected frequencies (e.g., granularity or specificity at the bandwidth part (BWP) or physical resource block (PRB) level). In addition, TDM-based methods may also be implemented by indicating the UE preferred TDM mode for UL / DL and specified RRM requirements or parameters.

[0167] Therefore, in order to resolve possible interference issues between 3GPP (including various MR-DC architectures such as NR-DC and EN-DC) and non-3GPP RATs (e.g., WiFi), it may be beneficial for the UE to inform the NW of potential IDC issues regarding certain radio resources. For example, in some scenarios, the UE may detect internal problems or the potential for internal problems caused by in-device coexistence related to the use of certain radio resources. Therefore, in some embodiments, if the UE cannot resolve these problems by itself, the UE may provide information to the NW (e.g., gNB) to assist the NW in limiting the use of specified radio resources in order to avoid UE internal problems (or potential problems) caused by coexistence.

[0168] Figure 7 —Methodology used for enhanced IDC reporting

[0169] Figure 7 is a communication flow diagram illustrating exemplary aspects of a method for enhanced IDC reporting according to at least some embodiments.

[0170] Figure 7 Various aspects of the method may be implemented by a wireless device 106 (such as the UE 106 illustrated in the various figures herein), a network (for example, which may be provided by one or more base stations (such as BS102) illustrated in the various figures herein), and / or more generally, may be implemented in combination with any of the computer circuits, systems, devices, elements or components, etc., shown in the above figures as needed. For example, a processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements.

[0171] It should be noted that although the enhanced IDC report is mainly used to describe Figure 7 However, the various techniques described herein may also or alternatively be applied to any of a variety of other scenarios that may be further defined or described in appropriate 3GPP specifications and standards.

[0172] In various embodiments, some of the elements of the method shown may be performed simultaneously in an order different from that shown, may be replaced by other method elements, or may be omitted. Additional elements may also be performed as needed. As shown in the figure, Figure 7 The method can be operated as follows.

[0173] In 702, according to some embodiments, the UE may establish an RRC connection with a network node through a radio resource control (RRC) connection establishment process. For example, according to some embodiments, the UE may establish communication with a cellular network, for example, via a wireless link with one or more base stations (102). The communication may include a cellular link according to a wireless standard such as 5G NR and / or 6G. For example, a wireless device may establish a session with an AMF entity of a cellular network through one or more base stations that provide radio access to the cellular network. According to various embodiments, other types of cellular links are also possible, and the cellular network may also or alternatively operate according to another cellular communication technology (e.g., LTE, UMTS, CDMA2000, GSM, etc.).

[0174] Establishing an RRC connection may include configuring various parameters for communication between a wireless device (e.g., UE) and a cellular base station, establishing environmental information of the wireless device, and / or any of a variety of other possible features, for example, involving establishing an air interface of the wireless device for cellular communication with a cellular network associated with the cellular base station. After establishing the RRC connection, the wireless device may operate in an RRC connected state. In some instances, the RRC connection may also be released (e.g., after a certain period of inactivity relative to data communications), in which case the wireless device may operate in an RRC idle state or an RRC inactive state. In some instances, the wireless device may perform a handover (e.g., when in an RRC connected mode) or a cell reselection (e.g., when in an RRC idle mode or an RRC inactive mode) to a new serving cell, for example, due to wireless device mobility, changes in wireless medium conditions, and / or any of a variety of other possible reasons.

[0175] In at least some instances, establishing the wireless link may include the wireless device providing capability information of the wireless device. Such capability information may include information related to any of a plurality of types of wireless device capabilities.

[0176] In 704, according to some embodiments, the UE may receive an RRC reconfiguration message from the network node. For example, as part of the RRC connection establishment process in 702 or in addition to the process, the UE may also receive an RRC reconfiguration message. Additionally, in addition to other RRC configuration information, the RRC reconfiguration message may also provide and / or include a complete or partial configuration for a primary cell (PCell) or a secondary cell (SCell). In addition, corresponding operations and RRC messages, such as the RRC connection establishment in 702 and the RRC reconfiguration in 704, may be further defined or described in appropriate 3GPP specifications and standards. According to some embodiments, the RRC reconfiguration message may include configuration information corresponding to at least one of the following: carrier aggregation,

[0177] Dual connectivity, one or more BWPs and / or an absolute radio frequency channel number (ARFCN) configured by a network node. In some embodiments, these examples may include applying or comparing time and frequency resource configurations in different ways. According to some embodiments, the RRC reconfiguration message may include an Otherconfig parameter. For example, according to some embodiments, the NW may be able to configure the maximum rejection probability through the configuration of the parameter Otherconfig.

[0178] In 706, according to some embodiments, the UE may determine one or more conflicts corresponding to in-device coexistence (IDC) of one or more resources. For example, the UE may determine that certain resources are not suitable (e.g., due to in-device coexistence) for future communications or other operations based on configuration information provided in the RRC reconfiguration message. In other words, due to IDC-related issues regarding the configuration of resources and PCell and / or SCell, the UE may be aware of problematic resources (e.g., one or more conflicts). For example, as a possible scenario, the configured resources may be determined to be incompatible to use the configured PCell and / or SCell for communication or other operations. According to some embodiments, the UE may have received configuration information in the RRC reconfiguration message corresponding to an AutonomousDenial configuration, an intermodulation (IMD) problem corresponding to UL CA, an IDC configuration for hardware sharing, or an IDC configuration for EN-DC. Therefore, the UE may be able to determine an IDC conflict for resources based on these configurations or IMD issues, which will be described in the additional information section below. For example, according to some embodiments, the UE may be able to determine and indicate that certain IDC problems or resource conflicts may occur through configuration information including certain parameters (eg, hardwareSharingProblem-r13).

[0179] According to some embodiments, IDC resource conflicts may be determined based on comparing the frequencies of non-cellular (e.g., BT, Wi-Fi) resources with the frequencies of cellular (3GPP defined) resources. Thus, in the case where non-cellular frequencies and cellular frequencies overlap, resource conflicts or resource contention may occur. Thus, according to some embodiments, determining one or more IDC resource conflicts may include determining a cellular frequency, determining a non-cellular frequency, and comparing them to determine overlap and / or conflict.

[0180] In some embodiments, IDC resource conflicts may be determined based on a time domain comparison. For example, the UE may be able to compare the time domain parameters of the non-cellular resources with the time domain parameters of the cellular resources, and further determine any contention or overlap between the two. Thus, according to some embodiments, determining one or more IDC resource conflicts may include determining a cellular time domain parameter, a non-cellular time domain parameter based on the resource, and comparing them to determine overlap and / or conflict.

[0181] In 708, according to some embodiments, the UE may send uplink assistance information (UAI) to the network node. The UAI may include information corresponding to one or more resources and IDC conflicts. More specifically, if the UE detects an IDC problem corresponding to certain determined radio resources as in 706, the UE may provide this information to the network so that the network can adjust or restrict (e.g., restrict, prohibit, deactivate or release) the use of radio resources that may be problematic accordingly. According to some embodiments, the UAI may include or be included as part of the InDeviceCoexIndication message. Additionally or alternatively, according to some embodiments, the InDeviceCoexIndication message may include certain parameters (e.g., hardwareSharingProblem-r13) or assistance information (e.g., mrdc-AssistanceInfo-r15), which may be used to indicate certain IDC problems or assistance information to the network. According to some embodiments, the UAI may be sent as part of RRC, medium access control (MAC) signaling, physical uplink control channel (PDCCH) or physical uplink shared channel signaling.

[0182] According to some embodiments, information corresponding to at least one resource of the one or more resources and / or at least one IDC conflict may correspond to one or more bandwidth parts (BWPs) of one or more serving cells, one or more physical resource blocks (PRBs) of one or more serving cells, or an absolute radio frequency channel number (ARFCN) configured by a network node. In other words, the UAI may include information about certain BWPs, PRBs, or ARFCNs, which may be used by the network node when performing operations to restrict (e.g., deactivate, release, restrict, prohibit) the use of problematic resources due to IDC problems. Additionally or alternatively, the UAI may be sent to various nodes or network nodes corresponding to different radio access technologies. In other words, in various scenarios involving multiple or different RATs and different MN and SN configurations, it may be beneficial to provide the UAI to other network entities so that they can also perform resource restriction procedures (e.g., deactivation, deconfiguration, or release of resources) when necessary. For example, performing the resource restriction process may include at least one of the following: the network performs scheduling based on a hybrid automatic repeat request mode, configures the UE to utilize a time domain multiplexing (TDM) mode, or configures the UE to utilize a discontinuous reception (DRX) configuration.

[0183] In some embodiments, the UAI may include information corresponding to at least one clean or unclean bandwidth part (BWP) or at least one clean or unclean physical resource block (PRB). Additionally or alternatively, at least one clean or unclean BWP or at least one clean or unclean PRB may correspond to one or more component carriers (CCs). In other words, the UAI may include information about clean (e.g., non-conflicting or non-problematic) resources or unclean (conflicting or problematic) resources, which may be used by the network to constrain, limit or prohibit the use of unclean resources. Additionally or alternatively, according to some embodiments, the UAI may be received via medium access control-control element (MAC-CE) signaling.

[0184] According to some embodiments, the UAI may include an indication of clean and / or unclean resources, wherein the clean resources correspond to resources that are not associated with conflicts, and the unclean resources are associated with one or more conflicts. Additionally or alternatively, according to some embodiments, the UAI may include an indication of conflicts and various mappings between clean resources and unclean resources, potential conflicts and their related parameters, and a bit field in the UAI signaling, or any combination thereof. In some embodiments, the UAI may include an indication of a preferred TDM mode for UL and / or DL. Therefore, according to some embodiments, the NW may be able to configure the UE with a recommended DRX configuration, or perform scheduling based on the HARQ reservation mode indicated by the UE.

[0185] In 710, the NW may restrict (e.g., as some examples, by deactivating, deconfiguring, or releasing) the use of one or more resources associated with one or more IDC problems based on the received UAI. For example, a base station or network node may use FDM to specifically allocate resources (and / or ignore / avoid reported problematic resources) to effectively reduce or mitigate interference issues that may have occurred if problematic or conflicting resources have been used for subsequent communications or other operations. According to some embodiments, the restriction of unclean resources may correspond to at least one of the following: using only (e.g., transferring or allocating) clean resources on one or more CCs, deconfiguring / deactivating / releasing unclean resources or restricting / prohibiting their use, or releasing a secondary cell (SCell) on one of the one or more CCs associated with unclean resources.

[0186] According to some embodiments, the network node may be able to limit or release unclean resources in order to avoid using conflicting resources. For example, the network may release one or more of at least one unclean BWP or at least one unclean PRB on one of the one or more CCs. Additionally or alternatively, the network node may release a secondary cell (SCell) on one of the one or more CCs based on at least one unclean BWP or one or more unclean PRBs. In some embodiments, the network node may allocate resources to one or more CCs based on at least one clean BWP or one or more clean PRBs. In other words, the network may be able to avoid subsequent communication errors or problems by releasing BWPs, PRBs, or secondary cells corresponding to unclean resources and allocating appropriate resources corresponding to other resources (such as any reported clean resources).

[0187] In other words, the presented method may allow the UE to detect internal problems or the potential for internal problems caused by coexistence related to the use of certain radio resources. Additionally, in scenarios where the UE cannot resolve these problems on its own, the UE may seek to provide this information to the network for assistance. Thus, the NW may constrain, limit or prohibit radio resource usage to avoid UE internal problems (or potential problems) caused by coexistence.

[0188] According to some embodiments, the IDC report may be provided, sent or forwarded to various nodes or a combination thereof. For example, the IDC report may be provided only to a master node (MN) (LTE or NR), only to a secondary node (SN) (LTE or NR), or to both MN and SN. Additionally or alternatively, the IDC report may also include information about the direction of interference (e.g., parameters such as InterferenceDirection). For example, according to some embodiments, InterferenceDirection may allow the UE (and the network) to distinguish or determine which radio access technologies (RATs) are victims or aggressors (causes) of interference. More specifically, according to some embodiments, InterferenceDirection may be used to indicate the interference role (e.g., victim or aggressor) of only a master node (MN) (LTE or NR), only a secondary node (SN) (LTE or NR), MN and SN, MN and another RAT, SN and another RAT, MN, SN and another RAT, and / or only another RAT.

[0189] In some embodiments, the prohibition timer can be used to specify or enable a certain reporting scheme or schedule. For example, according to some embodiments, the NW may be able to configure the IDC report prohibition timer to the UE. Once the UE sends the UAI, the UE may start the prohibition timer (e.g., the IDC report timer). Therefore, according to some embodiments, when the prohibition timer is running, the UE may not be able to send the UAI again. In some embodiments, it may be beneficial for the network node to control the frequency of the UE providing the UAI by prohibiting the UE from sending the UAI when the prohibition timer is running. According to some embodiments, the IDC report may include sending the UAI to the network. For example, according to some embodiments, the IDC report or the IDC report message may include the UAI or be included as part of the UAI. Additionally or alternatively, the UAI may include or be included as part of the IDC report or the IDC report message.

[0190] However, it should be noted that Figure 7 Examples and About Figure 7 The exemplary details described are not intended to limit the present disclosure as a whole: many variations and alternatives to the details provided herein below are possible and are to be considered within the scope of the present disclosure.

[0191] Figure 8A-8C — Enhanced IDC reporting using frequency division multiplexing (FDM)

[0192] Figure 8A-8C is a flow chart illustrating aspects and methods for enhanced IDC reporting involving frequency division multiplexing (FDM) according to some embodiments.

[0193] In some embodiments, when a UAI including a bandwidth part (BWP) report is received from a UE, the NW may incorporate frequency division multiplexing (FDM). For example, a serving cell and a BWP may be configured for the UE, and the UE may indicate an IDC problem to the NW based on the BWP currently configured on the serving cell. According to some embodiments, when a UAI including a physical resource block (PRB) report is received from a UE, the NW may incorporate FDM. For example, according to some embodiments, the UE may perform an IDC report corresponding to the PRB of the serving cell that has been configured for the UE. In other scenarios, the UAI including the corresponding PRB may be based on the target frequency (ARFCN) configured by the network (NW).

[0194] In some embodiments, the NW may utilize FDM to IDC reporting corresponding to one or more reported BWPs. In other words, the NW may implement FDM based on UAI from the UE. For example, the UE may report a "clean" (e.g., not associated with an IDC problem) downlink or uplink (DL / UL) BWP number or a "non-clean" (e.g., associated with an IDC problem) DL / UL BWP number. Additionally or alternatively, the UAI may include a UL BWP number indicating that the 3GPP RAT affects or can affect another RAT. In some embodiments, the UAI may include a DL (as a possible extension to the UL) BWP number indicating that another RAT affects or can affect the 3GPP RAT.

[0195] In some embodiments, the UE may provide the UAI to the network based on the configured serving cell and using one or more PRBs. Fig. 8A As shown, according to some embodiments, the UE may report or send a UAI that includes one or more starting points of the lower edge of the component carrier CC 804a based on clean or unclean resources (such as PRB 802a and / or PRB 806a). Additionally or alternatively, the UE may report the starting point based on the lower edge of the CC and the end point of clean or unclean resources (such as PRB 802a and / or PRB 806a). In other words, the UE may provide the network with information necessary to determine which PRBs are considered clean or unclean.

[0196] According to some embodiments, the UE may provide the network with UAI based on the target frequency configured by the network. For example, as shown in FIG8b, according to some embodiments, the UE may report (e.g., send UAI) the start and / or end points of clean or unclean resources (e.g., PRBs 802b and 804b based on an absolute radio frequency channel number (ARFCN) (e.g., a target frequency). In other words, the UE may provide the network with information necessary to determine which PRBs are considered clean or unclean based on or in relation to the target frequency.

[0197] In some embodiments, the UE may be configured to provide hybrid UAI to the network on both BWP and PRB. In other words, the UE may apply both CC-based IDC reporting and target frequency-based IDC reporting. Thus, the UE may be able to report clean or unclean resources at the PRB level for each BWP. For example, Figure 8C As shown, according to some embodiments, the UE may report one or more starting points of the lower edge of the component carrier CC 806c based on clean or unclean resources (such as PRB 802c, which may correspond to or be included in BWP 804c). Additionally or alternatively, the UE may report the starting point of BWP 804c based on the lower edge of CC 806c and the end point of the clean or unclean resources (which may include PRB 802c) of BWP 804c. In other words, the UE may provide the network with information necessary to determine which PRBs and / or BWPs are considered clean or unclean. Additionally or alternatively, according to some embodiments, the number of BWPs and PRB resources may be based on the lower edge of the BWP.

[0198] It is also noted that, according to various implementations, the techniques described herein may be applied to either or both of the NR and LTE IDC reports or IDC-related UAI techniques.

[0199] Figure 9A-9D — Enhanced IDC reporting for single carrier reporting and carrier aggregation reporting

[0200] Figure 9A-9D Various aspects and methods for enhanced IDC reporting or IDC UAI involving single carrier FDM and carrier aggregation FDM according to some embodiments are illustrated. More specifically, Fig.9A illustrates the BWP configuration of two different component carriers, and Figure 9B-9D Harmonics and IMD signals corresponding to the UE's IDC reporting of clean or unclean resources are illustrated.

[0201] For example, according to some embodiments, Fig.9A Includes CC#1 902a corresponding to BWP1, BWP2, BWP3, and BWP4. Additionally, Fig.9A CC#2 904a is illustrated which may correspond to BWP1 and BWP2. In a single carrier FDM scenario, the UE may report clean or unclean resources from a single carrier such as CC#1 902a or CC#2 904a.

[0202] Furthermore, in some embodiments, the affected resource report for a single CC may relate to a 3GPP RAT that affects another RAT due to harmonic distortion / interference. Thus, the UE may report a dirty or clean BWP to the network via UAI in order to receive assistance from the NW regarding potentially problematic resources (e.g., based on IDC issues). For example, Fig. 9B As shown, the UE may provide an IDC report to the network based on the BWP from CC#1 902a. More specifically, the UE may include certain BWPs in the report 904b (e.g., UAI), such as BWP1, BWP2, and BWP3 from CC#1 902a, which further correspond to clean or unclean resources. Thus, according to some embodiments, the synthesized harmonic signal from CC#1 is shown as 902b, which affects another RAT due to harmonic distortion / interference caused by IMD reporting.

[0203] According to some scenarios, a 3GPP RAT may affect another RAT due to intermodulation (IMD) issues from two or more (e.g., multiple) UL BWPs. Therefore, the UE may report unclean or clean BWPs from the same CC. In other words, the UE may be able to choose how to report clean or unclean resources and indicate them to the NW. For example, Fig. 9C As shown, the UE may provide an IDC report to the network based on the BWP from CC#1 902a. More specifically, the UE may include certain BWPs, such as BWP1 and BWP3 from CC#1 902a, in a report 904c (e.g., UAI), which further correspond to clean or unclean resources. Thus, according to some embodiments, the composite IMD signal of the two BWPs from CC#1 is shown as 902c, which may affect another RAT due to intermodulation (IMD) distortion / interference from the IDC report.

[0204] According to some embodiments, the affected resource report for CA may involve the 3GPP RAT that affects another RAT due to IMD issues. As an option, according to some embodiments, the UE may report non-clean resources (e.g., UL resources on two or more CCs) that will interfere with another RAT. However, these resources may cause IMD interference to other RATs (e.g., CC#1 UL BWP1 and CC#2 UL BWP 2 or CC#1 UL PRB resources and CC#2 UL BWP 2), such as Fig.9D More specifically, Fig.9DIllustrated is how a UE may perform IDC reporting to a network based on BWPs from two CCs (e.g., CC#1 902a and CC#2 904a). For example, a UE may provide an IDC report to a network based on BWPs from CC#1 in 904d and from CC#2 in 906d. More specifically, the UE may include certain BWPs in a report 904d (e.g., UAI), such as BWP1, BWP2, and BWP3 from CC#1 902a, which further correspond to clean or unclean resources from CC#1. Additionally or alternatively, the UE may include certain BWPs in a report 906d (e.g., UAI), such as BWP1 and BWP3 from CC#2 904a, which further correspond to clean or unclean resources from CC#2. Thus, according to some embodiments, a composite IMD signal from CC#1 and CC#2 is shown as 902d, which may affect another RAT due to IMD distortion / interference related to IDC reporting.

[0205] In addition, according to some scenarios, the IMD interference may not be limited to only two CCs. Therefore, according to some embodiments, NW processing may involve not using (e.g., restricting, limiting or prohibiting) resource pairs at the same time, and further releasing problematic UL BWPs on one CC or releasing a secondary cell (SCell). As a second option, the UE may report clean resources. For example, the UE may report resources on multiple CCs that do not interfere with another RAT. Therefore, according to some embodiments, NW processing may involve ensuring that clean BWP combinations are used on multiple CCs.

[0206] In some embodiments, by reporting the affected resources caused by 3GPP RAT affecting (or possibly affecting) another RAT due to one or more harmonic problems, the UE may be able to utilize FDM in a CA scenario. Thus, the UE may report a clean or unclean resource set corresponding to an UL BWP or PRB resource, and the NW processing may involve not using the unclean UL BWP or PRB resource. According to another scenario where another RAT affects (or is affecting) the 3GPP RAT, according to some embodiments, the UE may report unclean resources so that the affected DL BWP is reported on each affected CC or the affected PRB resources are reported. Additionally or alternatively, the UE may report clean resources so that the clean DL BWP on each CC is reported or the clean PRB resources are reported. Thus, the NW processing may involve only using the clean DL BWP as the active BWP. Additionally or alternatively, according to some embodiments, the NW may choose to release the unclean BWP. In addition, according to some embodiments, parameters such as InterferenceDirection included in the UAI can be used to distinguish between the above-mentioned scenarios, in which the 3GPP RAT affects another RAT due to harmonic or IMD issues (e.g., distortion / interference), or another RAT affects the 3GPP RAT.

[0207] Fig.10 — Enhanced IDC reporting for multi-RAT dual connectivity

[0208] Fig.10 An exemplary configuration of component carriers for enhanced IDC reporting for multi-radio access technology-dual connectivity (MR-DC) according to some embodiments is illustrated. More specifically, according to some embodiments, Fig.10 A master cell group (MCG) including CC#1 1002 corresponding to BWP1, BWP2, BWP3, and BWP4. Additionally, Fig.10 The secondary cell group (SCG) of CC#1 1004 is illustrated, which may correspond to BWP1 and BWP2. In MR-DC, the UE may also connect to another RATLTE CC#1 1006 that may not include any BWP. However, according to some scenarios, the SCG of CC#1 1008 may include BWP1 and BWP2.

[0209] In some embodiments, the affected resource report for the MR-DC scenario of IMD may be caused by problems from two cell groups or branches (e.g., two UL BWP / PRBs on two cell groups or branches). However, the UE IDC report can be performed in a similar manner as in CA. For example, according to some embodiments, the master node (MN) may configure IDC to the UE, and the UE may report the IDC information back to the MN. Additionally or alternatively, there may be coordination between the MN and the secondary node (SN). In some embodiments, the network node may receive a configuration for carrier aggregation (CA) from a secondary cell group (SCG). Additionally or alternatively, the network node may receive at least one bandwidth part (BWP) or absolute radio frequency channel number (ARFCN) from the SN. In some embodiments, the network may forward the UAI to the SN. In other words, according to some embodiments, the SN may provide the MN with SCG configurations for CA and BWP or target frequencies for IDC reporting. Additionally or alternatively, the MN may provide or forward IDC auxiliary information (reported by the UE) to the SN. Therefore, according to some embodiments, static NW processing may involve using actual BWP, SCell or PRB in one cell group (CG).

[0210] In some embodiments, it may be beneficial to constrain, limit or prohibit a node (e.g., SN) so that it cannot configure the BWP / SCell / PRB corresponding to the problematic resource combination. Additionally or alternatively, according to some embodiments, another node (e.g., MN) may be able to use another resource in the problematic resource pair. In addition, both nodes (e.g., MN and SN) may be able to reconfigure the BWP / SCell / PRB to ensure that only clean resources are configured. For example, according to some embodiments, in an Xn exchange (e.g., via an Xn interface), a node may reconfigure its BWP / SCell / PRB and notify the other node of the update. Additionally or alternatively, according to some embodiments, an Xn exchange may involve the MN notifying the SN which BWP / SCell / PRB to use (or not use).

[0211] According to some embodiments, in addition to the above-mentioned static exchange, dynamic NW processing may also correspond to NWs exchanging the BWP / SCell / PRB being used. Additionally or alternatively, according to some embodiments, when BWP switching / SCell addition / release / deactivation / activation occurs, the UE may send auxiliary information to the NW.

[0212] In some embodiments, the affected resource report for MR-DC may include scenarios involving harmonic (one UL) interference and IMD interference from one cell group or branch (two ULs on one cell group or branch). Therefore, the UE report content can be performed similarly to what is done for CA. However, in some embodiments, it may be beneficial to perform an independent NW processing process. For example, according to some embodiments, the MN or SN may be able to independently configure IDC for the UE. Therefore, there may be no coordination (related to IDC reporting) between the MN and the SN. In other words, according to some embodiments, the MCG or SCG may configure the UE to perform IDC reporting so that the UE reports IDC information directly to the MN or SN.

[0213] Figure 11-Figure 12 —Enhanced IDC reporting using MAC-CE

[0214] According to some embodiments, the UE may apply FDM based on IDC reporting by utilizing a medium access control-control element (MAC-CE). In other words, as an alternative to some of the above-mentioned FDM methods in which the UE may use a radio resource control (RRC) message for IDC reporting, the UE may also be capable of or configured to utilize MAC-CE to report IDC issues or resources associated with IDC issues.

[0215] For example, Fig.11 An exemplary MAC-CE structure illustrating how multiple BWP IDs 1104 and 1106 (e.g., as clean or non-clean resources) may be reported with respect to fields of an octet 1102 including the C1-C7 and UL / DL fields. In other words, according to some embodiments, the octet 1102 may be used to report the BWP IDs 1104 and 1106 using a mapping between the UL / DL and C1-C7 fields and the BWP IDs 1104 and 1106.

[0216] As another example, Fig.12 An exemplary MAC-CE structure illustrating how a PRB start, PRB number, or PRB end (e.g., as a clean or non-clean resource) may be reported or indicated with respect to fields of an octet 1202 including C1-C7 and UL / DL fields. In other words, according to some embodiments, octet 1202 may be used to report or indicate a PRB start (such as 1204) and a PRB number or a PRB end (such as 1206) using a mapping between the UL / DL and C1-C7 fields and 1204 and 1206.

[0217] Furthermore, BWP based reporting via MAC-CE may be an option since the BWP configuration may have been provided to the UE. Thus, once an IDC problem is detected, the UE may be able to report unclean or clean resources via MAC-CE using BWP or PRB.

[0218] Additional Information

[0219] According to some embodiments, the NW may be able to configure the maximum rejection probability. For example, the NW may configure the maximum number of rejections through the configuration of the parameter Otherconfig. For example, the Otherconfig parameter may include the first part of the code block, which includes:

[0220] IDC-Config-r11::=SEQUENCE{

[0221] idc-Indication-r11 ENUMERATED{setup}OPTION,--Need OR

[0222] Additionally, the Otherconfig parameter may include a second portion of a code block corresponding to the AutonomousDenial configuration, which includes:

[0223]

[0224] Additionally, the Otherconfig parameter may include a third portion of a code block corresponding to an IMD problem due to UL CA, which includes:

[0225] [[idc-Indication-UL-CA-r11ENUMERATED{setup}OPTIONAL–Cond idc-Ind

[0226] ]],

[0227] Additionally, the Otherconfig parameter may include a fourth portion of a code block corresponding to an IDC configuration for hardware sharing, including:

[0228] [[idc-HardwareSharingIndication-r13ENUMERATED{setup}OPTIONAL–Need OR

[0229] ]],

[0230] Additionally, the Otherconfig parameter may include a fifth portion of a code block corresponding to an IDC configuration for EN-DC, including:

[0231]

[0232] Additionally or alternatively, the UE report (e.g., IDC report, UAI) may include or be included in the InDeviceCoexIndication message. For example, the InDeviceCoexIndication message may include a first part of a code block, which includes:

[0233]

[0234]

[0235] Additionally, VictimSystemType-r11 may include:

[0236]

[0237] Additionally, TDM-AssistanceInfo-r11 may include:

[0238]

[0239]

[0240] Additionally, the InDeviceCoexIndication message may include a first portion of a code block related to hardware sharing, which includes:

[0241]

[0242] Additionally, the InDeviceCoexIndication message may include a second portion of a code block related to EN-DC, which includes:

[0243]

[0244] Additionally, the InDeviceCoexIndication message may include a third portion of a code block, which includes:

[0245]

[0246]

[0247] Additionally, according to some embodiments, the affectedCarrierFreqCombList parameter may indicate a list of E-UTRA carrier frequencies that may be affected by IDC issues due to intermodulation distortion and harmonics from E-UTRA when UL CA is configured. In some embodiments, affectedCarrierFreqCombList-r13 may be used when more than five serving cells are configured or the affected combination contains more than 32 MeasObjectIds. Additionally or alternatively, if affectedCarrierFreqCombList-r13 is included, affectedCarrierFreqCombList-r11 may not be included.

[0248] In some embodiments, the affectedCarrierFreqCombMRDC parameter may indicate a set of at least one NR carrier frequency and optionally one or more E-UTRA carrier frequencies that are affected by IDC issues due to intermodulation distortion and harmonics when MR-DC is configured.

[0249] Yet another exemplary embodiment may include a device comprising: an antenna; a radio coupled to the antenna; and a processing element operably coupled to the radio, wherein the device is configured to implement any or all of the foregoing examples.

[0250] Yet another exemplary embodiment may include a method, the method comprising: performing, by an apparatus: any or all of the foregoing examples.

[0251] Another example embodiment may include a non-transitory computer-accessible storage medium that, when executed at a device, causes the device to implement any or all of any of the foregoing examples.

[0252] Still another exemplary embodiment may include a computer program including instructions for performing any or all portions of any of the foregoing examples.

[0253] Still another exemplary embodiment may include an apparatus including means for performing any or all of the elements of any of the foregoing examples.

[0254] Still another example embodiment may include an apparatus including a processing element configured to cause a wireless device to perform any or all elements of any of the foregoing examples.

[0255] 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 the authorized use should be clearly stated to users.

[0256] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0257] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if executed by a computer system, the program instructions cause the computer system to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0258] In some embodiments, a device (e.g., UE 106 or BS 102) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any method implementation of the method implementations described herein or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0259] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method, comprising: By User Equipment (UE): establishing a radio resource control (RRC) connection with a network node; receiving an RRC reconfiguration message from the network node; determining at least one of one or more clean resources or one or more non-clean resources based on the RRC reconfiguration message, wherein the one or more non-clean resources correspond to at least one in-device coexistence (IDC) conflict; as well as Uplink assistance information (UAI) is sent to the network node, wherein the UAI includes information corresponding to one or more start points and one or more end points of at least one of the one or more clean resources or the one or more non-clean resources.

2. The method of claim 1 , wherein the information comprises one or more resource numbers of the one or more clean resources and the one or more unclean resources, and wherein at least one of the one or more start points or one or more end points is reported by the UE with respect to at least one of a lower edge of a component carrier (CC) or an absolute radio frequency channel number (ARFCN).

3. The method of claim 1, wherein the one or more clean resources and the one or more unclean resources are at least one of one or more bandwidth parts (BWPs) or one or more physical resource blocks (PRBs).

4. The method of claim 1 , wherein the RRC reconfiguration message comprises configuration information corresponding to at least one of: Carrier aggregation; Dual connection; one or more BWPs; or An Absolute Radio Frequency Channel Number (ARFCN) configured by the network node.

5. The method of claim 1 , wherein the network node comprises a master node (MN) corresponding to a first radio access technology (RAT), and wherein the UAI is sent to at least one of: the MN; or A secondary node (SN) corresponding to the first RAT.

6. The method according to claim 1, further comprising: Configuration information corresponding to an IDC report prohibit timer is received from the network node.

7. The method according to claim 6, further comprising: The IDC report prohibit timer is started after sending the UAI, wherein when the IDC report prohibit timer is running, the UE is prohibited from sending additional UAI.

8. A method comprising: By network nodes: Establishing a radio resource control (RRC) connection with a user equipment (UE); Sending an RRC reconfiguration message to the UE; receiving uplink assistance information (UAI) from the UE, wherein the UAI includes information corresponding to at least one of one or more clean resources or one or more unclean resources associated with one or more component carriers (CCs), and wherein the one or more unclean resources correspond to at least one in-device coexistence (IDC) conflict; as well as Usage of the one or more non-clean resources is limited based on the UAI. 9 . The method of claim 8 , wherein the UAI comprises information corresponding to at least one of one or more start points or one or more end points of at least one of the one or more clean resources or the one or more non-clean resources.

10. The method of claim 8, wherein the one or more clean resources and the one or more unclean resources are at least one of one or more bandwidth parts (BWPs) or one or more physical resource blocks (PRBs).

11. The method of claim 8, wherein the RRC reconfiguration message includes configuration information corresponding to at least one of: Carrier aggregation; Dual connection; one or more BWPs; or An Absolute Radio Frequency Channel Number (ARFCN) configured by the network node. 12 . The method of claim 8 , wherein limiting usage of the one or more non-clean resources comprises releasing one or more of the non-clean resources.

13. The method of claim 8, wherein limiting usage of the one or more unclean resources comprises releasing a secondary cell (SCell) on one of the one or more CCs.

14. The method of claim 8, wherein limiting usage of the one or more non-clean resources comprises at least one of: Perform scheduling based on hybrid automatic repeat request mode; configuring the UE to utilize a time domain multiplexing (TDM) mode; or The UE is configured to utilize a discontinuous reception (DRX) configuration.

15. The method according to claim 8, further comprising: receiving a secondary cell group (SCG) configuration for carrier aggregation (CA) from a secondary node (SN); as well as The UAI is forwarded to the SN.

16. The method according to claim 8, further comprising: Configuration information corresponding to an IDC report prohibit timer is sent to the UE, wherein when the IDC report prohibit timer is running, the UE is prohibited from sending additional UAI.

17. The method of claim 8, wherein the UAI is received via Medium Access Control - Control Element (MAC-CE) signaling.

18. A device, comprising: At least one processor, the at least one processor being configured to cause a user equipment (UE) to perform any one of the methods according to claims 1 to 7.

19. A device, comprising: At least one processor, the at least one processor being configured to cause the network node to perform any of the methods according to claims 8 to 17.

20. A computer program product comprising computer instructions which, when executed by one or more processors, perform the steps of the method according to any one of claims 1 to 17.

Images