Channel monitoring method and apparatus, terminal and network device

Abstract

This application discloses a channel monitoring method and apparatus, a terminal, and a network device. The method includes: if there are M control resource sets (CORESETs) in the monitoring time of the physical downlink control channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, then the terminal monitors the PDCCH in the M CORESETs, where M is an integer greater than or equal to 1, thereby enabling monitoring of the PDCCH in the CORESETs with duplicate associated PDCCHs, improving the reliability of the PDCCH, and thus ensuring the flexibility, stability, and reliability of system communication.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a channel monitoring method and apparatus, terminal and network device. Background Technology

[0002] Currently, the 3rd Generation Partnership Project (3GPP) is standardizing support for physical downlink control channel repetition (PDCCH repetition), which is implemented as follows: Since a search space may be associated with multiple PDCCH candidates, the network can configure repeated PDCCHs in the PDCCH candidates associated with different search spaces, thereby achieving PDCCH repetition and improving the reliability of PDCCH.

[0003] For example, a PDCCH candidate associated with one search space may be duplicated (or identical) with a PDCCH candidate associated with another search space. That is, a PDCCH candidate associated with one search space may have the same PDCCH content as a PDCCH candidate associated with another search space, such as the same downlink control information (DCI) carried by the PDCCH candidate.

[0004] However, since a search space is associated with a control resource set (CORESET), duplicate PDCCHs may be associated with different or the same CORESET. Therefore, how the terminal listens to PDCCHs in the presence of duplicate PDCCHs requires further investigation. Summary of the Invention

[0005] This application provides a channel monitoring method, apparatus, terminal, and network device, aiming to enable monitoring of PDCCH in CORESETs with repeated associated PDCCH, thereby improving the reliability of PDCCH and ensuring the flexibility, stability, and reliability of system communication.

[0006] In a first aspect, embodiments of this application provide a channel monitoring method, including:

[0007] If there are M control resource sets (CORESETs) during the listening time of the physical downlink control channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, then the terminal listens for PDCCHs in the M CORESETs, where M is an integer greater than or equal to 1.

[0008] As can be seen in this embodiment, if there are M CORESETs in the overlapping PDCCH listening time on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, then PDCCHs are listened to in the M CORESETs, thereby realizing the listening of PDCCHs in the CORESETs with duplicate associated PDCCHs, improving the reliability of PDCCHs, and thus ensuring the flexibility, stability and reliability of system communication.

[0009] Secondly, embodiments of this application provide a channel monitoring method, including:

[0010] During the listening time of the Physical Downlink Control Channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), the network device configures M control resource sets (CORESETs), and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1.

[0011] As can be seen from the embodiments of this application, during the overlapping PDCCH listening time on the active downlink BWP, there are duplicate PDCCHs among the M CORESET-associated PDCCH candidates configured by the network device for the terminal. Therefore, the terminal can listen to PDCCHs in these M CORESETs, thereby achieving PDCCH listening in CORESETs with duplicate associated PDCCHs, improving the reliability of PDCCHs, and thus ensuring the flexibility, stability, and reliability of system communication.

[0012] Thirdly, embodiments of this application provide a channel monitoring device, the device including a processing unit, the processing unit being used for:

[0013] If there are M control resource sets (CORESETs) in the listening time of the physical downlink control channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, then the PDCCH is listened to in the M CORESETs, where M is an integer greater than or equal to 1.

[0014] Fourthly, embodiments of this application provide a listening device, the device including a processing unit, the processing unit being used for:

[0015] During the monitoring of the Physical Downlink Control Channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), M control resource sets (CORESETs) are configured, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1.

[0016] Fifthly, embodiments of this application provide a terminal including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the one or more programs include instructions for performing the steps in the first aspect of embodiments of this application.

[0017] In a sixth aspect, embodiments of this application provide a network device including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the one or more programs include instructions for performing the steps in the second aspect of embodiments of this application.

[0018] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the first or second aspect of embodiments of this application.

[0019] Eighthly, embodiments of this application provide a computer program operable to cause a computer to perform some or all of the steps described in the first or second aspects of embodiments of this application. The computer program may be a software installation package. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application;

[0022] Figure 2 This is a flowchart illustrating a channel monitoring method provided in an embodiment of this application;

[0023] Figure 3This is a flowchart illustrating another channel monitoring method provided in an embodiment of this application;

[0024] Figure 4 This is a functional unit block diagram of a channel monitoring device provided in an embodiment of this application;

[0025] Figure 5 This is a functional unit block diagram of another channel monitoring device provided in the embodiments of this application;

[0026] Figure 6 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0027] Figure 7 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. Detailed Implementation

[0028] To help those skilled in the art better understand the technical solutions of this application, the technical solutions in the embodiments of this application are described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.

[0029] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, software, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but also includes steps or units not listed, or other steps or units inherent to such processes, methods, products, or apparatus.

[0030] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0031] It should be noted that the term "connection" in the embodiments of this application refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices, and is not limited in any way. The terms "network" and "system" in the embodiments of this application express the same concept; a communication system is a communication network.

[0032] The technical solutions of this application embodiment can be applied to various wireless communication systems, such as: Global System for 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, New Radio (NR) system, evolution of NR system, LTE-based Access to Unlicensed Spectrum (LTE-U) system, NR-based Access to Unlicensed Spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), and Wireless Local Area Network (WLAN). Networks, WLAN, Wireless Fidelity (WiFi), 6th-Generation (6G) communication systems, or other communication systems, etc.

[0033] It should be noted that traditional wireless communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, wireless communication systems can support not only traditional wireless communication systems, but also communication such as device-to-device (D2D), machine-to-machine (M2M), machine-type communication (MTC), vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), and narrowband internet of things (NB-IoT). Therefore, the technical solutions of the embodiments in this application can also be applied to the above-mentioned wireless communication systems.

[0034] Optionally, the wireless communication system of this application embodiment can be applied to beamforming, carrier aggregation (CA), dual connectivity (DC), or standalone (SA) deployment scenarios.

[0035] Optionally, the wireless communication system of this embodiment can be applied to unlicensed spectrum. Unlicensed spectrum can also be considered as shared spectrum. Alternatively, the wireless communication system of this embodiment can also be applied to licensed spectrum. Licensed spectrum can also be considered as non-shared spectrum.

[0036] Since the embodiments of this application may be described in conjunction with terminals and network devices, the terminals and network devices involved will be described in detail below.

[0037] Specifically, a terminal can be user equipment (UE), a remote UE, a relay UE, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a mobile device, a user terminal, a smart terminal, a wireless communication device, a user agent, or a user device. It should be noted that a relay device is a terminal capable of providing relay forwarding services to other terminals (including remote terminals). Additionally, a terminal can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a next-generation communication system (such as an NR communication system), or a terminal in a future public land mobile network (PLMN), etc., without specific limitations.

[0038] Furthermore, the terminals can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; they can be deployed on water (such as ships); and they can also be deployed in the air (such as airplanes, balloons, and satellites).

[0039] Furthermore, the terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in autonomous driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0040] Furthermore, the terminal may include a device with transceiver capabilities, such as a chip system. The chip system may include a chip, and may also include other discrete components.

[0041] Specifically, network equipment can be devices used for communication with terminals, responsible for radio resource management (RRM), quality of service (QoS) management, data compression and encryption, and data transmission and reception on the air interface side. Network equipment can be a base station (BS) in a communication system or a device deployed in a radio access network (RAN) to provide wireless communication functions. Examples include base stations (BTS) in GSM or CDMA communication systems, node Bs (NBs) in WCDMA communication systems, evolved node Bs (eNBs or eNodeBs) in LTE communication systems, next-generation evolved node Bs (ng-eNBs) in NR communication systems, next-generation node Bs (gNBs) in NR communication systems, master nodes (MNs) in dual-link architectures, and secondary nodes (SNs) in dual-link architectures, without specific limitations.

[0042] Furthermore, network devices can also be other devices in the core network (CN), such as access and mobility management function (AMF), user plan function (UPF), etc.; they can also be access points (APs) and relay stations in wireless local area networks (WLANs), communication devices in future PLMN networks, and communication devices in NTN networks, etc.

[0043] Furthermore, network devices may include means for providing wireless communication capabilities to terminals, such as a chip system. For example, a chip system may include a chip, and may also include other discrete components.

[0044] Furthermore, network devices can communicate with Internet Protocol (IP) networks, such as the Internet, private IP networks, or other data networks.

[0045] It should be noted that in some network deployments, a network device can be a standalone node to implement all the functions of the aforementioned base station. This can include centralized units (CUs) and distributed units (DUs), such as gNB-CU and gNB-DU; it can also include active antenna units (AAUs). The CU can implement some of the network device's functions, and so can the DU. For example, the CU is responsible for handling non-real-time protocols and services, implementing the functions of the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, and packet data convergence protocol (PDCP) layer. The DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer. Additionally, the AAU can implement some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this network deployment, higher-layer signaling (such as RRC layer signaling) can be considered to be sent by the DU, or jointly by the DU and AAU. It is understood that network devices can include at least one of CU, DU, and AAU. Furthermore, the CU can be classified as a network device in the radio access network (RAN), or it can be classified as a network device in the core network; no specific limitation is made in this regard.

[0046] Furthermore, the network equipment can possess mobility characteristics; for example, the network equipment can be a mobile device. Optionally, the network equipment can be a satellite or a balloon station. For example, the satellite can be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earthorbit (GEO) satellite, or a high elliptical orbit (HEO) satellite. Optionally, the network equipment can also be a base station located on land, water, or other similar locations.

[0047] Furthermore, network devices can provide services to a cell, and terminals within that cell can communicate with the network devices through transmission resources (such as spectrum resources). This cell can include macro cells, small cells, metro cells, micro cells, pico cells, and femto cells, among others.

[0048] Based on the above description, the following is an exemplary description of the wireless communication system according to an embodiment of this application.

[0049] For an example, see the wireless communication system of this application embodiment. Figure 1 The wireless communication system 10 may include a terminal 110 and a network device 120, wherein the network device 120 may be a device that communicates with the terminal 110. Simultaneously, the network device 120 may provide communication coverage for a specific geographical area and may communicate with the terminal 110 located within that coverage area.

[0050] Optionally, the wireless communication system 10 may also include multiple network devices, and each network device may include a certain number of terminals within its coverage area, without specific limitations.

[0051] Optionally, the wireless communication system 10 may also include other network entities such as a network controller and a mobility management entity, without specific limitations.

[0052] Optionally, the communication between the network device and the terminal in the wireless communication system 10 can be wireless or wired communication, without specific restrictions.

[0053] Before providing a detailed description of the channel monitoring method provided in the embodiments of this application, the relevant content involved in the embodiments of this application will be introduced again.

[0054] 1. Bandwidth part (BWP) and overlapping PDCCH monitoring occasions

[0055] BWP is a subset of the total cell bandwidth, thus ensuring that the bandwidth required for terminal reception and transmission does not need to be as large as the total cell bandwidth. The downlink BWP (DL BWP) may contain at least one control resource set (CORESET) associated with the search space.

[0056] Overlapping PDCCH listening times can be understood as PDCCH listening times overlapping.

[0057] 2. Aggregation level and control channel element (CCE)

[0058] The resource unit of PDCCH is CCE, and one CCE contains nine resource element groups (REGs). CCE is a logical resource unit and corresponds to nine REGs on the PRB.

[0059] A PDCCH can consist of n consecutive CCEs. Here, n is called the aggregation level, and there are four aggregation levels: {1, 2, 4, 8}. If the aggregation level of a PDCCH is 8, it means that a PDCCH consists of 8 consecutive CCEs.

[0060] 3. Search space and control resource set (CORESET)

[0061] In 5G NR systems, due to the larger system bandwidth and the differences in terminal demodulation capabilities, the PDCCH no longer needs to occupy the entire frequency band in the frequency domain to improve resource utilization and reduce blind detection complexity. Furthermore, to increase system flexibility and adapt to different scenarios, the starting position of the PDCCH in the time domain can also be configured. Therefore, in 5G NR systems, information such as the frequency band occupied by the PDCCH in the frequency domain and the number of OFDM symbols occupied in the time domain is typically encapsulated in the CORESET, while information such as the starting OFDM symbol of the PDCCH, the PDCCH listening period, and its associated CORESET is encapsulated in the search space.

[0062] Search spaces can be categorized into common search spaces (CSS) and user-specific search spaces (USS).

[0063] It should be noted that a search space is associated with a CORESET, as indicated or configured by the higher-level parameter controlResourceSetId, and a search space can also be associated with multiple PDCCH candidates, as indicated or configured by the higher-level parameter nrofCandidates. Therefore, a relationship can be established between a CORESET and multiple PDCCH candidates through the search space approach.

[0064] Additionally, during an overlapping PDCCH listening period, the CORESET associated with a PDCCH candidate can be configured with at least one Transmission Configuration Indication (TCI) state, and higher layers can configure QCL through the TCI state. The TCI state may be associated with QCL-typeD. Therefore, the TCI state of the CORESET associated with a PDCCH candidate may be associated with QCL-typeD.

[0065] 4. Quasi-Co-Location (QCL)

[0066] To ensure correct signal reception and demodulation, standard protocols introduce the concept of reference signals with QCL relationships, such as the channel state information reference signal (CSI-RS) and the synchronization signal block (SSB). Terminals can then estimate large-scale characteristic parameters based on the CSI-RS. These large-scale characteristic parameters include at least one of the following: delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial information. For example, in Release 11 of the LTE communication system, the standard protocol introduces antenna port QCL. Antenna port QCL indicates that the signal transmitted from the antenna port will undergo the same large-scale fading, thus possessing the same large-scale characteristic parameters. For instance, when antenna ports A and B satisfy the QCL relationship, the large-scale characteristic parameters estimated from the signal at antenna port A are also suitable for the signal at antenna port B.

[0067] Furthermore, in 5G NR systems, terminals and network equipment may be configured with large-scale array structures of multiple antenna panels, and the large-scale characteristics of the beams formed by different antenna panels will also be different. In this case, in addition to the delay spread, Doppler spread, Doppler frequency shift, average gain, and average delay described above, the large-scale characteristic parameters also include the angle of arrival (AOA), angle of arrival spread (AAS), angle of departure (AOD), angle of departure spread (ADS), and spatial correlation.

[0068] 5. Quasi-co-located antenna ports

[0069] The higher-layer parameter PDSCH-Config can configure up to M TCI states for the terminal to decode the PDSCH based on the DCI in the detected PDCCH, where M depends on the terminal's capabilities. Each TCI state contains parameters for configuring the QCL relationship between one or two downlink reference signals (such as CSI-RS and / or SSB) and the demodulation reference symbol (DM-RS) port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. The QCL relationship can be configured by the higher-layer parameter qcl-Type1 for the first downlink reference signal and qcl-Type2 for the second downlink reference signal (if a second downlink reference signal is configured). In the case of two downlink reference signals, regardless of whether they are the same type of reference signal, the QCL types associated with the two downlink reference signals should not be the same. The QCL type associated with each downlink reference signal is defined by the higher-layer parameter qcl-Type in QCL-Info and may include:

[0070] QCL type A: {Doppler frequency shift, Doppler spread, average time delay, delay spread};

[0071] QCL type B: {Doppler frequency shift, Doppler spread};

[0072] QCL type C: {Doppler frequency shift, average time delay};

[0073] QCL type D (QCL-typeD): {space reception parameters}; etc.

[0074] The spatial reception parameters may include at least one of the following: AOA, average AOA, AOA spread, AOD, average AOD, AOD spread, receive antenna spatial correlation, transmit antenna spatial correlation, transmit beam, receive beam, resource identifier, etc. Furthermore, when the QCL type is QCL-TypeD, the TCI state can be used to indicate the beam. Each TCI state can provide (contain) one or two QCL type parameters. If a TCI state contains two QCL type parameters, then the QCL type will include QCL-TypeD. That is, a TCI state may be associated with QCL-typeD.

[0075] Additionally, the TCI status can be activated by an activation command issued from the network side (such as the MAC control unit CE) or indicated by the TCI field in the DCI. For example, when the TCI status is used to indicate the QCL type of the PDSCH, the network device can first activate it via MACCE.N One active TCI state, and then through the N-bit TCI field in the DCI, from this 2 N One TCI state is indicated by each active TCI state. When N=3, if the TCI field in the DCI is '000', then the TCI indicates the first TCI state activated by the MAC CE. Additionally, the reference signal for this TCI state is QCL with the DM-RS port of the PDSCH, relative to the QCL type parameter given for that TCI state.

[0076] 6. Same QCL-typeD attribute

[0077] To determine if the QCL-typeD attributes are the same, you can do the following:

[0078] → In order to determine CORESET, an SSB is considered to have a QCL-typeD attribute that is different from CSI-RS;

[0079] →To determine CORESET, the first CSI-RS associated with one SSB in the first cell and the second CSI-RS associated with that SSB in the second cell have the same QCL-typeD attribute; and so on.

[0080] For example, if the reference signal for QCL-TypeD corresponding to the TCI state of CORESET#1 is the first CSI-RS, and the reference signal for QCL-TypeD corresponding to the TCI state of CORESET#2 is also the first CSI-RS, then CORESET#1 and CORESET#2 have the same QCL-typeD attribute.

[0081] Based on the above description, this application provides a flowchart of a channel monitoring method. Please refer to [link / reference]. Figure 2 The method includes:

[0082] S210. If there are M CORESETs in the overlapping PDCCH listening time on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, then the terminal listens for PDCCHs in the M CORESETs, where M is an integer greater than or equal to 1.

[0083] It should be noted that the network can configure a CORESET for each search space through high-level parameters (such as controlResourceSetId), meaning that one search space may be associated with one CORESET. Simultaneously, the network can also configure multiple PDCCH candidates for each search space through high-level parameters (such as nrofCandidates), meaning that one search space may also be associated with multiple PDCCH candidates. Therefore, the association between CORESETs and PDCCH candidates can be established through the search space approach, meaning that one CORESET can be associated with multiple PDCCH candidates.

[0084] By establishing mapping relationships, such as one-to-one mapping relationships, between PDCCH candidates associated with different search spaces, the network can configure duplicate PDCCHs in the PDCCH candidates associated with different search spaces, thereby achieving PDCCH repetition and improving the reliability of PDCCH.

[0085] Table 1

[0086]

[0087] For example, as shown in Table 1, when the USS includes USS#1 and USS#2, if the aggregation level corresponding to USS#1 is 4, then USS#1 is associated with 2 PDCCH candidates. Similarly, if the aggregation level corresponding to USS#2 is 4, then USS#2 is associated with 2 PDCCH candidates. Specifically, if the aggregation level is 4, the first PDCCH candidate associated with USS#1 is only mapped to the first PDCCH candidate associated with USS#2, and the second PDCCH candidate associated with USS#1 is only mapped to the second PDCCH candidate associated with USS#2. Therefore, through implicit or explicit network configuration of PDCCH duplication, the first PDCCH candidate associated with USS#1 may duplicate (or be identical to) the first PDCCH candidate associated with USS#2. In other words, the first PDCCH candidate associated with USS#1 may have the same PDCCH content (such as DCI content) as the first PDCCH candidate associated with USS#2, i.e., duplicate PDCCHs exist. Similarly, the second PDCCH candidate associated with USS#1 may overlap with (or be the same as) the second PDCCH candidate associated with USS#2. Therefore, there are duplicate PDCCH candidates associated with the CORESET linked through USS#1 and the CORESET linked through USS#2.

[0088] Specifically, PDCCH repetition in this application embodiment can be understood as the PDCCH content transmitted by the PDCCH candidates associated with at least two search spaces (or different search spaces) being the same (e.g., the DCI content carried by the PDCCH candidates being the same).

[0089] Specifically, the existence of duplicate PDCCHs among the M CORESET-associated PDCCH candidates can be understood as at least two PDCCH candidates with the same PDCCH content among the M CORESET-associated PDCCH candidates.

[0090] Specifically, the existence of duplicate PDCCHs among the M CORESET-associated PDCCH candidates can be understood as the existence of PDCCH candidates that are implicitly or explicitly configured to be duplicated among the M CORESET-associated PDCCH candidates.

[0091] In other words, the core set associated with duplicate PDCCHs may exist in different PDCCH listening times. For example, the core set associated with one of the M core sets may belong to one of the M core sets, but the core set associated with the other PDCCH may not belong to one of the M core sets. That is to say, the core sets associated with the two duplicate PDCCHs may exist in different PDCCH listening times.

[0092] Specifically, the search space associated with PDCCH duplication can be understood as follows: if there are duplicate PDCCHs between multiple PDCCH candidates associated with a certain search space and multiple PDCCH candidates associated with certain search spaces, then that search space and those search spaces are collectively referred to as the search space associated with PDCCH duplication.

[0093] For example, if there are duplicate PDCCHs among the multiple PDCCH candidates associated with CSS#1 and the multiple PDCCH candidates associated with CSS#2, then CSS#1 and CSS#2 are collectively referred to as the search space with duplicate associated PDCCHs.

[0094] Specifically, the association between search spaces can be understood as the relationship between various search spaces in the search space where the associated PDCCH repeats.

[0095] For example, if there are duplicate PDCCHs (or duplicate PDCCHs) between multiple PDCCH candidates associated with CSS#1 and multiple PDCCH candidates associated with CSS#2, then CSS#1 is associated with CSS#2. Similarly, if there are duplicate PDCCHs between multiple PDCCH candidates associated with USS#1 and multiple PDCCH candidates associated with USS#2, then USS#1 is associated with USS#2.

[0096] Specifically, a CORESET with repeated PDCCH can be understood as a CORESET with repeated PDCCH if there are repeated PDCCHs between multiple PDCCH candidates associated with a certain CORESET and multiple PDCCH candidates associated with certain CORESETs.

[0097] For example, if there are duplicate PDCCHs among the multiple PDCCH candidates associated with CORESET#1 and the multiple PDCCH candidates associated with CORESET#2, then CORESET#1 and CORESET#2 are collectively referred to as CORESETs with duplicate PDCCHs.

[0098] Specifically, the association between CORESETs can be understood as the association between individual CORESETs that have duplicate PDCCHs. For example, if there are duplicate PDCCHs between multiple PDCCH candidates associated with CORESET#1 and multiple PDCCH candidates associated with CORESET#2, then CORESET#1 is associated with CORESET#2.

[0099] In summary, the embodiments of this application consider the following: if there are M cores in the overlapping PDCCH listening time on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M cores, then PDCCH listening is performed in the M cores, thereby realizing PDCCH listening in cores with duplicate PDCCHs, improving the reliability of PDCCH, and ensuring the flexibility, stability and reliability of the communication system.

[0100] Specifically, all CORESETs in the M CORESETs have the same quasi-co-addressable QCL type D attribute; or, there are CORESETs in the M CORESETs with different QCL type D attributes; or, there are CORESETs in the M CORESETs with the same QCL type D attribute.

[0101] It should be noted that during overlapping PDCCH listening times on a certain active BWP, the CORESET associated with the PDCCH candidate can be configured with at least one TCI state, and higher layers can configure QCL through the TCI state. The TCI state may be associated with QCL-typeD. Therefore, the TCI state of the CORESET associated with the PDCCH candidate is associated with QCL-typeD. In this embodiment, the QCL-typeD attribute can be determined by the reference signal corresponding to QCL-typeD.

[0102] Furthermore, duplicate PDCCHs may be associated with the same or different CORESETs, and different CORESETs have different QCL-typeD attributes. Therefore, the terminal in this embodiment can listen to PDCCHs in CORESETs with different QCL-typeD attributes or in CORESETs with the same QCL-typeD attributes, thereby helping to ensure the flexibility, stability and reliability of the communication system.

[0103] In summary, if there are M cores in the overlapping PDCCH listening time on an active downlink BWP, and duplicate PDCCHs exist among the PDCCH candidates associated with these M cores; simultaneously, all cores in these M cores have the same QCL-typeD attribute (i.e., all cores in these M cores have one QCL-typeD attribute); or, there are cores in these M cores with different QCL-typeD attributes (i.e., cores in these M cores have multiple QCL-typeD attributes); or, there are cores in these M cores with the same QCL-typeD attribute (i.e., cores in these M cores have multiple QCL-typeD attributes). Therefore, the terminal may listen for PDCCH in these M cores under the following circumstances:

[0104] 1. The terminal can listen to the PDCCH only in CORESETs with a QCL-typeD attribute, i.e., "Scenario 1";

[0105] 2. The terminal listens to the PDCCH in CORESETs with multiple QCL-typeD attributes, i.e., "Scenario 2".

[0106] The following embodiments of this application will provide a detailed description of "Scenario 1" and "Scenario 2".

[0107] Scenario 1:

[0108] In one possible example, the terminal listening to the PDCCH in the M CORESETs may include: the terminal listening to the PDCCH in a first reference CORESET and / or a CORESET that has the same QCL type D property as the first reference CORESET, where the first reference CORESET is one of the M CORESETs.

[0109] Specifically, the first reference CORESET can be a CORESET with a QCL-typeD attribute.

[0110] Specifically, a CORESET that has the same QCL-typeD attribute as the first reference CORESET may include one or more of the M CORESETs.

[0111] It should be noted that, firstly, since one CORESET can be associated with one TCI state, and each TCI state may be associated with QCL-typeD, this embodiment can select the corresponding CORESET by determining whether the QCL-typeD attributes corresponding to the TCI states of different CORESETs are the same. Based on this, a CORESET with the same QCL-typeD attribute as the first reference CORESET can be understood as a CORESET that can be used as a reference in this embodiment. Then, the embodiment can determine the CORESET with the same QCL-typeD attribute as the first reference CORESET from the M CORESETs to obtain other CORESETs, and finally realize the listening of PDCCH in these other CORESETs.

[0112] Secondly, the first reference CORESET can be determined from the M CORESETs using certain criteria. Meanwhile, regarding "Scenario 1," it can be understood that the terminal only listens to the PDCCH in CORESETs that have a single QCL-typeD attribute, where the QCL-typeD attribute is the QCL-typeD attribute of the first reference CORESET.

[0113] Finally, the terminal can listen to the PDCCH according to the following three principles: listen to the PDCCH in the first reference CORESET; listen to the PDCCH in the first reference CORESET and the CORESET with the same QCL-typeD attribute as the first reference CORESET; listen to the PDCCH in the CORESET with the same QCL-typeD attribute as the first reference CORESET.

[0114] The following example illustrates this.

[0115] Example 1: During the PDCCH listening time overlapping on an active downlink BWP, the following CORESETs exist (M=4): CORESET#0 (associated with 1 TCI state), CORESET#1 (associated with 1 TCI state), CORESET#2 (associated with 1 TCI state), CORESET#3 (associated with 1 TCI state);

[0116] →There are duplicate PDCCHs between multiple PDCCH candidates associated with CORESET#1 and multiple PDCCH candidates associated with CORESET#2, that is, CORESET#1 is associated with CORESET#2;

[0117] →The QCL-typeD property corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD property corresponding to the TCI state of CORESET#0;

[0118] →The QCL-typeD property corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD property corresponding to the TCI state of CORESET#3;

[0119] →The QCL-typeD property corresponding to the TCI state of CORESET#2 is different from the QCL-typeD property corresponding to the TCI state of CORESET#0.

[0120] When the first reference CORESET is determined to be "CORESET#1" according to certain criteria, since the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is the same as that of CORESET#0 and CORESET#3, while the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is different from that of CORESET#2, the terminal listens to the PDCCH in "CORESET#0", "CORESET#1" and "CORESET#3".

[0121] Based on the above description, the following embodiments of this application will specifically explain the criteria for determining the first reference CORESET from the M CORESETs.

[0122] Guideline 1-1:

[0123] In one possible example, during the overlapping PDCCH listening time on an active downlink BWP, if there is a CORESET with associated CSS in the first CORESET, then the first reference CORESET is specifically: the CORESET that belongs to the first CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the first CORESET belongs; wherein, the first CORESET includes: CORESETs with repeated associated PDCCH in M ​​CORESETs.

[0124] It should be noted that, firstly, since a search space can be associated with a CORESET, and the types of search spaces can include CSS and USS, each CORESET can be associated with (or contain) CSS and / or USS.

[0125] Secondly, during the overlapping PDCCH listening time on the active downlink BWP, each of the M CORESETs may be associated with (or belong to) a cell, and each cell has its corresponding index, i.e., a cell index. Therefore, in this embodiment, the cell with the smallest index can be selected from among the cells according to the minimum index principle. Similarly, each search space (CSS and / or USS) also has its corresponding index, so in this embodiment, the CORESET associated with the minimum index search space can also be selected from the CORESETs associated with the search space according to the minimum index principle.

[0126] For example, in a PDCCH listening scenario with overlapping activity on an active downlink BWP, there are four CORESETs. These four CORESETs are associated with cells 1 and 2. Cell 1 is associated with CORESET#1_1 (associated with one TCI state, associated with CSS#1) and CORESET#1_2 (associated with one TCI state, associated with CSS#2); Cell 2 is associated with CORESET#2_1 (associated with one TCI state, associated with USS#1) and CORESET#2_2 (associated with one TCI state, associated with CSS#3). Furthermore, the index of cell 1 is less than the index of cell 2, and the index of CSS#1 is less than the index of CSS#2.

[0127] Furthermore, during the overlapping PDCCH listening time on the active downlink BWP, since there may be CORESETs with duplicate associated PDCCHs among the M CORESETs, this embodiment considers the CORESETs with duplicate associated PDCCHs among the M CORESETs as the first CORESET. That is, each CORESET in the first CORESET has duplicate associated PDCCHs.

[0128] For example, in "Example 1", during an overlapping PDCCH listening event on an active downlink BWP, there are 4 CORESETs, and CORESET#1 is associated with CORESET#2. Therefore, the first CORESET includes CORESET#1 and CORESET#2.

[0129] For example, in "Example 1", during the overlapping PDCCH listening time on a certain active downlink BWP, there are 4 CORESETs, and CORESET#1 is associated with a duplicate PDCCH. Therefore, the first CORESET includes CORESET#1.

[0130] Finally, the first coreset may or may not contain coresets with associated CSS. Therefore, if the first coreset contains coresets with associated CSS, the coreset belonging to the first coreset and associated with the smallest index CSS in the smallest cell of each coreset belonging to the first coreset is taken as the first reference coreset. That is, first, the coresets with associated CSS are determined from the first coreset to obtain at least one coreset, then the cells to which each of the at least one coreset belongs are determined to obtain at least one cell, then the cell with the smallest index is determined from the at least one cell, and finally, the coreset belonging to the first coreset and associated with the smallest index CSS is determined from the cell with the smallest index to obtain the first reference coreset.

[0131] As can be seen, by using the “Guideline 1-1” described in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the first reference CORESET) that is associated with PDCCH overlap, the minimum cell index, and the minimum CSS index during the PDCCH listening time on the active downlink BWP, thereby enabling PDCCH listening in CORESETs with overlapping associated PDCCH, and thus ensuring the flexibility, stability and reliability of system communication.

[0132] Guideline 1-2:

[0133] In one possible example, during the PDCCH listening time overlapping on the active downlink BWP, if there is no CORESET associated with CSS in the first CORESET, then the first reference CORESET is specifically: the CORESET that belongs to the first CORESET and is associated with the smallest index USS in the cell to which the CORESET associated with USS in the first CORESET belongs.

[0134] The first CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

[0135] It should be noted that, similarly, USS also has its corresponding index. Therefore, in this embodiment, the CORESET with the smallest associated index USS can be determined from multiple CORESETs associated with (including) USS according to the principle of minimum index.

[0136] Additionally, if there is no associated CSS in the first CORESET, then the CORESET belonging to the first CORESET and associated with the minimum index USS in the cells of the cells to which the associated USS belongs in the first CORESET is taken as the first reference CORESET. That is, firstly, the associated USS CORESET is determined from the first CORESET to obtain at least one CORESET; then, the cells to which each of these at least one CORESET belongs are determined to obtain at least one cell; next, the cell with the minimum index is determined from these at least one cell; finally, the CORESET belonging to the first CORESET and associated with the minimum index USS is determined from the cell with the minimum index to obtain the first reference CORESET.

[0137] As can be seen, by following the "Guidelines 1-2" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the first reference CORESET) that is associated with PDCCH overlap, the smallest cell index, and the smallest USS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCH, thereby ensuring the flexibility, stability, and reliability of system communication.

[0138] The following embodiments of this application provide an example to illustrate "Guideline 1-1" and "Guideline 1-2".

[0139] Example 2: In the case of overlapping PDCCH listening on an active downlink BWP, the following CORESETs exist (when M=6):

[0140] Cell 1: CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);

[0141] →There are duplicate PDCCHs between the multiple PDCCH candidates associated with CSS#1 and the multiple PDCCH candidates associated with CSS#4, that is, CSS#1 is associated with CSS#4 (or CORESET#2 is associated with CORESET#3);

[0142] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 in cell 1.

[0143] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 in cell 1.

[0144] →The QCL-typeD attribute corresponding to the TCI state of CORESET#4 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1.

[0145] Cell 2: CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);

[0146] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 in cell 2.

[0147] →The QCL-typeD attribute of the TCI state corresponding to CORESET#2 in cell 2 is the same as the QCL-typeD attribute of the TCI state corresponding to CORESET#2 in cell 1.

[0148] First, during the overlapping PDCCH listening time on the active downlink BWP, the cells associated with the aforementioned CORESETs (M=6) include cell 1 and cell 2. Cell 1 is associated with CORESET#0, CORESET#2, CORESET#3, and CORESET#4, while cell 2 is associated with CORESET#1 and CORESET#2. Cell 1's CORESET#0 is associated with one TCI state, and the search space associated with CORESET#0 includes CSS#0, which is associated with multiple PDCCH candidates; the other CORESETs are known sequentially.

[0149] Secondly, the index of cell 1 is less than the index of cell 2, the index of CSS#0 is less than the index of CSS#1, and the index of CSS#1 is less than the index of CSS#4.

[0150] Secondly, there are duplicate PDCCHs among the aforementioned CORESETs, namely CORESET#2 and CORESET#3 of cell 1 (i.e., the first CORESET). Since both CORESET#2 and CORESET#3 of cell 1 are associated CSS CORESETs, meaning that the first CORESET contains an associated CSS CORESET, the first reference CORESET is determined to be "CORESET#2" of cell 1 according to "Criterion 1-1":

[0151] From the first CORESET, determine the CORESET associated with the CSS, and obtain "CORESET#2" and "CORESET#3" of cell 1; determine the cell to which "CORESET#2" and "CORESET#3" of cell 1 belong, cell 1; from cell 1, determine the CORESET that belongs to the first CORESET and is associated with the smallest index CSS, and obtain "CORESET#2" of cell 1.

[0152] Next, other CORESETs with the same QCL-typeD attribute as the first reference CORESET are determined from the above CORESETs (M=6), resulting in “CORESET#0” for cell 1, “CORESET#4” for cell 2, “CORESET#1” for cell 2, and “CORESET#2” for cell 2.

[0153] Finally, the terminal listens to the PDCCH in "CORESET#2" of cell 1, "CORESET#0" of cell 1, "CORESET#4" of cell 1, "CORESET#1" of cell 2 and "CORESET#2" of cell 2, thereby realizing the listening of PDCCH in CORESETs with repeated associated PDCCH.

[0154] Scenario 2:

[0155] In one possible example, the terminal listening to the PDCCH in the M CORESETs may include: the terminal listening to the PDCCH in a second reference CORESET and / or a CORESET that has the same QCL type D attribute as the second reference CORESET, and listening to the PDCCH in a third reference CORESET and / or a CORESET that has the same QCL type D attribute as the third reference CORESET; wherein the second reference CORESET is one of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from that of the third reference CORESET.

[0156] Specifically, the second reference CORESET can be a CORESET with a QCL-typeD attribute.

[0157] Specifically, a CORESET that has the same QCL-typeD attribute as the second reference CORESET may include one or more of the M CORESETs.

[0158] Specifically, the third reference CORESET can be a CORESET with a QCL-typeD attribute.

[0159] Specifically, a CORESET that has the same QCL-typeD property as the third reference CORESET may include one or more of the M CORESETs.

[0160] It should be noted that, firstly, regarding "Scenario 2", it can be understood that the terminal needs to listen to the PDCCH in CORESETs with multiple QCL-typeD attributes. The terminal's PDCCH monitoring can include the following principles: monitoring PDCCH in the second reference CORESET and the third reference CORESET; monitoring PDCCH in the CORESET and the third CORESET that have the same QCL type D attribute as the second reference CORESET; monitoring PDCCH in the second reference CORESET and the CORESET that have the same QCL type D attribute as the third reference CORESET; monitoring PDCCH in the second reference CORESET and the third reference CORESET; monitoring PDCCH in the second reference CORESET, the CORESET that have the same QCL type D attribute as the second reference CORESET, and the third CORESET; monitoring PDCCH in the second reference CORESET, the CORESET that have the same QCL type D attribute as the second reference CORESET, and the third CORESET; monitoring PDCCH in the second reference CORESET, the CORESET that have the same QCL type D attribute as the second reference CORESET, and the third CORESET; and so on.

[0161] Secondly, a CoreSet with the same QCL-typeD attribute as the second reference CoreSet can be understood as follows: in this embodiment, the second reference CoreSet can be used as a reference CoreSet, and then other CoreSets can be obtained from the M CoreSets by using the second reference CoreSet as a reference. Finally, PDCCH can be listened to in these other CoreSets. Similarly, a CoreSet with the same QCL-typeD attribute as the third reference CoreSet can be understood as follows: in this embodiment, the third reference CoreSet can be used as a reference CoreSet, and other CoreSets can be obtained from the M CoreSets by using the third reference CoreSet as a reference. Finally, PDCCH can be listened to in these other CoreSets.

[0162] Finally, the second reference core set can be determined from the M core sets using certain criteria. Similarly, the third reference core set can be determined from the M core sets using certain criteria.

[0163] Based on the above description, the following embodiments of this application will specifically explain the criteria for determining the second reference CORESET and the third reference CORESET among the M CORESETs.

[0164] Guideline 2-1-1:

[0165] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is a cell in the first cell set that contains a CORESET with associated CSS, then the second reference CORESET can be specifically: the CORESET with the smallest associated index CSS in the cell with the smallest index in the cell containing the CORESET with associated CSS in the first cell set.

[0166] The first cell set includes the cells corresponding to the M CORESETs.

[0167] It should be noted that during the overlapping PDCCH listening time on the active downlink BWP, since each of the M CORESETs may correspond to (or be associated with) a cell, the first cell set in this application embodiment includes the cell corresponding to each of the M CORESETs.

[0168] Furthermore, if the first cell set contains a cell that includes a CORESET with associated CSS, then the CORESET with the smallest index among the cells containing the associated CORESET in the first cell set is taken as the second reference CORESET. In other words, at least one cell containing the associated CSS is first determined from the first cell set, then the cell with the smallest index is determined from that at least one cell, and finally the CORESET with the smallest index is determined from that cell to obtain the second reference CORESET.

[0169] As can be seen, unlike the aforementioned "first reference CORESET," which is a COSESET associated with PDCCH overlap, the smallest cell index, and the smallest CSS / USS index, the second reference CORESET in 'Guideline 2-1-1' can be a COSESET associated with the smallest cell index and the smallest CSS index. Furthermore, through "Guideline 2-1-1" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the second reference CORESET) associated with the smallest cell index and the smallest CSS index during the PDCCH listening opportunity on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCHs, thereby ensuring the flexibility, stability, and reliability of system communication.

[0170] Guideline 2-1-2:

[0171] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no cell in the first cell set that contains a CORESET with an associated CSS, then the second reference CORESET can be: the CORESET with the smallest associated index of the cell in the first cell set that contains a CORESET with an associated USS.

[0172] It should be noted that, similarly to the above, the second reference CORESET in 'Guideline 2-1-2' can be a COSESET that is associated with PDCCH overlap, the minimum cell index, and the minimum CSS / USS index, unlike the "first reference CORESET" mentioned above which is a COSESET associated with PDCCH overlap, the minimum cell index, and the minimum CSS / USS index.

[0173] Furthermore, if no cell in the first cell set contains a CORESET with an associated CSS, then the CORESET with the smallest associated USS index among the cells in the first cell set that contain a CORESET with an associated USS is taken as the second reference CORESET. In other words, at least one cell containing a CORESET with an associated USS is first determined from the first cell set; then, the cell with the smallest index is determined from that at least one cell; and finally, the CORESET with the smallest associated USS index is determined from that cell to obtain the second reference CORESET.

[0174] As can be seen, by using the “Guideline 2-1-2” described in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the second reference CORESET) with an associated minimum cell index and an associated minimum USS index during the PDCCH listening time overlapping on the active downlink BWP, thereby enabling PDCCH listening in CORESETs with repeated associated PDCCH, and thus ensuring the flexibility, stability and reliability of system communication.

[0175] The following embodiment of this application provides an example to illustrate "Guideline 2-1-1" and "Guideline 2-1-2".

[0176] Example 3: In the case of overlapping PDCCH listening on an active downlink BWP, the following CORESETs exist (when M=6):

[0177] Cell 1: CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);

[0178] →There are duplicate PDCCHs between the multiple PDCCH candidates associated with CSS#1 and the multiple PDCCH candidates associated with CSS#4, that is, CSS#1 is associated with CSS#4 (or CORESET#2 is associated with CORESET#3);

[0179] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 in cell 1.

[0180] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 in cell 1.

[0181] →The QCL-typeD attribute corresponding to the TCI state of CORESET#4 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1.

[0182] Cell 2: CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);

[0183] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 in cell 2.

[0184] →The QCL-typeD attribute of the TCI state corresponding to CORESET#2 in cell 2 is the same as the QCL-typeD attribute of the TCI state corresponding to CORESET#2 in cell 1.

[0185] First, during the overlapping PDCCH monitoring on the active downlink BWP, the cells associated with the aforementioned CORESETs (M=6) include cell 1 and cell 2, i.e., the first cell set includes cell 1 and cell 2. Among them, the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, and the CORESETs associated with cell 2 include CORESET#1 and CORESET#2.

[0186] Secondly, the index of cell 1 is less than the index of cell 2, the index of CSS#0 is less than the index of CSS#1, and the index of CSS#1 is less than the index of CSS#4.

[0187] Secondly, since both cell 1 and cell 2 have associated CSS CORESETs, the first cell set contains cells with associated CSS CORESETs. Therefore, according to "Criterion 2-1-1", the second reference CORESET is determined to be "CORESET#0" of cell 1.

[0188] From the first cell set, identify the cell containing the associated CSS CORESET, resulting in cell 1 and cell 2; from cell 1 and cell 2, identify the cell with the smallest index, resulting in cell 1; from cell 1, identify the CORESET associated with the smallest index CSS, resulting in "CORESET#0" for cell 1.

[0189] Next, other CORESETs with the same QCL-typeD attribute as the second reference CORESET are determined from the above CORESETs (M=6), resulting in “CORESET#2” for cell 1, “CORESET#4” for cell 1, “CORESET#1” for cell 2, and “CORESET#2” for cell 2.

[0190] Finally, the terminal listens to the PDCCH in "CORESET#0", "CORESET#2", "CORESET#4" of cell 1, "CORESET#1" and "CORESET#2" of cell 2, thereby enabling it to listen to the PDCCH in CORESETs where the associated PDCCH is repeated.

[0191] Guideline 2-2-1:

[0192] In one possible example, during the overlapping PDCCH listening time on an active downlink BWP, if there is a CORESET with associated CSS in the second CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the second CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the second CORESET belongs; wherein, the second CORESET includes: CORESETs with repeated non-associated PDCCHs among M CORESETs.

[0193] It should be noted that during the overlapping PDCCH listening time on the active downlink BWP, since there may be CORESETs with duplicate PDCCHs that are not associated among the M CORESETs, this embodiment of the application considers the CORESETs with duplicate PDCCHs that are not associated among the M CORESETs as the second CORESET. That is to say, there are no duplicate PDCCHs among the CORESETs in the second CORESET.

[0194] For example, in "Example 1", during an overlapping PDCCH listening event on an active downlink BWP, there are 4 CORESETs, and CORESET#1 is associated with CORESET#2. Therefore, the second CORESET includes CORESET#0 and CORESET#3.

[0195] Furthermore, the second coreset may or may not contain coresets with associated CSS. Therefore, if a coreset with associated CSS exists in the second coreset, the coreset belonging to the second coreset and associated with the smallest index CSS from the smallest index cell of each coreset belonging to the associated CSS in the second coreset is taken as the second reference coreset. In other words, first, the coresets with associated CSS are determined from the second coreset to obtain at least one coreset; then, the cells to which each of these at least one coreset belongs are determined to obtain at least one cell; next, the cell with the smallest index is determined from these at least one cell; and finally, the coreset belonging to the second coreset and associated with the smallest index CSS is determined from the cell with the smallest index to obtain the second reference coreset.

[0196] As can be seen, unlike the "second reference CORESET" in the above "Guideline 2-1-1" and "Guideline 2-1-2", which is a COSESET that is associated with the smallest cell index and the smallest CSS / USS index, through the "Guideline 2-2-1" of this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the second reference CORESET) that is not associated with PDCCH overlap, but is associated with the smallest cell index and the smallest CSS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.

[0197] Guideline 2-2-2:

[0198] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the second CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the second CORESET and is associated with the smallest index USS in the cell to which each associated USS CORESET belongs in the second CORESET.

[0199] The second CORESET includes: a CORESET with unassociated PDCCH repetitions in M ​​CORESETs.

[0200] It should be noted that if there is no associated CSS in the second CORESET, then the CORESET belonging to the second CORESET and associated with the minimum index USS in the cells of the respective cells of the associated USS in the second CORESET is taken as the second reference CORESET. That is, first, the associated USS CORESET is determined from the second CORESET to obtain at least one CORESET, then the cells to which each of the at least one CORESET belongs are determined to obtain at least one cell, then the cell with the minimum index is determined from the at least one cell, and finally the CORESET belonging to the second CORESET and associated with the minimum index USS is determined from the cell with the minimum index to obtain the second reference CORESET.

[0201] As can be seen, by following the “Guideline 2-2-2” in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the second reference CORESET) that is not associated with PDCCH overlap, but is associated with the minimum cell index and the minimum USS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with PDCCH overlap, thereby ensuring the flexibility, stability and reliability of system communication.

[0202] The following embodiment of this application provides an example to illustrate "Guideline 2-2-1" and "Guideline 2-2-2".

[0203] Example 4: In the case of overlapping PDCCH listening on an active downlink BWP, the following CORESETs exist (when M=6):

[0204] Cell 1: CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);

[0205] →There are duplicate PDCCHs between the multiple PDCCH candidates associated with CSS#1 and the multiple PDCCH candidates associated with CSS#4, that is, CSS#1 is associated with CSS#4 (or CORESET#2 is associated with CORESET#3);

[0206] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 in cell 1.

[0207] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 in cell 1.

[0208] →The QCL-typeD attribute corresponding to the TCI state of CORESET#4 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1.

[0209] Cell 2: CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);

[0210] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 in cell 2.

[0211] →The QCL-typeD attribute of the TCI state corresponding to CORESET#2 in cell 2 is the same as the QCL-typeD attribute of the TCI state corresponding to CORESET#2 in cell 1.

[0212] First, during the PDCCH monitoring period that overlaps on the active downlink BWP, the cells associated with the aforementioned CORESETs (M=6) include cell 1 and cell 2. Among them, the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, and the CORESETs associated with cell 2 include CORESET#1 and CORESET#2.

[0213] Secondly, the index of cell 1 is less than the index of cell 2, the index of CSS#0 is less than the index of CSS#1, and the index of CSS#1 is less than the index of CSS#4.

[0214] Secondly, there are duplicate PDCCHs in the aforementioned CORESETs, namely CORESET#2 and CORESET#3 of cell 1. Therefore, the non-associated PDCCH duplicate CORESETs (i.e., the second CORESETs) in the aforementioned CORESETs (M=6) include: CORESET#0 of cell 1, CORESET#3 of cell 1, CORESET#4 of cell 1, CORESET#1 of cell 2, and CORESET#2 of cell 2. Since there are CORESETs associated with CSSs in the second CORESETs, the second reference CORESET is determined to be "CORESET#0" of cell 1 according to "Criterion 2-2-1".

[0215] Next, other CORESETs with the same QCL-typeD attribute as the second reference CORESET are determined from the above CORESETs (M=6), resulting in “CORESET#2” for cell 1, “CORESET#4” for cell 1, “CORESET#1” for cell 2, and “CORESET#2” for cell 2.

[0216] Finally, the terminal listens to the PDCCH in "CORESET#0", "CORESET#2", "CORESET#4" of cell 1, "CORESET#1" and "CORESET#2" of cell 2, thereby enabling it to listen to the PDCCH in CORESETs where the associated PDCCH is repeated.

[0217] Based on the above description, the following embodiments of this application will specifically explain the criteria for determining the third reference CORESET from the M CORESETs.

[0218] Criterion 2-xy-1: (x is 1 or 2, y is 1 or 2)

[0219] In one possible example, if there is no CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated associated PDCCHs in the M CORESETs, then if there is a CORESET with associated CSS in the third CORESET, the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS belongs in the third CORESET; wherein, the third CORESET includes: the CORESETs with repeated associated PDCCHs among the M CORESETs.

[0220] It should be noted that during the overlapping PDCCH listening time on the active downlink BWP, since there may be CORESETs with duplicate associated PDCCHs among the M CORESETs, this embodiment considers the CORESETs with duplicate associated PDCCHs among the M CORESETs as the third CORESET. That is, each CORESET in the third CORESET has duplicate associated PDCCHs.

[0221] Furthermore, the third coreset may or may not contain a coreset with the same QCL-type D property as the second reference coreset. Therefore, to ensure that the QCL-type D property of the second reference coreset is different from that of the third reference coreset, it is necessary to analyze whether there is a coreset in the third coreset with the same QCL-type D property as the second reference coreset. Additionally, the third coreset may or may not contain coresets with associated CSS. Therefore, if the third coreset does not contain a coreset with the same QCL-type D property as the second reference coreset, but contains coresets with associated CSS, then the coreset belonging to the third coreset and associated with the smallest index CSS in the smallest sub-sub ...

[0222] As can be seen, by using "Guideline 2-xy-1" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the third reference CORESET) that is associated with PDCCH overlap, has a different QCL-typeD attribute from the second reference CORESET, and is associated with the minimum cell index and the minimum CSS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.

[0223] Criterion 2-xy-2: (x is 1 or 2, y is 1 or 2)

[0224] In one possible example, if there is no CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated PDCCH in the M CORESETs, then in the case that there is no CORESET with associated CSS in the third CORESET, the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index USS in the cell to which the CORESET with associated USS belongs.

[0225] As can be seen, by using "Guideline 2-xy-2" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the third reference CORESET) that is associated with overlapping PDCCHs, has a different QCL-typeD attribute from the second reference CORESET, and is associated with the smallest cell index and the smallest USS index, in the PDCCH listening time of overlapping PDCCHs on active downlink BWPs. This enables PDCCH listening in CORESETs with overlapping associated PDCCHs, thereby ensuring the flexibility, stability and reliability of system communication.

[0226] Criterion 2-xy-3: (x is 1 or 2, y is 1 or 2)

[0227] In one possible example, if among the M CORESETs with repeated associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then in the case where the fourth CORESET has a CORESET with associated CSS, the third reference CORESET specifically refers to: the CORESET belonging to the fourth CORESET and associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS belongs in the fourth CORESET; wherein, the fourth CORESET includes: among the CORESETs associated with the CORESETs in the M CORESETs that have the same QCL type D property as the second reference CORESET, the CORESETs with a different QCL type D property than the second reference CORESET; or, the fourth CORESET includes: among the CORESETs with repeated associated PDCCH in the M CORESETs, the CORESETs with a different QCL type D property than the second reference CORESET.

[0228] It should be noted that among the M CORESETs, there may be CORESETs associated with the same QCL type D attribute as the second reference CORESET. At the same time, among the CORESETs associated with the same QCL type D attribute as the second reference CORESET, there may be CORESETs with different QCL type D attributes than the second reference CORESET.

[0229] Example 5: During the PDCCH listening time overlapping on an active downlink BWP, the following CORESETs exist (M=4): CORESET#0 (associated with 1 TCI state), CORESET#1 (associated with 1 TCI state), CORESET#2 (associated with 1 TCI state), CORESET#3 (associated with 1 TCI state).

[0230] →There are duplicate PDCCHs between multiple PDCCH candidates associated with CORESET#1 and multiple PDCCH candidates associated with CORESET#2, that is, CORESET#1 is associated with CORESET#2;

[0231] →The QCL-typeD property corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD property corresponding to the TCI state of CORESET#0;

[0232] →The QCL-typeD property corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD property corresponding to the TCI state of CORESET#3;

[0233] →The QCL-typeD property corresponding to the TCI state of CORESET#1 is different from the QCL-typeD property corresponding to the TCI state of CORESET#2.

[0234] If the second reference CORESET is "CORESET#0", then the CORESETs with the same QCL-typeD attribute as the second reference CORESET in the above CORESETs (M=4) include: CORESET#1 and CORESET#3.

[0235] Furthermore, since CORESET#1 is associated with CORESET#2, the CORESET associated with the same QCL-typeD attribute as the second reference CORESET in the aforementioned CORESETs (M=4) includes: CORESET#2. Meanwhile, since the QCL-typeD attribute of CORESET#2 is different from that of the second reference CORESET, the fourth CORESET includes: CORESET#2.

[0236] As can be seen, by using "Guideline 2-xy-3" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the third reference CORESET) that is associated with PDCCH overlap, has a different QCL-typeD attribute from the second reference CORESET, and is associated with the minimum cell index and the minimum CSS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.

[0237] Rule 2-xy-4: (x is 1 or 2, y is 1 or 2)

[0238] In one possible example, if there is a CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated PDCCH in the M CORESETs, then in the case that there is no CORESET with associated CSS in the fourth CORESET, the third reference CORESET is specifically: the CORESET that belongs to the fourth CORESET and is associated with the smallest index USS in the cell to which the CORESET with associated USS in the fourth CORESET belongs.

[0239] The fourth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET that has a different QCL type D attribute from the second reference CORESET; or, the fourth CORESET includes: among the CORESETs with repeated associated PDCCHs among the M CORESETs, the CORESET that has a different QCL type D attribute from the second reference CORESET.

[0240] As can be seen, by using "Guideline 2-xy-4" in this example, the embodiments of this application can accurately and quickly identify a COSESET (i.e., the third reference CORESET) that is associated with overlapping PDCCHs, has a different QCL-typeD attribute from the second reference CORESET, and is associated with the smallest cell index and the smallest USS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCHs, thereby ensuring the flexibility, stability and reliability of system communication.

[0241] The following embodiment of this application provides an example to illustrate "Guideline 2-2-1" and "Guideline 2-2-2".

[0242] Example 6: In the case of overlapping PDCCH listening on an active downlink BWP, the following CORESETs exist (when M=6):

[0243] Cell 1: CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);

[0244] →There are duplicate PDCCHs between the multiple PDCCH candidates associated with CSS#1 and the multiple PDCCH candidates associated with CSS#4, that is, CSS#1 is associated with CSS#4 (or CORESET#2 is associated with CORESET#3);

[0245] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 in cell 1.

[0246] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 in cell 1.

[0247] →The QCL-typeD attribute corresponding to the TCI state of CORESET#4 in cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 1.

[0248] Cell 2: CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);

[0249] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 in cell 2.

[0250] →The QCL-typeD attribute corresponding to the TCI state of CORESET#2 in cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#3 in cell 1.

[0251] First, during the overlapping PDCCH listening time on the active downlink BWP, the cells associated with the aforementioned CORESETs (M=6) include cell 1 and cell 2. Specifically, the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, while the CORESETs associated with cell 2 include CORESET#1 and CORESET#2. The index of cell 1 is less than the index of cell 2, the index of CSS#0 is less than the index of CSS#1, and the index of CSS#1 is less than the index of CSS#4.

[0252] Secondly, if the second reference CORESET is “CORESET#0” of cell 1, then the CORESETs with the same QCL-typeD attribute as the second reference CORESET in the above CORESETs (M=6) include: “CORESET#2” of cell 1, “CORESET#4” of cell 1, “CORESET#1” of cell 2, and “CORESET#2” of cell 2.

[0253] Secondly, since "CORESET#2" and "CORESET#3" of cell 1 are associated, according to "Guideline 2-xy-3", the CORESET associated with the CORESET that has the same QCL-typeD property as the second reference CORESET includes: "CORESET#3" of cell 1. Meanwhile, since the QCL-typeD property of "CORESET#3" of cell 1 is different from the QCL-typeD property of the second reference CORESET, the fourth CORESET includes: "CORESET#3" of cell 1. Furthermore, since the fourth CORESET contains a CORESET associated with a CSS, the third reference CORESET is determined to be "CORESET#3" of cell 1.

[0254] Next, other CORESETs with the same QCL-typeD attribute as the second reference CORESET are determined from the above CORESETs (M=6), resulting in "CORESET#2" and "CORESET#4" for cell 1; similarly, other CORESETs with the same QCL-typeD attribute as the third reference CORESET are determined from the above CORESETs (M=6), resulting in "CORESET#1" and "CORESET#2" for cell 2.

[0255] Finally, the terminal listens to the PDCCH in "CORESET#0", "CORESET#2", "CORESET#3", "CORESET#4" of cell 1, "CORESET#1" of cell 2 and "CORESET#2" of cell 2, thereby realizing the listening of PDCCH in CORESETs with repeated associated PDCCH.

[0256] Based on the above description, the following embodiments of this application will further explain the criteria for determining the second reference CORESET and the third reference CORESET among the M CORESETs.

[0257] Guideline 2-3-1:

[0258] In one possible example, during the overlapping PDCCH listening time on the active downlink BWP, if there is a CORESET with associated CSS in the fifth CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the fifth CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the fifth CORESET belongs; wherein, the fifth CORESET includes: the CORESET with repeated associated PDCCH in the M CORESETs.

[0259] It should be noted that "Guideline 2-3-1" is similar to "Guideline 1-1", so it will not be elaborated on further.

[0260] As can be seen, unlike the "second reference CORESET" in the above "Guideline 2-2-1" and "Guideline 2-2-2", which is a COSESET that is not associated with PDCCH overlap, associated with the minimum cell index, and associated with the minimum CSS / USS index, through "Guideline 2-3-1" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the second reference CORESET) that is associated with PDCCH overlap, associated with the minimum cell index, and associated with the minimum CSS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with associated PDCCH repetition, thereby ensuring the flexibility, stability, and reliability of system communication.

[0261] Guideline 2-3-2:

[0262] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the fifth CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the fifth CORESET and is associated with the smallest index USS in the cell to which each associated USS CORESET in the fifth CORESET belongs.

[0263] The fifth CORESET includes: the CORESET with the associated PDCCH repeating in the M CORESETs.

[0264] It should be noted that "Guideline 2-3-2" is similar to "Guideline 1-2", so it will not be elaborated further.

[0265] As can be seen, by following the "Guideline 2-3-2" in this example, the embodiments of this application can accurately and quickly determine a COSESET (i.e., the second reference CORESET) that is associated with PDCCH overlap, the minimum cell index, and the minimum USS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCH, thereby ensuring the flexibility, stability, and reliability of system communication.

[0266] Based on the above description, the following embodiments of this application will further explain the criteria for determining the third reference CORESET from the M CORESETs.

[0267] Criterion 2-3-z-1 (z is 1 or 2):

[0268] In one possible example, if there is a CORESET with associated CSS in the sixth CORESET, then the third reference CORESET is specifically: the CORESET belonging to the sixth CORESET and associated with the smallest index CSS in the cell to which the CORESET with associated CSS in the sixth CORESET belongs; wherein, the sixth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D property as the second reference CORESET among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET; or, the sixth CORESET includes: among the CORESETs with repeated associated PDCCH among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET.

[0269] As can be seen, by following the "Guideline 2-3-z-1" in this example, the embodiments of this application can accurately and quickly identify a COSESET (i.e., the third reference CORESET) that is associated with PDCCH overlap, has a different QCL-typeD attribute from the second reference CORESET, and is associated with the minimum cell index and the minimum CSS index during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.

[0270] Criterion 2-3-z-2 (z is 1 or 2):

[0271] In one possible example, during the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the sixth CORESET, then the third reference CORESET is specifically: the CORESET that belongs to the sixth CORESET and is associated with the smallest index USS in the cell to which the associated USS CORESET in the sixth CORESET belongs.

[0272] The sixth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D attribute as the second reference CORESET among the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, the sixth CORESET includes: among the CORESETs with repeated associated PDCCH among the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

[0273] As can be seen, by following the "Guideline 2-3-z-2" in this example, the embodiments of this application can accurately and quickly identify a COSESET (i.e., the third reference CORESET) that is associated with overlapping PDCCHs, has a different QCL-typeD attribute from the second reference CORESET, and is associated with the smallest cell index and the smallest USS index, during the PDCCH listening time on the active downlink BWP. This enables PDCCH listening in CORESETs with overlapping associated PDCCHs, thereby ensuring the flexibility, stability and reliability of system communication.

[0274] Consistent with the above embodiments, this application provides a flowchart of another channel monitoring method. Please refer to [link / reference]. Figure 3 The method includes:

[0275] S310. During the PDCCH listening time overlapping on the active downlink BWP, the network device is configured with M CORESETs, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1.

[0276] Specifically, all CORESETs in the M CORESETs have the same quasi-co-addressable QCL type D attribute; or, there are CORESETs among the M CORESETs with different QCL type D attributes; or, there are CORESETs among the M CORESETs with the same QCL type D attribute.

[0277] Specifically, the M CORESETs include a first reference CORESET and / or a CORESET with the same quasi-co-located QCL type D attribute as the first reference CORESET, wherein the first reference CORESET is one of the M CORESETs; or, the M CORESETs include a second reference CORESET and / or a CORESET with the same QCL type D attribute as the second reference CORESET, and a third reference CORESET and / or a CORESET with the same QCL type D attribute as the third reference CORESET; wherein the second reference CORESET is one of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from that of the third reference CORESET.

[0278] It should be noted that the descriptions of the various embodiments in this application each have their own emphasis, therefore Figure 3 For parts not described in detail in the embodiments, please refer to [link / reference]. Figure 2 The relevant descriptions of the embodiments will not be repeated here.

[0279] As can be seen from the embodiments of this application, during the overlapping PDCCH listening time on the active downlink BWP, there are duplicate PDCCHs among the M CORESET-associated PDCCH candidates configured by the network device for the terminal. Therefore, the terminal can listen to PDCCHs in these M CORESETs, thereby achieving PDCCH listening in CORESETs with duplicate associated PDCCHs, improving the reliability of PDCCHs, and thus ensuring the flexibility, stability, and reliability of system communication.

[0280] The foregoing primarily describes the solutions of the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the aforementioned functions, the terminal or network device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0281] This application embodiment can divide a terminal or network device into functional units based on the above method examples. For example, each function can be divided into separate functional units, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software program module. It should be noted that the unit division in this application embodiment is illustrative and only represents a logical functional division; in actual implementation, there may be other division methods.

[0282] When using integrated units, Figure 4 A functional block diagram of a channel monitoring device is provided. The channel monitoring device 400 includes a processing unit 402 and a communication unit 403. The processing unit 402 is used to control and manage the actions of the terminal. For example, the processing unit 402 is used to support the terminal in performing... Figure 2 The steps in the process and other processes used in the technical solutions described in this application. The communication unit 403 is used to support communication between the terminal and other devices in the wireless communication system. The channel monitoring device 400 may also include a storage unit 401 for storing the program code executed by the channel monitoring device 400 and the data transmitted.

[0283] It should be noted that the channel monitoring device 400 can be a chip or a chip module.

[0284] The processing unit 402 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processing unit 402 can also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. The communication unit 403 can be a communication interface, transceiver, transceiver circuit, etc., and the storage unit 401 can be a memory. When the processing unit 402 is a processor, the communication unit 403 is a communication interface, and the storage unit 401 is a memory, the channel monitoring device 400 involved in the embodiments of this application can be... Figure 6 The terminal shown.

[0285] In specific implementation, the processing unit 402 is used to execute any step performed by the terminal as described in the above method embodiment, and when performing data transmission such as sending, it can optionally call the communication unit 403 to complete the corresponding operation. A detailed description follows.

[0286] The processing unit 402 is configured to: if there are M CORESETs in the overlapping PDCCH listening time on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, then listen to the PDCCH in the M CORESETs, where M is an integer greater than or equal to 1.

[0287] It should be noted that, Figure 4 The specific implementation of each operation in the embodiments can be found in the above description. Figure 2 The descriptions in the method embodiments shown will not be repeated here.

[0288] As can be seen in this embodiment, if there are M cores in the overlapping PDCCH listening time on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M cores, then the channel listening device listens for PDCCHs in the M cores, thereby realizing the listening for PDCCHs in the cores with duplicate associated PDCCHs, improving the reliability of PDCCHs, and thus ensuring the flexibility, stability and reliability of system communication.

[0289] In one possible example, all CORESETs in the M CORESETs have the same quasi-co-located QCL type D attribute; or, there are CORESETs in the M CORESETs with different QCL type D attributes; or, there are CORESETs in the M CORESETs with the same QCL type D attribute.

[0290] In one possible example, regarding listening to PDCCH in M ​​CORESETs, processing unit 402 is specifically configured to: listen to PDCCH in a first reference CORESET and / or a CORESET having the same quasi-co-addressable QCL type D attribute as the first reference CORESET, wherein the first reference CORESET is one of the M CORESETs; or, listen to PDCCH in a second reference CORESET and / or a CORESET having the same QCL type D attribute as the second reference CORESET, and listen to PDCCH in a third reference CORESET and / or a CORESET having the same QCL type D attribute as the third reference CORESET; wherein the second reference CORESET is one of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from that of the third reference CORESET.

[0291] In one possible example, during the PDCCH listening time overlapping on the active downlink BWP, if there is a CORESET in the first CORESET that is associated with the common search space CSS, then the first reference CORESET is specifically: the CORESET that belongs to the first CORESET and is associated with the smallest index CSS in the cell to which the CORESET associated with the CSS in the first CORESET belongs.

[0292] The first CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

[0293] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the first CORESET, then the first reference CORESET is specifically: the CORESET that belongs to the first CORESET and is associated with the smallest index USS in the cell to which the CORESET associated with the user-specific search space USS belongs in the first CORESET.

[0294] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is a cell in the first cell set that contains a CORESET with associated CSS, then the second reference CORESET is specifically: the CORESET with the smallest associated index CSS in the cell with the smallest index in the cell containing the CORESET with associated CSS in the first cell set; wherein, the first cell set includes: cells corresponding to M CORESETs.

[0295] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no cell in the first cell set that contains a CORESET with an associated CSS, then the second reference CORESET is specifically: the CORESET with the smallest associated index USS in the cell with the smallest index among the cells in the first cell set that contain a CORESET with an associated USS.

[0296] In one possible example, during the overlapping PDCCH listening time on an active downlink BWP, if there is a CORESET with associated CSS in the second CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the second CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the second CORESET belongs; wherein, the second CORESET includes: CORESETs with repeated non-associated PDCCHs among M CORESETs.

[0297] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the second CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the second CORESET and is associated with the smallest index USS in the cell to which each associated USS CORESET belongs in the second CORESET.

[0298] In one possible example, if there is no CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated associated PDCCHs in the M CORESETs, then if there is a CORESET with associated CSS in the third CORESET, the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS belongs in the third CORESET; wherein, the third CORESET includes: CORESETs with repeated associated PDCCHs among the M CORESETs.

[0299] In one possible example, if there is no CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated associated PDCCH in the M CORESETs, then in the case that there is no CORESET associated with CSS in the third CORESET, the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index USS in the cell to which each of the CORESETs associated with USS belongs.

[0300] In one possible example, if among the M CORESETs with repeated associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then in the case where there is a CORESET with associated CSS in the fourth CORESET, the third reference CORESET specifically refers to: the CORESET belonging to the fourth CORESET and associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS belongs in the fourth CORESET; wherein, the fourth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D property as the second reference CORESET among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET; or, the fourth CORESET includes: among the CORESETs with repeated associated PDCCH among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET.

[0301] In one possible example, if among the CORESETs with repeated associated PDCCH in M ​​CORESETs, there exists a CORESET with the same QCL type D property as the second reference CORESET, then in the case that there is no associated CSS CORESET in the fourth CORESET, the third reference CORESET is specifically: the CORESET belonging to the fourth CORESET and associated with the smallest index USS in the cell to which each of the associated USS CORESETs in the fourth CORESET belongs.

[0302] In one possible example, during the overlapping PDCCH listening time on an active downlink BWP, if there is a CORESET with associated CSS in the fifth CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the fifth CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the fifth CORESET belongs; wherein, the fifth CORESET includes: CORESETs with repeated associated PDCCH in M ​​CORESETs.

[0303] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the fifth CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the fifth CORESET and is associated with the smallest index USS in the cell to which each associated USS CORESET in the fifth CORESET belongs.

[0304] In one possible example, if there is a CORESET with associated CSS in the sixth CORESET, then the third reference CORESET is specifically: the CORESET belonging to the sixth CORESET and associated with the smallest index CSS in the cell to which the CORESET with associated CSS in the sixth CORESET belongs; wherein, the sixth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D property as the second reference CORESET among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET; or, the sixth CORESET includes: among the CORESETs with repeated associated PDCCH among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET.

[0305] In one possible example, during the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the sixth CORESET, then the third reference CORESET is specifically: the CORESET that belongs to the sixth CORESET and is associated with the smallest index USS in the cell to which the associated USS CORESET in the sixth CORESET belongs.

[0306] When using integrated units, Figure 5A functional block diagram of another channel monitoring device is provided. The channel monitoring device 500 includes a processing unit 502 and a communication unit 503. The processing unit 502 is used to control and manage the operations of network devices. For example, the processing unit 502 is used to support network devices in performing... Figure 3 The steps in the process and other processes used in the technical solutions described in this application. The communication unit 503 is used to support communication between the network device and other devices in the wireless communication system. The channel monitoring device 500 may also include a storage unit 501 for storing the program code executed by the channel monitoring device 500 and the data transmitted.

[0307] It should be noted that the channel monitoring device 500 can be a chip or a chip module.

[0308] The processing unit 502 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processing unit 502 can also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. The communication unit 503 can be a communication interface, transceiver, transceiver circuit, etc., and the storage unit 501 can be a memory. When the processing unit 502 is a processor, the communication unit 503 is a communication interface, and the storage unit 501 is a memory, the channel monitoring device 500 involved in the embodiments of this application can be... Figure 7 The network device shown.

[0309] In specific implementation, the processing unit 502 is used to execute any step performed by the network device as described in the above method embodiment, and when performing data transmission such as sending, it may selectively call the communication unit 503 to complete the corresponding operation. A detailed description follows.

[0310] The processing unit 502 is used to: configure M CORESETs during the PDCCH listening time of overlapping PDCCHs on the active downlink BWP, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1.

[0311] It should be noted that, Figure 5 The specific implementation of each operation in the embodiments can be found in the above description. Figure 2 and Figure 3 The descriptions in the method embodiments shown will not be repeated here.

[0312] As can be seen in this embodiment, during the overlapping PDCCH monitoring time on the active downlink BWP, there are duplicate PDCCHs among the M CORESET-associated PDCCH candidates configured by the channel monitoring device for the terminal. Therefore, the terminal can monitor PDCCHs in these M CORESETs, thereby achieving PDCCH monitoring in CORESETs with duplicate associated PDCCHs, improving the reliability of PDCCHs, and thus ensuring the flexibility, stability, and reliability of system communication.

[0313] In one possible example, all CORESETs in the M CORESETs have the same quasi-co-located QCL type D attribute; or, there are CORESETs in the M CORESETs with different QCL type D attributes; or, there are CORESETs in the M CORESETs with the same QCL type D attribute.

[0314] In one possible example, the M CORESETs include a first reference CORESET and / or a CORESET with the same quasi-co-located QCL type D attribute as the first reference CORESET, wherein the first reference CORESET is one of the M CORESETs; or, the M CORESETs include a second reference CORESET and / or a CORESET with the same QCL type D attribute as the second reference CORESET, and a third reference CORESET and / or a CORESET with the same QCL type D attribute as the third reference CORESET; wherein the second reference CORESET is one of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from that of the third reference CORESET.

[0315] In one possible example, during the overlapping PDCCH listening time on an active downlink BWP, if there is a CORESET in the first CORESET that is associated with a common search space CSS, then the first reference CORESET is specifically: the CORESET that belongs to the first CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs associated with the CSS in the first CORESET belongs; wherein, the first CORESET includes: CORESETs with repeated associated PDCCHs in M ​​CORESETs.

[0316] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the first CORESET, then the first reference CORESET is specifically: the CORESET that belongs to the first CORESET and is associated with the smallest index USS in the cell to which the CORESET associated with the user-specific search space USS belongs in the first CORESET.

[0317] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is a cell in the first cell set that contains a CORESET with associated CSS, then the second reference CORESET is specifically: the CORESET with the smallest associated index CSS in the cell with the smallest index in the cell containing the CORESET with associated CSS in the first cell set; wherein, the first cell set includes: cells corresponding to M CORESETs.

[0318] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no cell in the first cell set that contains a CORESET with an associated CSS, then the second reference CORESET is specifically: the CORESET with the smallest associated index USS in the cell with the smallest index among the cells in the first cell set that contain a CORESET with an associated USS.

[0319] In one possible example, during the overlapping PDCCH listening time on an active downlink BWP, if there is a CORESET with associated CSS in the second CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the second CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the second CORESET belongs; wherein, the second CORESET includes: CORESETs with repeated non-associated PDCCHs among M CORESETs.

[0320] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the second CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the second CORESET and is associated with the smallest index USS in the cell to which each associated USS CORESET belongs in the second CORESET.

[0321] In one possible example, if there is no CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated associated PDCCHs in the M CORESETs, then if there is a CORESET with associated CSS in the third CORESET, the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS belongs in the third CORESET; wherein, the third CORESET includes: CORESETs with repeated associated PDCCHs among the M CORESETs.

[0322] In one possible example, if there is no CORESET with the same QCL type D property as the second reference CORESET among the CORESETs with repeated associated PDCCH in the M CORESETs, then in the case that there is no CORESET associated with CSS in the third CORESET, the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index USS in the cell to which each of the CORESETs associated with USS belongs.

[0323] In one possible example, if among the M CORESETs with repeated associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then in the case where there is a CORESET with associated CSS in the fourth CORESET, the third reference CORESET specifically refers to: the CORESET belonging to the fourth CORESET and associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS belongs in the fourth CORESET; wherein, the fourth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D property as the second reference CORESET among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET; or, the fourth CORESET includes: among the CORESETs with repeated associated PDCCH among the M CORESETs, the CORESET with a different QCL type D property than the second reference CORESET.

[0324] In one possible example, if among the CORESETs with repeated associated PDCCH in M ​​CORESETs, there exists a CORESET with the same QCL type D property as the second reference CORESET, then in the case that there is no associated CSS CORESET in the fourth CORESET, the third reference CORESET is specifically: the CORESET belonging to the fourth CORESET and associated with the smallest index USS in the cell to which each of the associated USS CORESETs in the fourth CORESET belongs.

[0325] In one possible example, during the overlapping PDCCH listening time on the active downlink BWP, if there is a CORESET with associated CSS in the fifth CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the fifth CORESET and is associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the fifth CORESET belongs; the fifth CORESET includes: CORESETs with repeated associated PDCCH in M ​​CORESETs.

[0326] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is no associated CSS CORESET in the fifth CORESET, then the second reference CORESET is specifically: the CORESET that belongs to the fifth CORESET and is associated with the smallest index USS in the cell to which each associated USS CORESET in the fifth CORESET belongs.

[0327] In one possible example, during the PDCCH listening time overlapping on an active downlink BWP, if there is a CORESET with associated CSS in the sixth CORESET, then the third reference CORESET is specifically: the CORESET belonging to the sixth CORESET and associated with the smallest index CSS in the cell to which each of the CORESETs with associated CSS in the sixth CORESET belongs; wherein, the sixth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D property as the second reference CORESET among the M CORESETs, the CORESET with a different QCL type D property from the second reference CORESET; or, the sixth CORESET includes: among the CORESETs with repeated associated PDCCHs among the M CORESETs, the CORESET with a different QCL type D property from the second reference CORESET.

[0328] In one possible example, during the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the sixth CORESET, then the third reference CORESET is specifically: the CORESET that belongs to the sixth CORESET and is associated with the smallest index USS in the cell to which the associated USS CORESET in the sixth CORESET belongs.

[0329] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal 600 includes a processor 610, a memory 620, a communication interface 630, and a communication bus for connecting the processor 610, the memory 620, and the communication interface 630.

[0330] The memory 620 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used to store program code executed by terminal 600 and data transmitted.

[0331] The communication interface 630 is used to receive and send data.

[0332] The processor 610 can be one or more CPUs. If the processor 610 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0333] The processor 610 in terminal 600 is used to read one or more programs 621 stored in memory 620 and perform the following operations: if there are M CORESETs in the overlapping PDCCH listening time on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, then listen to the PDCCH in the M CORESETs, where M is an integer greater than or equal to 1.

[0334] It should be noted that the specific implementation of each operation can adopt the methods described above. Figure 2 The corresponding description of the method embodiments shown indicates that the terminal 600 can be used to execute the terminal-side methods of the above method embodiments of this application, and will not be described in detail here.

[0335] It is evident that if there are M cores in the overlapping PDCCH listening opportunities on the active downlink BWP, and there are duplicate PDCCHs among the PDCCH candidates associated with these M cores, then PDCCHs can be listened to in these M cores. This enables listening to PDCCHs in cores with duplicate associated PDCCHs, improving the reliability of PDCCHs and thus ensuring the flexibility, stability, and reliability of system communication.

[0336] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. The network device 700 includes a processor 710, a memory 720, a communication interface 730, and a communication bus for connecting the processor 710, the memory 720, and the communication interface 730.

[0337] The memory 720 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used to store program code executed by the network device 700 and data transmitted.

[0338] The communication interface 730 is used to receive and send data.

[0339] The processor 710 can be one or more CPUs. If the processor 710 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0340] The processor 710 in the network device 700 is used to read one or more programs 721 stored in the memory 720 and perform the following operations: during the overlapping PDCCH listening time on the active downlink BWP, configure M CORESETs, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1.

[0341] It should be noted that the specific implementation of each operation can adopt the methods described above. Figure 2 and Figure 3 The corresponding description of the method embodiments shown indicates that the network device 700 can be used to execute the network device-side methods of the above-described method embodiments of this application, and will not be described in detail here.

[0342] It is evident that during the overlapping PDCCH listening times on active downlink BWPs, there are duplicate PDCCHs among the M CORESET-associated PDCCH candidates configured by the network device for the terminal. Therefore, the terminal can listen for PDCCHs in these M CORESETs, thereby achieving PDCCH listening in CORESETs with duplicate associated PDCCHs, improving PDCCH reliability, and thus ensuring the flexibility, stability, and reliability of system communication.

[0343] This application also provides a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the above method embodiments for a terminal or management device.

[0344] This application also provides a computer program product, wherein the computer program product includes a computer program operable to cause a computer to perform some or all of the steps described in the above method embodiments for a terminal or management device. This computer program product may be a software installation package.

[0345] In the above embodiments, the descriptions of each embodiment in this application have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0346] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, read-only optical discs (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a terminal or management device. Of course, the processor and storage medium can also exist as discrete components in a terminal or management device.

[0347] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0348] The modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0349] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A channel monitoring method, characterized in that, include: If there are M control resource sets (CORESETs) in the listening time of the physical downlink control channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, then PDCCHs are listened to in the M CORESETs, where M is an integer greater than or equal to 1. The step of listening to the PDCCH in the M CORESETs includes: Listen to PDCCH in a second reference CORESET and / or a CORESET that has the same quasi-co-addressable QCL type D attribute as the second reference CORESET; If the first cell set contains a cell that contains a CORESET with associated public search space CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET with the smallest associated index CSS among the cells with the smallest index among the cells containing the associated CORESET in the first cell set. If the first cell set does not contain a cell that contains a CORESET associated with a CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET associated with the smallest index USS among the cells in the first cell set that contain a CORESET associated with a user-specific search space USS.

2. The method according to claim 1, characterized in that, All CORESETs among the M CORESETs have the same quasi-co-located QCL type D attribute; or... Among the M CORESETs, there exist CORESETs with different QCL type D attributes; or... Among the M CORESETs, there are CORESETs with the same QCL type D attribute.

3. The method of claim 1, wherein, The monitoring of PDCCH in the M CORESETs includes: Listen for PDCCH in a first reference CORESET and / or a CORESET with the same QCL type D property as the first reference CORESET, where the first reference CORESET is one of the M CORESETs; or... Listen to PDCCH in a third reference CORESET and / or a CORESET that has the same QCL type D property as the third reference CORESET; The third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from the QCL type D attribute of the third reference CORESET.

4. The method of claim 3, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is a CORESET with associated CSS in the first CORESET, then the first reference CORESET is: The CORESET that belongs to the first CORESET and is associated with the smallest index CSS in the cell of the cell to which the CORESET with associated CSS belongs; The first CORESET includes: a CORESET with associated PDCCH repetition among the M CORESETs.

5. The method of claim 3, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the first CORESET, then the first reference CORESET is: The CORESET that belongs to the first CORESET and is associated with the smallest index of the USS in the cell to which each CORESET belongs.

6. The method of claim 1, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if a CORESET with associated CSS exists in the second CORESET, then the second reference CORESET is: The CORESET that belongs to the second CORESET and is associated with the smallest index CSS in the cell of the cell to which the CORESET of the associated CSS belongs; The second CORESET includes: a CORESET with non-associated PDCCH repetitions among the M CORESETs.

7. The method of claim 1, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the second CORESET, then the second reference CORESET is: The CORESET that belongs to the second CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The second CORESET includes: a CORESET with non-associated PDCCH repetitions among the M CORESETs.

8. The method of claim 3, wherein, If, among the M CORESETs with repeated associated PDCCH, there is no CORESET with the same QCL type D property as the second reference CORESET, then, if the third CORESET has an associated CSS CORESET, the third reference CORESET is: The CORESET with the smallest index in the cell of the cell to which the CORESET with the associated CSS belongs in the third CORESET and is associated with the smallest index CSS. The third CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

9. The method of claim 3, wherein, If, among the M CORESETs with duplicate associated PDCCH, there is no CORESET with the same QCL type D property as the second reference CORESET, then, in the case that the third CORESET has no associated CSS CORESET, the third reference CORESET is: The CORESET that belongs to the third CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The third CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

10. The method according to claim 3, characterized in that, If, among the M CORESETs with repeated associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then, in the case where the fourth CORESET has an associated CSS CORESET, the third reference CORESET is: The CORESET with the smallest index in the cell of the cell to which the CORESET with the associated CSS belongs in the fourth CORESET and is associated with the smallest index CSS. The fourth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The fourth CORESET includes: among the CORESETs with repeated associated PDCCH in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

11. The method according to claim 3, characterized in that, If, among the M CORESETs with duplicate associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then, in the case that the fourth CORESET does not have an associated CSS CORESET, the third reference CORESET is: The CORESET that belongs to the fourth CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The fourth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The fourth CORESET includes: among the CORESETs with repeated associated PDCCH in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

12. The method according to claim 1, characterized in that, During the PDCCH listening time overlapping on the active downlink BWP, if there is a CORESET associated with CSS in the fifth CORESET, then the second reference CORESET is: The CORESET with the smallest index in the cell of the cell to which the CORESET with the associated CSS belongs in the fifth CORESET and is associated with the smallest index CSS. The fifth CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

13. The method of claim 1, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the fifth CORESET, then the second reference CORESET is: The CORESET that belongs to the fifth CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The fifth CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

14. The method of claim 3, wherein, If the sixth CORESET contains a CORESET with associated CSS, then the third reference CORESET is: The cell with the smallest index in the cell to which the CORESET with the associated CSS belongs in the sixth CORESET and is associated with the smallest index CSS. The sixth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The sixth CORESET includes: among the CORESETs with associated PDCCH repetitions in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

15. The method of claim 3, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the sixth CORESET, then the third reference CORESET is: The CORESET that belongs to the sixth CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The sixth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The sixth CORESET includes: among the CORESETs with associated PDCCH repetitions in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

16. A channel monitoring method, characterized by, include: During the monitoring of the Physical Downlink Control Channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), M control resource sets (CORESET) are configured, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1. The M CORESETs include: a second reference CORESET and / or a CORESET having the same quasi-co-addressable QCL type D attribute as the second reference CORESET; If the first cell set contains a cell that contains a CORESET with associated public search space CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET with the smallest associated index CSS among the cells with the smallest index among the cells containing the associated CORESET in the first cell set. If the first cell set does not contain a cell that contains a CORESET associated with a CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET associated with the smallest index USS among the cells in the first cell set that contain a CORESET associated with a user-specific search space USS.

17. The method of claim 16, wherein, All CORESETs among the M CORESETs have the same quasi-co-located QCL type D attribute; or... Among the M CORESETs, there exist CORESETs with different QCL type D attributes; or... Among the M CORESETs, there are CORESETs with the same QCL type D attribute.

18. The method according to claim 16, characterized in that, The M CORESETs include a first reference CORESET and / or a CORESET with the same QCL type D attribute as the first reference CORESET, wherein the first reference CORESET is one of the M CORESETs; or, The M CORESETs also include a third reference CORESET and / or a CORESET with the same QCL type D attribute as the third reference CORESET; The third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from the QCL type D attribute of the third reference CORESET.

19. The method according to claim 18, characterized in that, During the PDCCH listening time overlapping on the active downlink BWP, if there is a CORESET with associated CSS in the first CORESET, then the first reference CORESET is: The CORESET that belongs to the first CORESET and is associated with the smallest index CSS in the cell of the cell to which the CORESET with associated CSS belongs; The first CORESET includes: a CORESET with associated PDCCH repetition among the M CORESETs.

20. The method of claim 18, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the first CORESET, then the first reference CORESET is: The CORESET that belongs to the first CORESET and is associated with the smallest index of the USS in the cell to which each CORESET belongs.

21. The method of claim 16, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if a CORESET with associated CSS exists in the second CORESET, then the second reference CORESET is: The CORESET that belongs to the second CORESET and is associated with the smallest index CSS in the cell of the cell to which the CORESET of the associated CSS belongs; The second CORESET includes: a CORESET with non-associated PDCCH repetitions among the M CORESETs.

22. The method of claim 16, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the second CORESET, then the second reference CORESET is: The CORESET that belongs to the second CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The second CORESET includes: a CORESET with non-associated PDCCH repetitions among the M CORESETs.

23. The method of claim 18, wherein, If, among the M CORESETs with repeated associated PDCCH, there is no CORESET with the same QCL type D property as the second reference CORESET, then, if the third CORESET has an associated CSS CORESET, the third reference CORESET is: The CORESET with the smallest index in the cell of the cell to which the CORESET with the associated CSS belongs in the third CORESET and is associated with the smallest index CSS. The third CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

24. The method of claim 18, wherein, If, among the M CORESETs with duplicate associated PDCCH, there is no CORESET with the same QCL type D property as the second reference CORESET, then, in the case that the third CORESET has no associated CSS CORESET, the third reference CORESET is: The CORESET that belongs to the third CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The third CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

25. The method of claim 18, wherein, If, among the M CORESETs with repeated associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then, in the case where the fourth CORESET has an associated CSS CORESET, the third reference CORESET is: The CORESET with the smallest index in the cell of the cell to which the CORESET with the associated CSS belongs in the fourth CORESET and is associated with the smallest index CSS. The fourth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The fourth CORESET includes: among the CORESETs with repeated associated PDCCH in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

26. The method of claim 18, wherein, If, among the M CORESETs with duplicate associated PDCCH, there exists a CORESET with the same QCL type D property as the second reference CORESET, then, in the case that the fourth CORESET does not have an associated CSS CORESET, the third reference CORESET is: The CORESET that belongs to the fourth CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The fourth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The fourth CORESET includes: among the CORESETs with repeated associated PDCCH in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

27. The method of claim 16, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is a CORESET associated with CSS in the fifth CORESET, then the second reference CORESET is: The CORESET with the smallest index in the cell of the cell to which the CORESET with the associated CSS belongs in the fifth CORESET and is associated with the smallest index CSS. The fifth CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

28. The method of claim 16, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the fifth CORESET, then the second reference CORESET is: The CORESET that belongs to the fifth CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The fifth CORESET includes: the CORESET with associated PDCCH repetition in the M CORESETs.

29. The method of claim 18, wherein, During the PDCCH listening time overlapping on the active downlink BWP, if there is a CORESET with associated CSS in the sixth CORESET, then the third reference CORESET is: The CORESET with the smallest index in the cell to which the CORESET with the associated CSS belongs in the sixth CORESET and is associated with the smallest index CSS. The sixth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, a CORESET with a different QCL type D attribute from the second reference CORESET; or, The sixth CORESET includes: among the CORESETs with associated PDCCH repetitions in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

30. The method according to claim 18, characterized in that, During the PDCCH listening time overlapping on the active downlink BWP, if there is no associated CSS CORESET in the sixth CORESET, then the third reference CORESET is: The CORESET that belongs to the sixth CORESET and is associated with the smallest index USS in the cell of the cell to which the CORESET of the associated USS belongs; The sixth CORESET includes: among the M CORESETs associated with a CORESET that has the same QCL type D attribute as the second reference CORESET, the CORESET whose QCL type D attribute is different from that of the second reference CORESET; or, The sixth CORESET includes: among the CORESETs with associated PDCCH repetitions in the M CORESETs, the CORESET whose QCL type D attribute is different from that of the second reference CORESET.

31. A channel monitoring device, characterized in that, The device includes a processing unit, the processing unit being used for: If there are M control resource sets (CORESETs) in the listening time of the physical downlink control channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, then PDCCHs are listened to in the M CORESETs, where M is an integer greater than or equal to 1. The step of listening to the PDCCH in the M CORESETs includes: Listen to PDCCH in a second reference CORESET and / or a CORESET that has the same quasi-co-addressable QCL type D attribute as the second reference CORESET; If the first cell set contains a cell that contains a CORESET with associated public search space CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET with the smallest associated index CSS among the cells with the smallest index among the cells containing the associated CORESET in the first cell set. If the first cell set does not contain a cell that contains a CORESET associated with a CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET associated with the smallest index USS among the cells in the first cell set that contain a CORESET associated with a user-specific search space USS.

32. A channel monitoring apparatus, comprising: The device includes a processing unit, the processing unit being used for: During the monitoring of the Physical Downlink Control Channel (PDCCH) overlapping on the active downlink bandwidth portion (BWP), M control resource sets (CORESET) are configured, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, where M is an integer greater than or equal to 1. The M CORESETs include: a second reference CORESET and / or a CORESET having the same quasi-co-addressable QCL type D attribute as the second reference CORESET; If the first cell set contains a cell that contains a CORESET with associated public search space CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET with the smallest associated index CSS among the cells with the smallest index among the cells containing the associated CORESET in the first cell set. If the first cell set does not contain a cell that contains a CORESET associated with a CSS, and the first cell set includes cells corresponding to the M CORESETs, then the second reference CORESET is: a CORESET associated with the smallest index USS among the cells in the first cell set that contain a CORESET associated with a user-specific search space USS.

33. A terminal, characterized by The method includes a processor, a memory, a communication interface, and one or more programs, said programs being stored in the memory and configured to be executed by the processor, said programs including instructions for performing the steps of the method as described in any one of claims 1-15.

34. A network device, comprising: The device includes a processor, a memory, a communication interface, and one or more programs, said programs being stored in the memory and configured to be executed by the processor, said programs including instructions for performing the steps of the method as described in any one of claims 16-30.

35. A computer readable storage medium, characterized in that, It stores a computer program for electronic data interchange, wherein the computer program causes the computer to perform the method as described in any one of claims 1-30.

Images