Method and device for reporting in-device coexistence interference

Abstract

The present disclosure describes methods, systems, and devices for reporting in-device coexistence (I DC) interference. A method includes a user equipment (UE) sending an IDC report to a base station by: the UE receiving a report configuration from the base station; and the UE sending an IDC report to the base station in response to the trigger condition, the IDC report comprising at least one bandwidth unit affected by the IDC. Another method comprises: a base station receiving an IDC report from a UE by the following means: the base station sending a report configuration to the UE; and the base station receiving an IDC report from the UE in response to the trigger condition, the IDC report comprising at least one bandwidth unit affected by the IDC.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to methods and devices for reporting In-Device Coexistence (IDC) interference. Background Art

[0002] Wireless communication technology is driving the world towards an increasingly interconnected and networked society. An emerging trend in mobile communications is the parallel use of multiple wireless technologies in user equipment (UE), which includes but is not limited to mobile devices, tablets, and other communication modules. To support this parallel operation, these devices are equipped with more than one wireless transceiver, which are located in close proximity to each other. When one or more wireless transceivers are operating, one or more nearby transceivers may interfere with each other, resulting in IDC interference.

[0003] The present disclosure describes various embodiments for reporting IDC interference, resolving at least one problem / issue associated with IDC, making improvements in the field of wireless communication technology, and increasing the efficiency and performance thereof. Summary of the invention

[0004] The present disclosure relates to methods, systems and devices for wireless communication (more specifically, for reporting IDC interference). Various embodiments of the present disclosure can be beneficial for improving IDC reporting, reducing IDC interference, improving resource utilization efficiency and enhancing wireless communication performance.

[0005] In one embodiment, the present disclosure describes a method for wireless communication. The method includes: a UE sends an IDC report to a base station in the following manner; the UE receives a report configuration from the base station; and the UE sends an IDC report to the base station in response to a trigger condition, the IDC report including at least one bandwidth unit affected by the IDC.

[0006] In one embodiment, the present disclosure describes a method for wireless communication. The method includes: a base station receives an IDC report from a UE in the following manner: the base station sends a reporting configuration to the UE; and the base station receives an IDC report from the UE in response to a trigger condition, the IDC report including at least one bandwidth unit affected by the IDC.

[0007] In some other embodiments, a device for wireless communication may include: a memory storing instructions; and a processing circuit communicating with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0008] In some other embodiments, a device for wireless communication may include: a memory storing instructions; and a processing circuit communicating with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0009] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the above method.

[0010] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1A An example of a wireless communication system is shown, which includes a radio network node and one or more user equipments.

[0012] Figure 1B A schematic diagram showing in-device co-existence interference within the same UE.

[0013] Figure 2 An example of a network node is shown.

[0014] Figure 3 An example of a user device is shown.

[0015] Figure 4A A flow chart of a wireless communication method is shown.

[0016] Figure 4B A flow chart of another wireless communication method is shown.

[0017] Figure 5 A schematic diagram illustrating one non-limiting embodiment of wireless communication.

[0018] Figure 6 A schematic diagram illustrating another non-limiting embodiment of wireless communication. DETAILED DESCRIPTION

[0019] The present disclosure will now be described in detail below with reference to the accompanying drawings, which are a part of the present disclosure and show specific examples of embodiments by way of illustration. However, it should be noted that the present disclosure can be implemented in various different forms, and therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any embodiment set forth below.

[0020] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied by the context, not just the explicitly stated meanings. Likewise, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. The phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. For example, the subject matter intended to be claimed includes exemplary embodiments or combinations of all or part of embodiments.

[0021] Typically, terms can be understood at least in part based on their use in context. For example, terms such as "and", "or" or "and / or" used herein can include multiple meanings, which can depend at least in part on the context in which the terms are used. Typically, "or" if used in an association list, such as A, B or C, means A, B and C, which are used here for inclusion, and A, B or C, which are used here for exclusion. In addition, the terms "one or more" or "at least one" used herein, at least in part depending on the context, can be used to describe any feature, structure or characteristic in a singular sense, or can be used to describe a combination of features, structures or characteristics in a plural sense. Similarly, terms such as "one", "a kind of" or "the" can be understood to express singular or plural usage, at least in part depending on the context. In addition, the term "based on" or "determined by..." can be understood to not necessarily be intended to express a set of exclusive factors, but can allow the presence of additional factors that are not necessarily explicitly described, which also depends at least in part on the context.

[0022] The present disclosure describes methods and apparatus for reporting IDC interference.

[0023] Next Generation (NG) or 5th Generation (5G) wireless communications can provide a range of capabilities from high-speed downloads to support for real-time low-latency communications. NG mobile communication systems are moving the world toward an increasingly connected and networked society.

[0024] An emerging trend in mobile communications is to use multiple wireless technologies in parallel in UEs, which include but are not limited to mobile devices, tablets, and other communication modules. To support this parallel operation, these devices are equipped with more than one wireless transceiver, which are located in close proximity to each other. When one or more wireless transceivers are operating, one or more nearby transceivers may interfere with each other, resulting in IDC interference.

[0025] like Figure 1B As shown, due to the close proximity of multiple wireless transceivers within the same UE, the transmit power of one transmitter may be much higher than the receive power level of another receiver. As a non-limiting example, the UE may include a first transceiver for Long Term Evolution (LTE), a second transceiver for GPS, a third transceiver for Wi-Fi, and / or a fourth transceiver for Bluetooth (BT). IDC interference may exist between any combination of the above transceivers. For example, when the first transceiver transmits or receives on a frequency carrier or a combination of more than one frequency carrier, there may be a first interference 182 to the second transceiver and / or a second interference 184 to the third transceiver; and / or when the third transceiver transmits or receives on a frequency carrier or a combination of more than one frequency carrier, there may be a third interference 186 and / or a second interference to the second transceiver.

[0026] In some embodiments, in order to solve these problems, IDC-related mechanisms can be introduced. For example, in LTE, when the network instructs to report IDC assistance information, IDC can be triggered for the serving frequency and the non-serving frequency. In addition, current IDC problems and potential IDC problems on secondary frequencies and non-serving frequencies (with measurement objects configured) can be reported. In some embodiments, similar IDC solutions can be introduced for the cases of New Radio (NR) and / or Evolved Universal Terrestrial Radio Access (EUTRA) and NR Duel Connectivity (EN-DC).

[0027] In some embodiments, the concept of bandwidth part (Bandwidth Part, BWP) can be introduced into the wireless communication system. For each cell, the network can configure multiple BWPs for a UE, and only one BWP can be activated at a time. At the same time, the UE can report its capabilities according to the requirements of the network. For dual connection (Dual Connection, DC) / carrier aggregation (Carrier Aggregation, CA), the network can configure the BWP of each band entry according to the band combination (Band Combination, BC) capability of the UE. The network can switch the BWP through at least one of the following items: Radio Resource Control (Radio Resource Control, RRC) signaling, downlink control information (Downlink Control Information, DCI), BWP inactivity timer or random access (Random Access, RA) process. In some embodiments, RRC signaling may have the longest delay. Through all these methods, each BWP can be activated or deactivated separately according to its corresponding control information. For example, in DCI, the bandwidth part indicator is used to indicate which BWP of the current serving cell can be activated / deactivated, for example as shown in Table 1.

[0028] Table 1: Values ​​of the BWP indicator field

[0029]

[0030] In some embodiments, a dormant BWP may be introduced, in which the concept of cell groups may be introduced. The network may switch a group of secondary cells (SCells) to their respective dormant BWPs via DCI. When configuring a dormant BWP for an Scell, the network may also configure the dormant cell group to which it belongs; and / or then in the DCI, a bitmap may be introduced for the dormant feature. The bitmap size is equal to the number of configured SCell groups, where each bit of the bitmap corresponds to one SCell group. In some embodiments, this group-based concept may be limited to dormant BWPs.

[0031] In some embodiments, UEBC capability may be achieved for any combination of configured BWPs. In other words, all potential combinations of BWPs configured on different frequency bands may satisfy the requirements of the reported UEBC capability. In some embodiments, this implementation may have a serious negative impact on system performance.

[0032] The present disclosure describes various embodiments for reporting IDC interference, including more efficiently configuring and / or managing BWP, and addressing at least one problem / issue associated with IDC reporting, such as, but not limited to, carrier-based IDC schemes, whereby affected frequencies may not be adequately indicated.

[0033] Figure 1A A wireless communication system 100 is shown, including a core network (CN) 110, a radio access network (RAN) 130, and one or more UEs (152, 154, 156). The RAN 130 may include a wireless network base station, or a NG radio access network (NG-RAN) base station or node, which may include a nodeB (NB, such as a gNB) in a mobile telecommunication environment. In one embodiment, the core network 110 may include a 5G core network (5G Core Network, 5GC), and the interface 125 may include an NG interface.

[0034] See also Figure 1A , the first UE 152 may wirelessly receive one or more downlink communications 142 from the RAN 130, and wirelessly send one or more uplink communications 141 to the RAN 130. Similarly, the second UE 154 may wirelessly receive downlink communications 144 from the RAN 130, and wirelessly send uplink communications 143 to the RAN 130; the third UE 156 may wirelessly receive downlink communications 146 from the RAN 130, and wirelessly send uplink communications 145 to the RAN 130. Downlink communications may include, for example but not limited to, a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH), and uplink communications may include, for example but not limited to, a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0035] Figure 2An exemplary radio access network or wireless communication base station 200 is shown. The base station 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 to send / receive communications with one or more UEs and / or one or more other base stations. The base station may also include network interface circuitry 209 to enable the base station to communicate with other base stations and / or a core network (e.g., optical or wired interconnects, Ethernet and / or other data transmission media / protocols). The base station 200 may optionally include an input / output (I / O) interface 206 to communicate with an operator or the like.

[0036] The base station 200 may also include a system circuit 204. The system circuit 204 may include a processor 221 and / or a memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may be configured for one or more of the processors 221 to perform the functions of the base station. The parameters 228 may include parameters that support the execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0037] Figure 3An example UE 300 is shown. UE 300 may be a mobile device (e.g., a smartphone or a mobile communication module provided in a vehicle). UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a storage device 309. The display circuit may include a user interface 310. System circuit 304 may include any combination of hardware, software, firmware, or other logic / circuits. System circuit 304 may be implemented, for example, with one or more systems on a chip (Systems on a Chip, SoC), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), discrete analog and digital circuits, and other circuits. System circuit 304 may be part of an implementation of any desired functionality in UE 300. In this regard, the system circuit 304 may include logic that facilitates, for example, decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playing); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, such as Internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the I / O interface 306 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Other examples of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0038] refer to Figure 3, the communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuits 316 that handle the transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuits, digital to analog converters (DAC), shaping tables, analog to digital converters (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium. The signals transmitted and received may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver that supports transmission and reception under 2G, 3G, BT, Wi-Fi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA) +, 4G / LTE, and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether derived from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0039] refer to Figure 3 , the system circuit 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to implement the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, Wi-Fi, 3G, 4G, 5G, or other data that the UE 300 will send or has received through the communication interface 302. In various embodiments, the system power of the UE 300 may be provided by a power storage device such as a battery or a transformer.

[0040] The present disclosure describes several embodiments of methods and devices for reporting IDC interference, which may be partially or completely described in the above Figure 2 and Figure 3 The invention is implemented on a wireless network base station and / or user equipment described in the specification.

[0041] In various embodiments, Figure 4A A flow chart of a method 400 for wireless communication is shown, including: a UE sends an IDC report to a base station. The method 400 may include some or all of the following steps: step 410, the UE receives a report configuration from the base station; and / or step 420, the UE sends an IDC report to the base station in response to a trigger condition, the IDC report including at least one bandwidth unit affected by the IDC.

[0042] In various embodiments, Figure 4B A flow chart of a method 450 for wireless communication is shown, including: a base station receiving an IDC report from a UE. The method 450 may include some or all of the following steps: step 46, the base station sends a reporting configuration to the UE; and / or step 470, the base station receives an IDC report from the UE in response to a trigger condition, the IDC report including at least one bandwidth unit affected by the IDC.

[0043] In some implementations, the reporting configuration indicates at least one of the following: whether IDC reporting is supported; the granularity of IDC reporting; and / or the resource range that the IDC reporting needs to cover.

[0044] In some implementations, in addition to part, any one or all of the implementations / examples, the resource range includes at least one of the following: one or more cells and / or one or more frequencies.

[0045] In some implementations, in addition to a part, any one or all of the implementations / examples, the base station sends an RRC reconfiguration message to the UE, where the RRC reconfiguration message includes a reporting configuration.

[0046] In some embodiments, in addition to part, any one or all of the embodiments / examples, the trigger condition includes at least one of the following: when the UE is subject to IDC interference on at least one bandwidth unit affected by IDC; and / or when the UE is expected to be subject to IDC interference on at least one bandwidth unit affected by IDC.

[0047] In some implementations, in addition to some, any one, or all of the implementations / examples described, the bandwidth unit affected by IDC is a BWP.

[0048] In some embodiments, in addition to some, any or all of the described embodiments / examples, the BWP is a configuration BWP.

[0049] In some implementations, in addition to a portion, any one or all of the implementations / examples, the reporting configuration indicates the BWP granularity reported by the IDC or the Physical Resource Block (PRB) granularity per BWP.

[0050] In some implementations, in addition to part, any one or all of the implementations / examples, the IDC report also includes at least one of the following: one or more single BWPs; one or more first-category BWP combinations; and / or one or more second-category BWP combinations.

[0051] In some embodiments, in addition to part, any one or all of the embodiments / examples, each of one or more first-class BWP combinations includes at least two BWPs; and / or the at least two BWPs include a first BWP and a second BWP, wherein the first BWP and the second BWP are configured in a carrier for the UE, and / or the first BWP is configured in a first carrier for the UE, and the second BWP is configured in a second carrier for the UE.

[0052] In some embodiments, in addition to part, any one or all of the embodiments / examples, each of the one or more second-type BWP combinations includes at least one BWP and at least one frequency, wherein the at least one BWP is configured in a first carrier for the UE and the at least one frequency is configured in a second carrier for the UE.

[0053] In some implementations, except for some, any one or all of the implementations / examples, the first carrier belongs to a new radio (NR) radio access technology (RAT).

[0054] In some implementations, except for some, any one, or all of the described implementations / examples, the first carrier and the second carrier belong to the same RAT.

[0055] In some implementations, except for some, any one, or all of the implementations / examples, the first carrier and the second carrier belong to different RATs.

[0056] In some embodiments, in addition to part, any one or all of the described embodiments / examples, the IDC report also includes the victim type of each of one or more single BWPs, each of one or more first-class BWP combinations, or each of one or more second-class BWP combinations.

[0057] In some embodiments, in addition to part, any one or all of the embodiments / examples, the UE receives a reconfiguration message from a master cell group (MCG), which reconfiguration message includes a reporting configuration, wherein a secondary cell group (SCG) indicates to the MCG the BWP information of the reporting configuration.

[0058] In some implementations, in addition to some, any or all of the implementations / examples, in response to receiving the BWP-based IDC report, the MCG transmits the IDC report to the SCG.

[0059] In some implementations, in addition to some, any one or all of the implementations / examples, the bandwidth unit affected by IDC is a PRB.

[0060] In some implementations, in addition to a part, any one or all of the implementations / examples, the reporting configuration indicates the PRB granularity reported by the IDC.

[0061] In some embodiments, in addition to part, any one or all of the embodiments / examples, the IDC report includes at least one of the following: one or more PRB lists; one or more first-category PRB combinations; and / or one or more second-category PRB combinations.

[0062] In some implementations, in addition to some, any or all of the described implementations / examples, each of the one or more PRB lists includes one or more PRB ranges in one or more carriers for the UE.

[0063] In some embodiments, in addition to part, any one or all of the embodiments / examples, each of one or more first-type PRB combinations includes at least two PRB lists; and / or the at least two PRB lists include a first PRB list and a second PRB list, wherein each of the first PRB list and the second PRB list includes one or more PRBs in a carrier for the UE, and / or the first PRB list includes one or more PRBs in a first carrier for the UE, and the second PRB list includes one or more PRBs in a second carrier for the UE.

[0064] In some embodiments, in addition to part, any one or all of the embodiments / examples, each of the one or more second-type PRB combinations includes at least one PRB list and at least one frequency, wherein the at least one PRB list includes one or more PRBs in a first carrier for the UE, and the at least one frequency is configured in a second carrier for the UE.

[0065] In some embodiments, in addition to part, any one or all of the embodiments / examples, the PRB list is indicated by at least one of the following: the center frequency of the carrier in which the PRB list is located, the starting offset of the PRB list relative to the center frequency of the carrier, the width of the PRB list, the center frequency of the PRB list, and / or the PRB index in the PRB list that is the lowest PRB or lowest subcarrier.

[0066] In some embodiments, except for part, any one or all of the embodiments / examples, the width of the PRB list is represented by one of the following: the number of at least one PRB, the number of at least one carrier, or a combination of at least one PRB and at least one carrier.

[0067] In some implementations, except for some, any one, or all of the described implementations / examples, the first carrier and the second carrier belong to the same RAT.

[0068] In some implementations, in addition to a part, any one or all of the implementations / examples, one or more second-type PRB combinations belong to intra-RAT combinations.

[0069] In some implementations, except for some, any one, or all of the implementations / examples, the first carrier and the second carrier belong to different RATs.

[0070] In some implementations, in addition to part, any one or all of the implementations / examples, one or more second-type PRB combinations belong to inter-RAT combinations.

[0071] In some embodiments, in addition to part, any one or all of the described embodiments / examples, the IDC report also includes a victim type for each of one or more PRB lists, each of one or more first-class PRB combinations, or each of one or more second-class PRB combinations.

[0072] In some implementations, in addition to a part, any one or all of the implementations / examples, the UE receives a reconfiguration message from the MCG, the reconfiguration message including a reporting configuration, wherein the SCG indicates to the MCG the PRB information of the reporting configuration.

[0073] In some implementations, in addition to some, any one or all of the implementations / examples, in response to receiving a PRB-based IDC report, the MCG transmits the IDC report to the SCG.

[0074] The first set of embodiments

[0075] The present disclosure describes various non-limiting embodiments for reporting IDC reports, which can use the BWP level as a non-limiting example. These embodiments can generally be applied to other levels of IDC reporting (such as but not limited to carrier level, PRB level, subcarrier level, etc.).

[0076] In various instances of BWP-level IDC reporting methods, the UE may report BWP-based IDC, including at least one of the following types: a first type (type 1) IDC caused by a single BWP, a second type (type 2) IDC caused by a BWP combination, and a third type (type 3) IDC caused by a BWP-frequency combination. In some embodiments, type 3 IDC may include intra-RAT type 3 IDC and / or inter-RAT type 3 IDC.

[0077] In some implementations, for Type 1, the UE may indicate one or more BWPs affected. For Type 2, the UE may indicate one or more BWP combinations. For Type 3, the UE may indicate one or more BWP-frequency combinations (including intra-RAT BWP-frequency combinations and inter-RAT BWP-frequency combinations).

[0078] In a non-limiting example of a BWP-based IDC type, the BWP and carrier configurations are as follows: For the serving cell and carrier information on the NR side, the primary cell (PCell): f1 UL BWP0 / 1 / 2 and DL BWP0 / 1 / 2; the secondary cell (Scell): f2 UL BWP0 / 1 and DL BWP0 / 1 / 2 / 3; and the non-serving cell f4. This configuration may indicate that the Pcell is on f1 and is configured with UL BWP0 / 1 / 2 and DL BWP0 / 1 / 2, and the Scell ​​is on f2 and is configured with UL BWP0 / 1 and DL BWP0 / 1 / 2 / 3. The frequencies on the EUTRA (also known as Eutra) side are as follows: The frequencies of the Eutra measurement objects are f5 and f6.

[0079] The different IDC interference types are as follows.

[0080] For Type 1 IDC, Pcell: f1 UL BWP0 / 1 and DL BWP0 / 2; Scell: f2 UL BWP0 and DL BWP0 / 3.

[0081] For Type 2 IDC, f1+f2: f1 UL BWP0+f2 BWP0.

[0082] For type 3 IDC within RAT, f1+f4: f1 UL BWP1+f4 (BWP+frequency combination); f2+f4: f2 UL BWP0+f4 (BWP+frequency combination).

[0083] For another inter-RAT type 3 IDC, f1+f5 (EN / NE-DC BC): f1 UL BWP0+f5.

[0084] In some implementations, in order to report the above-mentioned BWP-level IDC type, the signaling structure may be designed as follows.

[0085] For Type 1 IDC with single carrier -> Affected BWP:

[0086] AffectedBwpList-r17::=SEQUENCE(SIZE(1..maxBWPIDC-r17))OFAffectedBwp-r17

[0087] AffectedBwp-r17::=SEQUENCE{

[0088] serCellIndex Integer(),

[0089] AffectedDLBwpperCellList-r17::=SEQUENCE(SIZE(1..maxBWPIDC-r17))OFAffectedBwpperCell-r17

[0090] AffectedULBwpperCellList-r17::=SEQUENCE(SIZE(1..maxBWPIDC-r17))OFAffectedBwpperCell-r17

[0091] interferenceDirection-r16 ENUMERATED{nr,other,both,spare}}.

[0092] For Type 2 IDC, in case of UL CA / DC, the affected UL BWP combinations are:

[0093] AffectedBWPCombList-r17::=SEQUENCE(SIZE(1..maxCombIDC-r17))OFAffectedBWPComb-r17

[0094] AffectedBWPComb-r17::=SEQUENCE{

[0095] affectedBWPComb-r17 SEQUENCE(SIZE(2..maxNrofServingCells))OF BWPIndexOPTIONAL,

[0096] victimSystemType-r16 VictimSystemType-r16}

[0097] BWPIndex::=SEQUENCE{serCellIndex / BWPID}.

[0098] For type 3 IDC within RAT, the affected UL BWP+NR frequency combinations are:

[0099] AffectedBWPCarrierCombList-r17::=SEQUENCE(SIZE(1..maxCombIDC-r17))OFAffectedBWPCarrierComb-r17

[0100] AffectedBWPCarrierComb-r17::=SEQUENCE{

[0101] affectedBWPComb-r17 SEQUENCE(SIZE(1..maxNrofServingCells))OF BWPIndexOPTIONAL,

[0102] affectedCarrierFreqCombNR SEQUENCE(SIZE(1..maxServCell))OF ARFCN-ValueNR OPTIONAL,

[0103] victimSystemType-r16 VictimSystemType-r16}

[0104] interferenceDirection-r16 ENUMERATED{nr,other,both,spare}}.

[0105] For inter-RAT type 3 IDC, where the affected UL BWP+Eutra frequency combination: a similar structure to intra-RAT type 3 may be reused, except that the frequency is Eutra frequency.

[0106] In some embodiments, the structures of intra-RAT Type 3 IDC and inter-RAT Type 3 IDC may also be merged with the selection structure.

[0107] In some implementations, for a BWP-based solution, the affected PRBs of each BWP may be introduced to further optimize the BWP-based solution.

[0108] In various examples of how the network configures BWP level reporting, the network may indicate that it supports / or requires BWP level IDC interference reporting.

[0109] In one non-limiting example, the network may configure BWP reporting using the following fields in the RRC reconfiguration message:

[0110] IDC-BWP-AssistanceConfig-r18 ENUMERATED{true};

[0111] In some embodiments, the network may also indicate the granularity it supports (e.g., BWP granularity or per-cell PRB granularity or per-BWP per-PRB granularity). In some embodiments, the network may configure which BWP-level information needs to be reported, for example, the network may indicate which cells or which BWPs are needed to report BWP-level IDC.

[0112] In another non-limiting example, the network may configure BWP reporting using the following fields in the RRC reconfiguration message:

[0113] idc-AssistanceConfig-r18 SetupRelease{IDC-AssistanceConfig-r18}

[0114] IDC-AssistanceConfig-r18::= SEQUENCE{

[0115] candidateServingCellIndexList-r18 CandidateServingCellIndexList-r18OPTIONAL,--Need M...}.

[0116] In some implementations, the network may configure BWP reporting using the relevant frequency or the indicated BWP index. For example, when the frequency is within the relevant frequency range / list or the BWP index is within the indicated BWP index range / list, the UE may only report the IDC for that frequency or BWP index.

[0117] In some implementations, the IDC report may also be configured by the network, for example, in other configuration signaling, to which level (eg, BWP level / PRB level / per-BWP PRB level) should be reported.

[0118] In various examples of triggering conditions and / or ways in which the UE triggers IDC reporting, when the UE experiences or anticipates experiencing an activation IDC problem on a configured BWP, the UE may trigger BWP-level IDC reporting.

[0119] In a non-limiting example, Figure 5 As shown, the UE can be connected to the first cell (cell 1) with the initial BWP (BWP0, 510) and the dedicated BWP (BWP1, 520). There are three instances of interference situations: interference situation 1 (531), interference situation 2 (532) and interference situation 3 (533). When there is no IDC interference on the initial BWP0 and BWP1, there is no need to report the IDC problem on the corresponding carrier.

[0120] For interference case 1, since both BWP0 and BWP1 overlap with interference case 1, the UE may report the affected BWP0 and BWP1.

[0121] For interference case 2, the UE may report the affected BWP1, but may not report BWP0, because there is no IDC interference from interference case 2 on BWP0, while there is IDC interference from interference case 2 on BWP1.

[0122] For interference case 3, since there is no IDC interference from interference case 3 on BWP0 or BWP1, the UE may not trigger BWP-level IDC reporting.

[0123] In some embodiments, the UE may report the assistance information modification. For example, once the network reconfigures the BWP, the UE may determine whether it also needs to modify the IDC assistance information reporting. When the IDC assistance information is different from the previous IDC assistance information, the UE may report the BWP-based IDC again.

[0124] In some implementations, a prohibition timer may be introduced to prevent the UE from sending the IDC unified air interface (UAI) too frequently. For example, before the prohibition timer expires, the UE is prohibited from sending the IDCUAI, and the prohibition timer may be reset after the expiration of the timing.

[0125] In some embodiments, the victim type may be reported per BC (for CA or DC).For BWP level reporting, BWP level victim type may be supported, which means that for each BWP, each BWP combination, or each BWP-frequency combination, the victim type may be indicated.

[0126] In some embodiments, for Multi-RAT Duel Connectivity (MR-DC), the SCG may indicate the BWP / PRB / carrier information to the MCG for IDC reporting configuration. The MCG may then indicate it to the UE via a reconfiguration message. In some embodiments, when the MCG receives the BWP-based IDC information, the MCG may transmit it to the SCG.

[0127] In some implementations, regarding carriers configured with BWP, a list of carriers / carrier combinations may be reported, and the BWP level information may be considered as supplementary information.

[0128] Second Group of Embodiments

[0129] The present disclosure describes various non-limiting embodiments for reporting IDC reports, which can use the PRB level as a non-limiting example. For PRB-based solutions, IDC interference can be reported at the PRB level. These embodiments can generally be applied to other levels of IDC reporting (such as but not limited to carrier level, BWP level, subcarrier level, etc.).

[0130] In various instances of PRB-level IDC reporting, the UE may report PRB-based IDC, including at least one of the following types: a first type (type 1) IDC caused by PRBs on a single carrier, a second type (type 2) IDC caused by a combination of PRBs on different frequencies, and a third type (type 3) IDC caused by a PRB-frequency combination (including intra-RAT PRB-frequency combination and inter-RAT PRB-frequency combination).

[0131] In some embodiments, for type 1, the UE may indicate the affected PRBs on one or more frequencies; for type 2, the UE may indicate PRB combinations on different frequencies; for type 3, the UE may indicate PRB-frequency combinations (including intra-RAT PRB-frequency combinations and inter-RAT PRB-frequency combinations).

[0132] In one non-limiting example of PRB-based IDC, the carriers are configured as follows: Pcell f1; Scell ​​f2; and non-serving cell f4. The frequencies of the Eutra measurement objects are f5 and f6.

[0133] The different IDC interference types are as follows.

[0134] For Type 1 IDC with a single carrier: Pcell f1; Scell ​​f2; and non-serving cell f4.

[0135] For Type 2 IDC with PRB combinations on different frequencies: f1+f2: f1 PRB range + f2 PRB range (intra-RAT combination); and f1+f5 (EN / NE-DC BC): f1 PRB range + f5 PRB range (inter-RAT PRB combination).

[0136] For Type 3 IDC in the same RAT for UL CA or DC (as intra-RAT IDC): f1+f4: f1 PRB range + f4; and f2+f4: f2 PRB range + f4.

[0137] For Type 3 IDC in different RATs for UL CA (as inter-RAT IDC): f1+f6 (EN / NE-DC BC): f1PRB range+f6.

[0138] In the present disclosure, each type of IDC may include multiple PRB ranges. A PRB range may be referred to as a PRB list, which includes one or more separate discrete PRB indices and / or one or more PRB index ranges.

[0139] In some embodiments, the PRB range in a carrier may be indicated / configured by one of the following options: For option 1, the PRB range / list is indicated / configured by the center frequency of the carrier, the starting offset of the PRB range / list relative to the center frequency of the carrier, and the width of the PRB range / list.

[0140] For option 2: The PRB range / list is indicated / configured by the center frequency of the PRB range / list and the width of the PRB range / list.

[0141] For option 3: The PRB range / list is indicated / configured by a dedicated starting PRB index (PRB0 corresponds to the lowest PRB for the carrier). In some embodiments, the PRB range / list is implicitly or explicitly indicated / configured by the starting subcarrier and the affected bandwidth. In some embodiments, the implicit method may refer to that the UE may indicate a Resource Indicator Value (RIV) value, as indicated by the BWP configuration. In some embodiments, a common SCS may be employed.

[0142] Figure 6An IDC interference PRB range / list 610 is shown. In one non-limiting example, for option 1: the UE may indicate the PRB range / list by the center frequency of the carrier (fx 620), offset (622) and width (624). The offset / width may also be represented by a number of PRBs or subcarriers.

[0143] For option 2: The UE may indicate the PRB range / list by the center frequency and width of the PRB range / list (fy 630).

[0144] For option 3: The UE may indicate the PRB range / list implicitly or explicitly by the starting PRB (PRBm 640) (or starting subcarrier z) and the bandwidth / width (eg, n PRBs / n subcarriers).

[0145] In some implementations, the signaling structure may be designed as follows.

[0146] For Type 1 IDC with single carrier -> Affected PRBs:

[0147] AffectedPRBList-r17::=SEQUENCE(SIZE(1..maxPRBIDC-r17))OFAffectedPRB-r17

[0148] AffectedPRB-r17::= SEQUENCE{

[0149] centryfreqency ARFCN-ValueNR;

[0150] offset Offset;

[0151] Range bandwidth / Number of PRBs}

[0152] OR

[0153] AffectedPRB-r17::= SEQUENCE{

[0154] centryfreqency ARFCN-ValueNR;

[0155] Range bandwidth / Number of PRBs}.

[0156] For Type 2 IDC, in case of UL CA / DC, the affected UL PRB combinations are:

[0157] AffectedPRBCombList-r17::=SEQUENCE(SIZE(1..maxCombIDC-r17))OFAffectedPRBComb-r17

[0158] AffectedPRBComb-r17::=SEQUENCE{

[0159] affectedPRBComb-r17 SEQUENCE(SIZE(2..maxNrofcarriers))OFAffectedPRBList-r17

[0160] OPTIONAL,

[0161] victimSystemType-r16 VictimSystemType-r16}.

[0162] For Type 3 IDC, the affected UL PRB+NR frequency combinations within the RAT are:

[0163] AffectedPRBCarrierCombList-r17::=SEQUENCE(SIZE(1..maxCombIDC-r17))OFAffectedPRBCarrierComb-r17

[0164] AffectedPRBCarrierComb-r17::=SEQUENCE{

[0165] affectedPRBComb-r17 SEQUENCE(SIZE(2..maxNrofcarriers))OFAffectedPRBList-r17 OPTIONAL,

[0166] affectedCarrierFreqCombNR SEQUENCE(SIZE(1..maxServCell))OF ARFCN-ValueNR OPTIONAL,

[0167] victimSystemType-r16 VictimSystemType-r16}.

[0168] For type 4 IDC, where the affected inter-RAT UL PRB+Eutra frequency combination: a similar structure to intra-RAT type 3 may be reused, except that the frequency is the Eutra frequency.

[0169] In various examples of how the network configures PRB-level reporting, the network should indicate that it supports / or requires PRB-level IDC interference reporting.

[0170] In one non-limiting example, the network may use the following fields in the RRC reconfiguration message to configure BWP reporting. In some implementations, the network may indicate that it supports / or requires PRB-level IDC interference reporting.

[0171] IDC-PRB-AssistanceConfig-r18 ENUMERATED{true}.

[0172] In some embodiments, the network may also indicate the granularity it supports (eg, per-cell PRB granularity or per-BWP per PRB granularity).

[0173] In another non-limiting example, the network may utilize the following fields to configure which carriers require a PRB level.

[0174] idc-AssistanceConfig-r18 SetupRelease{IDC-AssistanceConfig-r18}

[0175] IDC-AssistanceConfig-r18::= SEQUENCE{

[0176] PRBrequiredCarrier SEQUENCE(SIZE(1..maxcarrier))OF ARFCN-ValueNR...}.

[0177] The third group of embodiments

[0178] The present disclosure describes various non-limiting embodiments of network configurations for different RAT IDC reporting. Potential IDC interference types can be reported according to the network configuration as follows: Type 1: (potential) interference from / to a single frequency; Type 2: (potential) interference caused by UL CA BC or UL DC BC (NR-DC) within 3GPP RAT to DL reception of non-3GPP RAT; Type 3: (potential) interference caused by UL DC (EN-DC or NE-DC BC) BC between 3GPP RATs to DL reception of non-3GPP RATs.

[0179] In some implementations, various MR-DC architectures may be considered, including but not limited to the following four scenarios: Scenario 1: IDC reporting when the UE works in a single CC / CA->SA situation; Scenario 2: IDC reporting when the UE works in NR-DC; Scenario 3: IDC reporting when the UE works in NE-DC; Scenario 4: IDC reporting when the UE works in EN-DC. As shown in Table 2, the IDC type in each scenario may be reported.

[0180] Table 2: IDC interference types for each working scenario

[0181]

[0182]

[0183] In some implementations, for NE-DC, the UE also reports LTE Type 1 interference, which may indicate Eutra (single carrier) in other configurations of the reconfiguration message.

[0184] In some embodiments, for EN-DC, the UE also reports NR type 1 interference, which may indicate NR (single carrier) in other configurations of the reconfiguration message.

[0185] In some implementations, for NE-DC, the UE also reports LTE Type 2 interference, which may indicate Eutra (CA or DC) in other configurations of the reconfiguration message.

[0186] In some embodiments, for EN-DC, the UE also reports NR type 2 interference, which may indicate NR (CA or DC) in other configurations of the reconfiguration message.

[0187] In some embodiments, for NR SA, the UE also reports type 3 interference, which may indicate MR-DC (EN DC or NE-DC) in other configurations of the reconfiguration message.

[0188] In some implementations, for NE-DC, the UE also reports type 3 interference, which may indicate MR-DC (EN DC or NE-DC) in other configurations of the reconfiguration message.

[0189] In some implementations, based on various described embodiments, the network may configure IDC reporting using RAT information, single carrier / CA / DC information, PRB / BWP information and / or any combination thereof.

[0190] The present disclosure describes methods, apparatus, and computer-readable media for wireless communications. The present disclosure solves problems related to IDC interference reporting. The methods, devices, and computer-readable media described in the present disclosure can improve the performance of wireless communications by reporting IDC interference, thereby improving efficiency and overall performance. The methods, devices, and computer-readable media described in the present disclosure can improve the overall efficiency of wireless communication systems.

[0191] Throughout the specification, references to features, advantages, or similar language do not mean that all features and advantages that can be achieved with the solution are or should be included in any single implementation thereof. Instead, language referring to features and advantages should be understood to mean that a particular feature, advantage, or characteristic described in conjunction with an embodiment is included in at least one embodiment of the solution. Therefore, throughout the specification, discussions of features and advantages and similar language may, but do not necessarily, refer to the same embodiment.

[0192] Furthermore, in one or more embodiments, the described features, advantages, and characteristics of the present solution may be combined in any suitable manner. Based on the description herein, one of ordinary skill in the relevant art will recognize that the present solution may be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be found in certain embodiments that may not be present in all embodiments of the present solution.

Claims

1. A method for wireless communication, comprising: The user equipment (UE) sends an in-device coexistence (IDC) report to the base station in the following manner: The UE receives a reporting configuration from the base station; as well as The UE sends the IDC report to the base station in response to a trigger condition, where the IDC report includes at least one bandwidth unit affected by the IDC.

2. A method for wireless communication, comprising: The base station receives an in-device coexistence (IDC) report from a user equipment (UE) in the following manner: The base station sends a reporting configuration to the UE; as well as The base station receives the IDC report from the UE in response to a trigger condition, where the IDC report includes at least one bandwidth unit affected by the IDC.

3. The method according to any one of claims 1 and 2, wherein: The reporting configuration indicates at least one of the following: Whether the IDC reporting is supported; the granularity reported by the IDC; or The IDC reports the resource range that needs to be covered.

4. The method according to claim 3, wherein: The resource scope includes at least one of the following: one or more cells; or One or more frequencies.

5. The method according to any one of claims 1 and 2, wherein: The base station sends a radio resource control (RRC) reconfiguration message to the UE, where the RRC reconfiguration message includes the reporting configuration.

6. The method according to any one of claims 1 and 2, wherein: The trigger condition includes at least one of the following: When the UE is subjected to IDC interference on the at least one IDC-affected bandwidth unit; or When the UE is expected to be subject to IDC interference on the at least one IDC-affected bandwidth unit.

7. The method according to any one of claims 1 and 2, wherein: The bandwidth unit affected by IDC is a bandwidth part (BWP).

8. The method according to claim 7, wherein: The BWP is a configuration BWP.

9. The method according to claim 7, wherein: The reporting configuration indicates the BWP granularity or the per-BWP PRB granularity reported by the IDC.

10. The method according to claim 7, wherein: The IDC report includes at least one of the following: One or more single BWPs; One or more Category 1 BWP combinations; or One or more BWP combinations of the second category.

11. The method according to claim 10, wherein: Each of the one or more first type BWP combinations includes at least two BWPs; and The at least two BWPs include a first BWP and a second BWP, wherein: The first BWP and the second BWP are configured in a carrier for the UE, or The first BWP is configured in a first carrier for the UE, and the second BWP is configured in a second carrier for the UE.

12. The method according to claim 10, wherein: Each of the one or more second-type BWP combinations includes at least one BWP and at least one frequency, wherein the at least one BWP is configured in a first carrier for the UE, and the at least one frequency is configured in a second carrier for the UE.

13. The method according to claim 12, wherein: The first carrier belongs to a new radio (NR) radio access technology (RAT).

14. The method of claim 12, wherein: The first carrier and the second carrier belong to the same RAT.

15. The method of claim 12, wherein: The first carrier and the second carrier belong to different RATs.

16. The method of claim 10, wherein: The IDC report further includes a victim type of each of the one or more single BWPs, each of the one or more first-type BWP combinations, or each of the one or more second-type BWP combinations.

17. The method of claim 7, wherein: The UE receives a reconfiguration message from a primary cell group (MCG), the reconfiguration message including the reporting configuration, wherein a secondary cell group (SCG) indicates BWP information of the reporting configuration to the MCG.

18. The method of claim 17, wherein: In response to receiving the IDC report based on the BWP, the MCG transmits the IDC report to the SCG.

19. The method according to any one of claims 1 and 2, wherein: The bandwidth unit affected by IDC is a physical resource block (PRB).

20. The method of claim 19, wherein: The reporting configuration indicates a PRB granularity reported by the IDC.

21. The method of claim 19, wherein: The IDC report includes at least one of the following: one or more PRB lists; one or more first type PRB combinations; or One or more second type PRB combinations.

22. The method of claim 21, wherein: Each of the one or more PRB lists includes one or more PRB ranges in one or more carriers for the UE.

23. The method of claim 21, wherein: Each of the one or more first-type PRB combinations includes at least two PRB lists; and The at least two PRB lists include a first PRB list and a second PRB list, wherein: Each of the first PRB list and the second PRB list includes one or more PRBs in a carrier for the UE, or The first PRB list includes one or more PRBs in a first carrier for the UE, and the second PRB list includes one or more PRBs in a second carrier for the UE.

24. The method of claim 21, wherein: Each of the one or more second-type PRB combinations includes at least one PRB list and at least one frequency, wherein the at least one PRB list includes one or more PRBs in a first carrier for the UE, and the at least one frequency is configured in a second carrier for the UE.

25. The method according to any one of claims 22 and 24, wherein: The PRB list is indicated by at least one of the following: The center frequency of the carrier where the PRB list is located, the starting offset of the PRB list relative to the carrier center frequency, the width of the PRB list, the center frequency of the PRB list, or The PRB index in the PRB list as the lowest PRB or the lowest subcarrier.

26. The method of claim 25, wherein: The width of the PRB list is represented by one of the following: the number of at least one PRB, the number of at least one carrier, or a combination of at least one PRB and at least one carrier.

27. The method of claim 24, wherein: The first carrier and the second carrier belong to the same RAT.

28. The method of claim 24, wherein: The one or more second-type PRB combinations belong to intra-RAT combinations.

29. The method of claim 24, wherein: The first carrier and the second carrier belong to different RATs.

30. The method of claim 24, wherein: The one or more second-type PRB combinations belong to inter-RAT combinations.

31. The method of claim 21, wherein: The IDC report further includes a victim type of each of the one or more PRB lists, each of the one or more first-type PRB combinations, or each of the one or more second-type PRB combinations.

32. The method of claim 19, wherein: The UE receives a reconfiguration message from the MCG, where the reconfiguration message includes the reporting configuration, wherein the SCG indicates the PRB information of the reporting configuration to the MCG.

33. The method of claim 32, wherein: In response to receiving the PRB-based IDC report, the MCG transmits the IDC report to the SCG.

34. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read code from the memory and execute the method according to any one of claims 1 to 33.

35. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 33.

Images