Terminal, network device, and method

Abstract

To provide a communication method, apparatus, and computer-readable medium.SOLUTION: A terminal receives an indication of a first transmissionconfigurationindicator (TCI) state in which at least one referencesignal (RS) is associated with a first physical cell identity (ID). Or the terminal device monitors a first physical downlink control channel (PDCCH) in a first monitoring occasion for a first search space based on a second TCI state or based on quasi-co-location (QCL), wherein at least one of an RS in the second TCI state and the QCL assumption is associated with a second physical cell ID; SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to communication methods, apparatus, and computer storage media. [Background technology]

[0002] At the RAN#86 meeting of the third generation partnership project (3GPP®), it was agreed to support enhancements to multi-beam operation, primarily targeting Frequency Range 2 (FR2) but also applicable to Frequency Range 1 (FR1). It was agreed to identify and specify features to facilitate more efficient (lower latency and overhead) downlink (DL) and uplink (UL) beam management within and between cells. For example, it was proposed to support a common beam for transmitting and receiving data and control information for DL ​​and UL. It was also proposed to support a unified Transmission Configuration Indication (TCI) framework for DL ​​and UL beam direction. Additionally, multi-input multi-output (MIMO) technology, including features that facilitate the use of multiple antenna elements at base stations for both sub- and above-6 GHz frequency bands, was proposed. Therefore, it is worthwhile to extend multi-beam operation. Summary of the Invention [Problem to be solved by the invention]

[0003] Generally, embodiments of the present disclosure provide a method, apparatus, and computer storage medium for communications. [Means for solving the problem]

[0004] In a first aspect, a method of communications is provided, the method including, in a terminal device, receiving from a network device an indication of a first transmission configuration indicator (TCI) state, the first TCI state having at least one reference signal (RS) associated with a first physical cell identity (ID), monitoring a first physical downlink control channel (PDCCH) within a first monitoring occasion for a first search space based on a second TCI state or based on quasi co-location (QCL), where at least one RS in the second TCI state and QCL assumption is associated with a second physical cell ID, and monitoring the second PDCCH within a second monitoring occasion for a second search space based on a condition.

[0005] In a second aspect, a method of communications is provided, the method including receiving, at a terminal device, from a network device, a first indication of a first set of transmission configuration indicator (TCI) states for a first set of control resource sets (CORESETs), receiving a second indication of a second set of TCI states for a second set of CORESETs, and performing one or two beam failure recovery procedures based on a condition.

[0006] In a third aspect, a method of communications is provided, the method including: transmitting, in a network device, to a terminal device an indication of a first transmission configuration indicator (TCI) state, the first TCI state having at least one reference signal (RS) associated with a first physical cell identity (ID); transmitting a first physical downlink control channel (PDCCH) within a first monitoring occasion for a first search space based on a second TCI state or based on quasi co-location (QCL), where at least one RS in the second TCI state and QCL assumption is associated with a second physical cell ID; and transmitting the second PDCCH within a second monitoring occasion for a second search space based on a condition.

[0007] In a fourth aspect, a method of communications is provided, the method including: transmitting, at a network device, to a terminal device, a first indication of a first set of transmission configuration indicator (TCI) states for a first set of control resource sets (CORESETs), and a second indication of a second set of TCI states for a second set of CORESETs.

[0008] In a fifth aspect, a terminal device is provided, the terminal device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform the method according to the first aspect of the present disclosure.

[0009] In a sixth aspect, a terminal device is provided, the terminal device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform the method according to the second aspect of the present disclosure.

[0010] In a seventh aspect, there is provided a network device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the network device to perform the method according to the third aspect of the present disclosure.

[0011] In an eighth aspect, there is provided a network device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the network device to perform the method according to the fourth aspect of the present disclosure.

[0012] In a ninth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the first, second, third, or fourth aspect of the present disclosure.

[0013] Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the accompanying drawings.

[0015] [Figure 1] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 illustrates a signaling flow for communication in accordance with some exemplary embodiments of the present disclosure. [Figure 3A] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 3B] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 4] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 5] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 6] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 7] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 8] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 9] FIG. 1 illustrates an example according to some embodiments of the present disclosure. [Figure 10] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0016] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0017] The principles of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are provided for illustrative purposes only to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from those described below.

[0018] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0019] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Things (IoE) device, machine-type communication (MTC) devices, and in-vehicle devices for V2X communications, where the "X" in V2X represents a pedestrian, vehicle, or infrastructure / network, or an image capture device such as a digital camera, a gaming device, a music storage and playback device, or an Internet appliance that enables wireless or wired Internet access and browsing. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Additionally, the term "network device" refers to a device capable of providing or hosting a cell or coverage area through which terminal devices can communicate. Examples of network devices include, but are not limited to, low power nodes such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a transmit / receive point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a femto node, and a pico node.

[0020] As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. The term "comprises" and variations thereof should be understood as open-ended terms meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." Terms such as "first," "second," etc. may refer to different or the same object. The following may include other explicit and implicit definitions.

[0021] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to illustrate that choices may be made from among many functional alternatives used, and that such choices are not necessarily better, smaller, higher, or otherwise more preferred than other choices.

[0022] As used herein, the term "circuitry" may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As yet another example, a circuit may be any portion of a hardware processor with software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or portion thereof, that requires software / firmware for operation, although the software may not be present if not necessary for operation. As used herein, the term "circuitry" also includes an implementation of a hardware circuit or one or more processors only, or a hardware circuit or portion of one or more processors and its / their accompanying software and / or firmware.

[0023] As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) available to network devices located at a particular geographic location. Although some embodiments of the present disclosure have been described with reference to multi-TRPs as examples, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in various ways different from those described below.

[0024] Generally speaking, for uplink (UL) transmissions, one TRP typically corresponds to one SRS resource set. As used herein, the term "single TRP for UL" means that a single SRS resource set is used to perform the associated transmission (e.g., PUSCH transmission), and the term "multiple TRP for UL" means that multiple SRS resource sets are used to perform the associated transmission (e.g., PUSCH transmission).

[0025] As mentioned above, there are enhancements for multi-beam operation that are primarily targeted at FR2 but are also applicable to FR1: a. Identify and specify features that facilitate more efficient (lower latency and overhead) DL / UL beam management for intra-cell and inter-cell scenarios to support higher UE speeds and / or more configured TCI states. i. Common beam for data and control transmission / reception for DL ​​and UL, especially for intra-band CA. ii. Unified TCI framework for DL ​​and UL beam indication. iii. Enhancements to the signaling mechanisms for the above features to improve latency and efficiency through increased use of dynamic control signaling (as opposed to RRC). iv. For inter-cell beam management, a UE can transmit or receive to only a single cell (i.e., the serving cell does not change when beam selection is complete). This includes L1-only measurement / reporting (i.e., no L3 impact) and beam indication associated with cells with any physical cell ID: beam indication is based on the Rel-17 unified TCI framework. The same beam measurement / reporting mechanism is reused for inter-cell mTRP. This work should only consider the intra-distributed unit (intra-DU) and intra-frequency cases.

[0026] As mentioned above, there are enhancements for multi-beam operation, primarily targeted at FR2 but also applicable to FR1: a. Identify and specify features that facilitate more efficient (lower latency and overhead) DL / UL beam management to support higher intra-cell and inter-cell mobility, especially L1 / L2, and / or more configured TCI states: i. Common beam for data and control transmission / reception for DL ​​and UL, especially intra-band CA; ii. Unified TCI framework for DL ​​and UL beam indication; iii. Enhancements to the signaling mechanisms for the above features to improve latency and efficiency through greater use of dynamic control signaling (as opposed to RRC).

[0027] It is proposed to support L1-based beam indication using at least a UE-specific (unicast) DCI to indicate combined or separate DL / UL beam indication from the active TCI state. Existing DCI formats 1_1 and 1_2 are reused for beam indication and support a mechanism for the UE to acknowledge successful decoding of the beam indication. The ACK / NACK of the PDSCH scheduled by the DCI carrying the beam indication may also be used as an ACK for the DCI.

[0028] It is also proposed to support activation of one or more TCI states via a Media Access Control (MAC) Control Element (CE) similar to Release 15 / 16, where in the case of at least a single activated TCI state, the activated TCI state applies.

[0029] For beam indication with Rel-17 integrated TCI, DCI format 1_1 / 1_2 without DL allocation is supported, and the acknowledgement / negative acknowledgement (ACK / NACK) mechanism is utilized similar to that of semi-persistent scheduling (SPS) PDSCH release with both Type 1 and Type 2 HARQ-ACK codebooks. Upon successful reception of the beam indication DCI, the UE reports an ACK.

[0030] In the case of a Type 1 HARQ-ACK codebook, the location for the ACK information in the HARQ-ACK codebook is determined based on the virtual PDSCH indicated by the time domain resource allocation (TDRA) field in the beam indication DCI, based on the time domain allocation list configured for the PDSCH. In the case of a Type 2 HARQ-ACK codebook, the location for the ACK information in the HARQ-ACK codebook is determined according to the same rules as for SPS release. The ACK is reported in the PUCCH k slots after the end of PDCCH reception, where k is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format, or if there is no PDSCH-to-HARQ_feedback timing indicator in the DCI, dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCI-Format1-2-r16 is provided.

[0031] When used for beam direction, the configured scheduling-radio network temporary identifier (CS-RNTI) is used to scramble the CRC for the DCI. The values ​​of the following DCI fields are set as follows: RV = all "1", MCS = all "1", NDI = 0, and set to all "0" for FDRA type 0, all "1" for FDRA type 1, or all "0" for dynamicSwitch (same as Table 10.2-4 of TS38.213).

[0032] The TCI field may be used to signal 1) combined DL / UL TCI status, 2) DL-only TCI status (in case of separate DL / UL TCIs), or 3) UL-only TCI status (in case of separate DL / UL TCIs).

[0033] Additionally, the following DCI fields are used in Rel-16: Identifier for DCI format, Carrier indicator, Bandwidth part indicator, Time domain resource assignment (TDRA), Downlink allocation index (if configured), Transmit power control (TPC) command for scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator (if present). The remaining unused DCI fields and codepoints are reserved for Release 17.

[0034] It is also proposed to support UE reporting whether TCI update via DCI format 1_1 / 1_2 is supported. For UEs that support TCI update via DCI format 1_1 / 1_2, they must support TCI update by using DCI 1_1 / 1_2 with DL allocation, and support for the above feature of TCI update via DCI format 1_1 / 1_2 without DL allocation is optional for UEs.

[0035] For beam direction based on Rel-17 DCI, in terms of the application time of beam direction, the first slot or first sub-slot is at least X ms or Y symbols after the last symbol of the combined or separate DL / UL beam direction acknowledgment.

[0036] In some embodiments, a slot includes 14 or 12 Orthogonal Frequency Division Multiplexing (OFDM) symbols. In some embodiments, a sub-slot includes at least one of {2, 4, 7} OFDM symbols.

[0037] According to TS 38.212 Section 7.3.1.2.2 Format 1_1, if the higher layer parameter tci-PresentInDCI is not enabled, the transmit configuration indication is a 0 bit, otherwise it is 3 bits as specified in Clause 5.1.5 of [6, TS38.214]. According to TS 38.212 Section 7.3.1.2.3 Format 1_2, if the higher layer parameter tci-PresentDCI-1-2 is not configured, the transmit configuration indication is a 0 bit, otherwise it is 1, 2, or 3 bits as determined by the higher layer parameter tci-PresentDCI-1-2 as specified in Clause 5.1.5 of [6, TS38.214].

[0038] The UE receives an activation command as described in 6.1.3.14 of [10, TS 38.321], which is used to map up to eight TCI states to codepoints of the DCI field "Transmission Configuration Indication" within one Component Carrier (CC) / DL Bandwidth Part (BWP) or within a set of CCs / DL BWPs, respectively. If a set of TCI state IDs is activated for a set of CCs / DL BWPs, where the available list of CCs is determined by the indicated CC in the activation command, the same set of TCI state IDs applies for all DL BWPs within the indicated CC.

[0039] If the UE supports two TCI states within a codepoint of the DCI field "Transmission Configuration Indication", the UE may receive an activation command as described in clause 6.1.3.24 of TS 38.321, which is used to map up to eight combinations of one or two TCI states to a codepoint of the DCI field "Transmission Configuration Indication". The UE is not expected to receive more than eight TCI states within the activation command.

[0040] If the DCI field "Transmission Configuration Indication" is present in DCI format 1_2 and the number of codepoints S in the DCI field "Transmission Configuration Indication" of DCI format 1_2 is less than the number of TCI codepoints activated by the activation command, only the first S activated codepoints are applied to DCI format 1_2, as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321]. For example, if the number of bits for the DCI field "Transmission Configuration Indication" of DCI format 1_2 or the number of bits for the upper layer parameter tci-PresentDCI-1-2 is 1 bit, S=2. For another example, if the number of bits for the DCI field "Transmission Configuration Indication" of DCI format 1_2 or the number of bits for the upper layer parameter tci-PresentDCI-1-2 is 2 bits, S=4. For another example, if the number of bits for the DCI field "Transmission Configuration Indication" of DCI format 1_2 or the number of bits for the upper layer parameter tci-PresentDCI-1-2 is 3 bits, S=8.

[0041] Furthermore, DCI format 1_1 / 1_2 with DL allocation and DCI format 1_1 / 1_2 without DL allocation may be used for dynamic beam direction. When beam direction is indicated by a DCI format with DL scheduling, the ACK / NACK of the PDSCH can be used to indicate ACK of the beam direction, and the indicated beam can be applied after timing.

[0042] 1 illustrates an exemplary communication network 100 in which embodiments of the present disclosure can be implemented. Network 100 includes a network device 110 and a terminal device 120 served by network device 110. Network 100 may provide one or more serving cells to serve terminal device 120.

[0043] The communication network 100 further includes a network device 110. In the communication network 100, the network device 110 and the terminal device 120 can communicate data and control information with each other. The number of devices shown in Figure 1 is for illustrative purposes only and does not imply any limitation.

[0044] In some scenarios, carrier aggregation (CA), in which two or more CCs are aggregated to support a wider bandwidth, may be supported in network 100. For example, in FIG. 1, network device 110 may provide multiple serving cells to terminal device 120, including one primary cell (Pcell) 101 corresponding to a primary CC and at least one secondary cell (Scell) 102 corresponding to at least one secondary CC. It should be understood that the number of network devices, terminal devices, and / or serving cells is for illustrative purposes only and does not imply any limitation to the present disclosure. Network 100 may include any appropriate number of network devices, terminal devices, and / or serving cells suitable for implementing embodiments of the present disclosure.

[0045] In some other scenarios, the terminal device 120 may establish connections with two different network devices (not shown in FIG. 1 ) and thus utilize the radio resources of the two network devices. These two network devices may be defined as a master network device and a secondary network device, respectively. The master network device may provide a group of serving cells also referred to as a “Master Cell Group (MCG).” The secondary network device may also provide a group of serving cells also referred to as a “Secondary Cell Group (SCG).” In the case of dual connectivity operation, the term “Special Cell (Spcell)” may refer to a Pcell of an MCG or a Primary Scell ​​(Pscell) of an SCG, depending on whether the terminal device 120 is associated with the MCG or SCG, respectively. In cases other than dual connectivity operation, the term “SpCell” may refer to a PCell.

[0046] In one embodiment, the terminal device 120 may be connected to a first network device and a second network device (not shown in FIG. 1). One of the first network device and the second network device may be in a master node, and the other may be in a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device may be an eNB, and the second RAT device may be a gNB. Information regarding the different RATs may be transmitted to the terminal device 120 from at least one of the first network device and the second network device. In one embodiment, the first information may be transmitted from the first network device to the terminal device 120, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device 120. In one embodiment, information regarding the terminal device configuration configured by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device set by the second network device may be transmitted to the terminal device directly from the second network device or via the first network device, and may be transmitted via any of Radio Resource Control (RRC) signaling, Media Access Control (MAC) control elements (CEs), or Downlink Control Information (DCIs).

[0047] 1, network device 110 can communicate data and control information to terminal device 120, and terminal device 120 can also communicate data and control information to network device 110. The link from network device 110 to terminal device 120 is referred to as the downlink (DL), and the link from terminal device 120 to network device 110 is referred to as the uplink (UL).

[0048] In some embodiments, for downlink transmission, network device 110 may transmit control information to terminal device 120 via a PDCCH and / or transmit data to terminal device 120 via a PDSCH. Furthermore, network device 110 may transmit one or more reference signals (RS) to terminal device 120. An RS transmitted from network device 110 to terminal device 120 may be referred to as a "DL RS." Examples of DL RSs may include, but are not limited to, a demodulation reference signal (DM-RS), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a phase tracking reference signal (PTRS), a fractional time and frequency tracking reference signal (TRS), etc.

[0049] In some embodiments, for uplink transmission, terminal device 120 may transmit control information to network device 110 via a PUCCH and / or transmit data to network device 110 via a PUSCH. Additionally, terminal device 120 may transmit one or more RSs to network device 110. RSs transmitted from terminal device 120 to network device 110 may be referred to as "UL RSs." Examples of UL RSs may include, but are not limited to, DM-RS, CSI-RS, SRS, PTRS, fractional time and frequency TRS, etc.

[0050] Communications in network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Furthermore, communications may be performed according to any generation of communication protocols now known or developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11, etc. Furthermore, communications may utilize any suitable wireless communication technology, including, but not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technology now known or developed in the future.

[0051] A network device 110 (e.g., a gNB) can include one or more TRPs or antenna panels. As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) available to a network device located at a particular geographic location. For example, a network device may be coupled to multiple TRPs in different geographic locations to achieve better coverage. The one or more TRPs can be included in the same serving cell or different serving cells.

[0052] It should be understood that a TRP may be a panel, and a panel may refer to an antenna array (having one or more antenna elements). Although several embodiments of the present disclosure have been described with reference to a multi-TRP as an example, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in various ways different from those described below.

[0053] As shown in FIG. 1 , for example, network device 110 may communicate with terminal device 120 via TRPs 130-1 and 130-2 (hereinafter collectively referred to as “TRP 130” or individually as “TRP 130”). For example, TRP 130-1 may be referred to as a first TRP, and TRP 130-2 may be referred to as a second TRP. As described above, network device 110 may provide a group of cells to serve terminal device 120. In some embodiments, the cell group may be divided into a first subset of cells associated with first TRP 130-1 and a second subset of cells associated with second TRP 130-2. For example, the first subset of cells and the second subset of cells may include one or more overlapping cells or may not overlap each other.

[0054] Embodiments of the present disclosure may be applied to any suitable scenario. For example, embodiments of the present disclosure may be implemented on a reduced-capability NR device. Alternatively, embodiments of the present disclosure may be implemented within one of NR multiple-input multiple-output (MIMO), NR sidelink enhancements, NR systems at frequencies higher than 52.6 GHz, enhanced NR operation up to 71 GHz, Narrowband Internet of Things (NB-IOT) / enhanced Machine Type Communications (eMTC) over Non-Terrestrial Networks (NTN), NTN, UE power saving enhancements, NR coverage enhancements, NB-IOT and LTE-MTC, integrated access and backhaul (IAB), NR multicast and broadcast services, or multi-radio dual connectivity enhancements.

[0055] It should be understood that the number of network devices, terminal devices, and / or TRPs is for illustrative purposes only and no limitation to the present disclosure is to be implied. Communications network 100 may include any suitable number of network devices, terminal devices, and / or TRPs suitable for implementing embodiments of the present disclosure.

[0056] In some embodiments, a TRP may be explicitly associated with an identity configured by a different higher layer. For example, an identity configured by a higher layer may be associated with a control resource set (CORESET), a group of CORESETs, a reference signal (RS), a set of RSs, a transmission configuration indication (TCI) state, or a group of TCI states used to distinguish transmissions between different TRPs and the terminal device 120. When the terminal device 120 receives two DCIs from two CORESETs associated with identities configured by different higher layers, the two DCIs may be transmitted or indicated from different TRPs. Furthermore, a TRP may be implicitly identified by dedicated configuration to a physical channel or signal. For example, a dedicated CORESET, RS, and TCI state associated with a TRP may be used to distinguish transmissions to the terminal device 120 from different TRPs. For example, when the terminal device 120 receives a DCI from a dedicated CORESET, the DCI is indicated from the associated TRP dedicated to the CORESET. In some embodiments, the RS may be at least one of a CSI-RS, an SRS, a positioning RS, an uplink DM-RS, a downlink DM-RS, an uplink PTRS, and a downlink PTRS.

[0057] 2 is a signaling diagram of communication between a network device and a terminal device according to some embodiments of the present disclosure. For illustrative purposes, process 200 will be described with reference to FIG. 1. As shown in FIG. 1, process 200 may involve network device 110 and terminal device 120.

[0058] In some embodiments, for example, as shown in FIG. 2 , network device 110 may configure / transmit one or more configurations 210 to terminal device 120. In some embodiments, for example, as shown in FIG. 2 , terminal device 120 may receive one or more configurations 210 from network device 110. In some embodiments, the one or more configurations 210 may include at least one of: configuring / indicating / activating a TCI state, configuring a physical cell identity (ID), configuring a CORESET, configuring a search space, configuring a PDCCH, configuring a PDSCH, configuring a PUSCH, configuring a PUCCH, configuring control information for data transmission / reception, configuring a reference signal (RS) transmission / reception, and configuring a repetition / transmission / reception scheme. In some embodiments, network device 110 may transmit a first PDCCH (e.g., 220 shown in FIG. 2 ) to terminal device 120. In some embodiments, terminal device 120 may receive the first PDCCH (e.g., 220 shown in FIG. 2 ) from network device 110. In some embodiments, network device 110 may transmit a second PDCCH (e.g., 230 shown in FIG. 2 ) to terminal device 120 based on a condition. In some embodiments, terminal device 120 may receive the second PDCCH (e.g., 230 shown in FIG. 2 ) from network device 110 based on a condition. In some embodiments, only a subset of the signaling may be present in process 200. For example, only 210 and 220 may be present in process 200. For another example, only 210 and 230 may be present in process 200.

[0059] In the following, the terms "transmission occasion", "reception occasion", "repetition", "transmission", "reception", "PDSCH transmission occasion", "PDSCH repetition", "PUSCH transmission occasion", "PUSCH repetition", "PUCCH occasion", "PUCCH repetition", "repetitive transmission", "repetitive reception", "PDSCH transmission", "PDSCH reception", "PUSCH transmission", "PUSCH reception", "PUCCH transmission", "PUCCH reception", "RS transmission", "RS reception", "communication", "scheduling", "transmission", and "reception" may be used interchangeably. The terms "TCI state", "set of QCL parameters", "QCL parameters", "QCL assumption", and "QCL configuration" may be used interchangeably. The terms "TCI field", "TCI state field", and "transmission configuration indication" may be used interchangeably. The terms "transmission occasion," "transmission," "repetition," "reception," "reception occasion," "monitoring occasion," "PDCCH monitoring occasion," "PDCCH transmission occasion," "PDCCH transmission," "PDCCH candidate," "PDCCH reception occasion," "PDCCH reception," "search space," "CORESET," "multiple chances," and "PDCCH repetition" may be used interchangeably. Hereinafter, the terms "PDCCH repetition," "repeated PDCCH," "repeated PDCCH signal," "PDCCH candidate configured for the same scheduling," "PDCCH," "PDCCH candidate," and "linked PDCCH candidate" may be used interchangeably. The terms "DCI" and "DCI format" may be used interchangeably. In some embodiments, embodiments of the present disclosure may be applied to PDSCH and PUSCH scheduling, and PDSCH scheduling will be described below as an example. For example, embodiments of the present disclosure may be applied to PUSCH by replacing "transmission" with "reception" and / or "reception" with "transmission." The terms "PDSCH" and "PUSCH" may be used interchangeably. The terms "transmit" and "receive" may be used interchangeably.

[0060] As specified in the 3GPP specification (TS 38.214), a UE can be configured with a list of up to M TCI state configurations in the higher layer parameter PDSCH-Config to decode PDSCH from a detected PDCCH with DCI targeted for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI state includes parameters for configuring a quasi-co-location relationship between one or two downlink reference signals and a DM-RS port of the PDSCH, a DM-RS port of the PDCCH, or a channel state information reference signal (CSI-RS) port of a CSI-RS resource. The quasi-co-location relationship is configured by the higher layer parameters qcl-Type1 of the first downlink (DL) RS and qcl-Type2 of the second DL RS (if configured). For two DL RSs, the QCL types must not be the same, whether they refer to the same DL RS or different DL RSs. The quasi-collocation type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can be one of the following values: - "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread} - "QCL-TypeB": {Doppler shift, Doppler spread} - "QCL-TypeC": {Doppler shift, average delay} - "QCL-TypeD": {Spatial reception parameters} The UE receives an activation command according to clause "TCI state activation / deactivation for UE-specific PDSCH MAC CE" (e.g., clause 6.1.3.14) of TS 38.321 or clause "Extended TCI state activation / deactivation for UE-specific PDSCH MAC CE" (e.g., clause 6.1.3) of TS 38.321, which is used to map up to eight TCI states to code points of the DCI field "Transmission Configuration Indication" within one CC / DL BWP or a set of CC / DL BWPs, respectively. If a set of TCI state IDs is activated for a set of CC / DL BWPs, where the available list of CCs is determined by the indicated CC in the activation command, the same set of TCI state IDs applies to all DL BWPs within the indicated CC.

[0061] If the UE supports two TCI states within a codepoint of the DCI field "Transmission Configuration Indication", the UE may receive an activation command as described in TS 38.321 clause "TCI state activation / deactivation for UE-specific PDSCH MAC CE" or clause "Extended TCI state activation / deactivation for UE-specific PDSCH MAC CE" (e.g., clause 6.1.3.14 or subclause 6.1.3), where the activation command is used to map up to eight combinations of one or two TCI states to a codepoint of the DCI field "Transmission Configuration Indication". The UE is not expected to receive more than eight TCI states within an activation command.

[0062] If the DCI field "Transmission Configuration Indication" is present in DCI format 1_2 and the number of code points S in the DCI field "Transmission Configuration Indication" of DCI format 1_2 is less than the number of TCI code points activated by the activation command, only the first S activated code points are applied for DCI format 1_2 as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321].

[0063] If the UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying an activation command, the indicated mapping between the TCI state and the codepoint of the DCI field "Transmission Configuration Indication" is

number

[0064] In some embodiments, if the UE is configured with the higher layer parameter tci-PresentInDCI set to "enabled", or if tci-PresentInDCI-ForFormat1_2 is configured for the CORESET scheduling the PDSCH, the UE assumes that a TCI field is present in the DCI of the PDCCH transmitted on the CORESET (e.g., DCI format 1_1 or DCI format 1_2). If tci-PresentInDCI or tci-PresentInDCI-ForFormat1_2 is not configured for the CORESET scheduling the PDSCH, or if the PDSCH is scheduled by DCI (e.g., DCI format 1_0), the UE assumes that a TCI field is not present in the DCI of the PDCCH transmitted on the CORESET (e.g., DCI format 1_1 or DCI format 1_2 or DCI format 1_0). If a PDSCH is scheduled with a DCI format in which the TCI field is not present and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL (if applicable) based on the reported UE capabilities [13, TS 38.306] for determining PDSCH antenna port quasi-co-location, the UE shall assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0065] If tci-PresentInDCI is set to "enabled" or tci-PresentInDCI-ForFormat1_2 is configured for the CORESET scheduling PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL (if applicable), after the UE receives the initial higher layer configuration of the TCI state and before receiving the activation command, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the SS / PBCH block determined in the initial access procedure for "QCL-TypeA" and, if applicable, for "QCL-TypeD". The value of timeDurationForQCL is based on the reported UE capabilities.

[0066] If the UE is configured with the higher layer parameter tci-PresentInDCI set to "enabled" for the CORESET scheduling the PDSCH, the UE shall assume that a TCI field is present in the DCI of the PDCCH transmitted on the CORESET (e.g., DCI format 1_1). If the UE is configured with the higher layer parameter tci-PresentInDCI-ForFormat1_2 for the CORESET scheduling the PDSCH, the UE shall assume that a TCI field with the DCI field size indicated by tci-PresentInDCI-ForFormat1_2 is present in the DCI of the PDCCH transmitted on the CORESET (e.g., DCI format 1_2). If a PDSCH is scheduled with a DCI format in which the TCI field is not present and the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationForQCL (if applicable) based on the reported UE capabilities [TS 38.306] for determining PDSCH antenna port quasi-co-location, the UE shall assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the serving cell's active BWP.

[0067] If the PDSCH is scheduled using a DCI format in which a TCI field is present and the TCI field in the DCI in the scheduling component carrier indicates an activated TCI state in the scheduling component carrier or DL ​​BWP, the UE determines the PDSCH antenna port quasi-co-location using the TCI state according to the value of the "Transmission Configuration Indication" field in the detected PDCCH with the DCI. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than the threshold timeDurationForQCL based on the reported UE capabilities [TS 38.306], the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS in the TCI state with respect to the QCL type parameter given by the indicated TCI state. If the UE is configured with a single-slot PDSCH, the indicated TCI state should be based on the activated TCI state in the slot with the scheduled PDSCH. If the UE is configured with a multi-slot PDSCH, the indicated TCI state should be based on the activated TCI state in the first slot or sub-slot with a scheduled PDSCH, and the UE should expect the activated TCI state to be the same across slots with scheduled PDSCHs.When a UE is configured with CORESET associated with a search space set for cross-carrier scheduling, and a PDCCH carrying a scheduling DCI and a PDSCH scheduled by the DCI are transmitted on the same carrier, the UE expects tci-PresentInDCI to be set to 'enabled' or tci-PresentInDCI-ForFormat1_2 to be configured for CORESET, and if one or more of the TCI states configured for the serving cells scheduled by the search space set include 'QCL-TypeD', the UE expects the time offset between reception of a detected PDCCH in the search space set and the corresponding PDSCH to be greater than or equal to a threshold timeDurationForQCL.

[0068] Regardless of the configuration of tci-PresentInDCI and tci-PresentInDCI-ForFormat1_2 in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state for the serving cell of the scheduled PDSCH includes qcl-Type set to "typeD";

[0069] - The UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS with respect to the QCL parameter used for the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space with the lowest controlResourceSetId in the last slot monitored by the UE for one or more CORESETs in the active BWP of the serving cell. In this case, the UE is expected to prioritize reception of the PDCCH associated with the CORESET if the qcl-Type set to "type D" of the PDSCH DM-RS is different from the qcl-Type of the PDCCH DM-RS that overlaps within at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are in different component carriers).

[0070] - if the UE is configured with enableDefaultTCIStatePerCoresetPoolIndex and the UE is configured with the higher layer parameter PDCCH-Config containing two different coresetPoolIndex values ​​in different ControlResourceSets;

[0071] The UE may assume that the DM-RS port of the PDSCH associated with the coresetPoolIndex value of the serving cell is quasi-co-located with the RS for the QCL parameter used for the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space with the lowest controlResourceSetId among the CORESETs configured to have the same coresetPoolIndex value as the PDCCH scheduling the PDSCH in the last slot monitored by the UE, the CORESETs being associated with the same coresetPoolIndex value as the PDCCH scheduling the PDSCH in the active BWP of the serving cell. In this case, if the "QCL-TypeD" of the PDSCH DM-RS overlaps within at least one symbol and differs from that of the PDCCH DM-RS associated with the same coresetPoolIndex, the UE is expected to prioritize reception of the PDCCH associated with that CORESET. This also applies in the case of intra-band CA (when the PDSCH and CORESET are in different component carriers).

[0072] - if the UE is configured with enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS port of the PDSCH of the serving cell or a PDSCH transmission occasion is quasi-co-located with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. If the UE is configured with the higher layer parameter repetitionScheme set to "tdmSchemeA" or with the higher layer parameter repetitionNumber, it determines the mapping of TCI states to PDSCH transmission occasions according to clause 5.1.2.1 based on the activated TCI states in the slot with the first PDSCH transmission occasion by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. In this case, if the "QCL-TypeD" in both TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states differs from that of the overlapping PDCCH DM-RS within at least one symbol, the UE is expected to prioritize reception of the PDCCH associated with the CORESET. This also applies in the case of intra-band CA (when the PDSCH and CORESET are in different component carriers).

[0073] - In any of the above cases, if none of the configured TCI states for the serving cell of the scheduled PDSCH is configured to have qcl-Type set to "typeD", the UE should derive other QCL assumptions from the indicated TCI state for the scheduled PDSCH, regardless of the time offset between reception of the DL DCI and the corresponding PDSCH.

[0074] If a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by the DCI is on another component carrier, and the UE is configured with enableDefaultBeam-ForCCS:

[0075] - timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If μ PDCCH <μ PDSCH If so, additional timing delay

number

[0076] - In both cases, if the offset between reception of the DL DCI and the corresponding PDSCH is smaller than the threshold timeDurationForQCL, and if the TCI field is not present in the DL DCI, the UE derives its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable to the PDSCH in the active BWP of the scheduled cell.

[0077] For periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE should expect the TCI-State to indicate one of the following quasi-co-location types:

[0078] - "type C" with SS / PBCH blocks and, if applicable, "type D" with the same SS / PBCH blocks, or

[0079] - "type C" with SS / PBCH blocks and, if applicable, "type D" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or Aperiodic CSI in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info

[0080] - For RS resources, the UE should expect the TCI-State to indicate qcl-Type set to 'typeA' with periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, if applicable, qcl-Type set to 'typeD' with the same periodic CSI-RS resources.

[0081] For periodic CSI-RS resources in an NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, the UE should expect the TCI-State to indicate one of the following quasi-co-location types:

[0082] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or

[0083] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with SS / PBCH blocks, or

[0084] - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0085] - If 'typeD' is not applicable, 'typeB' with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info.

[0086] For periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, the UE should expect the TCI-State to indicate one of the following quasi-co-location types:

[0087] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or

[0088] - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0089] - "typeC" with SS / PBCH blocks and, if applicable, "typeD" with the same SS / PBCH blocks.

[0090] For DM-RS of PDCCH, the UE should expect the TCI-State to indicate one of the following quasi-co-location types:

[0091] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or

[0092] - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0093] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, and "typeD" with the same CSI-RS resources, if applicable.

[0094] For DM-RS of PDSCH, the UE should expect the TCI-State to indicate one of the following quasi-co-location types:

[0095] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or

[0096] - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0097] - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, and "typeD" with the same CSI-RS resources, if applicable.

[0098] When a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by the DCI is on another component carrier, timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If μPDCCH<μPDSCH, an additional timing delay d is added to timeDurationForQCL, where d is defined as 8 symbols if the subcarrier spacing for the PDCCH is 15 kHz, or 8 symbols if the subcarrier spacing for the PDCCH is 30 kHz, or 14 symbols if the subcarrier spacing for the PDCCH is 60 kHz. For example, the symbol is a PDCCH symbol, or the symbol is based on the subcarrier spacing of the PDCCH (e.g., as specified in Table 5.2.1.5.1a-1 of TS 38.214). In both cases, if tci-PresentInDCI is set to "enabled" and the offset between reception of the DL DCI and the corresponding PDSCH is smaller than the threshold timeDurationForQCL, and if tci-PresentInDCI is not configured, the UE derives its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable to the PDSCH in the active BWP of the scheduled cell.

[0099] As specified in the 3GPP specification (TS 38.214), if a UE is configured with the higher layer parameter RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", or "TDMSchemeA", and if the UE indicates two TCI states in a codepoint of the DCI field "Transmission Configuration Indication" and indicates DM-RS ports in one Code Domain Multiplexing (CDM) group in the DCI field "Antenna Port(s)", then if two TCI states are indicated in the DCI and the UE is configured to "FDMSchemeA", the UE should receive a single PDSCH transmission occasion for the TB, where each TCI state is associated with a non-overlapping frequency domain resource allocation, as described in the clause "Physical resource block (PRB) bundling" in TS 38.214 (e.g., clause 5.1.2.3). If two TCI states are indicated in the DCI and the UE is configured for "FDMSchemeB", the UE shall receive two PDSCH transmission occasions of the same TB, each associated with a PDSCH transmission occasion having a non-overlapping frequency-domain resource allocation with respect to other PDSCH transmission occasions, as described in clause "Physical Resource Block (PRB) Bundling" (e.g., clause 5.1.2.3) in TS 38.214. If two TCI states are indicated in the DCI and the UE is configured for "TDMSchemeA", the UE shall receive two PDSCH transmission occasions of the same TB, each associated with a PDSCH transmission occasion having a non-overlapping time-domain resource allocation with respect to other PDSCH transmission occasions, as described in clause "Resource Allocation in the Time Domain" (e.g., clause 5.1.2.1) in TS 38.214, and all two PDSCH transmission occasions shall be received within a given slot.

[0100] If the UE is configured by the higher layer parameter PDSCH-config indicating at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, the UE may expect one or two TCI states to be indicated in the codepoints of the DCI field "Transmission Configuration Indication" and DM-RS ports in one CDM group to be indicated in the DCI field "Antenna Port(s)", together with the DCI field "Time domain resource assignment" indicating an entry containing RepNumR16 in PDSCH-TimeDomainResourceAllocation. If two TCI states are indicated in the "Transmission Configuration Indication" field in the DCI, the UE may expect to receive multiple slot-level PDSCH transmission occasions of the same TB, with two TCI states used across multiple PDSCH transmission occasions, as described in "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1). If one TCI state is indicated in the "Transmission Configuration Indication" field in the DCI, the UE may expect to receive multiple slot-level PDSCH transmission occasions of the same TB, where one TCI state is used across multiple PDSCH transmission occasions, as described in "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1).

[0101] If the UE is not indicated a DCI where the DCI field "Time domain resource assignment" indicates an entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, and two TCI states are indicated in the codepoint of the DCI field "Transmission Configuration Indication", and DM-RS ports in two CDM groups are indicated in the DCI field "Antenna Port(s)", the UE may expect to receive a single PDSCH where the association between DM-RS ports and TCI states is defined in clause "DM-RS reception procedure" in TS 38.214 (e.g., clause 5.1.6.2).

[0102] If the UE is not indicated a DCI where the DCI field "Time domain resource assignment" indicates an entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation and one TCI state is indicated in the codepoint of the DCI field "Transmission Configuration Indication", the UE procedure for receiving the PDSCH upon detection of a PDCCH shall follow clause "UE procedure for receiving the physical downlink shared channel" in TS 38.214 (e.g. clause 5.1).

[0103] In the following, the terms "FDMSchemeA" and "Scheme2a" may be used interchangeably. The terms "FDMSchemeB" and "Scheme2b" may be used interchangeably. The terms "TDMSchemeA" and "Scheme3" may be used interchangeably. The terms "RepNumR16" and "Scheme4" may be used interchangeably.

[0104] As specified in the 3GPP specification (TS 38.214), when a UE is configured with the higher layer parameter RepSchemeEnabler set to "TDMSchemeA" and the DM-RS ports in one CDM group indicated in the DCI field "Antenna Ports", the number of PDSCH transmission occasions is derived from the number of TCI states indicated by the DCI field "Transmission Configuration Indication" of the scheduling DCI. If two TCI states are indicated by the DCI field "Transmission Configuration Indication", the UE is expected to receive two PDSCH transmission occasions, where the first TCI state applies to the first PDSCH transmission occasion and the resource allocation in the time domain for the first PDSCH transmission occasion follows the clause "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1). The second TCI state applies to the second PDSCH transmission occasion, which should have the same number of symbols as the first PDSCH transmission occasion.

number

number

number

number

number

[0105] As specified in the 3GPP specification (TS 38.214), if the UE is configured with the higher layer parameter PDSCH-config indicating at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, and two TCI states are indicated by the DCI field "Transmission Configuration Indication" and the DCI field "Time domain resource assignment" indicating an entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation and DM-RS ports in one CDM group in the DCI field "Antenna Port(s)", then the same SLIV (Start and length indicator value) applies to all PDSCH transmission occasions, the first TCI state applies to the first PDSCH transmission occasion, and the resource allocation in the time domain for the first PDSCH transmission occasion is ...". 38.214, clause "Resource Allocation in the Time Domain" (e.g., clause 5.1.2.1). If the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation is equal to 2, the second TCI state applies to the second PDSCH transmission occasion. If the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation is greater than 2, the UE may be further configured to enable CycMapping or SeqMapping in RepTCIMapping. If CycMapping is enabled, the first and second TCI states apply to the first and second PDSCH transmission occasions, respectively, and the same TCI mapping pattern continues to apply to the remaining PDSCH transmission occasions.If SeqMapping is enabled, the first TCI state applies to the first and second PDSCH transmissions, the second TCI state applies to the third and fourth PDSCH transmissions, and the same TCI mapping pattern continues to apply to the remaining PDSCH transmission occasions. The UE may expect each PDSCH transmission occasion to be limited to two transmission layers. For all PDSCH transmission occasions associated with the first TCI state, the applied redundancy version is derived according to Table 5.1.2.1-2 [TS 38.214], where:

number

[0106] For a UE configured with the higher layer parameter RepSchemeEnabler set to "FDMSchemeA" or "FDMSchemeB" as specified in the 3GPP specification (TS 38.214), if the UE receives two TCI states indicated in the codepoints of the DCI field "Transmission Configuration Indication" and one DM-RS port in one Code Domain Multiplexing (CDM) group indicated in the DCI field "Antenna Port(s)",

number

number

number

number

[0107] For a UE configured with the higher layer parameter RepSchemeEnabler set to "FDMSchemeB", and if the UE has two TCI states indicated in the DCI field "Transmission Configuration Indication" codepoint and DM-RS ports in one CDM group indicated in the DCI field "Antenna Port(s)", each PDSCH transmission shall follow clause "Physical Downlink Shared Channel" of [TS 38.211] (e.g. clause 7.3.1), whose mapping to resource elements is determined by the allocated PRB for the corresponding TCI state of the PDSCH transmission occasion, and the UE shall expect only a maximum of two code blocks for each PDSCH transmission occasion if a single transmission layer is scheduled, and only a single code block for each PDSCH transmission occasion if two transmission layers are scheduled. For the two PDSCH transmission occasions, the applied redundancy version is derived according to Table 5.1.2.1-2 of [TS 38.214], where:

number

[0108] As specified in the 3GPP specification (TS 38.213), for CORESETs other than the CORESET with index 0, - if the UE is not provided with a TCI state configuration via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for this CORESET, or is provided with the initial configuration of two or more TCI states via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for this CORESET but the UE has not received a MAC CE activation command for one of the TCI states, the UE shall assume that the DM-RS antenna port associated with PDCCH reception is quasi-co-located with the SS / PBCH block identified by the UE during the initial access procedure; - If the UE has been provided with the configuration of two or more TCI states via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for this CORESET as part of the Reconfiguration with sync procedure, but the UE has not received a MAC CE activation command for one of the TCI states, the UE shall assume that the DM-RS antenna port associated with PDCCH reception is quasi-co-located with the SS / PBCH block or CSI-RS resource identified by the UE during the random access procedure initiated by the Reconfiguration with sync procedure.

[0109] In some embodiments, for a CORESET with index 0, the UE determines that the DM-RS antenna ports for PDCCH reception within this CORESET are: - one or more DL RSs configured by the TCI state indicated by the MAC CE Activate Command (if any) for the CORESET, or - SS / PBCH blocks identified by the UE during the most recent random access procedure that was not initiated by a PDCCH order triggering a contention-free random access procedure, if a MAC CE Activate Command indicating the TCI state for CORESET has not been received after the most recent random access procedure. Assume that the pseudo-collocations are:

[0110] In some embodiments, for a CORESET other than the CORESET with index 0, if a single TCI state for the CORESET is provided to the UE, or if the UE receives a MAC CE activation command for one of the provided TCI states for the CORESET, the UE assumes that the DM-RS antenna port associated with PDCCH reception in this CORESET is quasi-co-located with one or more DL-RSs configured by the TCI state. For the CORESET with index 0, the UE expects the CSI-RS configured with qcl-Type set to "typeD" to be provided by the SS / PBCH block in the TCI state indicated by the MAC CE activation command for the CORESET, and if the UE receives a MAC CE activation command for one of the TCI states, the UE shall

number

[0111] In some embodiments, when a UE is configured for single cell operation or operation with carrier aggregation within the same frequency band and monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs configured to have the same or different qcl-Type set to the "typeD" property on active DL BWPs of one or more cells, the UE monitors PDCCHs only in one CORESET and not in any other CORESETs from the multiple CORESETs configured to have the qcl-Type set to the same "typeD" property as the CORESET on active DL BWPs of cells from the one or more cells. - the CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index that contains the CSS (if any), otherwise it corresponds to the USS set with the lowest index in the cell with the lowest index; - the lowest USS set index is determined over all USS sets having at least one PDCCH candidate within overlapping PDCCH monitoring occasions; - For the purposes of determining CORESET, SS / PBCH blocks are considered to have different QCL "Type D" properties than CSI-RS - to determine the CORESET, it is assumed that a first CSI-RS associated with an SS / PBCH block in a first cell and a second CSI-RS associated with the same SS / PBCH block in a second cell have the same QCL "type D" property; - allocating non-overlapping CCEs and PDCCH candidates for PDCCH monitoring according to all search space sets associated with the plurality of CORESETs on an active DL BWP of the one or more cells; - The number of active TCI states is determined from the plurality of CORESETs.

[0112] In some embodiments, if a UE is configured for single cell operation or operation with carrier aggregation within the same frequency band and monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs that do not have any TCI state configured to have qcl-Type set to "typeD", the UE needs to monitor PDCCH candidates in overlapping PDCCH monitoring occasions for search space sets associated with different CORESETs.

[0113] In some embodiments, there is an application timing for the beam indication or TCI status indication. In some embodiments, the application timing may be the first slot or first subslot that is at least X ms or Y symbols after the last symbol of the acknowledgement of the combined or separate DL / UL beam indication. For example, Y may be an integer, where 1≦Y≦336. In some embodiments, a slot may include 12 or 14 symbols. In some embodiments, a subslot may include S symbols, where S is an integer, where 1≦S≦14. For example, S may be at least one of {2, 4, 7}. In some embodiments, the beam indication is indicated in a DCI in a PDCCH. For example, the DCI in a PDCCH may schedule a PDSCH or may not schedule a PDSCH. In some embodiments, the gap between the last symbol of the DCI and the first slot or first subslot should meet the capabilities of the terminal device. In some embodiments, the acknowledgement of the combined or separate DL / UL beam indication may be an acknowledgement of the PDSCH scheduled by the DCI. For example, when the DCI schedules a PDSCH. In some embodiments, the acknowledgement of the combined or separate DL / UL beam indication may be an acknowledgement of the DCI, for example, when the DCI does not schedule a PDSCH.

[0114] In some embodiments, the terminal device may receive or detect a DCI (e.g., represented as “DCI_t”) in a PDCCH, the DCI indicating a combined DL / UL TCI state or a separate DL / UL TCI state or a DL TCI state or a UL TCI state or a pair of DL / UL TCI states. In some embodiments, the second time threshold H2 may indicate a predetermined / configured period after the first or last symbol of the PDCCH or the first or last symbol of the indication acknowledgment. In some embodiments, the indicated combined DL / UL TCI state or a separate DL / UL TCI state or a DL TCI state or a UL TCI state or a pair of DL / UL TCI states may be applied to the PDSCH and / or CORESET and / or PUSCH and / or PUCCH and / or uplink RS and / or downlink RS after the application timing or second time threshold H2. For example, if a combined DL / UL TCI state is indicated in a DCI, the combined DL / UL TCI state may be applied to the PDSCH and / or CORESET and / or PUSCH and / or PUCCH and / or uplink RS and / or downlink RS after the application timing or the second time threshold H2. For another example, if a DL TCI state is indicated in a DCI, the DL TCI state may be applied to the PDSCH and / or CORESET and / or downlink RS after the application timing or the second time threshold H2. For another example, if a UL TCI state is indicated in a DCI, the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing or the second time threshold H2. For another example, if a pair of DL / UL TCI states is indicated in the DCI, the DL TCI state may be applied to the PDSCH and / or CORESET and / or downlink RS after the application timing or the second time threshold H2, and the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing or the second time threshold H2.

[0115] In some embodiments, terminal device 120 may receive an indication of a downlink TCI state (or set of beams or QCL parameters) in which a source reference signal provides QCL information for reception on at least a PDSCH and all CORESETs in a component carrier (CC). For example, the PDSCH may be dedicated or UE-specific.

[0116] In some embodiments, terminal device 120 may receive an indication of an uplink TCI state (or beam or spatial relationship), where a source reference signal in the TCI state provides a reference for determining an uplink transmit spatial filter for the PUSCH and all PUCCH resources in the CC based on at least a dynamic grant or a configured grant, e.g., the PUCCH is dedicated or UE-specific.

[0117] In some embodiments, the terminal device 120 may receive an indication indicating a combined TCI state (or set of beams or QCL parameters), where the TCI state refers to a common source reference signal used to determine at least both the downlink QCL information and the uplink transmit spatial filter.

[0118] In some embodiments, terminal device 120 may receive an indication indicating a downlink TCI state (or beam or set of QCL parameters) and an uplink TCI state (or beam or spatial relationship), where a source reference signal in the DL TCI state provides QCL information for reception on at least a PDSCH and all CORESETs in a component carrier (CC), and the source reference signal in the TCI state provides a reference for determining an uplink transmit spatial filter for at least a PUSCH based on a dynamic grant or a configured grant and all PUCCH resources in the CC. For example, the PUCCH may be dedicated or UE-specific. For another example, the PDSCH may be dedicated or UE-specific.

[0119] In some embodiments, terminal device 120 may be configured to have two or more (e.g., denoted as M, where M is a positive integer, e.g., M may be 2, 3, or 4) downlink TCI states, and / or terminal device 120 may receive an indication indicating one of the M TCI states, where a source reference signal within the one of the M TCI states or within the indicated one TCI state provides QCL information for reception on at least a subset of the PDSCH and / or CORESET within the CC. For example, the PDSCH may be dedicated or UE-specific.

[0120] In some embodiments, terminal device 120 may be configured to have two or more (e.g., represented as N, where N is a positive integer, e.g., N may be 2, 3, or 4) uplink TCI states, and / or terminal device 120 may receive an indication indicating one of the N TCI states, where a source reference signal in the one of the N TCI states or in the indicated one TCI state provides a reference for determining an uplink transmit spatial filter for at least a subset of PUSCH and / or PUCCH resources in a CC based on a dynamic grant or a configured grant. For example, the PUCCH may be dedicated or UE-specific.

[0121] In some embodiments, the terminal device 120 may be configured to have two or more (e.g., represented as M, where M is a positive integer, e.g., M may be 2, 3, or 4) combined DL / UL TCI states and / or may receive an indication indicating one out of the M combined TCI states, where each TCI state or the indicated one TCI state among the M TCI states references at least a common source reference signal used to determine both the downlink QCL information and the uplink transmit spatial filter.

[0122] In some embodiments, terminal device 120 may be configured to have two or more (e.g., denoted as M, where M is a positive integer, e.g., M may be 2, 3, or 4) downlink TCI states, and terminal device 120 may be configured to have two or more (e.g., denoted as N, where N is a positive integer, e.g., N may be 2, 3, or 4) uplink TCI states, and / or terminal device 120 may receive an indication indicating one out of M downlink TCI states and one out of N uplink TCI states, where each DL TCI state within the M DL TCI states or the indicated one DL TCI state provides QCL information for reception on at least a subset of PDSCH and / or CORESET within a component carrier (CC), and The source reference signal in the TCI state provides a reference for determining an uplink transmit spatial filter for a subset of PUCCH resources in the CC and / or PUSCH based on at least dynamic grants or configured grants. For example, the PUCCH may be dedicated or UE-specific. For another example, the PDSCH may be dedicated or UE-specific.

[0123] In the following, DCI_t is used to describe a DCI for a combined DL / UL TCI status indication or for a separate DL / UL TCI status indication. In the following, the terms "DCI", "PDCCH", "DCI_t", "DCI for combined DL / UL TCI status indication", "DCI for separate DL / UL TCI status indication", "DCI for DL ​​TCI status indication", "DCI for UL TCI status indication", "PDCCH for combined DL / UL TCI status indication", "PDCCH for separate DL / UL TCI status indication", "PDCCH for DL ​​TCI status indication", "PDCCH for UL TCI status indication", ... "DCI for TCI status indication" and "PDCCH for TCI status indication" may be used interchangeably.

[0124] In some embodiments, the DCI may be used to indicate the TCI status for a combined DL / UL TCI status indication or for separate DL / UL TCI status indications. The DCI may also schedule a PDSCH (e.g., DCI format 1_1 and format 1_2). In some embodiments, the HARQ of the PDSCH scheduled by the DCI may be used as an ACK for the DCI. For example, the DCI may be DCI_t.

[0125] In some embodiments, a DCI may be used to indicate the TCI status for a combined DL / UL TCI status indication or for separate DL / UL TCI status indications. Also, the DCI may not schedule a PDSCH (e.g., DCI format 1_1 and format 1_2). In some embodiments, HARQ of the DCI may be introduced to indicate whether the DCI or TCI status indication was successful. For example, the DCI may be DCI_t.

[0126] In some embodiments, if the decoding result of DCI_t or the decoding result of the PDSCH scheduled by DCI_t is ACK, the indicated TCI state may be applied to all or a subset of the PDSCH and / or CORESET after a certain application timing.

[0127] In some embodiments, a DCI (e.g., DCI_t) may be used to indicate one or more TCI states. For example, the one or more TCI states may be for a combined DL / UL TCI state indication or separate DL / UL TCI state indications. The DCI may also not schedule a PDSCH (e.g., DCI Format 1_1 and Format 1_2). In some embodiments, upon successful reception / decoding of a DCI, terminal device 120 may report an ACK. In some embodiments, upon unsuccessful reception / decoding of a DCI, terminal device 120 may report a NACK. For example, the ACK and / or NACK may be reported in a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). In some embodiments, terminal device 120 may be configured with one type of HARQ codebook. For example, the type may be at least one of Type 1 (e.g., semi-static), Type 2 (e.g., dynamic), and Type 3 (one-time feedback). For example, the type may be configured via at least one of RRC, MAC CE, and DCI. In some embodiments, the DCI is received / detected in the PDCCH.

[0128] In some embodiments, terminal device 120 may be configured / indicated to have a first TCI state for reception of all or a subset of the PDSCH and / or CORESET. Terminal device 120 may also receive or detect a first PDCCH using the first TCI state, where the PDCCH is within the first CORESET. In some embodiments, terminal device 120 may be indicated with a second TCI state in DCI received or detected in the first PDCCH. In some embodiments, the DCI in the PDCCH may or may not schedule the first PDSCH or the first PUSCH. In some embodiments, terminal device 120 may report decoding results or HARQ-ACK information for at least one of the DCI, PDCCH, or first PDSCH to network device 110. For example, the decoding results or HARQ-ACK information may be transmitted / reported in the PUCCH or the second PUSCH. In some embodiments, after the application timing or after the second time threshold H2, terminal device 120 may receive all or a subset of the PDSCH and / or CORESET using the second TCI state. For example, terminal device 120 may receive another PDCCH using the second TCI state, where the other PDCCH is in the second CORESET. For another example, terminal device 120 may receive another PDCCH using the second TCI state, where the other PDCCH is in the first CORESET.

[0129] In some embodiments, terminal device 120 may receive an indication of a first TCI state, where one or two RSs in the first TCI state may be associated with a first physical cell identity (ID). In some embodiments, terminal device 120 may monitor or receive a first PDCCH within a first monitoring occasion for a first search space and / or an associated scheduling or PDSCH scheduled by a first PDCCH based on a second TCI state or a quasi-co-location (QCL) assumption, where the one or two RSs in the second TCI state and / or the QCL assumption may be associated with a second physical cell ID. In some embodiments, terminal device 120 may monitor or receive a second PDCCH within a second monitoring occasion for a second search space and / or an associated scheduling scheduled by a second PDCCH based on a condition.

[0130] In some embodiments, the scheduling may be for at least one of PDSCH, PUSCH, PUCCH, HARQ feedback, CSI-RS, SRS, downlink DM-RS, uplink DM-RS, downlink PTRS, uplink PTRS and TRS.

[0131] In some embodiments, there may be a first time interval, which may be at least one of: a time interval between a first timing / location and a second timing / location; a time interval from a first timing / location to a second timing / location; a time interval between a first number of symbols for a first PDCCH and a second number of symbols for an associated PDSCH and / or scheduling scheduled by the first PDCCH; and a time interval between a first slot / subslot for a first PDCCH and a second slot / subslot for an associated PDSCH and / or scheduling scheduled by the first PDCCH. For example, the first PDCCH may be within the first slot / subslot. For another example, the associated PDSCH and / or scheduling scheduled by the first PDCCH may be within the second slot / subslot. In some embodiments, the first timing / position may be at least one of: a first symbol / starting symbol of the first PDCCH, a first symbol / starting symbol of the first slot / subslot for the first PDCCH, a first symbol / starting symbol of a span for first PDCCH monitoring, and a first symbol / starting symbol of a first monitoring occasion for the first PDCCH. In some embodiments, the second timing / position may be at least one of: a last symbol / end symbol of an associated PDSCH and / or scheduling scheduled by the first PDCCH, a last symbol / end symbol of an associated PDSCH and / or scheduling scheduled by the first PDCCH, a last symbol / end symbol of a second slot / subslot for scheduling, a last symbol / end symbol of HARQ feedback corresponding to the first PDCCH and / or associated PDSCH scheduled by the first PDCCH, and a last / end symbol / slot / subslot that overlaps with the threshold or the second time threshold H2. For example, the threshold or the second time threshold H2 may start from the last / ending symbol of the first PDCCH.

[0132] For example, as shown in FIG. 3A , terminal device 120 may receive a first PDCCH (e.g., PDCCH 310) within a first search space from network device 110. Terminal device 120 may also receive a PDSCH (e.g., PDSCH 320) scheduled by PDCCH 310. For example, terminal device 110-120 may transmit HARQ feedback (e.g., HARQ 330) to network device 110. For example, timing 340 may be the first symbol of PDCCH 310. For another example, timing 340 may be the start symbol or first symbol of a monitoring occasion for PDCCH 310. For example, timing 350 may be the last symbol of PDCCH 310. For another example, timing 350 may be the end symbol or last symbol of a monitoring occasion for PDCCH 310. For example, timing 360 may be the end symbol or last symbol of PDSCH 320. For example, timing 370 may be the end or last symbol of HARQ 330. For example, HARQ 330 may be transmitted within a PUCCH resource or a PUSCH resource. In some embodiments, the first time interval may be from timing 340 to timing 350. In some embodiments, the first time interval may be from timing 340 to timing 360. In some embodiments, the first time interval may be from timing 340 to timing 370.

[0133] In some embodiments, there may be a second time interval, which may be at least one of: a time interval between a third timing / location and a fourth timing / location; a time interval from the third timing / location to the fourth timing / location; a time interval between a third number of symbols for the second PDCCH and a fourth number of symbols for an associated PDSCH and / or scheduling scheduled by the second PDCCH; and a time interval between a third slot / subslot for the second PDCCH and a fourth slot / subslot for an associated PDSCH and / or scheduling scheduled by the second PDCCH. For example, the second PDCCH may be in the third slot / subslot. For another example, the associated PDSCH and / or scheduling scheduled by the second PDCCH may be in the fourth slot / subslot. In some embodiments, the third timing / position may be at least one of the first symbol / starting symbol of the second PDCCH, the first symbol / starting symbol of the third slot / subslot for the second PDCCH, the first symbol / starting symbol of the span for second PDCCH monitoring, and the first symbol / starting symbol of the second monitoring occasion for the second PDCCH. In some embodiments, the fourth timing / position may be at least one of the last symbol / end symbol of the associated PDSCH and / or scheduling scheduled by the second PDCCH, the last symbol / end symbol of the fourth slot / subslot for the associated PDSCH and / or scheduling scheduled by the second PDCCH, and the last / end symbol / slot / subslot that overlaps with the threshold or second time threshold H2. For example, the threshold or second time threshold H2 may start from the last / end symbol of the second PDCCH.

[0134] For example, as shown in FIG. 3B , terminal device 120 may receive a second PDCCH (e.g., PDCCH 311) within a second search space from network device 110. Terminal device 120 may also receive a PDSCH (e.g., PDSCH 321) scheduled by PDCCH 311. For example, terminal device 110-120 may transmit HARQ feedback (e.g., HARQ 331) to network device 110. For example, timing 341 may be the first symbol of PDCCH 311. For another example, timing 341 may be the start symbol or first symbol of a monitoring occasion for PDCCH 311. For example, timing 351 may be the last symbol of PDCCH 311. For another example, timing 351 may be the end symbol or last symbol of a monitoring occasion for PDCCH 311. For example, timing 361 may be the end symbol or last symbol of PDSCH 321. For example, timing 371 may be the end symbol or last symbol of HARQ 331. For example, HARQ 331 may be transmitted within a PUCCH resource or a PUSCH resource. In some embodiments, the second time interval may be from timing 341 to timing 351. In some embodiments, the second time interval may be from timing 341 to timing 361. In some embodiments, the second time interval may be from timing 341 to timing 371.

[0135] In some embodiments, the condition may be at least one of a first condition and a second condition. In some embodiments, the first condition may be at least one of: the first time interval may overlap with the second time interval in the time domain; any one symbol of the first time interval may overlap with any one symbol of the second time interval in the time domain; the second monitoring occasion may be within the same time interval as the first monitoring occasion; one or more symbols of the second monitoring occasion may overlap with one or more symbols of the first monitoring occasion in the time domain; the second monitoring occasion may fully or partially overlap with the first monitoring occasion in the time domain; any symbol of the second monitoring occasion overlaps with the first time interval in the time domain; any symbol of the associated PDSCH and / or fourth number of symbols for scheduling scheduled by the second PDCCH overlaps with the first time interval in the time domain; any symbol of the second monitoring occasion overlaps with any symbol of the first monitoring occasion in the time domain.

[0136] In some embodiments, the second condition may be: the first time interval may not overlap with the second time interval in the time domain; any symbol of the first time interval may not overlap with any symbol of the second time interval in the time domain; any symbol of the first time interval may not overlap with any symbol of the second time interval in the time domain; the second monitoring occasion may be in a different time interval than the first monitoring occasion; any symbol of the second monitoring occasion may not overlap with any symbol of the first monitoring occasion in the time domain; any symbol of the second monitoring occasion does not overlap with any symbol of the first monitoring occasion in the time domain; The second monitoring occasion may be at least one of the following: none of the symbols of the monitoring occasion overlaps with the first time interval in the time domain; none of the symbols of the associated PDSCH scheduled by the second PDCCH and / or the fourth number of symbols for scheduling overlaps with the first time interval in the time domain; none of the symbols of the second monitoring occasion overlaps with the first time interval in the time domain; none of the symbols of the associated PDSCH scheduled by the second PDCCH and / or the fourth number of symbols for scheduling overlaps with the first time interval in the time domain; the second monitoring occasion may not overlap with the first monitoring occasion in the time domain.

[0137] In some embodiments, the terminal device 120 may monitor or receive the second PDCCH and / or associated PDSCH and / or scheduling scheduled by the second PDCCH based on the first TCI state after the applied timing based on the second condition.

[0138] In some embodiments, terminal device 120 may monitor or receive the second PDCCH and / or associated PDSCH and / or scheduling scheduled by the second PDCCH based on the second TCI state based on the first condition.

[0139] In some embodiments, if the second condition is met and the TCI state or QCL assumption for the second PDCCH and / or the second search space and / or the second CORESET is different from the first TCI state, the terminal device 120 may not monitor or receive the second PDCCH and / or the associated PDSCH and / or schedule scheduled by the second PDCCH.

[0140] In some embodiments, if the second condition is met and the properties of the qcl_type having type D configured for the second PDCCH and / or the second search space and / or the second CORESET are different from the properties of the qcl_type having type D configured for the first TCI state or for the first PDCCH and / or the first search space and / or the first CORESET, the terminal device 120 may not monitor or receive the second PDCCH and / or the associated PDSCH and / or schedule scheduled by the second PDCCH.

[0141] In some embodiments, based on the condition that the second monitoring occasion and / or the associated PDSCH and / or scheduling does not overlap with the first time interval in the time domain, the terminal device 120 may monitor or receive the second PDCCH and / or the associated PDSCH and / or scheduling scheduled by the second PDCCH based on the first TCI state after the applied timing.

[0142] In some embodiments, based on a condition that the second monitoring occasion and / or the associated PDSCH and / or scheduling symbol is within a time interval different from the first monitoring occasion or the first time interval, terminal device 120 may monitor or receive the second PDCCH and / or the associated PDSCH and / or scheduling symbol scheduled by the PDCCH based on the first TCI state after the applied timing. For example, the time interval may be at least one of a slot and a span. For example, a span may be multiple consecutive symbols within a slot. For another example, a span may be multiple consecutive slots.

[0143] In some embodiments, based on the condition that the second monitoring occasion and / or the associated PDSCH and / or scheduling overlaps with the first time interval in the time domain, the terminal device 120 may monitor or receive the second PDCCH and / or the associated PDSCH and / or scheduling scheduled by the second PDCCH based on the second TCI state or based on the QCL assumption.

[0144] In some embodiments, terminal device 120 may monitor or receive the second PDCCH and / or associated PDSCH and / or scheduling scheduled by the second PDCCH based on a condition that the second monitoring occasion and / or associated PDSCH and / or scheduling is within the same time interval as the first monitoring occasion or first time interval, based on a second TCI state or based on a QCL assumption. For example, the time interval may be at least one of a slot and a span. For example, a span may be multiple consecutive symbols within a slot. For another example, a span may be multiple consecutive slots.

[0145] In some embodiments, based on the condition that the symbols for the second monitoring occasion and / or the associated PDSCH and / or scheduling do not overlap with the first monitoring occasion or the first time interval in the time domain, the terminal device 120 may monitor or receive the second PDCCH and / or the associated PDSCH and / or scheduling scheduled by the second PDCCH based on the first TCI state after the applied timing.

[0146] In some embodiments, based on the condition that the symbols for the second monitoring occasion and / or the associated PDSCH and / or scheduling overlap with the first monitoring occasion or the first time interval in the time domain, the terminal device 120 may monitor or receive the second PDCCH and / or the associated PDSCH and / or scheduling scheduled by the second PDCCH based on the second TCI state or based on QCL assumptions.

[0147] In some embodiments, if the symbols for the second monitoring occasion and / or the associated PDSCH and / or scheduling overlap with the first monitoring occasion or the first time interval in the time domain, and the property of the qcl_type having type D set for the second PDCCH and / or the second search space and / or the second CORESET is different from the property of the qcl_type having type D set for the first TCI state or for the first PDCCH and / or the first search space and / or the first CORESET, the terminal device 120 may not monitor or receive the second PDCCH and / or the associated PDSCH and / or schedule scheduled by the second PDCCH.

[0148] In some embodiments, terminal device 120 may receive an indication or activation of the second TCI state from network device 110, for example, via downlink control information (DCI) and / or MAC CE and / or RRC.

[0149] In some embodiments, terminal device 120 may receive an indication or activation of the first TCI state from network device 110, for example, via downlink control information (DCI) and / or MAC CE and / or RRC.

[0150] In some embodiments, the first search space may be associated with a first CORESET, and in some embodiments, the second search space may be associated with the first CORESET or may be associated with a second CORESET.

[0151] In some embodiments, the first search space may be a common search space (CSS). For example, the search space type of the first search space may be set to be common. In some embodiments, the first search space may be a first user equipment (UE) specific search space (USS). For example, the search space type of the first search space may be set to be UE specific. In some embodiments, the second search space may be a second UE specific search space. For example, the search space type of the second search space may be set to be UE specific.

[0152] In some embodiments, there may be a first set of search spaces associated with the first CORESET. In some embodiments, at least one of the first set of search spaces may be a common search space. In some embodiments, the search space type of at least one of the first set of search spaces may be set to common.

[0153] In some embodiments, there may be a second set of search spaces associated with the second CORESET. In some embodiments, at least one of the second set of search spaces may be a common search space. In some embodiments, the search space type of at least one of the second set of search spaces may be set to common.

[0154] In some embodiments, there may be a second set of search spaces associated with the second CORESET. In some embodiments, all of the search spaces in the second set of search spaces may be UE-specific search spaces. In some embodiments, the search space type of all of the search spaces in the second set of search spaces may be set to be UE-specific.

[0155] In some embodiments, the first TCI state may be indicated to apply to PDCCH reception for an associated PDSCH scheduled by the first CORESET and the second CORESET and / or PDCCH or a UE-specific search space associated with the scheduling. In some embodiments, the first TCI state may not apply to PDCCH reception for an associated PDSCH scheduled by the first CORESET and / or the second CORESET and / or PDCCH or a common search space associated with the scheduling.

[0156] In some embodiments, if all of the search spaces associated with the second CORESET are UE-specific search spaces, the first TCI state may be indicated to apply to PDCCH reception for all search spaces associated with the second CORESET.

[0157] In some embodiments, the second TCI state may be indicated to apply to PDCCH reception for the first search space or for all search spaces associated with the first CORESET, hi some embodiments, the second TCI state may be indicated to apply to PDCCH reception for any common search space associated with the first CORESET and / or the second CORESET.

[0158] In some embodiments, the second physical cell ID may be the physical cell ID of a serving cell configured for terminal device 120. In some embodiments, the first physical cell ID may be different from the physical cell ID of the serving cell. For example, the serving cell may be provided by network 100.

[0159] In some embodiments, when terminal device 120 monitors or receives a PDCCH based on a TCI state, terminal device 120 may assume that the DM-RS antenna port for PDCCH reception is quasi-co-located with one or more RSs configured by or within the TCI state.

[0160] In some embodiments, when terminal device 120 monitors or receives a PDCCH or PDSCH based on the TCI state, terminal device 120 may assume that the DM-RS antenna port for PDCCH or PDSCH reception is quasi-co-located with one or more RSs configured by or within the TCI state.

[0161] In some embodiments, when terminal device 120 monitors or receives a PDSCH based on a TCI state, terminal device 120 may assume that the DM-RS port of the PDSCH is quasi-co-located with the RS in the TCI state with respect to the QCL type parameter given by the TCI state.

[0162] In some embodiments, when terminal device 120 monitors or receives a PDCCH based on a QCL assumption, terminal device 120 may assume that the DM-RS antenna port for PDCCH reception is quasi-co-located with the SS / PBCH block. For example, terminal device 120 may identify the SS / PBCH block during a random access procedure. For example, the random access procedure may be a recent random access procedure that was not initiated by a PDCCH order that triggered a contention-free random access procedure. For another example, terminal device 120 may identify the SS / PBCH block during an initial access procedure.

[0163] In some embodiments, the terminal device 120 may be configured to have two subsets of TCI states (e.g., a first subset and a second subset). For example, this may be done via at least one of MAC CE and RRC. In some embodiments, the TCI states in the first subset are associated with a second physical cell ID. In some embodiments, the TCI states in the second subset are associated with the first physical cell ID. In some embodiments, the TCI states in the second subset may be configured or added after the TCI states in the first subset. In some embodiments, the first subset may have S_1 TCI states, where S_1 is a non-negative integer. For example, 0≦S_1≦128. In some embodiments, the second subset may have S_2 TCI states, where S_2 is a non-negative integer. For example, 0≦S_2≦128. In some embodiments, the index for the TCI states in the first subset may be any one of {0, 1, ... S_1-1}. In some embodiments, the index for the TCI states in the second subset may be any one of {S_1, S_1+1, ... S_1+S_2-1}.

[0164] In some embodiments, terminal device 120 may determine a set of reference signals to include CSI-RS indices having the same value as an RS index indicated by a TCI state for at least one CORESET. In some embodiments, terminal device 120 may determine a set of reference signals to include CSI-RS indices having the same value as an RS index indicated by one or more TCI states for at least one CORESET, where the one or more TCI states may be associated with a second physical cell ID. For example, the set of reference signals may be applied for beam failure detection. For example, the CSI-RS may be periodic CSI-RS. For example, the at least one CORESET may be applied to or used by terminal device 120 to monitor a PDCCH. In some embodiments, if there are two RS indices in a TCI state, the set of reference signals includes an RS index configured to have qcl-Type set to type D for the corresponding TCI state. In some embodiments, the TCI state indicated for the at least one CORESET is associated with a second physical cell ID. In some embodiments, the CSI-RS included in the set of reference signals may be associated with a second physical cell ID, and in some embodiments, the set of reference signals may not include a CSI-RS index having the same value as an RS index indicated by a TCI state for a CORESET if the TCI state is associated with a first physical cell ID.

[0165] In some embodiments, terminal device 120 may be configured with a CORESET, which is associated with a common search space and a UE-specific search space. In some embodiments, a second TCI state may be indicated, activated, configured, or applied for the common search space, and a first TCI state may be indicated, activated, configured, or applied for the UE-specific search space. In some embodiments, terminal device 120 may determine a set of reference signals to include a CSI-RS index having the same value as an RS index indicated by the first TCI state for CORESET.

[0166] In some embodiments, terminal device 120 may be activated with one or two groups of TCI states (e.g., the first group and / or the second group) based on the TCI states of the two subsets, e.g., via MAC CE. In some embodiments, the TCI state activation of the one or two groups may be based on the order of the TCI states in the first subset and the order of the TCI states in the second subset. In some embodiments, the TCI state activation of the one or two groups may be based on the order of the TCI states associated with the second physical cell ID and the order of the TCI states associated with the first physical cell ID.

[0167] In some embodiments, there may be a first TCI state activation command (e.g., via MAC CE, e.g., represented as Command_1), and Command_1 may be applied to activate a TCI state for a set of channels and reference signals (e.g., for PDCCH reception for the first CORESET and the second CORESET and / or associated PDSCH scheduled by the PDCCH or UE-specific search space associated with the scheduling. For another example, for the first CORESET and / or the second CORESET and associated PDSCH scheduled by the PDCCH or PDCCH within the scheduling). For example, the first TCI state and / or the second TCI state may be activated based on Command_1. For example, there may be no indication of the index of the CORESET in Command_1.

[0168] In some embodiments, there may be a second TCI state activation command (e.g., via MAC CE, e.g., represented as Command_2), which may be applied to activate a TCI state for the CORESET and / or a common search space of the CORESET (e.g., for the first search space and / or the first CORESET). For example, the second TCI state may be activated based on Command_2. For example, within Command_2 there may be an indication of the index of the CORESET.

[0169] In some embodiments, there may be a third TCI state activation command (e.g., via MAC CE, e.g., represented as Command_3), which may be applied to activate the TCI state for the PDSCH (e.g., a UE-specific PDSCH MAC CE as defined in TS 38.321). In some embodiments, the terminal device 120 may not expect to receive both Command_1 and Command_3. In some embodiments, if the terminal device 120 receives Command_1, the terminal device 120 may not expect to receive Command_3. In some embodiments, if the terminal device 120 receives Command_1 and if the terminal device 120 receives Command_3, the activated TCI state in Command_3 may be applied to the PDSCH scheduled by the PDCCH, where the PDCCH has its TCI state within the CORESET activated based on Command_2. In some embodiments, the TCI state activated based on Command_3 may be a subset of the TCI state activated based on Command_1.

[0170] In some embodiments, terminal device 120 may be configured to not apply the second TCI state to the first search space and / or the first CORESET.

[0171] In some embodiments, terminal device 120 may monitor or receive a PDCCH within a first search space, and if terminal device 120 is not provided with a TCI state using a Rel-15 / 16 MAC CE (e.g., Command_2) for the CORESET, terminal device 120 may assume that a DM-RS antenna port associated with the PDCCH reception is quasi-co-located with a corresponding SS / PBCH block, and terminal device 120 may assume that a DM-RS antenna port associated with the PDCCH reception is quasi-co-located with one or more DL RSs configured by the TCI state indicated by a Rel-15 / 16 MAC CE (e.g., Command_2) for the CORESET. In some embodiments, terminal device 120 may receive a PDSCH scheduled by a PDCCH. In some embodiments, the TCI state or QCL assumption for a PDSCH is the same as the TCI state or QCL assumption for the corresponding PDCCH, for example, regardless of whether the scheduling offset is greater than or equal to a threshold or less than a threshold. For example, terminal device 120 may ignore the TCI field in the DCI in the PDCCH (e.g., for some Type 3 CSSs). In some embodiments, the presence or absence of the TCI field is configured separately for the common search space and the UE-specific search space within the same CORESET. For example, for the common search space, the TCI field may be configured to be absent or disabled. For another example, the presence or absence of the TCI field may be based on the number of activated TCI states or codepoints for the UE-specific search space (e.g., based on Command_1). In some embodiments, in addition to a Rel-17 MAC CE for Rel-17 TCI state activation (e.g., Command_1), a Rel-15 / 16 MAC CE (e.g., Command_3) for activating the TCI state for the PDSCH may be required.

[0172] In some embodiments, the TCI state (e.g., Command_3) activated via the Rel-15 / 16 MAC CE may only apply to PDSCHs scheduled by PDCCHs in the common search space (e.g., for PDCCHs in the search space that do not apply the indicated Rel-17 TCI state).

[0173] In some embodiments, if the scheduling offset for the PDSCH is less than a threshold, terminal device 120 may assume that the DM-RS port of the PDSCH is quasi-co-located with the RS with respect to the first TCI state / QCL parameter used for the PDCCH quasi-co-location indication of a CORESET associated with a monitored search space in which one or more CORESETs in the serving cell's active BWP have the lowest controlResourceSetId in the last slot monitored by terminal device 120. For example, the one or more CORESETs may include a common search space. For another example, the one or more CORESETs and / or common search space may not apply the Rel-17 TCI state indicated or activated (e.g., based on Command_1).

[0174] For example, as shown in FIG. 4, terminal device 120 may be configured to have a second TCI state (e.g., TCI_1 or QCL_1) to monitor or receive a PDCCH within a common search space. Terminal device 120 may be configured to have a first TCI state (e.g., TCI_2) to monitor or receive a PDCCH within a UE-specific search space. In some embodiments, when the common search space and the UE-specific search space overlap in the time domain or within the same time interval, terminal device 120 may receive a PDCCH within the UE-specific search space within the overlapping time interval or within the same time interval based on the second TCI state (TCI_1 or QCL_1 shown in FIG. 4). In some embodiments, when the time interval for the UE-specific search space does not overlap with the CSS, terminal device 120 may receive a PDCCH within the UE-specific search space within the time interval based on the first TCI state (TCI_2 shown in FIG. 4).

[0175] In some embodiments, terminal device 120 may be indicated with a first TCI state. For example, if the time interval does not overlap with the first time interval, terminal device 120 may monitor or receive a PDCCH in a USS in the CORESET within the time interval based on the first TCI state. In some embodiments, the terminal device may monitor or receive a PDCCH in a USS and / or a CSS starting from the first symbol of a monitoring occasion for any CSS based on a second TCI state.

[0176] For example, as shown in FIG. 5, terminal device 120 may be configured to have a second TCI state (e.g., TCI_1 or QCL_1) to monitor or receive a PDCCH within a common search space. Terminal device 120 may be configured to have a first TCI state (e.g., TCI_2) to monitor or receive a PDCCH within a UE-specific search space. In some embodiments, within a time interval from when the first TCI state becomes applicable to the start of the first occasion of the CSS, terminal device 120 may receive a PDCCH within the USS based on the first TCI state (TCI_2 shown in FIG. 5). In some embodiments, starting from the start of the first occasion of the CSS, terminal device 120 may receive a PDCCH within the USS and / or within the CSS based on the second TCI state (TCI_1 or QCL_1 shown in FIG. 5).

[0177] In some embodiments, terminal device 120 may be configured to have a CORESET. Furthermore, CORESET is associated with a common search space and a UE-specific search space. In some embodiments, terminal device 120 may be indicated or activated to have a first TCI state (e.g., Command_1), and terminal device 120 may be indicated or activated to have a second TCI state (e.g., Command_2). In some embodiments, terminal device 120 may monitor or receive a PDCCH within the common search space based on the second TCI state. In some embodiments, the second TCI state may be indicated or activated after the first TCI state. For example, terminal device 120 may monitor or receive a PDCCH within a UE-specific search space based on the first TCI state. For example, the UE-specific search space does not overlap with the common search space.

[0178] In some embodiments, terminal device 120 may be indicated or activated to have a second TCI state (e.g., Command_2), and terminal device 120 may be indicated or activated to have a first TCI state (e.g., Command_1). For example, terminal device 120 may monitor or receive a PDCCH within a common search space and / or within a UE-specific search space based on the second TCI state. In some embodiments, the first TCI state may be indicated or activated after the second TCI state. For example, terminal device 120 may monitor or receive a PDCCH within a UE-specific search space based on the first TCI state after an application timing. For example, the UE-specific search space does not overlap with the common search space.

[0179] In some embodiments, terminal device 120 may receive an indication or activation of a Rel-17 TCI state (e.g., a combined TCI state or separate DL and / or UL TCI states), where if the Rel-17 TCI state is associated with the physical cell ID of the serving cell or a second physical cell ID (e.g., the second TCI state), the TCI state applies to a first set of signals and channels (e.g., all signals and channels for intra-cell beam management (e.g., aperiodic CSI-RS for beam management, aperiodic CSI-RS for channel state information (CSI)), a UE-dedicated PDSCH, CORESET and non-UE-dedicated CORESET and associated PDSCHs)), and if the Rel-17 TCI state is associated with a physical cell ID different from the serving cell or the first physical cell ID (e.g., the first TCI state), the TCI state applies to a second set of signals and channels (e.g., the first set excluding non-UE-dedicated signals and channels).

[0180] For example, as shown in FIG. 6 , terminal device 120 may be configured to have a second TCI state (e.g., TCI state A) to monitor or receive a PDCCH within a common search space. For example, TCI state A may be associated with a second physical cell ID. Terminal device 120 may be configured to have a first TCI state (e.g., TCI state B) to monitor or receive a PDCCH within a UE-specific search space. For example, TCI state B may be associated with a first physical cell ID. In some embodiments, when the common search space and the UE-specific search space overlap in the time domain or within the same time interval, terminal device 120 may receive a PDCCH within the UE-specific search space within the overlapping time interval or within the same time interval based on the second TCI state (TCI state A shown in FIG. 6 ). In some embodiments, if a time interval for a UE-specific search space does not overlap with the CSS, the terminal device 120 may receive a PDCCH within the UE-specific search space within the time interval based on a first TCI state (TCI state B shown in FIG. 6).

[0181] For example, as shown in FIG. 7 , terminal device 120 may be configured to have a second TCI state (e.g., TCI state A) to monitor or receive a PDCCH in a common search space. For example, TCI state A may be associated with a second physical cell ID. Terminal device 120 may be configured to have a first TCI state (e.g., TCI state B) to monitor or receive a PDCCH in a UE-specific search space. For example, TCI state B may be associated with a first physical cell ID. In some embodiments, when the common search space and the UE-specific search space overlap in the time domain or within the same time interval, terminal device 120 may not monitor or receive a PDCCH in the UE-specific search space within the overlapping time interval or within the same time interval. For example, terminal device 120 may monitor or receive a PDCCH in the common search space within the overlapping time interval or within the same time interval based on TCI state A. In some embodiments, if a time interval for a UE-specific search space does not overlap with the CSS, the terminal device 120 may receive a PDCCH within the UE-specific search space within the time interval based on a first TCI state (TCI state B shown in FIG. 7).

[0182] For example, as shown in FIG. 8 , terminal device 120 may be configured to have a second TCI state (e.g., TCI state A) to monitor or receive a PDCCH within a common search space. Terminal device 120 may be configured to have a first TCI state (e.g., TCI state B) to monitor or receive a PDCCH within a UE-specific search space. In some embodiments, within a time interval from when the first TCI state becomes applicable to the start of the first occasion of the CSS, terminal device 120 may receive a PDCCH within the USS based on the first TCI state (TCI state B shown in FIG. 8 ). In some embodiments, starting from the start of the first occasion of the CSS, terminal device 120 may receive a PDCCH within the USS and / or within the CSS based on the second TCI state (TCI state A shown in FIG. 8 ).

[0183] In some embodiments, the UE - configured for single cell operation or operation with carrier aggregation within the same frequency band, and - monitoring PDCCH candidates in multiple CORESETs configured with the same or different qcl-Type set to the 'typeD' property on the active DL BWP of one or more cells, or in overlapping PDCCH monitoring occasions in multiple search space sets within a CORESET; The UE monitors the PDCCH only in a CORESET or search space set, and in any other CORESET from the plurality of CORESETs or in any other search space set from the plurality of search space sets that is configured to have qcl-Type set to the same "typeD" property as the CORESET or the search space set on an active DL BWP of a cell from the one or more cells. - the CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index that contains a CSS (if any), otherwise it corresponds to the USS set with the lowest index in the cell with the lowest index, if all search space sets are set to have the same qcl-Type set to the "typeD" property in each CORESET; - the CSS set with the lowest index in the cell with the lowest index that contains the CSS (if any); otherwise, if the search space set is set to have a qcl-Type with a different "typeD" property set in a CORESET, the USS set with the lowest index in the cell with the lowest index; - the lowest USS set index is determined over all USS sets having at least one PDCCH candidate within overlapping PDCCH monitoring occasions; - For the purposes of determining CORESET, SS / PBCH blocks are considered to have different QCL "Type D" properties than CSI-RS - to determine the CORESET, it is assumed that a first CSI-RS associated with an SS / PBCH block in a first cell and a second CSI-RS associated with the same SS / PBCH block in a second cell have the same QCL "type D" property; - allocating non-overlapping CCEs and PDCCH candidates for PDCCH monitoring according to all search space sets associated with the plurality of CORESETs on an active DL BWP of the one or more cells; The number of active TCI states is determined based on the number of CORESETs and the number of PCIs different from the serving cell.

[0184] In some embodiments, the UE - configured for single cell operation or operation with carrier aggregation within the same frequency band; - when monitoring PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs where none of the CORESETs has a TCI state configured to have the qcl type set to 'type D'; The UE needs to monitor PDCCH candidates in overlapping PDCCH monitoring occasions for search space sets associated with different CORESETs.

[0185] In some embodiments, for a CORESET other than the CORESET with index 0, if a single TCI state for the CORESET is provided to the UE, or if the UE receives a MAC CE activation command for one of the provided TCI states for the CORESET, the UE assumes that the DM-RS antenna port associated with PDCCH reception in this CORESET is quasi-co-located with one or more DL-RSs configured by that TCI state. For a CORESET with index 0, if the TCI state indicated by the MAC CE activation command or DCI for that CORESET is associated with the PCI of the serving cell, the UE expects the CSI-RS configured with qcl-Type set to "Type D" in that TCI state to be provided by the SS / PBCH block associated with the PCI of the serving cell, and if the TCI state indicated by the MAC CE activation command or DCI for that CORESET is associated with a different PCI of the serving cell, the UE expects the CSI-RS configured with qcl-Type set to "Type D" in that TCI state to be provided by the SS / PBCH block associated with the different PCI of the serving cell. - If the UE receives a MAC CE activation command for one of the TCI states, the UE shall

number

[0186] In some embodiments, the UE may configure a periodic CSI-RS resource configuration set for each CORESET that the UE uses to monitor the PDCCH, to include a periodic CSI-RS resource configuration index that has the same value as an RS index in the RS set indicated by the TCI-State. TIFF2026001124000019.tif66, where CORESET is set to have the same CORESETPoolIndex value, the TCI state is associated with the physical cell ID of the serving cell, and if there are two RS indices in the TCI state, the set TIFF2026001124000020.tif66 includes an RS index set to have qcl-Type set to "typeD" for the corresponding TCI state. You may expect TIFF2026001124000021.tif66 to contain up to two RS indices.

[0187] In some embodiments, the terminal device 120 may be configured to have a common search space (CSS) and a UE-specific search space (USS). For example, the CSS and the USS may be associated with the same CORESET. For another example, the CSS and the USS may be associated with different CORESETs. In some embodiments, there may be a first TCI field in the DCI in the PDCCH for the CSS. In some embodiments, any one of the codepoints for the first TCI field may be associated only with a TCI state associated with a second physical cell ID. In some embodiments, there may be a second TCI field in the DCI in the PDCCH for the USS. In some embodiments, the codepoints for the second TCI field may be associated with a TCI state associated with the second physical cell ID and a TCI state associated with the first physical cell ID. In some embodiments, some codepoints for the second TCI field may be associated with a TCI state associated with the second physical cell ID, and other codepoints for the second TCI field may be associated with a TCI state associated with the first physical cell ID.

[0188] In some embodiments, terminal device 120 may receive a first DCI in a PDCCH, where the first DCI may indicate a first TCI state. For example, the first TCI state may be associated with a first physical cell ID. Terminal device 120 may receive a second DCI in another PDCCH, where the second DCI may indicate a second TCI state. For example, the second TCI state may be associated with a second physical cell ID. In some embodiments, HARQ feedback corresponding to the first DCI or a PDSCH scheduled by the first DCI and HARQ feedback corresponding to the second DCI or a PDSCH scheduled by the second DCI may be in the same HARQ codebook. For example, the HARQ codebook may be transmitted in a PUCCH resource or a PUSCH resource. In some embodiments, the first TCI state and the second TCI state may be applicable after application timing. For example, a first TCI state may apply to PDCCH reception within a UE-specific search space. For another example, a second TCI state may apply to PDCCH reception within a common search space.

[0189] In some embodiments, the terminal device may be configured to have separate downlink and uplink TCI states. In some embodiments, terminal device 120 may receive a first DCI in a PDCCH, and the first DCI may indicate a first TCI state. For example, the first TCI state may be a downlink TCI state, a pair of a downlink TCI state and an uplink TCI state, or an uplink TCI state. Terminal device 120 may receive a second DCI in another PDCCH, and the second DCI may indicate a second TCI state. For example, the second TCI state may be an uplink TCI state or a downlink TCI state. In some embodiments, the HARQ feedback corresponding to the first DCI or the PDSCH scheduled by the first DCI and the HARQ feedback corresponding to the second DCI or the PDSCH scheduled by the second DCI may be in the same HARQ codebook. For example, the HARQ codebook may be transmitted within a PUCCH resource or within a PUSCH resource. In some embodiments, both the first TCI state and the second TCI state may be applicable after application timing. In some embodiments, the downlink TCI state within the first TCI state may be applied to a downlink channel and / or a reference signal, and the second TCI state may be applied to an uplink channel and / or a reference signal. For example, the first TCI state may be a downlink TCI state or a pair of a downlink TCI state and an uplink TCI state, and the second TCI state may be an uplink TCI state. In some embodiments, the uplink TCI state within the first TCI state may be applied to an uplink channel and / or a reference signal, and the second TCI state may be applied to a downlink channel and / or a reference signal. For example, the first TCI state may be an uplink TCI state or a pair of a downlink TCI state and an uplink TCI state, and the second TCI state may be a downlink TCI state.

[0190] For example, as shown in FIG. 9, terminal device 120 may receive PDCCH 910 and PDCCH 920. For example, DCI in PDCCH 910 may indicate a first TCI state (TCI state A shown in FIG. 9). For another example, DCI in PDCCH 920 may indicate a second TCI state (TCI state B shown in FIG. 9). Terminal device 120 may apply both the first TCI state and the second TCI state to the corresponding channels and / or RSs after the application timing.

[0191] In some embodiments, terminal device 120 may be configured to have a first CORESET or first search space and a second CORESET or second search space. In some embodiments, the first CORESET or first search space is according to an indicated Rel-17 TCI state, such as the first TCI state or a TCI state associated with a second physical cell ID. The second CORESET or second search space is according to an indicated Rel-17 TCI state, such as the first TCI state or the second TCI state, or a TCI state associated with one of the first physical cell ID or the second physical cell ID. In some embodiments, codepoints in the TCI field in the PDCCH of the first CORESET or first search space are mapped (e.g., in order) only to the activated TCI state associated with the second physical cell ID. In some embodiments, codepoints in the TCI field in the PDCCH of the second CORESET or second search space are mapped (e.g., sequentially) to activated TCI states, e.g., TCI states activated via Command_1.

[0192] In some embodiments, only the TCI states associated with the second physical cell ID may be applied to CORESET 0. In some embodiments, when CORESET 0 is associated with a common search space and a UE-specific search space, only the TCI states associated with the second physical cell ID may be applied to the common search space, and the TCI states associated with either the first physical cell ID or the second physical cell ID may be applied to the UE-specific search space.

[0193] In some embodiments, the terminal device 120 may receive a first indication or setting or activation of a first set of TCI states for a first set of CORESETs, and the terminal device 120 may receive a second indication or setting or activation of a second set of TCI states for a second set of CORESETs. In some embodiments, the terminal device 120 may perform one or two beam failure recovery procedures based on the condition.

[0194] In some embodiments, the condition may be at least one of a third condition and a fourth condition. In some embodiments, the third condition may be that a second set of reference signals (RS) in the second set of TCI states is associated with a first physical cell ID. In some embodiments, the fourth condition may be that a second set of reference signals (RS) in the second set of TCI states is associated with a second physical cell ID.

[0195] In some embodiments, based on the third condition, the terminal device 120 may perform a first beam failure detection based on the first set of RSs within the first set of TCI states.

[0196] In some embodiments, based on the fourth condition, the terminal device 120 may perform a first beam failure detection based on a first set of RSs in a first set of TCI states, and a second beam failure detection based on a second set of RSs in a second set of TCI states.

[0197] In some embodiments, the first set of RSs in the first set of TCI states may be associated with a second physical cell ID. In some embodiments, the second physical cell ID is the physical cell ID of a serving cell configured for terminal device 120. In some embodiments, the first physical cell ID may be different from the physical cell ID of the serving cell.

[0198] In some embodiments, a first set of beam failure detection (BFD) RSs for the terminal device may be determined based on the first set of RSs within the first set of TCI states.

[0199] In some embodiments, if the second set of RSs in the second set of TCI states are associated with a second physical cell ID, the second set of beam failure detection RSs for the terminal device may be determined based on the second set of RSs in the second set of TCI states.

[0200] In some embodiments, if a second set of reference signals (RSs) in the second set of TCI states is associated with the first physical cell ID, no beam failure detection RSs may be determined based on the second set of RSs in the second set of TCI states.

[0201] In some embodiments, if one or more TCI states activated for a first value of CORESETPoolIndex are associated with a second physical cell ID and one or more TCI states activated for a second value of CORESETPoolIndex are also associated with the second physical cell ID, a TRP-specific BFR may be applied. For example, for a first set of CORESETs (e.g., TRP1) associated with the first value of CORESETPoolIndex, beam failure detection (BFD) RS set 1 (e.g., BFD_set_1) may be applied for beam failure detection, and new beam identification (NBI) RS set 1 (e.g., NBI_set_1) may be applied for candidate beam identification. For TRP2, BFD RS set 2 (e.g., BFD_set_2) may be applied for beam failure detection, and NBI RS set 2 (e.g., NBI_set_2) may be applied for candidate beam identification.

[0202] In some embodiments, if one or more TCI states are indicated or activated for one value of CORESETPoolIndex associated with a first physical cell ID, the TRP-specific BFR may be changed to a cell-specific BFR. For example, if only one set of BFD RSs is applied for beam failure detection and in the implicit configuration, the BFD RSs are based on the CORESET whose TCI state is associated with a second physical cell ID.

[0203] In some embodiments, terminal device 120 may determine a first set of BFD RSs to include CSI-RS indices having the same values ​​as RS indices indicated by one or more TCI states for a CORESET configured to have a first value of CORESETPoolIndex, where the one or more TCI states for the CORESET are associated with a second physical cell ID. In some embodiments, terminal device 120 may determine a second set of BFD RSs to include CSI-RS indices having the same values ​​as RS indices indicated by one or more TCI states for a CORESET configured to have a second value of CORESETPoolIndex, where the one or more TCI states for the CORESET are associated with a second physical cell ID. For example, the set of reference signals may be applied for beam failure detection. For example, the CSI-RSs may be periodic CSI-RSs. For example, these CORESETs may be applied to or used by terminal device 120 to monitor the PDCCH. In some embodiments, if there are two RS indices in a TCI state, the set of reference signals includes an RS index configured to have qcl-Type set to type D for the corresponding TCI state. In some embodiments, the TCI state indicated for CORESET is associated with a second physical cell ID. In some embodiments, the CSI-RS included in the set of reference signals may be associated with a second physical cell ID. In some embodiments, the set of reference signals may not include a CSI-RS index having the same value as the RS index indicated by the TCI state if the TCI state for CORESET is associated with a first physical cell ID.

[0204] In some embodiments, terminal device 120 may be configured with a CORESET, which is associated with a common search space and a UE-specific search space. In some embodiments, a second TCI state may be indicated, activated, configured, or applied for the common search space, and a first TCI state may be indicated, activated, configured, or applied for the UE-specific search space. In some embodiments, terminal device 120 may determine the set of reference signals, or the first set of BFD RSs, or the second set of BFD RSs, to include CSI-RS indices having the same values ​​as RS indices indicated by the first TCI state for CORESET.

[0205] In some embodiments, if all TCI states for all CORESETs configured to have a first value of CORESETPoolIndex are associated with a first physical cell ID, then the first set of BFD RSs may not exist, or the terminal device 120 may not perform beam failure detection based on the first set of BFD RSs, or the terminal device 120 may not perform beam failure detection for the first TRP or for the CORESET configured to have a first value of CORESETPoolIndex. In some embodiments, if all TCI states for all CORESETs configured to have a second value of CORESETPoolIndex are associated with a first physical cell ID, then the second set of BFD RSs may not exist, or the terminal device 120 may not perform beam failure detection based on the second set of BFD RSs, or the terminal device 120 may not perform beam failure detection for the second TRP or for the CORESET configured to have a second value of CORESETPoolIndex.

[0206] In some embodiments, there may be a first SS and / or a first PBCH associated with a first physical cell ID, and there may be a second SS and / or a second PBCH associated with a second physical cell ID. In some embodiments, terminal device 120 may communicate with network device 110 based on a first payload or first information in the second SS and / or the second PBCH. For example, the first payload or the first information may include at least one of a system frame number, a half-frame indication, and a subframe index. In some embodiments, terminal device 120 may ignore a second payload or second information in the first SS and / or the first PBCH. For example, the second payload or the second information may include at least one of a system frame number, a half-frame indication, and a subframe index.

[0207] In some embodiments, the sequence for the RS may be generated based on information associated with the second physical cell ID, which may include at least one of a system frame number, a half-frame indication, a subframe index, a symbol index, and a scrambling ID.

[0208] In some embodiments, terminal device 120 may be configured to have a pair of linked PDCCH candidates. For example, a first PDCCH candidate and a second PDCCH candidate. In some embodiments, the first PDCCH candidate may be associated with a first search space, and the second PDCCH candidate may be associated with a second search space. In some embodiments, if one of the linked PDCCH candidates uses the same set of control channel elements (CCEs) as an individual (e.g., unlinked) PDCCH candidate (e.g., a third PDCCH candidate), both are associated with the same DCI size, scrambling, and CORESET. For example, the third PDCCH candidate may be associated with a third search space. In some embodiments, terminal device 120 may determine a PUCCH resource for a DCI in at least one of the first PDCCH candidate, the second PDCCH candidate, and the third PDCCH candidate based on a lower index between the index of the first search space and the index of the second search space. In some embodiments, terminal device 120 may determine the PUCCH resource based on the lowest index among the index of the first search space, the index of the second search space, and the index of the third search space for DCI in at least one of the first PDCCH candidate, the second PDCCH candidate, and the third PDCCH candidate. In some embodiments, terminal device 120 may not expect to monitor or receive a PDCCH if both linked PDCCH candidates overlap with the third PDCCH candidate and the fourth PDCCH candidate. In some embodiments, terminal device 120 may not expect to monitor or receive a PDCCH if the first PDCCH candidate overlaps with the third PDCCH candidate and the second PDCCH candidate overlaps with the fourth PDCCH candidate.

[0209] In one embodiment, a method is provided that is performed by a network device 110. In the method, an indication of a first transmission configuration indicator (TCI) state may be transmitted to a terminal device 120. At least one reference signal (RSS) in the first TCI state may be associated with a first physical cell identity (ID). A first physical downlink control channel (PDCCH) in a first monitoring occasion for a first search space may be transmitted to the terminal device based on a second TCI state or based on a quasi-co-location (QCL). At least one RS in the second TCI state and QCL assumption may be associated with a second physical cell ID. A second PDCCH in a second monitoring occasion for a second search space is based on a condition.

[0210] The method performed by the network device 110 further includes at least one of: transmitting the second PDCCH based on the first TCI state after an applied timing based on a condition that the second monitoring occasion is within a time interval different from the first time interval; transmitting the second PDCCH based on the second TCI state or based on the QCL assumption based on a condition that the second monitoring occasion is within the same time interval as the first time interval; transmitting the second PDCCH based on the first TCI state after the applied timing based on a condition that the second monitoring occasion does not overlap with the first time interval in the time domain; and transmitting the second PDCCH based on the second TCI state or based on the QCL assumption based on a condition that the second monitoring occasion overlaps with the first time interval in the time domain.

[0211] It should be noted that the features, parameters, and steps mentioned in the method performed by the network device 110 have already been described in the method performed by the terminal device 120. Therefore, these disclosures may be considered to be part of the method performed by the network device 110.

[0212] 10 is a schematic block diagram of an apparatus 1000 suitable for implementing embodiments of the present disclosure. The apparatus 1000 may be considered as another exemplary implementation of the network apparatus 110, the TRP 130, and / or the terminal device 120 as shown in FIG. 1. Accordingly, the apparatus 1000 may be implemented in, or as at least a portion of, the network apparatus 110, the TRP 130, and / or the terminal device 120 as shown in FIG. 1.

[0213] As shown, the apparatus 1000 comprises a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX / RX 1040. The memory 1010 stores at least a portion of a program 1030. The TX / RX 1040 is used for bidirectional communication. The TX / RX 1040 has at least one antenna to facilitate communication, although the access nodes referred to herein may actually have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0214] The program 1030 is assumed to include program instructions that, when executed by an associated processor 1010, enable the device 1000 to operate according to embodiments of the present disclosure, as described herein with reference to FIGS. 1-9. The embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1010 and the memory 1020 may form a processing means 1050 suitable for implementing various embodiments of the present disclosure.

[0215] The memory 1020 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. While only one memory 1020 is shown in the device 1000, several physically distinct memory modules may be present within the device 1000. The processor 1010 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1000 may have multiple processors, for example, application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0216] Overall, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure have been illustrated and described using block diagrams, flowcharts, or other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0217] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, that execute within a device on a target real or virtual processor to perform the processes or methods described above with reference to Figures 2-14. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. The machine-executable instructions of the program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0218] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, and when executed by the processor or controller, cause the program code to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0219] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that can contain or store a program used by or associated with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the aforementioned media. More specific examples of a machine-readable storage medium may include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0220] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order shown, or in any sequential order, or performing all of the operations described, is required to achieve desirable results. In some cases, multitasking or parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0221] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. means for receiving a first transmission configuration indicator (TCI) state and a second TCI state from a network device; means for monitoring a first physical downlink control channel (PDCCH) within a first monitoring occasion based on the second TCI state associated with a first control resource set (CORESET); means for monitoring a second PDCCH in the second monitoring occasion based on the first TCI state associated with a second CORESET when the second monitoring occasion and the first monitoring occasion do not overlap; the second CORESET is associated only with a user equipment (UE)-specific search space, and the first CORESET is associated with at least one common search space; Terminal device.

2. The second CORESET is associated with a physical cell ID of a serving cell, and the first CORESET is associated with another physical cell ID different from the physical cell ID of the serving cell. The terminal device according to claim 1 .

3. both the first CORESET and the second CORESET are configured to have the same quasi-collocation (QCL) type including spatial receiver (Rx) parameters; The terminal device according to claim 1 .

4. a demodulation reference signal (DMRS) antenna port for the first PDCCH is quasi-collocated with at least one RS set to the second TCI state; a DMRS antenna port for the second PDCCH is quasi-co-located with at least one RS set to the first TCI state; The terminal device according to claim 1 .

5. means for transmitting a first transmission configuration indicator (TCI) state and a second TCI state to a terminal device; the second TCI state associated with a first control resource set (CORESET) is used to monitor a first physical downlink control channel (PDCCH) within a first monitoring occasion; the first TCI state associated with a second CORESET is used to monitor a second PDCCH in a second monitoring occasion when the second monitoring occasion and the first monitoring occasion do not overlap; the second CORESET is associated only with a user equipment (UE)-specific search space, and the first CORESET is associated with at least one common search space; Network equipment.

6. The second CORESET is associated with a physical cell ID of a serving cell, and the first CORESET is associated with another physical cell ID different from the physical cell ID of the serving cell. The network device according to claim 5 .

7. both the first CORESET and the second CORESET are configured to have the same quasi-collocation (QCL) type including spatial receiver (Rx) parameters; The network device according to claim 5 .

8. a demodulation reference signal (DMRS) antenna port for the first PDCCH is quasi-collocated with at least one RS set to the second TCI state; a DMRS antenna port for the second PDCCH is quasi-co-located with at least one RS set to the first TCI state; The network device according to claim 5 .

9. 1. A method performed by a terminal device, comprising: receiving a first transmission configuration indicator (TCI) state and a second TCI state from a network device; monitoring a first physical downlink control channel (PDCCH) within a first monitoring occasion based on the second TCI state associated with a first control resource set (CORESET); and if a second monitoring occasion does not overlap with the first monitoring occasion, monitoring a second PDCCH within the second monitoring occasion based on the first TCI state associated with a second CORESET; the second CORESET is associated only with a user equipment (UE)-specific search space, and the first CORESET is associated with at least one common search space; method.

10. The second CORESET is associated with a physical cell ID of a serving cell, and the first CORESET is associated with another physical cell ID different from the physical cell ID of the serving cell.

10. The method of claim 9.

11. both the first CORESET and the second CORESET are configured to have the same quasi-collocation (QCL) type including spatial receiver (Rx) parameters; 10. The method of claim 9.

12. a demodulation reference signal (DMRS) antenna port for the first PDCCH is quasi-collocated with at least one RS set to the second TCI state; a DMRS antenna port for the second PDCCH is quasi-co-located with at least one RS set to the first TCI state; 10. The method of claim 9.

13. 1. A method performed by a network device, comprising: transmitting a first transmission configuration indicator (TCI) state and a second TCI state to a terminal device; the second TCI state associated with a first control resource set (CORESET) is used to monitor a first physical downlink control channel (PDCCH) within a first monitoring occasion; the first TCI state associated with a second CORESET is used to monitor a second PDCCH in a second monitoring occasion when the second monitoring occasion and the first monitoring occasion do not overlap; the second CORESET is associated only with a user equipment (UE)-specific search space, and the first CORESET is associated with at least one common search space; method.

14. The second CORESET is associated with a physical cell ID of a serving cell, and the first CORESET is associated with another physical cell ID different from the physical cell ID of the serving cell. The method of claim 13.

15. both the first CORESET and the second CORESET are configured to have the same quasi-collocation (QCL) type including spatial receiver (Rx) parameters; The method of claim 13.

Images