Wireless communication method, terminal device and network device

Abstract

The invention provides a wireless communication method, terminal equipment and network equipment. The wireless communication method comprises the following steps that: if the terminal equipment determines or predicts that an IDC problem exists, the terminal equipment sends IDC auxiliary information of BWP granularity to network equipment. In the embodiment of the invention, when the terminal equipment sends the IDC auxiliary information to the network equipment, the IDC auxiliary information is the IDC auxiliary information taking the BWP as the granularity. Compared with the IDC auxiliary information taking ARFCN as granularity, the granularity of the IDC auxiliary information provided by the embodiment of the invention is finer, so that the precision of the frequency band which is determined by the network equipment and causes interference or is interfered is higher, and the network equipment can be better assisted to solve the data transmission interference problem caused by the IDC problem.

Description

Wireless communication method, terminal device and network device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art

[0002] In some cases, when a terminal device determines or predicts that an in-device coexistence (IDC) problem exists and the terminal device cannot resolve the IDC problem on its own, the terminal device can report IDC auxiliary information to the network device so that the network device can determine the frequency band causing interference or being interfered with.

[0003] In related technologies, terminal devices report IDC auxiliary information to network devices at the granularity of absolute radio frequency channel number (ARFCN), resulting in poor accuracy of the frequency bands causing or being interfered with when determined by network devices. This in turn leads to the inability to effectively resolve data transmission interference problems caused by IDC issues.

[0004] Summary of the Invention

[0005] The present application provides a wireless communication method, terminal device, and network device. The following introduces various aspects of the present application.

[0006] In a first aspect, a wireless communication method is provided, comprising: if a terminal device determines or predicts that an IDC problem exists, the terminal device sends IDC auxiliary information with a granularity of a bandwidth part (BWP) to a network device.

[0007] In a second aspect, a wireless communication method is provided, comprising: a network device receiving IDC auxiliary information with BWP granularity sent by a terminal device, wherein the IDC auxiliary information with BWP granularity is sent by the terminal device when it is determined or predicted that an IDC problem exists.

[0008] According to a third aspect, a terminal device is provided, comprising: a sending module configured to send IDC auxiliary information with a BWP granularity to a network device if the terminal device determines or predicts that an IDC problem exists.

[0009] In a fourth aspect, a network device is provided, comprising: a receiving module for receiving IDC auxiliary information with BWP granularity sent by a terminal device, wherein the IDC auxiliary information with BWP granularity is sent by the terminal device when it is determined or predicted that an IDC problem exists.

[0010] In a fifth aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0011] In the sixth aspect, a network device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the second aspect.

[0012] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided in the embodiment of the present application.

[0013] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a terminal device / network device to execute part or all of the steps in the methods of the above aspects.

[0014] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a terminal device / network device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0015] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0016] In the embodiment of the present application, when the terminal device sends (or reports) IDC auxiliary information to the network device, the IDC auxiliary information is IDC auxiliary information with BWP as the granularity. Compared with IDC auxiliary information with ARFCN as the granularity, the IDC auxiliary information provided in the embodiment of the present application has a finer granularity, which enables the network device to determine the frequency band causing or being interfered with with higher accuracy, thereby better assisting the network device in resolving data transmission interference problems caused by IDC problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system applicable to an embodiment of the present application.

[0018] FIG2 is a schematic flow chart of a wireless communication method provided in an embodiment of the present application.

[0019] FIG3 is an example diagram of different BWPs configured in a network device according to an embodiment of the present application.

[0020] FIG4 is a schematic flow chart of a wireless communication method provided in another embodiment of the present application.

[0021] FIG5 is a flowchart of a wireless communication method provided in yet another embodiment of the present application.

[0022] FIG6 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.

[0023] FIG7 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.

[0024] FIG8 is a schematic structural diagram of the device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] Communication system architecture

[0026] FIG1 is a diagram illustrating an exemplary system architecture of a wireless communication system 100 to which embodiments of the present application may be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0027] FIG1 exemplarily shows a network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0028] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0029] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), new radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, non-terrestrial networks (NTN) system, universal mobile telecommunication system (UMTS), wireless local area network (WLAN) system, LTE-U system, NR-U system, non-terrestrial networks (NTN) system, universal mobile telecommunication system (UMTS), wireless local area network (WLAN) system, LTE-A system, LTE-FDD ... networks (WLAN), wireless fidelity (WIFI), fifth-generation (5G) systems, etc. The technical solutions provided in this application can also be applied to other communication systems, such as future communication systems, such as the sixth-generation mobile communication system, and satellite communication systems.

[0030] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application can also be applied to these communication systems.

[0031] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0032] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as a dedicated spectrum.

[0033] The embodiments of the present application can be applied to NTN systems as well as terrestrial networks (TN) systems. As an example and not a limitation, NTN systems include NR-based NTN systems and IoT-based NTN systems.

[0034] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0035] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, a modem or a chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0036] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0037] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0038] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0039] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0040] IDC issues

[0041] In the embodiments of the present application, the terminal device can communicate using multiple radio access technologies (RATs), such as 3GPP RATs (e.g., NR, LTE) and non-3GPP RATs (e.g., Wi-Fi, Bluetooth, etc.). The frequency bands used by the 3GPP RAT and the non-3GPP RAT may partially overlap. Therefore, when the terminal device transmits signals based on the 3GPP RAT and the non-3GPP RAT, mutual interference may occur, affecting the communication quality. This situation is called IDC interference.

[0042] Taking the NR system as an example, the terminal device may include communication modules based on NR technology and communication modules based on non-NR technology, such as Wi-Fi modules, Bluetooth modules, and global navigation satellite system (GNSS) modules. These non-NR technology-based communication modules usually use the industrial, scientific, and medical (ISM) frequency band. The frequency band used by NR technology may partially overlap with the ISM band, resulting in IDC interference.

[0043] In response to the IDC problem existing in terminal devices, an IDC solution has been introduced in the relevant technology. Specifically, when the terminal device determines or predicts that there is IDC interference and the terminal device cannot solve it by itself, the terminal device can report IDC indication information to the network device. The IDC indication information reported by the terminal device may include IDC auxiliary information, so that the network device can determine the frequency band that causes interference or is interfered with (in some embodiments, it can also be understood as the carrier frequency point or carrier frequency that causes interference or is interfered with), which is conducive to the network device determining a strategy that can enable the terminal device to reduce or eliminate IDC interference based on the IDC auxiliary information.

[0044] The following uses the NR system as an example to introduce the IDC solution for the NR system.

[0045] NR IDC solutions can include NR IDC frequency division multiplexing (FDM) solutions and NR IDC time division multiplexing (TDM) solutions. For the NR IDC FDM solution, the solution allows network devices to configure a set of candidate frequencies with ARFCNs granularity in the parameter RRCReconfiguration=>otherConfig=>IDC-assistanceConfig. The specific configuration information is shown below.

[0046]

[0047] Among them, CandidateServingFreqListNR is used to indicate the central frequency for each candidate NR service cell, and requires the terminal device to report IDC problems at the central frequency of these candidate NR service cells.

[0048] If the terminal device encounters (or will encounter) an IDC problem on any of these candidate ARFCNs (the central frequency of the candidate NR serving cell) and the terminal device cannot resolve it by itself, the terminal device can send an IDC indication message. The IDC auxiliary information included in the IDC indication message sent by the terminal device is as follows:

[0049] 1> If configured to provide IDC assistance information:

[0050] 2> If the terminal device has not sent a UEAssistanceInformation message with idc-Assistance since it was configured to provide IDC assistance information:

[0051] 3> If the terminal equipment encounters IDC problems that it cannot solve by itself on one or more frequencies included in candidateServingFreqListNR; or (if on one or more frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself; or)

[0052] 3> If the terminal device encounters IDC problems that it cannot solve by itself on one or more supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR:

[0053] 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;

[0054] 2> Or if the current IDC assistance information is different from the one indicated in the last transmission of the UEAssistanceInformation message:

[0055] 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information.

[0056] It should be noted that the term "IDC problems" refers to interference issues applicable across several subframes / slots where not necessarily all the subframes / slots are affected.

[0057] It should be noted that for one or more frequencies configured as active serving cells, IDC problems include interference problems that the terminal device cannot resolve on its own, either during active data exchange or during upcoming data activity expected to last for several hundred milliseconds. For one or more frequencies of inactive secondary cells (SCells), reporting an IDC problem indicates that the activation of one or more SCells is expected to result in interference problems that the terminal device cannot resolve on its own. For non-serving frequencies, reporting an IDC problem indicates that it is expected that if the non-serving frequency becomes a serving frequency, it will result in interference problems that the terminal device cannot resolve on its own.(For the frequencies on which a serving cell or serving cells is configured that is activated, IDC problems consist of interference issues that the UE cannot solve by itself, during either active data exchange or upcoming data activity which is expected in up to a few hundred milliseconds. For frequencies on which a SCell or SCells is configured that is deactivated, reporting IDC problems indicates an anticipation that the activation of the SCell or SCells would result in interference issues that the UE would not be able to solve by itself. For a non-serving frequency, reporting IDC problems indicates an anticipation that if the non-serving frequency or frequencies became a serving frequency or serving frequencies then this would result in interference issues that the UE would not be able to solve by itself.)。

[0058] Exemplarily, in the NR system, the content of UEAssistanceInformation is as follows.

[0059]

[0060]

[0061] In the UEAssistanceInformation message, the affectedCarrierFreqList field is used to indicate a list of NR carrier frequencies that are affected by IDC problem.

[0062] The affectedCarrierFreqCombList field indicates a list of NR carrier frequency combinations that are affected by IDC problems due to Inter-Modulation Distortion and harmonics from NR when configured with UL CA.

[0063] The interferenceDirection field is used to indicate the direction of IDC interference. The value nr indicates that only NR is victim of IDC interference, the value other indicates that only another radio is victim of IDC interference, and the value both indicates that both NR and another radio are victims of IDC interference. The other radio refers to either the ISM radio or GNSS. (interferenceDirection indicates the direction of IDC interference. Value nr indicates that only NR is victim of IDC interference, value other indicates that only another radio is victim of IDC interference, and value both indicates that both NR and another radio are victims of IDC interference. The other radio refers to either the ISM radio or GNSS.)

[0064] The victimSystemType field is used to indicate the list of victim system types to which IDC interference is caused from NR when configured with UL CA. Value gps,glonass,bds,galileo and navIC indicates the type of GNSS. Value wlan indicates WLAN and value bluetooth indicates Bluetooth.

[0065] Depending on the cause of the IDC problem, the IDC auxiliary information reported by the terminal device may include different types. Specifically, if the IDC problem is caused by a single frequency band (one or more carrier frequencies), the IDC auxiliary information can be carried in the field affectedCarrierFreqList, which can be used to indicate the information of the interfered carrier frequency and the IDC interference direction information. Among them, the information of the interfered carrier frequency can be carried in the field affectedCarrierFreqList=>carrierFreq, and carrierFreq is indicated by ARFCN; the IDC interference direction information can be carried in the field affectedCarrierFreqList=>interferenceDirection, and the value of interferenceDirection can include nr, other and both. If the IDC problem is caused by one or more uplink CA combinations (intermodulation interference) including carrier frequencies, the IDC auxiliary information can be carried in the field affectedCarrierFreqCombList, which can be used to indicate the information of the interfered carrier frequency combination and the victim system type information. Among them, the information of the interfered carrier frequency combination can be carried in the field affectedCarrierFreqCombList=>carrierFreqComb, and carrierFreqComb is indicated by ARFCN; the victim system type information can be carried in the field affectedCarrierFreqCombList=>victimSystemType, and the value of victimSystemType can include wlan, bluetooth and gps, etc.

[0066] As can be seen from the preceding description, in related technologies, terminal devices report IDC auxiliary information to network devices at the ARFCN granularity. This approach can lead to poor accuracy in determining the frequency bands causing or receiving interference, which in turn hinders the effective resolution of data transmission interference caused by IDC issues.

[0067] Regarding the above issues, the NR Release 18 (R18) IDC project work item description (WID) clearly states the following research objectives:

[0068] This work item aims to address interference between 3GPP (including various multi-radio dual connectivity architectures such as NR-DC and EN-DC) and non-3GPP RATs (e.g., Wi-Fi).

[0069] Research Goal 1: Enhancement of the FDM solution to allow for a more granular indication of the affected frequencies. It should be noted that enhancement of the FDM solution should be given priority.

[0070] Research Objective 2: Introduction of TDM solutions (e.g., indication of TDM mode preference in uplink / downlink scenarios). It should be noted that TDM solutions can serve as a supplement to FDM solutions.

[0071] Study Objective 3: Specify the radio resource management (RRM) requirements for TDM solutions.

[0072] It should be noted that the LTE IDC solution should be considered as the basis for the solutions proposed in this work item.

[0073] Based on this, in order to solve the above problems, the embodiments of the present application provide a wireless communication method, terminal device and network device, which can provide more fine-grained IDC auxiliary information, so that the network device can determine the frequency band causing interference or being interfered with with higher accuracy, thereby better assisting the network device to solve the data transmission interference problem caused by IDC problems.

[0074] The embodiments provided in this application are described in detail below with reference to the accompanying drawings. Figure 2 is a flow chart of a wireless communication method provided in one embodiment of this application. The method shown in Figure 2 is described from the perspective of the interaction between a terminal device and a network device. The terminal device and network device may be, for example, the terminal device 120 and network device 110 shown in Figure 1 above. The method shown in Figure 2 may include step S210, which is described in detail below.

[0075] In step S210, the terminal device sends IDC auxiliary information of BWP granularity to the network device.

[0076] In the embodiments of the present application, BWP-granular IDC auxiliary information may mean that the IDC auxiliary information sent by the terminal device to the network device is associated with the BWP. In other words, when the IDC auxiliary information is used to report the frequency band / band combination associated with the IDC problem to the network device, BWP-granular IDC auxiliary information can be understood as reporting the frequency band / band combination associated with the IDC problem to the network device via BWP indication information.

[0077] In some embodiments, the IDC auxiliary information is sent by the terminal device to the network device when the terminal device determines or predicts that an IDC problem exists.

[0078] In some embodiments, when there is mutual interference between 3GPP RAT (such as NR technology) and non-3GPP RAT (such as non-NR technology, such as WIFI, Bluetooth, etc.), it can be determined that the terminal device has an IDC problem.

[0079] In some embodiments, when mutual interference is about to occur between a 3GPP RAT and a non-3GPP RAT, it can be predicted that an IDC problem exists on a terminal device, or in other words, it can be determined that an IDC problem is about to occur on the terminal device. As an implementation method, a time period (preset time period) can be preset, and the terminal device can determine whether an IDC problem exists on the terminal device within the preset time period after the current moment. If the terminal device determines that an IDC problem exists on the terminal device within the preset time period after the current moment, it can be considered that the terminal device predicts that an IDC problem exists.

[0080] The embodiment of the present application does not limit the specific duration of the preset time period. For example, the unit of the preset time period can be a subframe, a time slot, a symbol, etc., or it can also be milliseconds, etc.

[0081] In some embodiments, the preset time period may be configured by a network device, may be set by the terminal device itself, or may be predefined by a protocol, and the embodiments of the present application do not limit this.

[0082] In some embodiments, the IDC problem is an IDC problem that the terminal device cannot resolve on its own. As an implementation method, when the terminal device determines or predicts the existence of an IDC problem, the terminal device may first determine whether the existing or impending IDC problem can be resolved on its own. If the terminal device determines that the IDC problem cannot be resolved on its own, the terminal device sends BWP-granular IDC auxiliary information to the network device.

[0083] In some embodiments, when the terminal device determines or predicts that an IDC problem exists, it is also necessary to determine whether IDC auxiliary information has been sent to the network device, or whether the sent IDC auxiliary information has changed. When the terminal device determines or predicts that an IDC problem exists and the terminal device has not sent IDC auxiliary information since being configured to request IDC auxiliary information, or the current IDC auxiliary information is inconsistent with the last sent IDC auxiliary information (i.e., the IDC auxiliary information has changed), the terminal device sends BWP-granular IDC auxiliary information to the network device.

[0084] In some embodiments, the IDC auxiliary information with BWP granularity sent by the terminal device to the network device may include IDC auxiliary information with BWP granularity corresponding to one or more frequency bands, or may include IDC auxiliary information with BWP granularity corresponding to one or more frequency band combinations. This embodiment of the present application is not limited to this.

[0085] It should be noted that the embodiment of the present application does not limit the name of IDC auxiliary information, as long as it can be used to indicate that the terminal device reports the frequency band / frequency band combination associated with the IDC problem to the network device. In some cases, IDC auxiliary information can also be replaced with other names, such as IDC indication information or first information, where the first information is used to indicate the frequency band / frequency band combination associated with the IDC problem.

[0086] Compared with the IDC auxiliary information with ARFCN granularity, the embodiment of the present application adopts the IDC auxiliary information with BWP granularity, which can provide the network equipment with finer-grained IDC auxiliary information, so that the network equipment can determine the frequency band causing interference or being interfered with with higher accuracy, thereby better assisting the network equipment to solve the data transmission interference problem caused by the IDC problem. This is because the network equipment can only determine that there is an IDC problem in one or some carriers based on the IDC auxiliary information with ARFCN granularity, that is, it is considered that there is an IDC problem in the entire carrier bandwidth. BWP is a group of continuous common resource blocks in the entire carrier bandwidth, which is a subset of the bandwidth of the total cell. Based on the IDC auxiliary information with BWP granularity, the network equipment can determine that there is an IDC problem in one or some BWPs on the carrier bandwidth, thereby ensuring that the accuracy of the frequency band causing interference or being interfered with is higher.

[0087] As mentioned above, the IDC auxiliary information at the BWP granularity can be understood as reporting the frequency band / frequency band combination associated with the IDC problem to the network device through the BWP indication information. The BWP indication information may include multiple types, which are not limited in the embodiments of the present application. For example, the BWP indication information may include one or more of the BWP identifier (ID), the frequency domain starting position corresponding to the BWP, the bandwidth, the subcarrier spacing, the cyclic prefix, and other information.

[0088] In some embodiments, BWP-level IDC assistance information may include BWP ID information corresponding to the frequency band / frequency band combination associated with the IDC problem. Using BWP ID information to indicate which frequency band / frequency band combination is affected, or indicating the affected carrier combination (including IDC problems caused by intermodulation interference and harmonic interference), can reduce signaling overhead.

[0089] In some embodiments, the BWP ID information reported by the terminal device needs to distinguish between uplink, uplink enhancement, and downlink. For example, the BWPs corresponding to the terminal device can be mapped in order, such as the BWP IDs for uplink are BWP 0-BWP 4, the BWP IDs for downlink are BWP 5-BWP 9, and the BWP IDs for uplink enhancement are BWP 10-BWP 14. In some embodiments, among these BWPs, BWPs with BWP IDs 0, 5, and 10 can be understood as the initial BWP corresponding to the terminal device.

[0090] In some embodiments, the IDC auxiliary information at the BWP granularity may further include other information, for example, one or more of the following information: IDC interference direction information; victim system type; and identification information for identifying the cell where the BWP is located.

[0091] Depending on the cause or scenario of the IDC problem, the information contained in the BWP-sized IDC auxiliary information may also be at least partially different. The following describes the information content contained in the BWP-sized IDC auxiliary information based on different causes of IDC problems.

[0092] In some embodiments, the IDC problem may be caused by a single frequency band (one or more carrier frequencies). In this case, the BWP-sized IDC auxiliary information sent by the terminal device may be associated with a single frequency band. When the IDC problem is caused by a single frequency band, the BWP-sized IDC auxiliary information sent by the terminal device may include one or more of the following information: BWP ID information corresponding to the frequency band associated with the IDC problem and IDC interference direction information.

[0093] As an implementation method, assuming that the existing field affectedCarrierFreqList is still used to carry IDC auxiliary information (of course, other fields, such as newly added fields, can also be used), this field can be used to indicate the information of the frequency band causing interference or interference and the IDC interference direction information. Among them, the information of the frequency band causing interference or interference can be carried in the field affectedCarrierFreqList=>carrierFreq (can be replaced by other fields, this is just an example), and carrierFreq is indicated by BWP (for example, BWP ID); IDC interference direction information can be carried in the field affectedCarrierFreqList=>interferenceDirection (can be replaced by other fields, this is just an example), and the value of interferenceDirection can include nr, other and both.

[0094] In some embodiments, if the IDC problem is caused by a single frequency band, the IDC auxiliary information with BWP granularity sent by the terminal device may include indication information of one or more BWPs (for example, including ID information of one or more BWPs). In this case, it can be understood that there is an IDC problem on the one or more BWPs. As an example, the primary cell (PCell) includes multiple BWPs (for example, BWP 1, BWP 2 and BWP 3). In the case that the IDC problem is caused by a single frequency band, the IDC auxiliary information with BWP granularity sent by the terminal device may include ID information of one or more BWPs (for example, BWP 1 and BWP 2). In this case, it can be understood that the one or more BWPs (i.e., BWP 1 and BWP 2) respectively (can also be replaced by other terms such as separate, single frequency band, etc.) cause the IDC problem or are interfered with by the IDC problem.

[0095] In some embodiments, the IDC problem may be caused by multiple frequency bands (one or more uplink CA combinations comprising carrier frequencies), or it can be understood that the IDC problem is caused by intermodulation interference or harmonic interference (IDC problem caused by one or more UL CA combination comprising of carrier frequency (inter-modulation interference)). In this case, the IDC auxiliary information with BWP granularity sent by the terminal device can be associated with multiple frequency bands, and the multiple frequency bands can be multiple frequency bands in CA or DC scenarios. In the case that the IDC problem is caused by multiple frequency bands, the IDC auxiliary information with BWP granularity sent by the terminal device may include one or more of the following information: ID information of the BWP corresponding to the frequency band combination associated with the IDC problem, the type of the victim system, and identification information for identifying the cell where the BWP is located.

[0096] In some embodiments, if the IDC problem is caused by multiple frequency bands in a CA or DC scenario, the frequency band combination associated with the IDC problem may include multiple BWPs, and the IDs of the corresponding BWPs may also be understood as a BWP ID combination.

[0097] As an implementation method, assuming that the existing field affectedCarrierFreqCombList is still used to carry IDC auxiliary information (of course, other fields, such as newly added fields, can also be used), this field can be used to indicate the information of the frequency band combination that causes interference or is interfered with and the type of victim system. Among them, the information of the frequency band combination that causes interference or is interfered with can be carried in the field affectedCarrierFreqCombList=>carrierFreqComb (can be replaced by other fields, this is just an example), and carrierFreqComb is indicated by BWP (for example, BWP ID combination); the victim system type information can be carried in the field affectedCarrierFreqCombList=>victimSystemType (can be replaced by other fields, this is just an example), and the value of victimSystemType can include wlan, bluetooth, and gps, etc.

[0098] In some embodiments, in a scenario where the IDC problem is caused by different frequency band combinations such as CA or DC, when indicating the BWP (for example, using the BWP ID indication), identification information for identifying the cell where the BWP is located can also be added to distinguish between BWPs in different cells. The embodiment of the present application does not specifically limit the type of identification information used to identify the cell where the BWP is located. For example, the identification information can be a physical cell identifier (PCI), a cell global identifier (CGI), etc.

[0099] In some embodiments, if the IDC problem is caused by different frequency band combinations such as CA or DC, the BWP-granular IDC auxiliary information sent by the terminal device may include indication information of the BWP combination (for example, BWP ID combination information). In this case, it can be understood that the IDC problem is caused by the BWP combination. As an example, BWP 1 / BWP 2 of PCell and BWP 3 of SCell form a BWP combination (that is, a BWP combination composed of multiple frequency bands in CA or DC scenarios). The BWP combination generates second harmonics, which modulate each other to form a mixed signal. The mixed signal causes IDC interference to external signals (for example, WIFI, Bluetooth, etc.).

[0100] The introduction of BWP-sized IDC auxiliary information in this embodiment of the present application can effectively improve the accuracy of the reported frequency bands / frequency band combinations associated with IDC issues. However, in some cases, there may be frequency band overlap between the BWPs configured on network devices. In this case, when the frequency band associated with the IDC issue happens to be in the overlapping area between the BWPs, how the terminal device should report the BWP-sized IDC auxiliary information and how the network device should understand the BWP-sized IDC auxiliary information reported by the terminal device are issues that need to be addressed.

[0101] The following, combined with Figure 3, details the issues that arise when reporting IDC auxiliary information when there is frequency band overlap between BWPs. As shown in Figure 3, the network device is configured with three different BWPs to accommodate different application scenarios. These three BWPs correspond to different bandwidths and subcarrier spacings. BWP 1 has a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 2 has a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 3 has a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. As shown in the example in Figure 3, there is frequency band overlap between BWP 1 and BWP 2. Therefore, if the frequency band associated with an IDC issue happens to occur in the overlapping frequency band between BWP 1 and BWP 2, how should the terminal device report BWP-level IDC information? For example, should the terminal device report BWP 1, BWP 2, or both? In addition, how network devices should understand the IDC information at the BWP granularity reported by terminal devices is also a problem that needs to be solved. For example, if the terminal device reports BWP 1 and BWP 2 at the same time, should the network device understand that there is an IDC problem in the frequency band corresponding to the intersection of BWP 1 and BWP 2, or that there is an IDC problem in the frequency band corresponding to the union of BWP 1 and BWP 2?

[0102] To address the above issues, in some embodiments, the BWP-granular IDC auxiliary information of the present application is determined by the terminal device according to a first rule. The first rule can be used by the terminal device to determine the BWP corresponding to the frequency band / band combination associated with the IDC issue. For example, the first rule can be used by the terminal device to determine the ID information of the BWP corresponding to the frequency band / band combination associated with the IDC issue.

[0103] The first rule mentioned in the embodiment of the present application may include multiple ones, as long as the first rule can ensure that the terminal device can clearly determine the IDC information of the BWP granularity, and / or the terminal device and the network device have the same understanding of the IDC auxiliary information of the BWP granularity.

[0104] Exemplarily, the first rule may include one or more of the following rules: selecting the BWP with the smallest bandwidth that includes the frequency band associated with the IDC problem as the BWP corresponding to the frequency band associated with the IDC problem; selecting all BWPs that include the frequency band associated with the IDC problem as the BWP corresponding to the frequency band associated with the IDC problem. Taking the example of BWP-granular IDC auxiliary information including BWP ID information, the first rule may specifically include one or more of the following rules: selecting the ID information of the BWP with the smallest bandwidth that includes the frequency band associated with the IDC problem as the BWP-granular IDC auxiliary information; selecting the ID information of all BWPs that include the frequency band associated with the IDC problem as the BWP-granular IDC auxiliary information.

[0105] Continuing with the example of FIG3 , if the frequency band associated with the IDC problem happens to occur in the overlapping area of ​​BWP 1 and BWP 2, as an example, the BWP ID with the smallest bandwidth associated with the IDC problem can be selected as the IDC auxiliary information at the BWP granularity, that is, BWP 2 can be selected as the IDC auxiliary information at the BWP granularity. In other words, the terminal device can report a smallest BWP (for example, BWP 2). In this case, the terminal device and the network device believe that the IDC problem occurs within the smallest BWP. As another example, all BWP IDs associated with the IDC problem can be selected as the IDC auxiliary information at the BWP granularity, that is, BWP 1 and BWP 2 can be selected as the IDC auxiliary information at the BWP granularity. In other words, the terminal device can report a list of all BWPs (for example, BWP 1 and BWP 2) where the IDC problem occurs.

[0106] However, the embodiments of the present application are not limited thereto. For example, the first rule may also include: selecting a BWP with the largest bandwidth that includes the frequency band associated with the IDC problem as the BWP corresponding to the frequency band associated with the IDC problem. Taking Figure 3 as an example, in this case, BWP 1 may be selected as the IDC auxiliary information with BWP granularity, that is, the terminal device may report a maximum BWP (e.g., BWP 1).

[0107] In some embodiments, if the IDC auxiliary information at the BWP granularity includes the ID information of multiple (at least two) BWPs, the network device considers that an IDC problem exists on all of the multiple BWPs. Alternatively, it can also be understood that, in some embodiments, the first rule may further include: if the IDC auxiliary information at the BWP granularity sent by the terminal device includes the ID information of multiple BWPs, the network device considers that an IDC problem exists on all of the multiple BWPs. Continuing with the example of FIG3 , if the frequency band associated with the IDC problem happens to occur in the overlapping area of ​​BWP 1 and BWP 2, if the IDC auxiliary information at the BWP granularity sent by the terminal device includes BWP 1 and BWP 2, the network device considers that an IDC problem exists on both BWP 1 and BWP 2.

[0108] The first rule may be predefined by the protocol or preconfigured, and this is not limited in the embodiments of the present application.

[0109] Determining the BWP corresponding to the frequency band associated with the IDC problem according to the first rule, or determining the IDC auxiliary information of BWP granularity corresponding to the frequency band associated with the IDC problem according to the first rule, can ensure that the terminal device clearly knows how to determine and report the IDC auxiliary information of BWP granularity, and further ensure that after the terminal device reports the IDC auxiliary information of BWP granularity, the network device and the terminal device have a consistent understanding of the IDC auxiliary information of the BWP granularity, thereby avoiding communication failure.

[0110] In some embodiments, the terminal device may send IDC auxiliary information of BWP granularity corresponding to the service frequency. In some embodiments, the terminal device may send IDC auxiliary information of BWP granularity corresponding to the non-service frequency. It should be understood that the service frequency may refer to the frequency corresponding to the service cell of the terminal device, or the frequency set by the service cell of the terminal device. The non-service frequency may refer to a frequency different from the frequency of the service cell of the terminal device, for example, it may be a frequency corresponding to the non-service cell. It should also be understood that the service frequency or non-service frequency corresponding to the terminal device may be variable, that is, the service frequency of the terminal device may become a non-service frequency after a period of time, and the non-service frequency of the terminal device may become a service frequency after a period of time.

[0111] In some embodiments, there may be multiple service frequencies corresponding to the terminal device. For example, in one implementation of DC, the terminal device may be in communication connection with multiple network devices at the same time and can receive / send data. The multiple network devices may include a master node and a secondary node. In DC, multiple service cells in the master node constitute a master cell group (MCG), and multiple service cells in the secondary node constitute a secondary cell group (SCG). Each cell in the MCG and each cell in the SCG can be called a service cell of the terminal device, and correspondingly, the frequency points corresponding to each cell in the MCG and the frequency points corresponding to each cell in the SCG can be called service frequencies of the terminal device.

[0112] The following is a brief introduction to the BWP mentioned in the embodiments of this application.

[0113] BWP can be understood as a set of continuous common resource blocks in the entire carrier bandwidth, which is a subset of the total cell bandwidth. In this way, by utilizing bandwidth adaptation, the sending and receiving bandwidth of the terminal device does not need to be as large as the cell bandwidth, and can be adjusted. For example, a small bandwidth can be allocated when the terminal device is in standby mode to reduce power consumption. In some embodiments, the position of BWP in the frequency domain can be adjusted, for example, the bandwidth position can be moved in the frequency domain to increase scheduling flexibility. In some embodiments, the subcarrier spacing can be changed by command to allow different services (or support different business types).

[0114] In some embodiments, a terminal device may be configured with multiple BWPs in the downlink, for example, 4 BWPs. In some embodiments, when a terminal device is configured with multiple downlink BWPs, only one BWP may be activated at a time.

[0115] In some embodiments, a terminal device can be configured with multiple BWPs for uplink, for example, four BWPs. In some embodiments, if the terminal device is configured with supplementary uplink (SUL), up to four additional BWPs can be configured for the supplementary uplink. In some embodiments, if a terminal device is configured with multiple uplink BWPs, only one BWP can be active at a time.

[0116] It should be noted that an activated BWP may mean that the working bandwidth of the terminal device is within the working bandwidth of the cell, and the terminal device receives / sends data on the activated BWP. Except for the activated BWP, other BWPs configured by the terminal device are deactivated. On the deactivated BWP, the terminal device does not receive / send data. For example, for the downlink, the terminal device cannot receive the physical downlink shared channel (PDSCH) / physical downlink control channel (PDCCH) / channel state information reference signal (CSI-RS) (except RRM) outside the activated BWP. Or, for the uplink, the terminal device cannot send the physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) outside the activated BWP.

[0117] In some embodiments, for an active cell, a terminal device cannot send a sounding reference signal (SRS) outside of an activated BWP.

[0118] In some embodiments, considering that a terminal device can be configured with multiple BWPs, but only one can be activated at the same time, dynamic switching is required to meet different services or scenarios. Therefore, in some embodiments, the network device can command the terminal device to dynamically switch the BWP. For example, the network device can dynamically switch the BWP through one or more of the following methods: RRC signaling, PDCCH (such as downlink control information (DCI)), BWP-associated timer (such as bwp-InactivityTimer), medium access control (MAC) entity initial random access process.

[0119] In some embodiments, each BWP may have its own subcarrier spacing and cyclic prefix.

[0120] In some embodiments, the center frequencies of the BWP pair (an activated uplink BWP and an activated downlink BWP) are the same. For example, when the communication system uses a time division duplexing (TDD) operation mode, the center frequencies of the BWP pair must be the same. In some embodiments, the center frequencies of the BWP pair can be different.

[0121] In some embodiments, for a group of uplink and downlink BWPs (e.g., a BWP pair) within a cell, the terminal device may be provided with one or more of the following parameters: subcarrierSpacing provides the subcarrier spacing; cyclicPrefix provides the cyclic prefix, and if the network does not set it, the default value, the normal cyclic prefix, is used; BWP-Id is used to distinguish each uplink and downlink BWP; BWP-DownlinkCommon and BWP-DownlinkDedicated provide common BWP and dedicated BWP parameters for downlink BWP; BWP-UplinkCommon and BWP-UplinkDedicated provide common BWP and dedicated BWP parameters for uplink BWP; the starting physical resource block (PRB) position of the BWP and the number of consecutive resource blocks (RB).

[0122] In some embodiments, the network device may instruct the terminal device whether to allow the terminal device to report IDC auxiliary information at the BWP granularity. For example, FIG4 is a flowchart of a wireless communication method provided by another embodiment of the present application. As shown in FIG4 , the method may include steps S410 and S420.

[0123] In step S410, the network device sends first indication information to the terminal device, wherein the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity.

[0124] In some embodiments, the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the service frequency.

[0125] In some embodiments, the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on a non-serving frequency point.

[0126] In some embodiments, the first indication information may be used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the serving frequency point and the non-serving frequency point.

[0127] As an implementation method, the first indication information may include multiple information fields, for example, a first information field and a second information field. The first information field can be used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the service frequency point, and the second information field can be used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the non-service frequency point.

[0128] As an implementation, if the first indication information is used only to indicate whether the terminal device is required to report BWP-granular IDC auxiliary information on the serving frequency, the first indication information may be 1-bit indication information, used to indicate "yes" or "no" respectively. For example, a value of 1 for the first indication information indicates "yes," and a value of 0 indicates "no." If the first indication information indicates "yes," the terminal device is required to send BWP-granular IDC auxiliary information to the network device when an IDC problem occurs on the serving frequency. If the first indication information indicates "no," the terminal device is not allowed to send BWP-granular IDC auxiliary information to the network device.

[0129] As another implementation method, if the first indication information can be used to simultaneously indicate whether the terminal device is required to report BWP-granular IDC auxiliary information on the service frequency and the non-service frequency, the first indication information can indicate separately for the service frequency and the non-service frequency, for example, using the multiple information fields described above for indication (the first indication information includes multiple information fields). In this case, if the first information field is used to indicate "yes", the terminal device needs to send BWP-granular IDC auxiliary information to the network device when an IDC problem occurs at the service frequency; if the first information field indicates "no", the terminal device is not allowed to send BWP-granular IDC auxiliary information to the network device when an IDC problem occurs at the service frequency. If the second information field is used to indicate "yes", the terminal device needs to send BWP-granular IDC auxiliary information to the network device when an IDC problem occurs at the non-service frequency; if the second information field indicates "no", the terminal device is not allowed to send BWP-granular IDC auxiliary information to the network device when an IDC problem occurs at the non-service frequency.

[0130] In some embodiments, the first indication information may be carried in the IDC assistance information reporting configuration information sent by the network device. The IDC assistance information reporting configuration information may be used to configure the terminal device to report IDC-related information. As an implementation method, the IDC assistance information reporting configuration information may be carried in the field idc-AssistanceConfig.

[0131] In some embodiments, the IDC auxiliary information reporting configuration information may be sent via RRC signaling. For example, it may be sent via RRC dedicated signaling. As a specific implementation, the IDC auxiliary information reporting configuration information may be carried in an other configuration information element (IE) of an RRC reconfiguration message, i.e., carried in the otherConfig IE of the RRC reconfiguration message.

[0132] In some embodiments, the IDC auxiliary information reporting configuration information may also include other information, such as a candidate serving frequency list. The candidate serving frequency list may be used to indicate the center frequency for each candidate serving cell, at which the terminal device is required to report IDC auxiliary information. As an implementation method, the candidate serving frequency list may be carried in the candidateServingFreqListNR field.

[0133] In step S420, when the first indication information requires the terminal device to report the IDC auxiliary information with a BWP granularity, the terminal device sends the IDC auxiliary information with a BWP granularity to the network device.

[0134] In the case where the first indication information requires the terminal device to report IDC auxiliary information with BWP granularity, for example, the terminal device is required to report IDC auxiliary information with BWP granularity on the service frequency and / or non-service frequency, if the terminal device determines or predicts that there is an IDC problem, the terminal device sends the IDC auxiliary information with BWP granularity to the network device.

[0135] In some cases, when the terminal device determines or predicts that there is an IDC problem, it also needs to determine whether the IDC problem can be solved by itself. If the terminal device determines that the IDC problem cannot be solved by itself, the terminal device sends BWP-granular IDC auxiliary information to the network device.

[0136] As an example, when the first indication information requires the terminal device to report IDC auxiliary information with BWP granularity on the service frequency and / or non-service frequency, if the terminal device is experiencing or is about to encounter an IDC problem on the service frequency or non-service frequency and cannot resolve it by itself, or if the terminal device is experiencing or is about to encounter an IDC problem on one or more CA / DC carrier frequency combinations (including service frequencies and / or non-service frequencies) and cannot resolve it by itself, the terminal device can send IDC auxiliary information with BWP granularity to the network device.

[0137] In some cases, when the terminal device determines or predicts that there is an IDC problem, it needs to further determine whether IDC auxiliary information has not been sent since it was configured to require the provision of IDC auxiliary information or whether the current IDC auxiliary information is inconsistent with the IDC auxiliary information sent last time. When the terminal device determines that IDC auxiliary information has not been sent since it was configured to require the provision of IDC auxiliary information, or the current IDC auxiliary information is inconsistent with the IDC auxiliary information sent last time (that is, the IDC auxiliary information has changed), the terminal device sends IDC auxiliary information with BWP granularity to the network device.

[0138] For other relevant contents about the terminal device sending the IDC auxiliary information of BWP granularity to the network device in step S420, please refer to the relevant description of step S210 above, which will not be repeated here.

[0139] In some embodiments, if the network device does not require the terminal device to report IDC auxiliary information with a BWP granularity, the terminal device may send IDC auxiliary information with an ARFCN granularity to the network device, that is, according to the existing technical solution.

[0140] As mentioned above, in some embodiments, the terminal device can report IDC auxiliary information with BWP granularity on non-service frequencies. However, BWP information is not configured on existing non-service frequencies, resulting in the network being unable to directly support reporting of IDC auxiliary information with BWP granularity on non-service frequencies. Based on this, in an embodiment of the present application, when the network device requires the terminal device to report IDC auxiliary information with BWP granularity on non-service frequencies, the method provided in the embodiment of the present application may further include: the network device sends first configuration information to the terminal device, and the first configuration information is used to configure corresponding candidate BWP information for the non-service frequency. In this way, the terminal device can report IDC auxiliary information with BWP granularity on the non-service frequency based on the configured candidate BWP information corresponding to the non-service frequency.

[0141] In some embodiments, specific parameters of the candidate BWP information corresponding to the non-serving frequency point can be configured with reference to the BWP of the serving cell, but the embodiments of the present application are not limited thereto.

[0142] In some embodiments, when a network device sends first configuration information to a terminal device, it can be considered that the first configuration information implicitly indicates that the terminal device is required to report IDC auxiliary information with BWP granularity, that is, the terminal device needs to report IDC auxiliary information with BWP granularity on a non-service frequency point that indicates candidate BWP information. As an implementation method, when sending the first configuration information, the sending of the first indication information can be omitted (for example, the second information field is not set or sent). In this case, when sending the first configuration information, it is considered that IDC auxiliary information with BWP granularity needs to be reported on a non-service frequency point that indicates candidate BWP information, and when not sending the first configuration information, it is considered that IDC auxiliary information with BWP granularity does not need to be reported on a non-service frequency point. Of course, the embodiments of the present application are not limited to this, and both the first indication information and the first configuration information can be sent.

[0143] In some embodiments, the first configuration information may be carried in the IDC auxiliary information reporting configuration information. In some embodiments, the first configuration information may also be carried in other messages, or may also be a separate message, which is not limited in the embodiments of the present application.

[0144] For ease of understanding, a specific implementation is given below. It should be understood that this implementation is only for illustration and is not intended to limit the technical solution of this application.

[0145] Figure 5 is a flow chart of a wireless communication method provided by another embodiment of the present application. As shown in Figure 5, the method may include step S510 and step S520.

[0146] In step S510, the network device sends IDC auxiliary information reporting configuration information to the terminal device.

[0147] The IDC auxiliary information reporting configuration information may include a candidate service frequency list and first indication information.

[0148] The candidate serving frequency list is used to indicate the center frequency for each candidate serving cell, at which the terminal device is required to report IDC auxiliary information. The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information at the BWP granularity.

[0149] In some embodiments, if the protocol specifies that only BWP-granular IDC assistance information reporting is supported for the serving frequency, the first indication information may be specific to the serving frequency. As an implementation, the first indication information may be a 1-bit indication, indicating "yes" or "no." If "yes" is indicated, the terminal device is required to report BWP-granular IDC assistance information when an IDC problem occurs on the serving frequency. If "no" is indicated, the terminal device is not permitted to report BWP-granular IDC assistance information when an IDC problem occurs on the serving frequency.

[0150] In some embodiments, if the protocol specifies that BWP granularity IDC auxiliary information reporting on both the serving frequency and the non-serving frequency is supported, then the first indication information needs to indicate the serving frequency and the non-serving frequency respectively.

[0151] For non-serving frequencies, the network device needs to configure corresponding candidate BWP information for the non-serving frequency for which the terminal device reports IDC auxiliary information with BWP granularity (i.e., configure the candidate BWP information through the first configuration information). In some embodiments, the specific parameters of the candidate BWP information can refer to the BWP configuration of the serving cell. In this case, the first configuration information can implicitly indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, that is, the terminal device needs to report IDC auxiliary information with BWP granularity on the non-serving frequency for which the candidate BWP information is indicated.

[0152] In some embodiments, the above-mentioned IDC auxiliary information reporting configuration information can be sent through RRC dedicated signaling, that is, it can be carried in other configuration IE (otherConfig) of the RRC reconfiguration message.

[0153] In step S520, if the terminal device determines or predicts that an IDC problem exists, the terminal device sends IDC auxiliary information of BWP granularity to the network device.

[0154] In some embodiments, when the terminal device detects an IDC problem and if the terminal device has not transmitted IDC auxiliary information since being configured to provide IDC auxiliary information, or the current IDC auxiliary information is inconsistent with the IDC auxiliary information transmitted last time (that is, the IDC auxiliary information has changed), the terminal device can send BWP-granular IDC auxiliary information to the network device if the network device requires reporting of BWP-granular IDC auxiliary information on the service frequency and / or non-service frequency.

[0155] In some embodiments, if the terminal device determines or predicts that an IDC problem exists and cannot be resolved by itself on a serving frequency or a non-serving frequency that indicates candidate BWP information, or if the terminal device determines or predicts that an IDC problem exists and cannot be resolved by itself on one or more CA / DC carrier frequency combinations (containing only serving frequencies and non-serving frequencies that indicate candidate BWP information), the terminal device may send BWP-granular IDC auxiliary information to the network device.

[0156] In some embodiments, the terminal device may select and report the BWP ID information of the BWP with the smallest bandwidth that can include the frequency band where the IDC problem occurs, that is, report a smallest BWP. In this case, it can be considered that the IDC problem occurs within the BWP.

[0157] In some embodiments, the terminal device may report a list of BWP ID information of all BWPs in the frequency band containing the IDC problem. In this case, it can be considered that all reported BWPs have the IDC problem.

[0158] In some embodiments, the reported BWP ID information needs to distinguish between uplink, uplink enhancement and downlink. For example, the respective four BWPs can be mapped in sequence: uplink: BWP 0-BWP 4, downlink: BWP 5-BWP 9, uplink enhancement: BWP 10-BWP 14 (BWP 0, BWP 5, BWP 10 are initial BWPs).

[0159] In some embodiments, for IDC problems caused by different frequency combinations such as CA / DC, the BWP ID information combination is reported. Therefore, in some embodiments, additional indication information is required to distinguish BWPs in different cells, such as PCI.

[0160] In some embodiments, if the network device does not indicate that the terminal device is required to report IDC auxiliary information with BWP granularity on the serving frequency or non-serving frequency, the terminal device can follow the existing NR IDC FDM solution.

[0161] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 5 , and the device embodiment of the present application is described in detail below in conjunction with Figures 6 to 8 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, and therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0162] FIG6 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application. The terminal device 600 shown in FIG6 may include a sending module 610.

[0163] The sending module 610 may be configured to send BWP-sized IDC auxiliary information to the network device if the terminal device determines or predicts that an IDC problem exists.

[0164] Optionally, the IDC auxiliary information at the BWP granularity includes: identification ID information of the BWP corresponding to the frequency band / frequency band combination associated with the IDC problem.

[0165] Optionally, the IDC auxiliary information of the BWP granularity is determined by the terminal device according to a first rule.

[0166] Optionally, the first rule includes one or more of the following rules: selecting the ID information of the BWP with the smallest bandwidth containing the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity; and selecting the ID information of all BWPs containing the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity.

[0167] Optionally, if the IDC auxiliary information at the BWP granularity includes ID information of at least two BWPs, IDC problems exist on the at least two BWPs.

[0168] Optionally, the IDC auxiliary information at the BWP granularity further includes one or more of the following information: IDC interference direction information; victim system type; and identification information for identifying the cell where the BWP is located.

[0169] Optionally, the IDC auxiliary information at the BWP granularity is associated with a single frequency band; and / or the IDC auxiliary information at the BWP granularity is associated with multiple frequency bands in a carrier aggregation or dual connectivity scenario.

[0170] Optionally, the terminal device 600 further includes a first receiving module 620. The first receiving module 620 may be configured to receive first indication information sent by the network device, where the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with a BWP granularity; and the sending module 610 is further configured to send the IDC auxiliary information with a BWP granularity to the network device if the first indication information requires the terminal device to report IDC auxiliary information with a BWP granularity.

[0171] Optionally, the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, including: the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the service frequency; and / or the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the non-service frequency.

[0172] Optionally, the first indication information is carried in IDC auxiliary information reporting configuration information sent by the network device.

[0173] Optionally, when the network device requires the terminal device to report IDC auxiliary information with BWP granularity on the non-serving frequency point, the terminal device 600 further includes a second receiving module 630. The second receiving module 630 can be used to receive first configuration information sent by the network device, where the first configuration information is used to configure corresponding candidate BWP information for the non-serving frequency point.

[0174] Optionally, the sending module 610 may be a transceiver 830 , as specifically shown in FIG8 .

[0175] FIG7 is a schematic diagram of the structure of a network device according to an embodiment of the present application. The network device 700 shown in FIG7 may include a receiving module 710.

[0176] The receiving module 710 may be configured to receive IDC auxiliary information with a BWP granularity sent by a terminal device. The IDC auxiliary information with a BWP granularity is sent by the terminal device when it is determined or predicted that an IDC problem exists.

[0177] Optionally, the IDC auxiliary information at the BWP granularity includes: identification ID information of the BWP corresponding to the frequency band / frequency band combination associated with the IDC problem.

[0178] Optionally, the IDC auxiliary information of the BWP granularity is determined by the terminal device according to a first rule.

[0179] Optionally, the first rule includes one or more of the following rules: selecting the ID information of the BWP with the smallest bandwidth containing the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity; and selecting the ID information of all BWPs containing the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity.

[0180] Optionally, if the IDC auxiliary information at the BWP granularity includes ID information of at least two BWPs, IDC problems exist on the at least two BWPs.

[0181] Optionally, the IDC auxiliary information at the BWP granularity further includes one or more of the following information: IDC interference direction information; victim system type; and identification information for identifying the cell where the BWP is located.

[0182] Optionally, the IDC auxiliary information at the BWP granularity is associated with a single frequency band; and / or the IDC auxiliary information at the BWP granularity is associated with multiple frequency bands in a carrier aggregation or dual connectivity scenario.

[0183] Optionally, the network device 700 further includes a first sending module 720. The first sending module 720 may be configured to send first indication information to the terminal device, where the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with a BWP granularity; and the receiving module 710 may be further configured to receive the IDC auxiliary information with a BWP granularity sent by the terminal device if the first indication information requires the terminal device to report IDC auxiliary information with a BWP granularity.

[0184] Optionally, the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, including: the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the service frequency; and / or the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on the non-service frequency.

[0185] Optionally, the first indication information is carried in IDC auxiliary information reporting configuration information sent by the network device.

[0186] Optionally, when the network device requires the terminal device to report IDC auxiliary information with BWP granularity on the non-serving frequency point, the network device 700 further includes a second sending module 730. The second sending module 730 can be used to send first configuration information to the terminal device, where the first configuration information is used to configure corresponding candidate BWP information for the non-serving frequency point.

[0187] Optionally, the receiving module 710 may be a transceiver 830 , as specifically shown in FIG8 .

[0188] Figure 8 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 8 indicate that the unit or module is optional. The device 800 may be used to implement the method described in the above method embodiment. The device 800 may be a chip, a terminal device, or a network device.

[0189] The device 800 may include one or more processors 810. The processor 810 may support the device 800 to implement the method described in the method embodiment above. The processor 810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0190] The apparatus 800 may further include one or more memories 820. The memories 820 store programs that can be executed by the processor 810, causing the processor 810 to perform the methods described in the above method embodiments. The memories 820 may be independent of the processor 810 or integrated into the processor 810.

[0191] The apparatus 800 may further include a transceiver 830. The processor 810 may communicate with other devices or chips via the transceiver 830. For example, the processor 810 may transmit and receive data with other devices or chips via the transceiver 830.

[0192] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0193] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0194] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0195] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0196] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0197] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0198] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0199] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0200] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0201] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0202] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0203] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0204] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0205] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0206] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0207] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: If the terminal device determines or predicts that there is an intra-device IDC coexistence problem, the terminal device sends IDC auxiliary information with a granularity of partial bandwidth BWP to the network device.

2. The method according to claim 1, characterized in that The IDC auxiliary information of the BWP granularity includes: identification ID information of the BWP corresponding to the frequency band / frequency band combination associated with the IDC problem.

3. The method according to claim 1 or 2, characterized in that The IDC auxiliary information of the BWP granularity is determined by the terminal device according to the first rule.

4. The method according to claim 3, characterized in that The first rule includes one or more of the following rules: Selecting the ID information of the BWP with the smallest bandwidth and the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity; as well as The ID information of all BWPs containing the frequency band associated with the IDC problem is selected as the IDC auxiliary information of the BWP granularity.

5. The method according to any one of claims 1 to 4, characterized in that If the IDC auxiliary information at the BWP granularity includes ID information of at least two BWPs, then IDC problems exist on the at least two BWPs.

6. The method according to any one of claims 2 to 5, characterized in that The BWP-sized IDC auxiliary information also includes one or more of the following information: IDC interference direction information; The type of system affected; and Identification information used to identify the cell where the BWP is located.

7. The method according to any one of claims 1 to 6, characterized in that The IDC assistance information of the BWP granularity is associated with a single frequency band; and / or The IDC auxiliary information of the BWP granularity is associated with multiple frequency bands in a carrier aggregation or dual connectivity scenario.

8. The method according to any one of claims 1 to 7, characterized in that Before the terminal device sends the IDC auxiliary information of the BWP granularity to the network device, the method further includes: The terminal device receives first indication information sent by the network device, where the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with a BWP granularity; The terminal device sends IDC auxiliary information of BWP granularity to the network device, including: In a case where the first indication information requires the terminal device to report IDC auxiliary information with a BWP granularity, the terminal device sends the IDC auxiliary information with a BWP granularity to the network device.

9. The method according to claim 8, characterized in that The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, including: The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information of BWP granularity on the serving frequency point; and / or The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on a non-serving frequency point.

10. The method according to claim 8 or 9, characterized in that The first indication information is carried in the IDC auxiliary information reporting configuration information sent by the network device.

11. The method according to any one of claims 1 to 10, characterized in that In a case where the network device requires the terminal device to report IDC auxiliary information of a BWP granularity on a non-serving frequency point, the method further includes: The terminal device receives first configuration information sent by the network device, where the first configuration information is used to configure corresponding candidate BWP information for the non-service frequency point.

12. A wireless communication method, characterized in that: include: The network device receives the intra-device coexistence IDC auxiliary information with a partial bandwidth BWP granularity sent by the terminal device. The IDC auxiliary information with the BWP granularity is sent by the terminal device when it is determined or predicted that an IDC problem exists.

13. The method according to claim 12, characterized in that The IDC auxiliary information of the BWP granularity includes: identification ID information of the BWP corresponding to the frequency band / frequency band combination associated with the IDC problem.

14. The method according to claim 12 or 13, characterized in that The IDC auxiliary information of the BWP granularity is determined by the terminal device according to the first rule.

15. The method according to claim 14, characterized in that The first rule includes one or more of the following rules: Selecting the ID information of the BWP with the smallest bandwidth and the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity; as well as The ID information of all BWPs containing the frequency band associated with the IDC problem is selected as the IDC auxiliary information of the BWP granularity.

16. The method according to any one of claims 12 to 15, characterized in that If the IDC auxiliary information at the BWP granularity includes ID information of at least two BWPs, then IDC problems exist on the at least two BWPs.

17. The method according to any one of claims 13 to 16, characterized in that The BWP-sized IDC auxiliary information also includes one or more of the following information: IDC interference direction information; The type of system affected; and Identification information used to identify the cell where the BWP is located.

18. The method according to any one of claims 12 to 17, characterized in that The IDC assistance information of the BWP granularity is associated with a single frequency band; and / or The IDC auxiliary information of the BWP granularity is associated with multiple frequency bands in a carrier aggregation or dual connectivity scenario.

19. The method according to any one of claims 12 to 18, characterized in that Before the network device receives the IDC auxiliary information of the BWP granularity sent by the terminal device, the method further includes: The network device sends first indication information to the terminal device, where the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with a BWP granularity; The network device receives the IDC auxiliary information of the BWP granularity sent by the terminal device, including: In a case where the first indication information requires the terminal device to report IDC auxiliary information with a BWP granularity, the network device receives the IDC auxiliary information with a BWP granularity sent by the terminal device.

20. The method according to claim 19, wherein The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, including: The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information of BWP granularity on the serving frequency point; and / or The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on a non-serving frequency point.

21. The method according to claim 19 or 20, characterized in that The first indication information is carried in the IDC auxiliary information reporting configuration information sent by the network device.

22. The method according to any one of claims 12 to 21, characterized in that In a case where the network device requires the terminal device to report IDC auxiliary information of a BWP granularity on a non-serving frequency point, the method further includes: The network device sends first configuration information to the terminal device, where the first configuration information is used to configure corresponding candidate BWP information for the non-service frequency point.

23. A terminal device, characterized in that: include: The sending module is used to send IDC auxiliary information with a granularity of partial bandwidth BWP to the network device if the terminal device determines or predicts that there is an IDC coexistence problem within the device.

24. The terminal device according to claim 23, characterized in that The IDC auxiliary information of the BWP granularity includes: identification ID information of the BWP corresponding to the frequency band / frequency band combination associated with the IDC problem.

25. The terminal device according to claim 23 or 24, characterized in that: The IDC auxiliary information of the BWP granularity is determined by the terminal device according to the first rule.

26. The terminal device according to claim 25, characterized in that The first rule includes one or more of the following rules: Selecting the ID information of the BWP with the smallest bandwidth and the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity; as well as The ID information of all BWPs containing the frequency band associated with the IDC problem is selected as the IDC auxiliary information of the BWP granularity.

27. The terminal device according to any one of claims 23 to 26, characterized in that: If the IDC auxiliary information at the BWP granularity includes ID information of at least two BWPs, then IDC problems exist on the at least two BWPs.

28. The terminal device according to any one of claims 24 to 27, characterized in that: The BWP-sized IDC auxiliary information also includes one or more of the following information: IDC interference direction information; The type of system affected; and Identification information used to identify the cell where the BWP is located.

29. The terminal device according to any one of claims 23 to 28, characterized in that: The IDC assistance information of the BWP granularity is associated with a single frequency band; and / or The IDC auxiliary information of the BWP granularity is associated with multiple frequency bands in a carrier aggregation or dual connectivity scenario.

30. The terminal device according to any one of claims 23 to 29, characterized in that: The terminal device further includes: A first receiving module is configured to receive first indication information sent by the network device, where the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with a BWP granularity; The sending module is further configured to: send the IDC auxiliary information with a BWP granularity to the network device when the first indication information requires the terminal device to report the IDC auxiliary information with a BWP granularity.

31. The terminal device according to claim 30, characterized in that The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, including: The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information of BWP granularity on the serving frequency point; and / or The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on a non-serving frequency point.

32. The terminal device according to claim 30 or 31, characterized in that: The first indication information is carried in the IDC auxiliary information reporting configuration information sent by the network device.

33. The terminal device according to any one of claims 23 to 32, characterized in that: In a case where the network device requires the terminal device to report IDC auxiliary information of a BWP granularity on a non-serving frequency point, the terminal device further includes: The second receiving module is used to receive first configuration information sent by the network device, where the first configuration information is used to configure corresponding candidate BWP information for the non-serving frequency point.

34. A network device, characterized in that: include: The receiving module is configured to receive intra-device IDC auxiliary information of partial bandwidth BWP granularity sent by a terminal device, wherein the IDC auxiliary information of BWP granularity is sent by the terminal device when it is determined or predicted that an IDC problem exists.

35. The network device according to claim 34, wherein: The IDC auxiliary information of the BWP granularity includes: identification ID information of the BWP corresponding to the frequency band / frequency band combination associated with the IDC problem.

36. The network device according to claim 34 or 35, characterized in that: The IDC auxiliary information of the BWP granularity is determined by the terminal device according to the first rule.

37. The network device according to claim 36, wherein: The first rule includes one or more of the following rules: Selecting the ID information of the BWP with the smallest bandwidth and the frequency band associated with the IDC problem as the IDC auxiliary information of the BWP granularity; as well as The ID information of all BWPs containing the frequency band associated with the IDC problem is selected as the IDC auxiliary information of the BWP granularity.

38. The network device according to any one of claims 34 to 37, characterized in that: If the IDC auxiliary information at the BWP granularity includes ID information of at least two BWPs, then IDC problems exist on the at least two BWPs.

39. The network device according to any one of claims 35 to 38, characterized in that: The BWP-sized IDC auxiliary information also includes one or more of the following information: IDC interference direction information; The type of system affected; and Identification information used to identify the cell where the BWP is located.

40. The network device according to any one of claims 34 to 39, characterized in that: The IDC assistance information of the BWP granularity is associated with a single frequency band; and / or The IDC auxiliary information of the BWP granularity is associated with multiple frequency bands in a carrier aggregation or dual connectivity scenario.

41. The network device according to any one of claims 34 to 40, characterized in that: The network device further includes: A first sending module is configured to send first indication information to the terminal device, where the first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with a BWP granularity; The receiving module is further configured to: receive the IDC auxiliary information with a BWP granularity sent by the terminal device when the first indication information requires the terminal device to report the IDC auxiliary information with a BWP granularity.

42. The network device according to claim 41, wherein: The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity, including: The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information of BWP granularity on the serving frequency point; and / or The first indication information is used to indicate whether the terminal device is required to report IDC auxiliary information with BWP granularity on a non-serving frequency point.

43. The network device according to claim 41 or 42, characterized in that: The first indication information is carried in the IDC auxiliary information reporting configuration information sent by the network device.

44. The network device according to any one of claims 34 to 43, characterized in that: In a case where the network device requires the terminal device to report IDC auxiliary information of a BWP granularity on a non-serving frequency point, the network device further includes: The second sending module is used to send first configuration information to the terminal device, where the first configuration information is used to configure corresponding candidate BWP information for the non-service frequency point.

45. A terminal device, characterized in that: The terminal device comprises a memory, a processor and a transceiver, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method according to any one of claims 1 to 11.

46. ​​A network device, characterized in that The device comprises a memory, a processor and a transceiver, wherein the memory is used to store a program, and the processor is used to call the program in the memory so as to enable the network device to execute the method according to any one of claims 12 to 22.

47. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 22.

48. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 22.

49. A computer-readable storage medium, characterized in that A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1 to 22.

50. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 22.

51. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 22.

Images