Terminal device, network device, and method

Abstract

The embodiments of the present disclosure relate to a communication method, an apparatus, and a computer storage medium. The method includes receiving, in a terminal device, from a network device, at least one configuration for a first list of cells, the first list of cells comprising a first cell and a second list of cells, where at least a first spatial reception parameter of the second list of cells refers to the first cell based on the at least one configuration, and performing a first beam failure recovery procedure for the first list of cells, or performing a first beam failure recovery procedure for the first cell and a second beam failure recovery procedure for the second list of cells. The second beam failure recovery procedure is the same as or related to the first beam failure recovery procedure.

Description

[Technical field]

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

[0002] At the third generation partnership project (3GPP) meeting RAN#86, 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 beam management (low latency, low overhead) for downlink (DL) and uplink (UL) within and between cells. For example, it is proposed to support a common beam for transmission and reception of data and control information for both DL and UL. It is also proposed to support a unified Transmission Configuration Indication (TCI) framework for DL ​​and UL beam indication. In addition, multi-input multi-output (MIMO) is proposed, which includes features to facilitate the utilization of a large number of antenna elements at the base station for both sub-6GHz and above 6GHz frequency bands. Therefore, it is worthwhile to enhance multi-beam operation. Summary of the Invention [Problem to be solved by the invention]

[0003] Generally, the exemplary 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 communication method is provided, comprising: receiving, in a terminal device, from a network device, at least one configuration for a first list of cells, the first list of cells comprising a first cell and a second list of cells, at least a first spatial reception parameter of the second list of cells referring to the first cell based on the at least one configuration, and performing a first beam failure recovery procedure for the first list of cells, or performing the first beam failure recovery procedure for the first cell and performing a second beam failure recovery procedure for the second list of cells, the second beam failure recovery procedure being the same as or related to the first beam failure recovery procedure.

[0005] In a second aspect, a communication method is provided, comprising: transmitting, in a network device, at least one configuration for a first list of cells to a terminal device, the first list of cells comprising a first cell and a second list of cells, where at least a first spatial reception parameter of the second list of cells refers to the first cell based on the at least one configuration; transmitting an indication of a first transmission configuration indicator (TCI); and transmitting, after or starting from an application timing, a first set of channels and / or reference signals based on the first spatial reception parameter on the first list of cells, where the first spatial reception parameter is based on the first TCI.

[0006] In a third aspect, a communication method is provided, comprising: receiving, in a terminal device, from a network device, at least one configuration of a set of transmission configuration indicator (TCI) states, the set of TCI states comprising at least one of a first subset of TCI states and a second subset of TCI states, at least one reference signal (RS) of the TCI states of the first subset being associated with a first physical cell identity (ID), and at least one RS of the TCI states of the second subset being associated with a second physical cell ID, performing a beam failure recovery procedure based on at least one of a first set of RSs for beam failure detection and a first set of RSs for candidate beam identification when a first TCI state of the first subset is indicated, and performing a beam failure recovery procedure based on at least one of a second set of RSs for beam failure detection and a second set of RSs for candidate beam identification when a second TCI state of the second subset is indicated.

[0007] In a fourth aspect, a communication method is provided, comprising: transmitting, in a network device, at least one configuration for a set of transmission configuration indicator (TCI) states to a terminal device, the set of TCI states comprising at least one of a first subset of TCI states and a second subset of TCI states, at least one reference signal (RS) of the TCI states of the first subset being associated with a first physical cell identity (ID), at least one RS of the TCI states of the second subset being associated with a second physical cell ID, the at least one configuration for the set of TCI states being configured for a first cell, the first cell being associated with the first physical cell ID; transmitting at least one configuration for a first list of cells, the first list of cells comprising a first cell and a second list of cells, at least a first spatial reception parameter of the second list of cells referring to the first cell based on the at least one configuration for the first list of cells; and transmitting, in response to the indication of a first TCI state of the first subset, after or starting from an application timing, a first TCI state of the first subset being configured for a first cell; and in response to a second TCI state of the second subset being indicated, not performing transmission or reception in the second list of cells after or starting from the application timing, or in response to a second TCI state of the second subset being indicated, transmitting at least one downlink channel and / or receiving at least one uplink channel in at least one cell of the second list of cells based on a latest or previous TCI state, wherein the latest or previous TCI state is associated with the first physical cell ID.

[0008] In a fifth aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the first aspect of the present disclosure described above.

[0009] In a sixth aspect, there is provided a network device, the network device comprising circuitry configured to perform the method according to the second aspect of the present disclosure described above.

[0010] In a seventh aspect, there is provided a computer program product comprising machine readable instructions which, when executed, cause a machine to perform a method according to the first or second aspect of the present disclosure as set forth above.

[0011] In an eighth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to the first or second aspect of the present disclosure as set forth above.

[0012] It should be understood that this Summary of the Invention is not intended to identify key features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent through the following description. [Brief description of the drawings]

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

[0014] [Figure 1] 1 illustrates an exemplary communications network in which embodiments of the present disclosure may be implemented;

[0015] [Diagram 2] 1 illustrates an example signaling chart in accordance with some embodiments of the present disclosure.

[0016] [Figure 3A] 1 illustrates an example of an embodiment of the present disclosure. [Figure 3B] 1 illustrates an example of an embodiment of the present disclosure. [Figure 3C] 1 illustrates an example of an embodiment of the present disclosure.

[0017] [Figure 4A] 1 illustrates an example of an embodiment of the present disclosure. [Figure 4B] 1 illustrates an example of an embodiment of the present disclosure.

[0018] [Figure 5A] 1 illustrates an example of an embodiment of the present disclosure. [Figure 5B] 1 illustrates an example of an embodiment of the present disclosure. [Figure 5C] 1 illustrates an example of an embodiment of the present disclosure. [Figure 5D] 1 illustrates an example of an embodiment of the present disclosure. [Figure 5E] 1 illustrates an example of an embodiment of the present disclosure.

[0019] [Figure 6A] 1 illustrates an example of an embodiment of the present disclosure. [Figure 6B] 1 illustrates an example of an embodiment of the present disclosure.

[0020] [Figure 7A] 1 illustrates an example of an embodiment of the present disclosure. [Figure 7B] 1 illustrates an example of an embodiment of the present disclosure. [Figure 7C] 1 illustrates an example of an embodiment of the present disclosure.

[0021] [Figure 8] 1 shows a flowchart of an exemplary method according to some embodiments of the present disclosure.

[0022] [Figure 9] 1 shows a flowchart of an exemplary method according to some embodiments of the present disclosure.

[0023] [Figure 10] FIG. 1 is a schematic block diagram of an apparatus suitable for practicing embodiments of the present disclosure.

[0024] Throughout the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] The principles of the present disclosure will be described with reference to some exemplary embodiments. It should be understood that these embodiments are merely described for illustrative purposes to aid those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitations on the scope of the present disclosure. The present disclosure described herein can be implemented in a variety of ways other than those described below.

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

[0027] As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. The term "comprises" and variations thereof are interpreted as open ended terms meaning "including, but not limited to." The term "based on" is interpreted as "based at least in part on." The terms "some embodiments" and "one embodiment" are interpreted as "at least some embodiments." The term "another embodiment" is interpreted as "at least one other embodiment." Terms such as "first," "second," and the like may refer to different objects or the same object. The following content may include other definitions, both explicit and implicit.

[0028] In some instances, values, processes or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It is understood that such descriptions are intended to indicate choices among multiple functional alternatives that may be used, and that such choices are not necessarily better, smaller, higher, or more preferred than other choices.

[0029] As used herein, the term "circuitry" may refer to hardware circuits and / or combinations of hardware circuits and software. For example, a circuit may be a combination of analog and / or digital hardware circuits and software / firmware. As a further example, a circuit may be any portion of a hardware processor with software, such as a digital signal processor, software, and memory that work together to perform various functions on a device, such as a terminal device or a network device. In yet another example, a circuit may be a hardware circuit and / or processor, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation, but the software may not be present when not required for operation. As used herein, the term circuitry also encompasses merely a hardware circuit or processor, or a portion of a hardware circuit or processor, and its (or their) accompanying software and / or firmware implementations.

[0030] As mentioned above, it is proposed to evaluate and, if necessary, specify beam management related enhancements for carrier aggregation (CA) and inter-cell beam management. However, how to solve beam failure recovery for CA and inter-cell beam management is a big challenge for reliable communication.

[0031] Generally, for uplink (UL) transmission, one TRP usually corresponds to one SRS resource set. As used herein, the term "single TRP for UL" refers to the use of a single SRS resource set to perform related transmissions (e.g., PUSCH transmissions), and the term "multiple TRP for UL" refers to the use of multiple SRS resource sets to perform related transmissions (e.g., PUSCH transmissions).

[0032] As mentioned above, enhancements to multi-beam operation primarily targeted at FR2 but also applicable to FR1 have been identified and specified to facilitate more efficient (low latency, low overhead) DL / UL beam management within and between cells to support higher UE speeds and / or more configured TCI states: i. Common beam for DL ​​and UL data and control transmission / reception, especially for in-band CA; ii. Uniform TCI framework for DL ​​and UL beam indication; iii. Enhanced signaling mechanisms for the above features to improve latency and efficiency by increasing the use of dynamic control signaling (as opposed to RRC); iv. For inter-cell beam management, a UE can only transmit or receive to a single cell (i.e., serving cell does not change when beam selection is made). This includes L1 only measurements / reports (i.e., no L3 impact) and beam indication associated to cells of any physical cell ID. Beam indication is based on the uniform TCI framework of Rel-17. The same beam measurement / reporting mechanism is reused for m TRPs between cells. In this work, we consider only the intra-DU and intra-frequency cases.

[0033] As mentioned above, as an enhancement to multi-beam operation primarily targeted at FR2 but also applicable to FR1, to support higher intra-cell and L1 / L2 centric inter-cell mobility and / or more configured TCI states, the following features are identified and specified to facilitate more efficient beam management (low latency, low overhead) for DL / UL: i. common beam for DL ​​and UL data and control transmission / reception, especially for in-band CA, ii. a unified TCI framework for DL ​​and UL beam direction, iii. enhanced signaling mechanisms for the above features to improve latency and efficiency by increasing the use of dynamic control signaling (as opposed to RRC).

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

[0035] It is also proposed to support activation of one or more TCI states via a medium access control (MAC) control element (CE) similar to Release.15 / 16, where at least in the case of a single activated TCI state, the activated TCI state applies.

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

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

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

[0039] The TCI field can be used to signal 1) combined DL / UL TCI status, 2) DL-only TCI status (in case of split DL / UL TCI), and 3) UL-only TCI status (in case of split DL / UL TCI).

[0040] Additionally, the following DCI fields are used in Rel-16: DCI format identifier, carrier indicator, bandwidth portion 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.

[0041] It is also proposed to support the UE to report whether it supports TCI update with DCI format 1_1 / 1_2. For a UE that supports TCI update with DCI format 1_1 / 1_2, it shall support TCI update by using DCI 1_1 / 1_2 with DL allocation, and support of the above functionality for TCI update with DCI format 1_1 / 1_2 without DL allocation is optional for the UE.

[0042] In Rel-17 DCI based beam direction, the application time of beam direction is the first slot or first sub-slot that is at least X ms or Y symbols from the last symbol of the acknowledgement of DL / UL beam direction of combining or separating.

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

[0044] According to format 1_1 in clause 7.3.1.2.2 of TS38.212, the transmit configuration indication is 0 bit if the higher layer parameter tci-PresentInDCI is not valid, otherwise it is 3 bits as defined in clause 5.1.5 of [6,TS38.214]. According to format 1_2 in clause 7.3.1.2.3 of TS38.212, the transmit configuration indication is 0 bit if the higher layer parameter tci-PresentDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentDCI-1-2 as defined in clause 5.1.5 of [6,TS38.214].

[0045] The UE receives an activation command which is used to map up to eight TCI states to code points in the DCI field "Transmission Configuration Indication" of one Component Carrier (CC) / DL Bandwidth Part (BWP) or one set of CCs / DL BWPs, respectively, as described in clause 6.1.3.14 of [10, TS38.321]. Once a set of TCI state IDs is activated for a set of CCs / DL BWPs and the applicable 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 in the indicated CCs.

[0046] If the UE supports two TCI states in the codepoints of the DCI field "transmission configuration indication", the UE may receive an activation command as described in clause 6.1.3.24 of [10, TS38.321], which is used to map up to eight combinations of one or two TCI states to the codepoints of the DCI field "transmission configuration indication". The UE is not expected to receive more than eight TCI states in an activation command.

[0047] If the DCI field "transmission configuration indication" exists in the DCI format 1_2 and the number of code points S of the DCI field "transmission configuration indication" of the DCI format 1_2 is smaller than the number of TCI code points activated by the activation command, as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321], only the first S activated code points are applied to the DCI format 1_2. For example, if the number of bits of the DCI field "transmission configuration indication" of the DCI format 1_2 or the number of bits of the upper layer parameter tci-PresentDCI-1-2 is 1 bit, S=2. As another example, if the number of bits of the DCI field "transmission configuration indication" of the DCI format 1_2 or the number of bits of the upper layer parameter tci-PresentDCI-1-2 is 2 bits, S=4. As another example, if the number of bits in the DCI field "transmission setting instruction" of DCI format 1_2 or the number of bits in the upper layer parameter tci-PresentDCI-1-2 is 3 bits, S=8.

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

[0049] An embodiment of the present disclosure provides a solution for solving the above problems and / or one or more other potential problems. According to the solution, in response to a beam failure being detected in at least one cell in a cell group by a terminal device, the terminal device may transmit a beam failure recovery request (BFRQ) to a network device. Here, the BFRQ comprises information of a TRP and / or a cell related to the beam failure detected in the cell. For example, the TRP information may indicate at least one of a number of TRPs related to the beam failure detected in the cell, a TRP index related to the beam failure detected in the cell, whether a new candidate beam is identified in the failed TRP, information on the new candidate beam if a new candidate beam is identified in the failed TRP, etc. As another example, the BFRQ may include at least one of a cell index or cell group information of a cell group related to the detected beam failure, whether a new candidate beam is identified in the failed cell or cell group, information on the new candidate beam if a new candidate beam is identified in the failed cell or cell group, etc.

[0050] 1 illustrates an example communication network 100 in which embodiments of the present disclosure may 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.

[0051] In this specification, the term "terminal device" refers to any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktops, mobile phones, cell phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, internet of things (IoT) devices, internet of everything (IoE) devices, machine type communication (MTC) devices, vehicle-mounted devices for V2X communication (where X means pedestrian, vehicle or infrastructure / network), imaging devices such as digital cameras, gaming devices, music storage and playback devices, internet devices that enable wireless / wired internet access and browsing, etc. For purposes of discussion, some embodiments will be described below with reference to a UE as an example of a terminal device 120.

[0052] As used herein, the term "network equipment" or "base station" (BS) refers to equipment capable of providing or hosting a cell or coverage through which terminal equipment can communicate. Examples of network equipment include, but are not limited to, a Node B (NodeB or NB), an Evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a low power node such as a femto node, a pico node, and the like.

[0053] The communication network 100 further comprises 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 provided for illustrative purposes and is not intended to imply any limitation.

[0054] In some scenarios, the network 100 may support Carrier Aggregation (CA), which aggregates two or more CCs to support a larger bandwidth. For example, in FIG. 1, the network device 110 may provide multiple serving cells to the terminal device 120, including one primary cell (Pcell (: primary cell) or Pscell or Spcell) 101 corresponding to a primary CC and at least one secondary cell (Scell: secondary cell) 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 merely for illustration purposes and does not imply any limitation to the present disclosure. The network 100 may include any suitable number of network devices, terminal devices, and / or serving cells consistent with the implementation of the present disclosure.

[0055] In some other scenarios, the terminal device 120 may establish a connection with two different network devices (not shown in FIG. 1 ) and thus utilize the radio resources of the two network devices. The two network devices may be defined as a master network device and a secondary network device, respectively. The master network device may provide a serving cell group also referred to as a “Master Cell Group (MCG)”. The secondary network device may also provide a serving cell group 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 an MCG or an SCG, respectively. In cases other than dual connectivity operation, the term “SpCell” may refer to a PCell.

[0056] In one embodiment, the terminal device 120 may be connected with 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 a master node, and the other may be 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 is a gNB. Information related to the different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device 120. 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 to the terminal device 120 directly or via the first network device. In one embodiment, information related to the configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related to the reconfiguration of the terminal device set by the second network device may be sent from the second network device directly to the terminal device or via the first network device, and may be sent via any of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) control element (CE), or Downlink Control Information (DCI).

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

[0058] In some embodiments, for downlink transmission, the network device 110 may transmit control information via a PDCCH and / or data via a PDSCH to the terminal device 120. In addition, the network device 110 may transmit one or more reference signals (RS) to the terminal device 120. The RS transmitted from the network device 110 to the terminal device 120 may also be referred to as a "DL RS." Examples of DL RS may include, but are not limited to, a Demodulation Reference Signal (DMRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Phase Tracking Reference Signal (PTRS), a Fine Time-Frequency Tracking Reference Signal (TRS), and the like.

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

[0060] 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-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. Additionally, communications may be performed according to any generation of communications 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, the communication may utilize any suitable wireless communication technology.Wireless communication techniques include, but are 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 techniques now known or developed in the future.

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

[0062] It should be understood that a TRP can also be a panel, and a panel can also refer to an antenna array (having one or more antenna elements). Although some embodiments of the present disclosure are described with reference to multiple TRPs, for example, these embodiments are merely for illustrative purposes to aid one of ordinary skill in the art in understanding and practicing the present disclosure, and are not intended to imply any limitation on the scope of the present disclosure. It should be understood that the present disclosure described herein can be implemented in a variety of ways other than those described below.

[0063] As an enhancement to multi-beam operation primarily targeted at FR2 but also applicable to FR1, to support higher intra-cell and L1 / L2 centric inter-cell mobility and / or more configured TCI states, the following features are identified and specified to facilitate more efficient beam management (low latency, low overhead) for DL / UL: i. Common beam for DL ​​and UL data and control transmission / reception, especially for in-band CA, ii. Uniform TCI framework for DL ​​and UL beam direction, iii. Enhanced signaling mechanisms for the above features to improve latency and efficiency by increasing the use of dynamic control signaling (as opposed to RRC).

[0064] As shown in FIG. 1, for example, the network device 110 may communicate with the terminal device 120 via TRPs 130-1 and 130-2 (hereinafter collectively referred to as "TRP 130" or individually referred to as "TRP 130"). For example, the TRP 130-1 may be referred to as a first TRP and the TRP 130-2 may be referred to as a second TRP. As described above, the network device 110 may provide a group of cells for serving the terminal device 120. In some embodiments, the group of cells may be divided into a first subset of cells associated with the first TRP 130-1 and a second subset of cells associated with the 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.

[0065] The embodiments of the present disclosure may be applied to any suitable scenario. For example, the embodiments of the present disclosure may be implemented in a low-capability NR device. Alternatively, the embodiments of the present disclosure may be implemented in any of the following: New Radio (NR) multiple-input and multiple-output (MIMO), NR Sidelink Enhancements, NR systems at frequencies above 52.6 GHz, NR operation extension to 71 GHz, narrow band-Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) in non-terrestrial networks (NTN), NTN, UE power saving enhancements, NR coverage extension, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB), NR multicast and broadcast services, or enhanced multi-radio dual connectivity.

[0066] It should be understood that the number of network devices, terminal devices, and / or TRPs is for illustrative purposes only and does not imply any limitations to the present disclosure. Communications network 100 may include any suitable number of network devices, terminal devices, and / or TRPs suitable for carrying out implementations of the present disclosure.

[0067] In some embodiments, a TRP may be explicitly associated with different higher layer configuration identities. For example, a higher layer configured identity 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, which are used to distinguish transmissions between different TRPs and the terminal device 120. If the terminal device 120 receives two DCIs from two CORESETs associated with different higher layer configuration identities, the two DCIs may be transmitted or indicated from different TRPs. Furthermore, a TRP may be implicitly identified by a dedicated configuration for a physical channel or signal. For example, a dedicated CORESET, RS, and TCI state associated with a TRP are used to identify transmissions to the terminal device 120 from different TRPs. For example, if the terminal device 120 receives a DCI from a dedicated CORESET, the DCI is indicated from an associated TRP dedicated to that CORESET. In some embodiments, the RS may be at least one of a CSI-RS, an SRS, a positioning RS, an uplink DMRS, a downlink DM-RS, an uplink PTRS, and a downlink PTRS.

[0068] FIG. 2 illustrates a signaling chart 200 according to an embodiment of the present disclosure. As shown in FIG. 2, the network device 110 may transmit at least one configuration to the terminal device 120 (210). In some embodiments, the at least one configuration may indicate at least one of a first list of cells comprising a first cell and a second list of cells, a reference configuration for at least a first spatial reception parameter of the second list of cells that references the first cell, a TCI state pool configured for the reference cell, and a TCI state set. The TCI state set comprises at least one of a first subset of TCI states, where at least one reference signal (RS) in the first subset of TCI states is associated with a first physical cell identity (ID). For example, the configuration may be transmitted from the network device 110 to the terminal device 120 via at least one of Radio Resource Control (RRC) signaling, a Medium Access Control (MAC) control element (CE), or Downlink Control Information (DCI). Terminal device 120 may perform beam failure detection based on the at least one configuration (220). In response to detecting beam failure in at least one cell in the cell group, terminal device 120 may transmit a BFRQ to network device 110 based on the at least one configuration. In some embodiments, the BFRQ may comprise information of the cell and / or the first list of cells or the second list of cells associated with the beam failure detected in the cell or the first list of cells or the second list of cells.

[0069] In some embodiments, the terminal device 120 may be configured with M TRPs in the bandwidth part (BWP) of the cell, where M is a positive integer. For example, 1≦M≦4. In another example, M=2. In some embodiments, each TRP of the M TRPs may be represented by or associated with at least one of the following: a control resource set (CORESET) pool index, a CORESET group identity (ID), a CORESET group, a CORESET set ID, a CORESET set, an SRS resource set, an SRS resource set ID, a TCI state, a group of TCI states, an ID of a reference signal (RS) set for beam failure detection, an ID of an RS set for new / candidate beam identification, spatial relationship information, a spatial relationship information group, a QCL parameter set, an RS group for beam failure detection, an RS group for new / candidate beam identification, etc. In the example shown in FIG. 1B, M=2. In some embodiments, the first TRP 130-1 receives a first CORESET pool index (e.g., one with a value of 0. In another example, a CORESET with no setting for the parameter “CORESET pool index”), a first CORESET group / set / subset ID, a CORESET (e.g., a CORESET with the first CORESET pool index or the first CORESET group / set / subset ID set.In another example, it may be represented by or associated with at least one of: a first group / set / subset of CORESET (for which the parameter "CORESET pool index" or the parameter "CORESET group / set / subset ID" is not set), a first SRS resource set, an ID of the first SRS resource set, a first TCI state, a first group of TCI states, an ID of a first set of reference signals (RSs) for beam failure detection, a first set of reference signals (RSs) for beam failure detection, an ID of a first set of RSs for new / candidate beam identification, a first set of RSs for new / candidate beam identification, first spatial relationship information, a first group of spatial relationship information, a first set of QCL parameters, a first group of RSs for beam failure detection, a first group of RSs for new / candidate beam identification, etc. The second TRP 130-2 may be represented by at least one of a second CORESET pool index (e.g., a value of 1), an ID of a second CORESET group / set / subset, a second group / set / subset of a CORESET (e.g., a CORESET with the second CORESET pool index or the ID of the second CORESET group / set / subset set), a second SRS resource set, an ID of the second SRS resource set, a second TCI state, a second group of TCI states, an ID of a second set of reference signals (RSs) for beam failure detection, a second set of reference signals (RSs) for beam failure detection, an ID of a second set of RSs for new / candidate beam identification, a second set of RSs for new / candidate beam identification, second spatial relationship information, a second group of spatial relationship information, a second set of QCL parameters, a second group of RSs for beam failure detection, a second group of RSs for new / candidate beam identification, etc.

[0070] In some embodiments, the terminal device 120 may be configured with a first TRP (eg, the first TRP 130-1) and a second TRP (eg, the second TRP 130-2) in the BWP of the cell.

[0071] In some embodiments, the terminal device 120 may receive a configuration or activation command, which is used to map up to eight combinations of one or two TCI states to a TCI code point set. For example, the number of TCI code points in a TCI set may be at least one of {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16}. For example, the TCI code point set is indicated in a DCI field "transmission configuration indication." In some embodiments, if at least one TCI code point indicates two TCI states (e.g., a first TCI state and a second TCI state), the terminal device 120 may be served by two TRPs (e.g., a first TRP and a second TRP). For example, the first TCI state is associated with the first TRP, and the second TCI state is associated with the second TRP.

[0072] In the following, the terms "TRP", "CORESET pool index", "CORESET group / set / subset ID", "CORESET group / set / subset", "SRS resource set", "SRS resource set ID", "TCI state", "group of TCI states", "ID of RS set for beam fault detection", "ID of RS set for new / candidate beam identification", "spatial relationship information", "spatial relationship information group", "QCL parameter set", "QCL parameters", "QCL assumptions", "QCL configuration", "RS group for beam fault detection", and "RS group for new / candidate beam identification" can be used interchangeably. The terms "first TRP", "first CORESET pool index", "ID of first CORESET group / set / subset", "first CORESET group / set / subset", "first SRS resource set", "ID of first SRS resource set", "first TCI state", "first TCI state of two TCI states corresponding to a TCI code point", "first group of TCI states", "ID of first set of RSs for beam failure detection", "first set of RSs for beam failure detection", "ID of first set of RSs for new / candidate beam identification", "first set of RSs for new / candidate beam identification", "first spatial relationship information", "first group of spatial relationship information", "first set of QCL parameters", "first group of RSs for beam failure detection", and "first group of RSs for new / candidate beam identification" can be used interchangeably.The terms "second TRP", "second CORESET pool index", "ID of second CORESET group / set / subset", "second CORESET group / set / subset", "second SRS resource set", "ID of second SRS resource set", "second TCI state", "second TCI state of the two TCI states corresponding to the TCI code point", "second group of TCI states", "ID of second set of RSs for beam failure detection", "second set of RSs for beam failure detection", "ID of second set of RSs for new / candidate beam identification", "second set of RSs for new / candidate beam identification", "second spatial relationship information", "second group of spatial relationship information", "second set of QCL parameters", "second group of RSs for beam failure detection", "second group of RSs for new / candidate beam identification" may be used interchangeably. The terms "PUSCH" and "PUSCH MAC CE" may be used interchangeably. The terms "QCL-TypeD", "Spatial Rx parameter", "Spatial receiving parameter" and "Spatial reception parameter" may be used interchangeably.

[0073] 3A-3C show examples according to some embodiments of the present disclosure.

[0074] As shown in FIG. 3A, the terminal device 120 includes a beam interference detection RS set (RS 0_0 , R.S. 0_1 ) and a new / candidate beam identification RS set (RS 1_0 , R.S. 1_1 ) may be set. RS 0_0 and R.S. 0_1 If there is a failure in the RS 1_0 and R.S. 1_1 New beams may be searched for based on

[0075] As shown in FIG. 3B, a timer (BeamFailureDetectionTimer) may be set in the terminal device 120, and if a beam failure instance indication is indicated or received from a lower layer of the terminal device, the value of BFI_COUNTER may be increased by one and the timer may be started or restarted. For example, if the timer has not expired and a beam failure instance indication is indicated or received from a lower layer of the terminal device, the value of BFI_COUNTER may be increased by one and the timer may be started or restarted. In another example, if the timer expires, the value of BFI_COUNTER is set to 0.

[0076] As shown in Figure 3C, if the value of BFI_COUNTER is greater than or equal to the maximum value (beamFailureInstanceMaxCount), a beam failure recovery procedure is triggered. For example, the value of BFI_COUNTER is set to 0 when the beamFailureDetectionTimer expires, or when the beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any RS used for beam failure detection are reset.

[0077] As specified in the 3GPP specification (TS38.214), the UE can configure a list of up to M TCI-State configurations in the higher layer parameter PDSCH-Config to decode the PDSCH according to the detected PDCCH with the intended DCI for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State includes a parameter to configure a quasi-co-location relationship between one or two downlink reference signals and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the channel state information reference signal (CSI-RS) resource. The quasi-co-location relationship is configured by the higher layer parameter qcl-Type1 of the first downlink (DL) RS and qcl-Type2 of the second DL RS (if configured). In the case of 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-colocation type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info and can take 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 Rx parameters}

[0078] The UE receives an activation command as described in the "UE specific PDSCH MAC CE TCI state activation / deactivation" clause (e.g., subclause 6.1.3.14) of [TS38.321] or the "UE specific PDSCH MAC CE TCI state activation / deactivation extension" clause (e.g., subclause 6.1.3) of [TS38.321]. The activation command is used to map up to eight TCI states to code points in the DCI field "Transmission configuration indication" of one CC / DL BWP or one set of CC / DL BWPs, respectively. Once a set of TCI state IDs is activated for a set of CC / DL BWPs and the applicable 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 in the indicated CC.

[0079] If the UE supports two TCI states in the codepoint of the DCI field "Transmission configuration indication", the UE may receive an activation command as described in the "UE specific PDSCH MAC CE TCI state activation / deactivation" or "UE specific PDSCH MAC CE extended TCI state activation / deactivation" clauses of [TS38.321] (e.g., clause 6.1.3.14 or clause 6.1.3 items), which is used to map up to eight combinations of one or two TCI states to the codepoint of the DCI field "Transmission configuration indication". The UE is not expected to receive more than eight TCI states in an activation command.

[0080] If the DCI field "transmission configuration indication" is present in DCI format 1_2 and the number of code points S of the DCI field "transmission configuration indication" of DCI format 1_2 is smaller than the number of TCI code points activated by the activation command, as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321], only the first S activated code points are applied to DCI format 1_2.

[0081] 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 tif858, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the synchronization signal / physical broadcast channel (SS / PBCH) block determined in the initial access procedure for qcl-Type set to "typeA" and also for qcl-Type set to "typeD", if applicable.

[0082] In some embodiments, if the UE has the higher layer parameter tci-PresentInDCI or tci-PresentInDCI-ForFormat1_2 set as "enabled" for the CORESET that schedules the PDSCH, the UE assumes that the TCI field is present in the DCI of the PDCCH transmitted in 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 that schedules the PDSCH, or if the PDSCH is scheduled by DCI (e.g., DCI format 1_0), the UE assumes that the TCI field is not present in the DCI of the PDCCH transmitted in 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 that does not have a TCI field and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is greater than or equal to a threshold timeDurationForQCL, if applicable, where the threshold is based on the reported UE capabilities ([13, ​​TS38.306]), then for the purpose of determining the quasi-co-location of the PDSCH antenna ports, the UE shall assume that the TCI state or QCL assumptions of the PDSCH are the same as the TCI state or QCL assumptions applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0083] If tci-PresentInDCI is set to "enabled" or tci-PresentInDCI-ForFormat1_2 is set for a CORESET scheduling a PDSCH, and the time offset between reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL, if applicable, then 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 also for "QCL-typeD", if applicable. The value of timeDurationForQCL is based on the reported UE capabilities.

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

[0085] If a PDSCH is scheduled by a DCI format with a TCI field and the TCI field in the DCI of the scheduling component carrier points to an activated TCI state of the scheduled component carrier or DL ​​BWP, the UE shall use the TCI-State according to the value of the "Transmission Configuration Indication" field in the detected PDCCH with DCI to determine the quasi-co-location of the PDSCH antenna ports. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on the reported UE capabilities ([TS38.306]), the UE shall assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS of the TCI state with respect to the QCL type parameter given by the indicated TCI state. If a single-slot PDSCH is configured for the UE, the indicated TCI state shall be based on the activated TCI state in the slot with the scheduled PDSCH. If a 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 all slots with scheduled PDSCH.If a UE is configured with a CORESET associated with a search space set for cross-carrier scheduling, and a PDCCH carrying a scheduling DCI and a PDSCH scheduled by that DCI are transmitted on the same carrier, the UE expects tci-PresentInDCI to be set as "enabled" or tci-PresentInDCI-ForFormat1_2 to be set for the 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 PDCCH detected in the search space set and the corresponding PDSCH to be greater than or equal to a threshold timeDurationForQCL.

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

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

[0088] -If the UE is configured with enableDefaultTCIStatePerCoresetPoolIndex and is configured by the higher layer parameter PDCCH-Config containing two different values ​​of coresetPoolIndex in different ControlResourceSets, then:

[0089] -The UE may assume that the DM / RS port of the PDSCH associated with the value of coresetPoolIndex of the serving cell is quasi-colocated with the RS in the latest slot in which one or more CORESETs associated with the same value of coresetPoolIndex as the PDCCH scheduling the PDSCH in the active BWP of the serving cell are monitored by the UE with respect to the QCL parameters used for the PDCCH quasi-colocation indication of the CORESET with the lowest controlResourceSetId associated with the monitored search space among the CORESETs with the same value of coresetPoolIndex as the PDCCH scheduling the PDSCH. In this case, if the "QCL-TypeD" of the PDSCH DM-RS is different from that of the PDCCH DM-RS that overlaps at least one symbol and they are associated with the same coresetPoolIndex, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET. This also applies to the intra-band CA case (when the PDSCH and CORESET are on different component carriers).

[0090] - if enableTwoDefaultTCI-States is configured in the UE and at least one TCI codepoint indicates two TCI states, the UE may assume that the PDSCH of the serving cell or the DM-RS port of a PDSCH transmission opportunity is quasi-collocated with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest codepoint of the TCI codepoints containing two different TCI states. If the UE is configured with the higher layer parameter repetitionScheme set to "tdmSchemeA" or the UE is configured with the higher layer parameter repetitionNumber, the mapping of TCI states to PDSCH transmission opportunities is determined according to clause 5.1.2.1 based on the activated TCI state in the slot with the first PDSCH transmission opportunity by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint of the TCI codepoints containing two different TCI states. In this case, if the "QCL-TypeD" of 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 by at least one symbol, the UE is expected to prioritize the reception of the PDCCH associated to that CORESET. This also applies to the intra-band CA case (when the PDSCH and CORESET are on different component carriers).

[0091] - In all the above cases, if none of the TCI states configured for the serving cell of a scheduled PDSCH has qcl-Type set to "typeD", the UE shall derive other QCL assumptions from the TCI state indicated for that scheduled PDSCH, regardless of the time offset between reception of the DL DCI and the corresponding PDSCH.

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

[0093] -timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. PDCCH <μ PDSCH If , the additional timing delay is added to timeDurationForQCL. TIFF2024541062000003.tif1421 is added, where d is defined in section 5.2.1.5.1a-1, otherwise d is zero.

[0094] - In either case, if the offset between reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and no TCI field is present in the DL DCI, the UE shall derive the 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.

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

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

[0097] -"type C" having SS / PBCH blocks and, if applicable, "type D" having CSI-RS resources in the NZP-CSI-RS-ResourceSet with the higher layer parameter repetition set, or

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

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

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

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

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

[0103] - "typeB" with CSI-RS resources in NZP-CSI-RS-ResourceSet with higher layer parameter trs-Info if "typeD" is not applicable.

[0104] For CSI-RS resources in the NZP-CSI-RS-ResourceSet with the higher layer parameter repetition set, the UE should expect the TCI-State to indicate one of the following quasi-colocation types:

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

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

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

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

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

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

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

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

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

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

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

[0116] If a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by that 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 PDCCH subcarrier spacing is 15 kHz, 8 symbols if the PDCCH subcarrier spacing is 30 kHz, and 14 symbols if the PDCCH subcarrier spacing is 60 kHz. For example, if the symbol is a PDCCH symbol or the symbol is based on the subcarrier spacing of the PDCCH (e.g., as defined in Table 5.2.1.5.1a-1 of TS38.214), then in both cases where tci-PresentInDCI is set to "enabled" and the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and where tci-PresentInDCI is not configured, the UE shall derive the 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.

[0117] When the UE is configured by the higher layer parameter RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", "TDMSchemeA" as specified in the 3GPP specification (TS38.214), two TCI states of a codepoint in the DCI field "Transmission configuration indication" and a DM-RS port in one Code Domain Multiplexing (CDM) group in the DCI field "Antenna port" are indicated to the UE. When two TCI states are indicated in the DCI and the UE is set to "FDMSchemeA", the UE shall receive a single PDSCH transmission opportunity for the TB in each TCI state associated with a non-overlapping frequency domain resource allocation as described in the "Physical resource block (PRB) bundling" clause of TS38.214 (e.g., subclause 5.1.2.3). If two TCI states are indicated in the DCI and the UE is set to "FDMSchemeB", the UE shall receive two PDSCH transmission opportunities of the same TB in the respective TCI states associated with PDSCH transmission opportunities having non-overlapping frequency domain resource allocations with respect to other PDSCH transmission opportunities as described in the "Physical resource block (PRB) bundling" section (e.g., section 5.1.2.3) of TS38.214. If two TCI states are indicated in the DCI and the UE is set to "TDMSchemeA", the UE shall receive two PDSCH transmission opportunities of the same TB in the respective TCI states associated with PDSCH transmission opportunities having non-overlapping time domain resource allocations with respect to other PDSCH transmission opportunities as described in the "Resource allocation in the time domain" section (e.g., section 5.1.2.1) of TS38.214, and both PDSCH transmission opportunities shall be received within a given slot.

[0118] If the UE is configured by higher layer parameter PDSCH-config indicating at least one entry of pdsch-TimeDomainAllocationList containing RepNumR16 of PDSCH-TimeDomainResourceAllocation, the UE may expect one or two TCI states of codepoints of DCI field "Transmission configuration indication" to be indicated together with DCI field "Time domain resource allocation" and DM-RS ports in one CDM group of DCI field "Antenna port". "Time domain resource allocation" indicates an entry of pdsch-TimeDomainAllocationList containing RepNum16 of PDSCH-TimeDomainResourceAllocation. If two TCI states are indicated in the DCI with "Transmission configuration indication" field, the UE may expect to receive multiple slot level PDSCH transmission opportunities of the same TB with two TCI states used across multiple PDSCH transmission opportunities as defined in clause "Resource allocation in the time domain" of TS38.214 (e.g., clause 5.1.2.1). If one TCI state is indicated in the DCI with the "Transmission Configuration Indication" field, the UE may expect to receive multiple slot-level PDSCH transmission opportunities of the same TB in one TCI state used across multiple PDSCH transmission opportunities as defined in the "Resource Allocation in the Time Domain" clauses of TS38.214 (e.g., clause 5.1.2.1).

[0119] If the DCI field "Time domain resource allocation" indicating one entry of pdsch-TimeDomainAllocationList including RepNumR16 of PDSCH-TimeDomainResourceAllocation is not indicated to the UE, and if two TCI states of codepoints of the DCI field "Transmission configuration indication" and DM-RS ports in two CDM groups of the DCI field "Antenna port" are indicated to the UE, the UE may expect to receive a single PDSCH, where the association of DM-RS ports with TCI states is as defined in the "DM-RS reception procedures" clause of TS38.214 (e.g., subclause 5.1.6.2).

[0120] If the DCI field "Time domain resource allocation" indicating one entry of pdsch-TimeDomainAllocationList including RepNumR16 of PDSCH-TimeDomainResourceAllocation is indicated to the UE, and if the TCI state of one of the codepoints of the DCI field "Transmission configuration indication" is indicated to the UE, the UE procedures for receiving the PDSCH upon detection of a PDCCH shall comply with the "UE procedures for receiving the physical downlink shared channel" clauses of TS38.214 (e.g. clause 5.1).

[0121] In the following, the terms "FDMSchemeA" and "Scheme 2a" can be used interchangeably. The terms "FDMSchemeB" and "Scheme 2b" can be used interchangeably. The terms "TDMSchemeA" and "Scheme 3" can be used interchangeably. The terms "RepNumR16" and "Scheme 4" can be used interchangeably.

[0122] As specified in the 3GPP specification (TS38.214), when the UE is configured by the higher layer parameter RepSchemeEnabler set to "TDMSchemeA" and the UE is indicated with DM-RS ports in one CDM group in the DCI field "antenna port", the number of PDSCH transmission opportunities is derived by 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 opportunities, where the first TCI state applies to the first PDSCH transmission opportunity, and the resource allocation in the time domain of the first PDSCH transmission opportunity follows the "resource allocation in the time domain" clause of TS38.214 (e.g., section 5.1.2.1). The second TCI state applies to the second PDSCH transmission opportunity, and the second PDSCH transmission opportunity shall have the same number of symbols as the first PDSCH transmission opportunity. The value of StartingSymbolOffsetK is sent to the UE by higher layers. If TIFF2024541062000004.tif64 is set, the UE shall It must be determined that the first symbol of the second PDSCH transmission opportunity starts after 64 symbols. The value is determined via the higher layer parameter StartingSymbolOffsetK. If TIFF2024541062000006.tif64 is not set, the UE It shall be assumed that TIFF2024541062000007.tif64=0. The UE is not expected to receive more than two PDSCH transmission layers for each PDSCH transmission opportunity. For two PDSCH transmission opportunities, the applied redundancy version is derived according to Table 5.1.2.1-2 of TS38.214, where n=0,1 applies to the first and second TCI states, respectively. Otherwise, the UE is expected to receive a single PDSCH transmission opportunity, and the resource allocation in the time domain shall follow the "Resource allocation in the time domain" clause of TS38.214 (e.g., clause 5.1.2.1).

[0123] As specified in the 3GPP specification (TS38.214), the UE is configured by the higher layer parameter PDSCH-config indicating at least one entry of pdsch-TimeDomainAllocationList containing RepNumR16 of PDSCH-TimeDomainResourceAllocation. If two TCI states are indicated by the DCI field "Transmission configuration indication" with the DCI field "Time domain resource allocation" indicating one entry of pdsch-TimeDomainAllocationList containing RepNumR16 of PDSCH-TimeDomainResourceAllocation and the DM-RS port in one CDM group in the DCI field "Antenna port", the same SLIV (Start and Length Indicator Value) applies for all PDSCH transmission opportunities, the first TCI state applies to the first PDSCH transmission opportunity, and the resource allocation in the time domain of the first PDSCH transmission opportunity is according to the "Resource allocation in the time domain" clause of TS38.214 (e.g., subclause 5.1.2.1). If the value indicated in RepNumR16 of PDSCH-TimeDomainResourceAllocation is equal to 2, the second TCI state is applied to the second PDSCH transmission opportunity. If the value indicated in RepNumR16 of PDSCH-TimeDomainResourceAllocation is greater than 2, the UE may be further configured to enable CycMapping or SeqMapping of RepTCIMapping. If CycMapping is enabled, the first and second TCI states are applied to the first and second PDSCH transmission opportunities, respectively, and the same TCI mapping pattern is continued for the remaining PDSCH transmission opportunities. If SeqMapping is enabled, the first TCI state is applied to the first and second PDSCH transmissions, the second TCI state is applied to the third and fourth PDSCH transmissions, and the same TCI mapping pattern is continued for the remaining PDSCH transmission opportunities. The UE may expect each PDSCH transmission opportunity to be limited to two transmission layers.For all PDSCH transmission opportunities associated with the first TCI state, the applied redundancy version is derived according to Table 5.1.2.1-2 of [TS38.214], where n is counted considering only PDSCH transmission opportunities associated with the first TCI state. The redundancy version for PDSCH transmission opportunities associated with the second TCI state is derived according to Table 5.1.2.1-3 of [TS38.214], where for each redundancy version rv. s The additional shift operation for is set by the higher layer parameter RVSeqOffset, and n is counted considering only the PDSCH transmission opportunities associated with the second TCI state. If one TCI state is indicated by the DCI field "Transmission configuration indication" with the DCI field "Time domain resource allocation" indicating one entry of pdsch-TimeDomainAllocationList including RepNumR16 of PDSCH-TimeDomainResourceAllocation and with the DM-RS port in one CDM group in the DCI field "Antenna port", the same SLIV applies for all PDSCH transmission opportunities and the first PDSCH transmission opportunity is according to the "Resource allocation in the time domain" clause of TS38.214 (e.g., clause 5.1.2.1) and the same TCI state applies for all PDSCH transmission opportunities. The UE may expect that each PDSCH transmission opportunity is limited to two transmission layers. For every PDSCH transmission opportunity, the applied redundancy version is derived according to Table 5.1.2.1-2 of [TS38.214], where n is counted considering the PDSCH transmission opportunity. Otherwise, the UE is expected to receive a single PDSCH transmission opportunity and the resource allocation in the time domain is according to the "Resource allocation in the time domain" clause of TS38.214 (e.g., clause 5.1.2.1). TIFF2024541062000008.tif51167 TIFF2024541062000009.tif70168

[0124] For a UE configured with the higher layer parameter RepSchemeEnabler set to "FDMSchemeA" or "FDMSchemeB" as specified in the 3GPP specification (TS38.214), two TCI states in the codepoints of the DCI field "Transmission configuration indication" and a DMRS port in one CDM group in the DCI field "Antenna port" are indicated to the UE. If TIFF2024541062000010.tif715 is determined as "broadband", the first TIFF2024541062000011.tif1313 PRBs are assigned to the first TCI state, the remaining TIFF2024541062000012.tif1313 PRBs are assigned to the second TCI state, where n PRB is the total number of PRBs allocated to the UE. If TIFF2024541062000013.tif715 is determined as one of {2,4}, then the even PRGs within the allocated frequency domain resources are assigned to the first TCI state and the odd PRGs within the allocated frequency domain resources are assigned to the second TCI state. The UE is not expected to receive more than two PDSCH transmission layers for each PDSCH transmission opportunity.

[0125] For a UE configured by higher layer parameter RepSchemeEnabler set to "FDMSchemeB", when the UE is indicated with two TCI states in the DCI field "Transmission configuration indication" codepoints and DM-RS ports in one CDM group in the DCI field "Antenna port", each PDSCH transmission opportunity shall follow the "Physical downlink shared channel" clauses (e.g., clause 7.3.1) of [TS38.211] for mapping to resource elements determined by the PRBs assigned to the corresponding TCI state of the PDSCH transmission opportunity. Also, the UE should expect only up to two code blocks per PDSCH transmission opportunity if a single transmission layer is scheduled, and only a single code block per PDSCH transmission opportunity if two transmission layers are scheduled. For the two PDSCH transmission opportunities, the applied redundancy version is derived according to Table 5.1.2.1-2 of [TS38.214], where n=0,1 applies to the first and second TCI state, respectively.

[0126] As specified in the 3GPP specification (TS38.213), for CORESETs other than the CORESET with index 0, - If the UE is not provided with a TCI state configuration by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for CORESET, or is provided with an initial configuration of multiple TCI states for CORESET by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but 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 multiple TCI state configurations via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for CORESET as part of a reconfiguration with sync procedure but 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.

[0127] In some embodiments, for a CORESET with index 0, the UE assumes that the DM-RS antenna ports for PDCCH reception in the CORESET are quasi-co-located with the following: - one or more DL RSs configured by the TCI state (TCI state is indicated by the MAC CE Activation Order for the CORESET, if any), or - SS / PBCH blocks identified by the UE during the most recent random access procedure that was not initiated by a PDCCH order triggering non-contention random access, if no MAC CE activation order has been received indicating a TCI state of CORESET after the most recent random access procedure.

[0128] In some embodiments, for a CORESET other than the CORESET with index 0, if a single TCI state is provided to the UE for the CORESET or if the UE receives a MAC CE activation command for one of the TCI states provided for the CORESET, the UE assumes that the DM-RS antenna port associated with PDCCH reception in the 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 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. If the UE receives a MAC CE activation command for one of the TCI states, the UE Apply the activation command in the first slot after TIFF2024541062000014.tif869, where k is the slot in which the UE transmits a PUCCH with HARQ-ACK information for the PDSCH providing the activation command, and μ is the SCS setting of the PUCCH. The active BWP is defined as the BWP active in that slot when the activation command is applied.

[0129] In some embodiments, when a UE is configured for single-cell operation or for operation with carrier aggregation in the same frequency band and monitors PDCCH candidates in overlapping PDCCH monitoring opportunities of multiple CORESETs with the same or different qcl-Type set to the "typeD" characteristic in the active DL BWP of one or more cells, the UE monitors PDCCH only in a CORESET and any other CORESETs from the multiple CORESETs with qcl-Type set to the same "typeD" characteristic as the CORESET in the active DL BWP of a cell from one or more cells. -CORESET corresponds to the lowest indexed CSS set in the lowest indexed cell containing a CSS, if any, otherwise corresponds to the lowest indexed USS set in the lowest indexed cell. The index of the lowest USS set is determined over all USS sets that have at least one PDCCH candidate in overlapping PDCCH monitoring occasions. For purposes of determining the -CORESET, the SS / PBCH block is considered to have a different QCL "type D" characteristic than the CSI-RS. For purposes of determining the CORESET, a first CSI-RS associated with an SS / PBCH block in a first cell and a second CSI-RS in a second cell also associated with the SS / PBCH block are assumed to have the same QCL “type D” characteristics. The allocation of non-overlapping CCEs and PDCCH candidates for PDCCH monitoring follows all search space sets associated with multiple CORESETs in the active DL BWP of one or more cells. The number of active TCI states is determined from multiple CORESETs.

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

[0131] In some embodiments, there is an application timing for the beam indication or the TCI status indication. In some embodiments, the application timing may be the first slot or the first sub-slot after at least X ms or Y symbols from the last symbol of the confirmation of the DL / UL beam indication of combining or separating. For example, Y may be an integer, where 1<=Y<=336. In some embodiments, the slot may include 12 or 14 symbols. In some embodiments, the sub-slot 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 by the DCI of the PDCCH. For example, the DCI of the 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 the first sub-slot should be commensurate with the capabilities of the terminal device. In some embodiments, the confirmation of the DL / UL beam indication of combining or separating may be a confirmation of the PDSCH scheduled by the DCI. For example, when the DCI schedules a PDSCH. In some embodiments, the confirmation of the DL / UL beam indication of combining or separating may be a confirmation of the DCI, for example, when the DCI does not schedule the PDSCH.

[0132] In some embodiments, the terminal device may receive or detect a DCI (e.g., denoted as “DCI_t”) in the PDCCH. The DCI indicates a combined DL / UL TCI state, or a split 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, a first time threshold may indicate a predefined / configured period after the first or last symbol of the PDCCH, or the first or last symbol of the confirmation of the indication. In some embodiments, the indicated combined DL / UL TCI state or split DL / UL TCI state or DL ​​TCI state or 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 an application timing or the first time threshold. For example, if a combined DL / UL TCI state is indicated in the 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 first time threshold. As another example, if a DL TCI state 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 first time threshold. As another example, if a UL TCI state is indicated in the DCI, the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing or the first time threshold. As 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 an application timing or a first time threshold, and the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after an application timing or a first time threshold.

[0133] In some embodiments, the terminal device 120 may receive an indication of a downlink TCI state (or beam or QCL parameter set), where the source reference signal of the TCI state provides QCL information for reception on at least the PDSCH and all CORESET of component carriers (CCs), e.g., the PDSCH is dedicated or UE-specific.

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

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

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

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

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

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

[0140] In some embodiments, a synchronization signal / physical broadcast channel (SS / PBCH) block may be referred to as an SSB in this disclosure.

[0141] In some embodiments, the terminal device 120 may be configured with a plurality of downlink TCI states (e.g., denoted as M, where M is a positive integer, e.g., M may be 2, 3, or 4), and the terminal device 120 may be configured with a plurality of uplink TCI states (e.g., denoted as N, where N is a positive integer, e.g., N may be 2, 3, or 4), and / or the terminal device 120 may receive an indication indicating one out of M downlink TCI states and one out of N uplink TCI states, where a source reference signal in each of the M DL TCI states or the indicated one DL TCI state provides QCL information for reception on at least a subset of a PDSCH and / or a CORESET of component carriers (CCs), and a source reference signal in each of the N TCI states or the indicated one UL TCI state provides a basis for determining an uplink transmit spatial filter for at least a subset of a PUSCH based on a dynamic grant or a configuration grant and / or a PUCCH in a CC. For example, the PUCCH is dedicated or UE specific. As another example, the PDSCH is dedicated or UE specific.

[0142] In the following, DCI_t may be used to describe DCI for joint DL / UL TCI status indication or split DL / UL TCI status indication. In the following, the terms "DCI", "PDCCH", "DCI_t", "DCI for joint DL / UL TCI status indication", "DCI for split DL / UL TCI status indication", "DCI for DL ​​TCI status indication", "DCI for UL TCI status indication", "PDCCH for joint DL / UL TCI status indication", "PDCCH for split 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.

[0143] In some embodiments, the DCI may be used to indicate a TCI state of a combined DL / UL TCI status indication or a split DL / UL TCI status indication. And the DCI may 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.

[0144] In some embodiments, the DCI may be used to indicate the TCI status of a combined DL / UL TCI status indication or a split DL / UL TCI status indication, and 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.

[0145] In some embodiments, if the decoding of DCI_t or the decoding of a 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 the application timing.

[0146] In some embodiments, the 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 joint DL / UL TCI state indication or a split DL / UL TCI state indication. And the DCI may not schedule a PDSCH (e.g., DCI format 1_1 and format 1_2). In some embodiments, if the reception / decoding of the DCI is successful, the terminal device 120 may report an ACK. In some embodiments, if the reception / decoding of the DCI is unsuccessful, the terminal device 120 may report a NACK. For example, the ACK and / or NACK may be reported on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). In some embodiments, the type of the HARQ codebook may be configured in the terminal device 120. 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-shot feedback). For example, the type may be set via at least one of RRC, MAC CE, and DCI. In some embodiments, the DCI is received / detected on the PDCCH.

[0147] In some embodiments, the terminal device 120 may be configured / indicated with a first TCI state for reception of all or a subset of the PDSCH and / or CORESET. The terminal device 120 may then receive or detect a PDCCH in the first TCI state, where the PDCCH is in the first CORESET. In some embodiments, the terminal device 120 may be indicated with a second TCI state for the 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, the terminal device 120 may report the decoding result or HARQ-ACK information for at least one of the DCI, the PDCCH, or the first PDSCH to the network device 110. For example, the decoding result or HARQ-ACK information may be transmitted / reported in the PUCCH or the second PUSCH. In some embodiments, after the applied timing or after the first time threshold, terminal device 120 may receive a PDSCH and / or all or a subset of the CORESET in the second TCI state. For example, terminal device 120 may receive another PDCCH in the second TCI state, where the other PDCCH is in the second CORESET. As another example, terminal device 120 may receive another PDCCH in the second TCI state, where the other PDCCH is in the first CORESET.

[0148] In some embodiments, terminal device 120 may receive an indication of a first TCI state, and the 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 at a first monitoring occasion for a first search space and / or an associated scheduling or PDSCH scheduled by the 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 QCL assumption may be associated with a second physical cell ID. In some embodiments, terminal device 120 may monitor or receive a second PDCCH at a second monitoring occasion for a second search space and / or an associated scheduling scheduled by the second PDCCH based on a condition.

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

[0150] 4A-4B show examples according to some embodiments of the present disclosure.

[0151] As shown in FIG. 4A, TCI state 1 may be set / indicated in the terminal device 120. For example, TCI state 1 is applied to reception of the PDSCH and / or all or a subset of the CORESET. Then, the terminal device 120 may receive or detect the PDCCH 411 in the TCI state 1. Then, the PDCCH 411 or the DCI detected in the PDCCH 411 may indicate TCI state 2. Then, the PDCCH 411 or the DCI detected in the PDCCH 411 may schedule the PDSCH 412. Then, the terminal device 120 may report a HARQ-ACK 413 for the PDSCH 412 to the network device 110. Then, after application timing 414, the terminal device 120 may receive the PDSCH and / or all or a subset of the CORESET in the TCI state 2. For example, the application timing 414 may be based on a first threshold and at least one of the first or last symbol of the PDCCH 411 and the first or last symbol of the PUCCH or PUSCH for reporting the HARQ-ACK 413. For example, the HARQ-ACK information may be an acknowledgement.

[0152] As shown in FIG. 4B, TCI state 1 may be set / indicated in the terminal device 120. For example, TCI state 1 is applied to reception of the PDSCH and / or all or a subset of the CORESET. Then, the terminal device 120 may receive or detect the PDCCH 421 in the TCI state 1. Then, the PDCCH 421 or the DCI detected in the PDCCH 421 may indicate TCI state 2. For example, the PDCCH 421 or the DCI detected in the PDCCH 421 may not schedule the PDSCH. Then, the terminal device 120 may report a HARQ-ACK 422 for the PDCCH 421 to the network device 110. Then, after application timing 423, the terminal device 120 may receive the PDSCH and / or all or a subset of the CORESET in the TCI state 2. For example, the application timing 423 may be based on a first threshold and at least one of the first or last symbol of the PDCCH 421 and the first or last symbol of the PUCCH or PUSCH for reporting the HARQ-ACK 422. For example, the HARQ-ACK information may be an acknowledgement.

[0153] In some embodiments, the terminal device 120 may be configured with a first list of cells, which may comprise a first cell and a second list of cells. For example, there may be C cells in the second list of cells, where C is a positive integer, e.g., 1<=C<=32.

[0154] In some embodiments, at least one TCI state of at least one cell in the second list may reference the first cell. In some embodiments, the first cell may be a reference cell of the second list of cells. In some embodiments, there may be at least one TCI state configured on the first cell, and the TCI state of the at least one cell in the second list may reference one of the at least one TCI state configured on the first cell. In some embodiments, there may be a list of TCI states configured on at least one cell in the second list, and the TCI state of the at least one cell (e.g., the TCI state is configured with an identity (ID) value of ID_1) may reference or correspond to the TCI state of the first cell (e.g., the TCI state is configured with the same ID value as ID_1 of the first cell). In some embodiments, at least one cell in the second list may be referred to as the second cell in this disclosure.

[0155] In some embodiments, at least for the source RS and / or quasi co-location (QCL) information with qcl-Type set to qcl-TypeA, the RS configured in the second cell is applied to the source RS. For example, the index of the RS associated with the TCI state of the second cell may be the same as or different from the index of the RS associated with the TCI state of the first cell. An example may be shown in Table 1. For example, the cell index and / or BWP ID associated with the TCI state of the second cell may not exist. As another example, the cell index and / or BWP ID associated with the TCI state of the second cell may be set, and the value may be ignored. TIFF2024541062000015.tif39156

[0156] In some embodiments, the ID set in the TCI state may be a non-negative integer, e.g., 0<=ID<=191. In some embodiments, ID_1, ID_2..., ID_n are non-negative integers, e.g., 0<=ID_1<=191. For example, 0<=ID_2<=191. For example, 0<=ID_n<=191.

[0157] In some embodiments, for a source RS and / or QCL information with qcl-Type set to qcl-TypeD, if the source RS and / or QCL information is associated with a TCI state of a second cell, the RS set for the first cell is applied to the source RS if the cell index is set as the index of the first cell. An example can be shown in Table 2. TIFF2024541062000016.tif30156

[0158] In some embodiments, for a source RS and / or QCL information with qcl-Type set to qcl-TypeD, if the source RS and / or QCL information is associated with a TCI state of a second cell, the cell index is set as the index of the first cell, and if BWP-ID is set to the value "bwp_id1" or "absent", the RS set in the active BWP of the first cell is applied to the source RS. In some embodiments, bwp_id1 is a non-negative value. For example, bwp_id1 may be at least one of {0, 1, 2, 3, 4}. For example, the value set in BWP-ID is ignored. In some embodiments, for source RS and / or QCL information with qcl-Type set to qcl-TypeD, if the source RS and / or QCL information is associated with a TCI state of a second cell, if the cell index is set as the index of the first cell and the BWP-ID is set with the value "bwp_id1", then the RS set in the BWP with the same value "bwp_id1" of the first cell is applied to the source RS. In some embodiments, for source RS and / or QCL information with qcl-Type set to qcl-TypeD, if the source RS and / or QCL information is associated with a TCI state of a second cell, if the cell index is set as the index of the first cell, then the BWP-ID is not expected to be set to "absent".

[0159] In some embodiments, for a source RS and / or QCL information with qcl-Type set to qcl-TypeD, if the source RS and / or QCL information is associated with a TCI state of a second cell, the RS set in the first cell is applied to the source RS if the cell index is set as the index of the first cell. In some embodiments, the first cell may have a TCI state with TCI state ID_1 set, and the second cell may have a TCI state with TCI state ID_1 set. In some embodiments, the first cell may have a first RS with TCI state ID_1 set, and the first RS is set to ID1_1. In some embodiments, the second cell may have a second RS with TCI state ID_1 set, and the second RS is set to ID2_1. In some embodiments, if TCI state ID_1 is indicated / activated / applied for the first list of cells and / or the first cell and / or the second cell, then in the second cell, the first RS of the first cell may be applied to the source RS of qcl-TypeD. In some embodiments, if TCI state ID_1 is indicated / activated / applied for the first list of cells and / or the first cell and / or the second cell, in the second cell, a third RS of the first cell may be applied as a source RS of qcl-TypeD. For example, the third RS is an RS with ID2_1 configured in the first cell. In some embodiments, the value of ID2_1 may be ignored. In some embodiments, the value of ID2_1 may be assumed to be the same as ID1_1.

[0160] In some embodiments, there may be a list of TCI states configured for the second cell, and the terminal device 120 may expect or assume that the presence and / or value of the cell configured in the list of TCI states and / or the value of the BWP-ID configured in the list of TCI states are the same.

[0161] In some embodiments, the terminal device 120 may be configured with a common configuration for reference in the second cell. For example, the common configuration may apply to a list of TCI states to be configured / indicated / activated for the first cell and / or the second cell. For example, the list of TCI states may be a pool of Rel-17 TCI states configured in the first cell. In some embodiments, the common configuration may be configured with a cell index and / or a BWP-ID.

[0162] In some embodiments, at least in the case of source RS and / or QCL information with qcl-Type set to qcl-TypeA, the RS configured in the second cell is applied to the source RS. For example, there may be no configuration of the index of the RS associated with the TCI state of the second cell. In some embodiments, there may be a TCI state with TCI state ID_1 set in the first cell. For example, there may be no configuration of the TCI state (with TCI state ID_1 set) in the second cell. In some embodiments, there may be a first RS configured in TCI state ID_1 of the first cell, and the index of the RS associated with TCI state ID_1 of the first cell may be set to ID1_1. In some embodiments, when TCI state ID_1 is indicated / activated and applied to the first cell and / or the second cell, the RS configured in the second cell with the same value as ID1_1 may be applied to the source RS. For example, in the case of qcl-TypeA for the second cell.

[0163] In some embodiments, for source RS and / or QCL information with qcl-Type set to qcl-TypeD, the RS configured in the first cell is applied to the source RS. In some embodiments, there may be a TCI state with TCI state ID_1 configured in the first cell. For example, the second cell may not have a TCI state (TCI state ID_1 configured). In some embodiments, there may be a first RS configured in TCI state ID_1 in the first cell, and the index of the RS associated with TCI state ID_1 in the first cell may be set to ID1_1. In some embodiments, when TCI state ID_1 is indicated / activated and applied to the first cell and / or the second cell, the RS with the same value as ID1_1 configured in the first cell may be applied to the source RS. For example, in the case of qcl-TypeD for the second cell.

[0164] In some embodiments, the terminal device 120 may be configured with a first list of TCI states (e.g., Rel-17 TCI states) and a second list of TCI states (e.g., Rel-15 / 16 TCI states) for the first cell. In some embodiments, when a TCI state in the first list is indicated / activated, the TCI state may be applied to the first cell and the second cell after the application timing. In some embodiments, when a TCI state in the second list is indicated / activated, the TCI state may be applied to the first cell (e.g., the TCI state may be applied to non-UE dedicated channels and / or UE dedicated channels and / or RS of the first cell), e.g., after the application timing. For example, the TCI state may not be applied to the second cell. In some embodiments, a previously or most recently indicated / activated / applied TCI state included in the first list may be applied to the second cell.

[0165] 5A-5E show examples according to some embodiments of the present disclosure.

[0166] As shown in FIG. 5A, the terminal device 120 may be configured with at least one TCI state of a second cell (e.g., CC2) that references a first cell (e.g., CC1), and the second TCI state configured in CC2 may correspond to or refer to a first TCI state configured with the same ID value as the second TCI state, and the first TCI state may be configured in CC1. For example, the second TCI state is configured with an ID value that is "ID_1", and the first TCI state is configured with the same ID value that is "ID_1". As shown in FIG. 5A, the TCI state ID_1 of CC2 may correspond to or refer to the TCI state ID_1 of CC1, and the TCI state ID_2 of CC2 may correspond to or refer to the TCI state ID_1 of CC2, and so on.

[0167] As shown in FIG. 5B, at least one TCI state of a second cell (e.g., CC2) may be configured in the terminal device 120, and the at least one TCI state refers to a first cell (e.g., CC1). In some embodiments, for a source RS and / or QCL information in which qcl-Type is set to qcl-TypeA, an RS configured in CC2 is applied to the source RS. For example, ID2_1 may be configured as an index of an RS associated with TCI state ID_1 of CC2, and ID1_1 may be configured as an index of an RS associated with TCI state ID_1 of CC1. For example, the value of ID2_1 may be the same as or different from the value of ID1_1.

[0168] In some embodiments, ID1_1 and ID2_1 may be non-negative integers, for example, 0<=ID1_1<=511, for example, 0<=ID2_1<=511.

[0169] As shown in FIG. 5C, at least one TCI state of a second cell (e.g., CC2) may be configured in the terminal device 120, and the at least one TCI state refers to a first cell (e.g., CC1). In some embodiments, for a source RS and / or QCL information with qcl-Type set to qcl-TypeD, the RS configured in CC1 applies to the source RS of CC2. In some embodiments, the cell index of the TCI state configured in CC2 is set as the index of the first cell (e.g., the ID of CC1). For example, the index of the RS associated with TCI state ID_1 of CC1 may be set to ID1_1, and it is expected that the index of the RS associated with TCI state ID_1 of CC2 is set to the same value ID1_1.

[0170] As shown in FIG. 5D, the terminal device 120 may be configured with a common configuration of the second cell (e.g., CC2). For example, the common configuration may include the configuration of the CC. For example, the index of the first cell (e.g., the ID of CC1) may be configured in the information of the cell of the common configuration. In some embodiments, a TCI state in which the TCI state ID_1 of the first cell is configured may exist. For example, the second cell may not have a configuration of a TCI state (TCI state ID_1 is configured). In some embodiments, a first RS configured with the TCI state ID_1 of the first cell may exist, the first RS may be associated with qcl-TypeA or may be configured with qcl-TypeA, and the index of the RS may be configured with ID1_1. In some embodiments, a second RS configured with the TCI state ID_1 of the first cell may exist, the second RS may be associated with qcl-TypeD or may be configured with qcl-TypeD, and the index of the RS may be configured with ID1_2. In some embodiments, when TCI state ID_1 is indicated / activated and applied to the first cell and / or the second cell, an RS configured in the second cell with the same value as ID1_1 may be applied to the source RS of qcl-Type A for the second cell. In some embodiments, when TCI state ID_1 is indicated / activated and applied to the first cell and / or the second cell, a second RS may be applied to the source RS of qcl-Type D for the second cell.

[0171] As shown in FIG. 5C, a first list of TCI states (e.g., TCI state ID 1_1, ... TCI state ID 1_n) and a second list of TCI states (e.g., TCI state ID 2_1, ... TCI state ID 2_m) for the first cell may be configured in the terminal device 120. In some embodiments, when a TCI state in the first list is indicated / activated, the TCI state may be applied to the first cell and the second cell after the application timing. In some embodiments, when a TCI state in the second list is indicated / activated, the TCI state may be applied to the first cell (e.g., the TCI state may be applied to non-UE-dedicated channels and / or UE-dedicated channels and / or RSs of the first cell), e.g., after the application timing. For example, the TCI state may not be applied to the second cell. In some embodiments, a previously or most recently indicated / activated / applied TCI state included in the first list may be applied to the second cell.

[0172] In some embodiments, the terminal device 120 may receive at least one configuration for a first list of cells. The first list of cells may comprise a first cell and a second list of cells, and at least a first spatial reception parameter or source RS for qcl-TypeD of the second list of cells may refer to the first cell based on the at least one configuration. In some embodiments, the terminal device 120 may perform a first beam failure recovery procedure for the first list of cells. In some embodiments, the terminal device 120 may perform a first beam failure recovery procedure for the first cell and a second beam failure recovery procedure for the second list of cells, and the second beam failure recovery procedure may be the same as or related to the first beam failure recovery procedure.

[0173] In some embodiments, the first beam failure recovery procedure may be based on at least one of a first set of parameters, a first set of reference signals for beam failure detection, and a first set of reference signals for candidate beam identification, wherein the first set of parameters comprises at least one of a first parameter for a counter, a first parameter for a timer, and a first threshold.

[0174] In some embodiments, the second beam failure recovery procedure may be based on at least one of a second set of parameters, a second set of reference signals for beam failure detection, and a second set of reference signals for candidate beam identification, the second set of parameters comprising at least one of a second parameter for a counter, a second parameter for a timer, and a second threshold.

[0175] In some embodiments, the terminal device 120 may receive an indication of a first transmission configuration indicator (TCI) and may receive a first set of channels and / or reference signals based on first spatial reception parameters on a first list of cells after or starting from the application timing. The first spatial reception parameters may be based on the first TCI.

[0176] In some embodiments, the first set of parameters may be at least one of configured for the first cell, configured and shared for the first list of cells, and determined based on a parameter set having a maximum or minimum value among the first list of cells.

[0177] In some embodiments, the first set of reference signals for beam failure detection may be at least one of: configured for the first cell; configured and shared for a first list of cells; determined based on a TCI state of a set of control resource sets (CORESET) for the first cell; and determined based on a first TCI.

[0178] In some embodiments, the first set of reference signals for candidate beam identification may be at least one of configured for a first cell and configured and shared for a first list of cells.

[0179] In some embodiments, the second set of parameters may be at least one of the same as the first set of parameters.

[0180] The second set of reference signals for beam failure detection may be at least one of the following: the same as or a subset of the first set of reference signals for beam failure detection; configured for the first cell; configured and shared for the first list of cells; configured and shared for the second list of cells; determined based on a set of parameters having maximum or minimum values ​​in the first list of cells; determined based on a set of parameters having maximum or minimum values ​​in the second list of cells.

[0181] In some embodiments, the second set of reference signals for candidate beam identification may be at least one of the following: the same as or a subset of the first set of reference signals for beam failure detection; configured for the first cell; configured and shared for the first list of cells; configured and shared for the second list of cells; determined based on a TCI state of a set of control resource sets (CORESET) of the first cell; determined based on a TCI state of a set of control resource sets (CORESET) of the second list of cells and determined based on the first TCI.

[0182] In some embodiments, the second set of reference signals for candidate beam identification may be at least one of configured for the first cell, configured and shared for a first list of cells, and configured and shared for a second list of cells.

[0183] In some embodiments, if the number of ports of a source reference signal in the first TCI with quasi co-location (QCL) type D configured is equal to and / or greater than two, the first beam failure recovery procedure and / or the second beam failure recovery procedure may be stopped, interrupted or reset.

[0184] In some embodiments, the terminal device 120 may transmit at least one information to the network device. The at least one information may be at least one of a single indication indicating beam failure detection for the first list of cells or the second list of cells, a single indication indicating the presence of a new reference signal for the first list of cells or the second list of cells, a single indication indicating an index of a new reference signal for the first list of cells or the second list of cells, a list of indications indicating beam failure detection for the first list of cells or the second list of cells (each indication in the list indicates beam failure detection for one cell in the first list of cells or the second list of cells, and the values ​​of the indications in the list may be the same), a list of indications indicating the presence of a new reference signal for the first list of cells or the second list of cells (each indication in the list indicates the presence of a new reference signal for one cell in the first list of cells or the second list of cells, and the values ​​of the indications in the list may be the same), a list of indications indicating an index of a new reference signal for the first list of cells or the second list of cells (each indication in the list indicates an index of a new reference signal for one cell in the first list of cells or the second list of cells, and the values ​​of the indications in the list may be the same).

[0185] In some embodiments, the new reference signal may be included in the first set of reference signals for candidate beam identification or the second set of reference signals for candidate beam identification.

[0186] In some embodiments, the terminal device 120 may monitor or receive at least one physical downlink control channel (PDCCH) in a corresponding CORESET of at least one cell in the first list of cells or the second list of cells using the same QCL parameters of the antenna ports as those associated with the new reference signal after or starting from the first timing. In some embodiments, the terminal device 120 may receive at least one physical downlink shared channel (PDSCH) in at least one cell in the first list of cells or the second list of cells using the same QCL parameters of the antenna ports as those associated with the new reference signal after or starting from the first timing. The at least one PDSCH is scheduled by the at least one PDCCH. In some embodiments, the terminal device 120 may transmit a physical uplink control channel (PUCCH) in the first cell using the same spatial domain filter as that corresponding to the new reference signal after or starting from the first timing. In some embodiments, the terminal device 120 may transmit at least one physical uplink shared channel (PUSCH) in at least one cell in the first list of cells or the second list of cells using the same spatial domain filter as the one corresponding to the new reference signal after or starting from the first timing.

[0187] In some embodiments, the TCI field in the DCI of the PDCCH may be 0 bits or may be omitted. In some embodiments, terminal device 120 may assume or expect to receive an index of the codepoint in the TCI field in the DCI of the PDCCH that is the same as the index of the codepoint with the first TCI.

[0188] In some embodiments, the terminal device 120 may perform a beam failure recovery procedure for each cell in the first list of cells, respectively, if an index of the cell index information of the spatial reception parameters of the cell is not present for that cell, based on at least one setting.

[0189] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may transmit at least one of an indication indicating a beam failure detection for the first cell, an indication indicating a presence of a new reference signal for the first cell, and an indication indicating an index of the new reference signal for the first cell, where the new reference signal is included in the first set of reference signals for candidate beam identification, to the network device.

[0190] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may monitor the PDCCH in the search space set provided by recoverySearchSpaceId after the first timing or starting from the first timing.

[0191] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may receive at least one PDSCH in the first cell using the QCL parameters of the same antenna port as that associated with the new reference signal after or starting from the first timing. For example, the at least one PDSCH may be scheduled by a PDCCH in a search space set.

[0192] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may transmit a PUCCH in the first cell to the network device using the same spatial domain filter as the one corresponding to the new reference signal after or starting from the first timing.

[0193] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may transmit at least one PUSCH in the first cell using the same spatial domain filter as the one corresponding to the new reference signal after or starting from the first timing.

[0194] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may monitor at least one PDCCH in a corresponding CORESET of at least one cell in the first list of cells or the second list of cells based on a second TCI indicated in the PDCCH of the first cell after or starting from the second timing. For example, the PDCCH of the first cell may be received after the first timing.

[0195] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may monitor at least one PDCCH in a corresponding CORESET of at least one cell in the first list of cells or the second list of cells using QCL parameters of the same antenna port as those associated with the new reference signal after or starting from the second timing.

[0196] In some embodiments, in response to the first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may receive at least one PDSCH in at least one cell in the first list of cells or the second list of cells using the QCL parameters of the same antenna port as that associated with the new reference signal or based on the second TCI after or starting from the second timing. For example, the at least one PDSCH may be scheduled by the at least one PDCCH.

[0197] In some embodiments, in response to a first beam failure detection being detected in the first beam failure recovery procedure, the terminal device 120 may transmit at least one PUSCH in at least one cell in the first list of cells or the second list of cells using the same spatial domain filter as the one corresponding to the new reference signal or based on the second TCI after or starting from the second timing.

[0198] In some embodiments, in response to a second beam failure detection being detected in the second beam failure recovery procedure, the terminal device 120 may transmit at least one piece of information in the first PUSCH to the network device.

[0199] In some embodiments, in response to detection of a second beam failure detection in the second beam failure recovery procedure, the terminal device 120 may monitor or receive at least one PDCCH in a corresponding CORESET of at least one cell in the first list of cells or the second list of cells using QCL parameters of the same antenna port as those associated with the new reference signal after or starting from the first timing.

[0200] In some embodiments, in response to a second beam failure detection being detected in the second beam failure recovery procedure, the terminal device 120 may receive at least one PDSCH in at least one cell in the first list of cells or the second list of cells using the QCL parameters of the same antenna port as that associated with the new reference signal after or starting from the first timing. For example, the at least one PDSCH may be scheduled by the at least one PDCCH.

[0201] In some embodiments, in response to detection of a second beam failure detection in a second beam failure recovery procedure, the terminal device 120 may transmit a PUCCH in the first cell using the same spatial domain filter as the one corresponding to the new reference signal after or starting from the first timing.

[0202] In some embodiments, in response to detection of a second beam failure detection in a second beam failure recovery procedure, the terminal device 120 may transmit at least one PUSCH in at least one cell in the first list of cells or the second list of cells using the same spatial domain filter as the one corresponding to the new reference signal after or starting from the first timing.

[0203] In some embodiments, the second beam failure detection may be detected in a second beam failure recovery procedure, and the first beam failure detection may not be detected in the first beam failure recovery procedure.

[0204] In some embodiments, the PDCCH of the first cell may comprise at least a PDCCH dedicated to a user equipment (UE). In some embodiments, the PDCCH of the first cell may be in a UE specific search space (USS). In some embodiments, the PDCCH of the first cell may be in a common search space (CSS). Demodulation reference signals of the PDCCH may be configured to share the same TCI designated for the UE dedicated channel.

[0205] In some embodiments, the first timing schedules a PUSCH transmission in slot n+4 (slot n is the slot for a physical random access channel (PRACH) transmission for a first beam failure recovery procedure of the first cell), 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId in the first cell, 28 symbols from the last symbol of the first PDCCH reception with the same hybrid automatic repeat request (HARQ) process number as the first PUSCH transmission, and 28 symbols from the last symbol of the PDCCH reception with Downlink Control Information (DCI) having a new data indicator (NDI) field value toggled (subcarrier spacing (SCS) for 28 symbols). scheduling a PUSCH transmission with the same HARQ process number as the first PUSCH transmission and may be at least one of: a first slot 28 symbols after the last symbol of PDCCH reception with DCI having a toggled NDI field value (the subcarrier spacing (SCS) setting for 28 symbols is the smallest of the SCS settings for the first list of cells or the second list of cells);

[0206] In some embodiments, the second timing may be at least one of: a first slot after a number of symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId in the first cell; a first slot after the first beam failure recovery procedure is completed or starting from the completion of the first beam failure recovery procedure; and a first slot after a number of symbols from the last symbol of the first PDCCH reception or an acknowledgment corresponding to a PDSCH scheduled by the first PDCCH.

[0207] In some embodiments, the terminal device 120 may receive at least one configuration for a set of transmission configuration indicator (TCI) states from a network device. The set of TCI states may be at least one of a first subset of TCI states and a second subset of TCI states. At least one reference signal (RS) in the first subset of TCI states may be associated with a first physical cell identity (ID). At least one RS in the second subset of TCI states may be associated with a second physical cell ID.

[0208] In some embodiments, the terminal device 120 may perform a beam failure recovery procedure based on at least one of the first set of RSs for beam failure detection and the first set of RSs for candidate beam identification when a first TCI state of the first subset is indicated. In some embodiments, the terminal device 120 may perform a beam failure recovery procedure based on at least one of the second set of RSs for beam failure detection and the second set of RSs for candidate beam identification when a second TCI state of the second subset is indicated.

[0209] In some embodiments, at least one configuration of the set of TCI states may be configured for a first cell, and the first cell may be associated with a first physical cell ID.

[0210] In some embodiments, the first set of RSs for beam obstruction detection may be associated with a first physical cell ID. In some embodiments, the first set of RSs for candidate beam identification may be associated with a first physical cell ID. In some embodiments, the second set of RSs for beam obstruction detection may be associated with a second physical cell ID. In some embodiments, the second set of RSs for candidate beam identification may be associated with the first physical cell ID and / or the second physical cell ID.

[0211] In some embodiments, the first set of beam failure detection RSs may be at least one of configured for the first cell, determined based on at least one TCI state of a first set of control resource set (CORESET) of the first cell, and determined based on a first TCI state, where the at least one TCI state may be associated with a first physical cell ID and / or a second physical cell ID.

[0212] In some embodiments, a first set of candidate beam identifying RSs is configured in a first cell.

[0213] In some embodiments, the second set of beam failure detection RSs may be at least one of configured in the first cell, determined based on at least one TCI state of a second set of control resource set (CORESET) of the first cell, and determined based on a second TCI state, where the at least one TCI state may be associated with the first physical cell ID and / or the second physical cell ID.

[0214] In some embodiments, a second set of candidate beam identifying RSs may be configured in the first cell.

[0215] In some embodiments, terminal device 120 may receive at least one configuration for a first list of cells, which may comprise a first cell and a second list of cells, and at least a first spatial reception parameter of the second list of cells may reference the first cell based on the at least one configuration for the first list of cells.

[0216] In some embodiments, in response to the first TCI state being indicated, the terminal device 120 may monitor or receive at least one physical downlink control channel (PDCCH) in a corresponding CORESET of at least one cell in the first list of cells based on the first TCI state after or starting from the application timing.

[0217] In some embodiments, in response to the first TCI state being indicated, the terminal device 120 may receive, starting after or from the application timing, at least one physical downlink shared channel (PDSCH) in at least one cell of the first list of cells based on the first TCI state, where the at least one PDSCH is scheduled by the at least one PDCCH.

[0218] In some embodiments, in response to the first TCI state being indicated, the terminal device 120 may transmit a physical uplink control channel (PUCCH) in the first cell based on the first TCI state after or starting from the application timing.

[0219] In some embodiments, in response to the first TCI state being indicated, the terminal device 120 may transmit at least one physical uplink shared channel (PUSCH) in at least one cell of the first list of cells based on the first TCI state after or starting from the application timing.

[0220] In some embodiments, in response to the second TCI state being indicated, the terminal device 120 may monitor or receive at least one PDCCH in the corresponding CORESET of the first cell based on the second TCI state after or starting from the application timing.

[0221] In some embodiments, in response to the second TCI state being indicated, the terminal device 120 may receive at least one PDSCH in the first cell based on the second TCI state after or starting from the application timing, for example, the at least one PDSCH may be scheduled by the at least one PDCCH.

[0222] In some embodiments, in response to the second TCI state being indicated, the terminal device 120 may transmit a PUCCH in the first cell based on the second TCI state after or starting from the application timing.

[0223] In some embodiments, in response to the second TCI state being indicated, the terminal device 120 may transmit at least one PUSCH in the first cell based on the second TCI state after or starting from the application timing.

[0224] In some embodiments, in response to the second TCI state being indicated, the terminal device 120 may not monitor or receive or transmit in the second list of cells after or starting from the application timing.

[0225] In some embodiments, in response to the second TCI state being indicated, the terminal device 120 may monitor or receive at least one PDCCH in a corresponding CORESET of at least one cell in the second list of cells based on the latest or previous TCI state.

[0226] In some embodiments, in response to the second TCI state being indicated, terminal device 120 may receive at least one PDSCH in at least one cell in the second list of cells based on the most recent or previous TCI state.

[0227] In some embodiments, in response to the second TCI state being indicated, terminal device 120 may transmit at least one PUSCH in at least one cell in the second list of cells based on a current or previous TCI state, which may be associated with the first physical cell ID.

[0228] In some embodiments, the applied timing may be a first slot that is a number of symbols after the last symbol of an acknowledgement corresponding to a PDCCH or a PDSCH scheduled by the PDCCH, which may indicate a first TCI state or a second TCI state.

[0229] In some embodiments, the first physical cell ID may be a cell ID of the serving cell. In some embodiments, the second physical cell ID may be different from the first physical cell ID. In some embodiments, the second physical cell ID may be a different ID from the serving cell. For example, the second physical cell ID may be an ID of a neighboring cell.

[0230] In some embodiments, the first TCI state is indicated / activated. For example, the first TCI state may be in a first list of TCI states. For example, the first TCI state may be applied to the first cell and the second cell, or to the first list of cells, after the application timing. In some embodiments, the terminal device 120 may perform a first beam failure recovery procedure for the second cell based on the configuration / parameters of the first cell. In some embodiments, the terminal device 120 may perform a common / unified / first beam failure recovery procedure for the first cell and the second cell.

[0231] In some embodiments, the parameters of the first beam failure recovery procedure may be based on at least one setting of the first cell, or based on a maximum / minimum between the setting of the first cell and the setting of the second cell, or based on a maximum / minimum of the setting of a first list of cells, or based on a maximum / minimum of the setting of a second list of cells. In some embodiments, the parameters may include at least one of beamFailureInstanceMaxCount, beamFailureDetectionTimer, rsrp-Threshold, candidateBeamRSList.

[0232] In some embodiments, a beam failure detection (BFD) RS set for the first beam failure recovery procedure may be determined based on the qcl-typeD configured RS in the first TCI state of the first cell, or the BFD RS set may be determined based on the RS of the TCI state for each CORESET in the first cell. For example, the terminal device 120 may not expect that the source RS of qcl-typeD of the first TCI state (e.g., CSI-RS of channel state information (CSI) as source RS) is not one port and / or two ports. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the first beam failure recovery (BFR) may be suspended or stopped. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the terminal device 120 may determine the CSI-RS with one port and / or two ports as the BFD RS. The CSI-RS may then be a source RS of qcl-type D for the source RS in the first TCI state and applied to the BFD RS. In some embodiments, the beam failure detection RS is based on a BFD RS set configured for the first cell.

[0233] In some embodiments, when a beam failure is declared, the value of the beam failure indication field in the MAC CE may be the same for the first cell and the second cell.

[0234] In some embodiments, a new beam or RS may be identified from the candidate beam RS list. For example, the new beam or RS may be for both the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, the candidate beam RS list may be configured for the first cell, or may be a common candidate beam RS list configured for the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, in the MAC CE, the existence of the new beam or RS and the index of the new beam or RS may be the same for the first cell and the second cell, or for the first list of cells, or for the second list of cells.

[0235] In some embodiments, the new beam or RS may be represented in this disclosure as qnew.

[0236] In some embodiments, the first qnew and the second qnew are identified from candidate beam RS lists configured for the first cell and the second cell, respectively. For example, after successful first beam failure recovery, the beams may not be unified for the first cell and the second cell until a new TCI state is activated / indicated and applied to the first cell and the second cell.

[0237] In some embodiments, terminal device 120 may monitor a PDCCH in the first cell and the second cell after the first timing, and the PDCCH may be based on a QCL parameter associated with qnew.

[0238] In some embodiments, after the first beam failure recovery procedure is successful, qnew may replace the source RS set to the first TCI state, or qnew may replace the first TCI state in the corresponding TCI codepoint, or qnew may replace the source RS of qcl-TypeD set to the first TCI state, e.g., until a new TCI state is indicated / activated for the first cell and the second cell. For example, qnew may be a periodic CSI-RS. For example, the number of ports of qnew may be one or two ports. In some embodiments, if qnew is a synchronization signal (SS) / physical broadcast channel (PBCH), qnew may not replace the source RS set to the first TCI state. In some embodiments, the source RS of qcl-TypeA set to the first TCI state may still be applied.

[0239] In some embodiments, the terminal device 120 may receive an indication / activation of the second TCI state. The fields of cell information in the source RS and QCL information of the second TCI state of the second cell may not be present. The terminal device 120 may perform a second beam failure recovery procedure with respect to the second cell. For example, the second beam failure recovery procedure may be separate from the first beam failure recovery procedure. In some embodiments, a beam failure detection RS may be configured for the second cell or may be determined based on the RS of the second cell. For example, the RS may be configured for the second TCI state and for the source RS and QCL information with qcl-TypeD configured. In some embodiments, parameters for the second beam failure recovery procedure may be configured for the second cell. In some embodiments, a candidate beam identification RS set for the second beam failure recovery procedure may be configured for the second cell, or may be configured for the first cell, or may be configured for the first / second list of cells. In some embodiments, multiple TCI states may be configured in the second cell, and at least the source RS or spatial reception parameters of qcl-Type D for different TCI states may refer to different cells, and the RS set for candidate beam identification for the second beam failure recovery procedure may be the RS set configured to the cell with the lowest ID among the different cells.

[0240] 6A-6B show examples according to some embodiments of the present disclosure.

[0241] As shown in FIG. 6A, the terminal device 120 may be activated with a list of TCI states, e.g., via a MAC CE. In some embodiments, the terminal device 120 may be indicated with a first TCI state. For example, the first TCI state may be applied to the first cell and the second cell after an application timing. In some embodiments, the first TCI state may be detected in the first cell and / or the second cell. After successful beam failure recovery, the first TCI state, or a TCI codepoint corresponding to the first TCI state, or a source RS of qcl-TypeA and / or a source RS of qcl-TypeD of the first TCI state may be replaced with qnew. For example, qnew may be identified from a candidate beam identification RS set for the first cell and / or the second cell.

[0242] As shown in FIG. 6B, at least one TCI state of a second cell (e.g., CC2) may be configured in the terminal device 120. In some embodiments, for a first TCI state (e.g., TCI state ID1), cell information of a source RS and / or QCL information with qcl-Type set to qcl-TypeA may be configured as a cell index (e.g., CC1 ID) of the first cell. In some embodiments, for a second TCI state (e.g., TCI state ID2), cell information of a source RS and / or QCL information with qcl-Type set to qcl-TypeA may be configured as not present. In some embodiments, when the first TCI state ID1 is indicated in the terminal device 120, beam failure recovery of the second cell may be performed based on the first cell. In some embodiments, when the second TCI state ID2 is indicated in the terminal device 120, beam failure recovery of the second cell may be performed based on the second cell.

[0243] In some embodiments, the first cell may be a primary cell. For example, the first cell may be a Pcell, a Spcell, or a Pscell. For example, the first beam failure recovery procedure may be based on a random access channel (RACH).

[0244] In some embodiments, the terminal device 120 may monitor PDCCH in the search space set provided by recoverySearchSpaceId after or starting from the first timing in the first cell. For example, when a beam failure is detected / declared in the first cell and / or the second cell. As another example, after a beam failure recovery request is sent to the network device. In some embodiments, the terminal device 120 may monitor PDCCH in the corresponding CORESET after or starting from the second timing. In some embodiments, the terminal device 120 may not monitor PDCCH in the second cell. For example, until a new TCI state is indicated / activated for the first cell and / or the second cell. For example, after the application timing.

[0245] In some embodiments, the first TCI state is indicated / activated. For example, the first TCI state may be in a first list of TCI states. For example, the first TCI state may be applied to the first cell and the second cell, or the first list of cells, after the application timing. In some embodiments, the first cell may be at least one of a Pcell, a primary cell, a Pscell, and a Spcell. In some embodiments, the terminal device 120 may perform a first beam failure recovery procedure (e.g., RACH-based) for the first cell.

[0246] In some embodiments, the parameters of the first beam failure recovery procedure may be based on at least one setting of the first cell, or based on a maximum / minimum between the setting of the first cell and the setting of the second cell, or based on a maximum / minimum of the setting of a first list of cells, or based on a maximum / minimum of the setting of a second list of cells. In some embodiments, the parameters may include at least one of beamFailureInstanceMaxCount, beamFailureDetectionTimer, rsrp-Threshold, candidateBeamRSList.

[0247] In some embodiments, a beam failure detection (BFD) RS set for the first beam failure recovery procedure may be determined based on the qcl-typeD configured RS in the first TCI state of the first cell, or the BFD RS set may be determined based on the RS of the TCI state for each CORESET in the first cell. For example, the terminal device 120 may not expect that the source RS of qcl-typeD of the first TCI state (e.g., CSI-RS of channel state information (CSI) as source RS) is not one port and / or two ports. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the first beam failure recovery (BFR) may be suspended or stopped. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the terminal device 120 may determine the CSI-RS with one port and / or two ports as the BFD RS. The CSI-RS may then be a source RS of qcl-type D for the source RS in the first TCI state and applied to the BFD RS. In some embodiments, the beam failure detection RS is based on a BFD RS set configured for the first cell.

[0248] In some embodiments, when a beam failure is declared, the value of the beam failure indication field in the MAC CE may be the same for the first cell and the second cell.

[0249] In some embodiments, a new beam or RS may be identified from the candidate beam RS list. For example, the new beam or RS may be for both the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, the candidate beam RS list may be configured for the first cell, or may be a common candidate beam RS list configured for the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, in the MAC CE, the existence of the new beam or RS and the index of the new beam or RS may be the same for the first cell and the second cell, or for the first list of cells, or for the second list of cells.

[0250] In some embodiments, the new beam or RS may be represented in this disclosure as qnew.

[0251] In some embodiments, the first qnew and the second qnew are identified from candidate beam RS lists configured for the first cell and the second cell, respectively. For example, after successful first beam failure recovery, the beams may not be unified for the first cell and the second cell until a new TCI state is activated / indicated and applied to the first cell and the second cell.

[0252] In some embodiments, terminal device 120 may monitor a PDCCH in the first cell and the second cell after the first timing, and the PDCCH may be based on a QCL parameter associated with qnew.

[0253] In some embodiments, after the first beam failure recovery procedure is successful, qnew may replace the source RS set to the first TCI state, or qnew may replace the first TCI state in the corresponding TCI codepoint, e.g., until a new TCI state is indicated / activated for the first cell and the second cell. For example, qnew may be a periodic CSI-RS. For example, the number of ports of qnew may be one or two ports. In some embodiments, if qnew is a synchronization signal (SS) / physical broadcast channel (PBCH), qnew may not replace the source RS set to the first TCI state.

[0254] In some embodiments, the terminal device 120 may receive an indication / activation of the second TCI state. The fields of cell information in the source RS and QCL information of the second TCI state of the second cell may not be present. The terminal device 120 may perform a second beam failure recovery procedure with respect to the second cell. For example, the second beam failure recovery procedure may be separate from the first beam failure recovery procedure. In some embodiments, a beam failure detection RS may be configured for the second cell or may be determined based on the RS of the second cell. For example, the RS may be configured for the second TCI state and for the source RS and QCL information with qcl-TypeD configured. In some embodiments, parameters for the second beam failure recovery procedure may be configured for the second cell. In some embodiments, a candidate beam identification RS set for the second beam failure recovery procedure may be configured for the second cell, or may be configured for the first cell, or may be configured for the first / second list of cells. In some embodiments, multiple TCI states may be configured in the second cell, and at least the source RS or spatial reception parameters of qcl-Type D for different TCI states may refer to different cells, and the RS set for candidate beam identification for the second beam failure recovery procedure may be the RS set configured to the cell with the lowest ID among the different cells.

[0255] In some embodiments, terminal device 120 may perform a second beam failure recovery procedure (eg, PUCCH-based, as another example, Scell ​​BFR) for a second cell or a second list of cells.

[0256] In some embodiments, the parameters of the second beam failure recovery procedure may be based on at least one setting of the first cell, or based on a maximum / minimum between the setting of the first cell and the setting of the second cell, or based on a maximum / minimum of the setting of the first list of cells, or based on a maximum / minimum of the setting of the second list of cells. In some embodiments, the parameters may include at least one of beamFailureInstanceMaxCount, beamFailureDetectionTimer, rsrp-Threshold, candidateBeamRSList.

[0257] In some embodiments, the beam failure detection (BFD) RS set for the second beam failure recovery procedure may be different from the BFD RS set for the first beam failure recovery procedure. In some embodiments, the beam failure detection (BFD) RS set for the second beam failure recovery procedure may be determined based on the qcl-typeD configured RS in the first TCI state of the first cell, or the BFD RS set may be determined based on the RS of the TCI state for the second cell or the respective CORESET in the second list of cells. For example, the terminal device 120 may not expect that the source RS of qcl-typeD of the first TCI state (e.g., the CSI-RS of the channel state information (CSI) as the source RS) is not one port and / or two ports. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the first beam failure recovery (BFR) may be suspended or stopped. For example, if the source RS of qcl-type D in the first TCI state is not one port and / or two ports, the terminal device 120 may determine a CSI-RS with one port and / or two ports as the BFD RS. The CSI-RS may then be the source RS of qcl-type D for the source RS in the first TCI state and applied to the BFD RS. In some embodiments, the beam failure detection RS is based on the BFD RS set configured in the first cell.

[0258] In some embodiments, a new beam or RS may be identified from the candidate beam RS list. For example, the new beam or RS may be for both the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, the candidate beam RS list may be configured for the first cell, or may be a common candidate beam RS list configured for the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, in the MAC CE, the existence of the new beam or RS and the index of the new beam or RS may be the same for the first cell and the second cell, or for the first list of cells, or for the second list of cells.

[0259] In some embodiments, the first qnew and the second qnew are identified from candidate beam RS lists configured for the first cell and the second cell, respectively. For example, after successful first beam failure recovery, the beams may not be unified for the first cell and the second cell until a new TCI state is activated / indicated and applied to the first cell and the second cell.

[0260] In some embodiments, if beam failure is detected / declared in the second beam failure recovery procedure and / or if beam failure is not detected / declared in the first beam failure recovery procedure, the terminal device 120 may monitor at least a UE dedicated PDCCH of the first cell based on a QCL parameter associated with qnew, e.g., after a first or second timing. And the terminal device 120 may monitor a PDCCH in the second cell or in a corresponding CORESET of the second list of cells based on a QCL parameter associated with qnew, e.g., after a first or second timing.

[0261] In some embodiments, if a beam failure is detected / declared in the first beam failure recovery procedure (e.g., regardless of whether a beam failure is detected / declared in the second beam failure recovery procedure), the terminal device 120 may monitor a PDCCH in the search space set provided by recoverySearchSpaceId after or starting from the first timing in the first cell. For example, if a beam failure is detected / declared in the first cell and / or the second cell. As another example, after a beam failure recovery request is sent to the network device. In some embodiments, the terminal device 120 may monitor a PDCCH in the corresponding CORESET of the second cell or the second list of cells after or starting from the second timing. In some embodiments, the terminal device 120 may not monitor a PDCCH in the second cell. For example, until a new TCI state is indicated / activated for the first cell and / or the second cell. For example, after the application timing.

[0262] In some embodiments, the first cell may be an Scell, and the second list of cells may include a Pcell or a Pscell or a primary cell or an Spcell (e.g., denoted as Spcell). In some embodiments, the first TCI state is indicated / activated. For example, the first TCI state may be in the first list of TCI states. For example, the first TCI state may be applied to the first cell and the second cell, or the first list of cells, after an application timing. In some embodiments, the terminal device 120 may perform a first beam failure recovery procedure (e.g., RACH-based) for the Spcell.

[0263] In some embodiments, the parameters of the first beam failure recovery procedure may be based on at least one of the settings of the first cell or Spcell, or based on the maximum / minimum between the settings of the first cell and the settings of the second cell, or based on the maximum / minimum of the settings of the first list of cells, or based on the maximum / minimum of the settings of the second list of cells. In some embodiments, the parameters may include at least one of beamFailureInstanceMaxCount, beamFailureDetectionTimer, rsrp-Threshold, candidateBeamRSList.

[0264] In some embodiments, a beam failure detection (BFD) RS set for the first beam failure recovery procedure may be determined based on the qcl-typeD configured RS in the first TCI state of the first cell or Spcell, or the BFD RS set may be determined based on the RS of the TCI state for each CORESET of the Spcell. For example, the terminal device 120 may not expect that the source RS of qcl-typeD in the first TCI state (e.g., the CSI-RS of the channel state information (CSI) as the source RS) is not one port and / or two ports. For example, if the source RS of qcl-typeD in the first TCI state is not one port and / or two ports, the first beam failure recovery (BFR) may be suspended or stopped. For example, if the source RS of qcl-type D in the first TCI state is not one port and / or two ports, the terminal device 120 may determine a CSI-RS with one port and / or two ports as the BFD RS. The CSI-RS may then be the source RS of qcl-type D for the source RS in the first TCI state and applied to the BFD RS. In some embodiments, the beam failure detection RS is based on the BFD RS set configured in the first cell or Spcell.

[0265] In some embodiments, a new beam or RS may be identified from the candidate beam RS list. For example, the new beam or RS may be for both the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, the candidate beam RS list may be configured for the first cell or Spcell, or may be a common candidate beam RS list configured for the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, in the MAC CE, the existence of the new beam or RS and the index of the new beam or RS may be the same for the first cell and the second cell, or for the first list of cells, or for the second list of cells.

[0266] In some embodiments, the first qnew and the second qnew are identified from candidate beam RS lists configured for the first cell and the second cell, respectively. For example, after successful first beam failure recovery, the beams may not be unified for the first cell and the second cell until a new TCI state is activated / indicated and applied to the first cell and the second cell.

[0267] In some embodiments, the terminal device 120 may perform a second beam failure recovery procedure (e.g., PUCCH-based, as another example, Scell ​​BFR) for the first cell and / or a second list of cells excluding the Spcell, or the first list of cells excluding the Spcell.

[0268] In some embodiments, the parameters of the second beam failure recovery procedure may be based on at least one setting of the first cell, or based on a maximum / minimum value of settings of a first list of cells excluding Spcell, or based on a maximum / minimum value of settings of a second list of cells excluding Spcell. In some embodiments, the parameters may include at least one of beamFailureInstanceMaxCount, beamFailureDetectionTimer, rsrp-Threshold, and candidateBeamRSList.

[0269] In some embodiments, the beam failure detection (BFD) RS set for the second beam failure recovery procedure may be different from the BFD RS set for the first beam failure recovery procedure. In some embodiments, the beam failure detection (BFD) RS set for the second beam failure recovery procedure may be determined based on the qcl-typeD configured RS in the first TCI state of the first cell, or the BFD RS set may be determined based on the RS of the TCI state for each CORESET in the first / second list of the cells excluding the Spcell. For example, the terminal device 120 may not expect that the source RS of qcl-typeD of the first TCI state (e.g., the CSI-RS of the channel state information (CSI) as the source RS) is not one port and / or two ports. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the first beam failure recovery (BFR) may be suspended or stopped. For example, if the source RS of qcl-type D in the first TCI state is not one port and / or two ports, the terminal device 120 may determine a CSI-RS with one port and / or two ports as the BFD RS. The CSI-RS may then be the source RS of qcl-type D for the source RS in the first TCI state and applied to the BFD RS. In some embodiments, the beam failure detection RS is based on the BFD RS set configured in the first cell.

[0270] In some embodiments, a new beam or RS may be identified from the candidate beam RS list. For example, the new beam or RS may be for both the first cell and the second cell, or the first list of cells excluding Spcell, or the second list of cells excluding Spcell. In some embodiments, the candidate beam RS list may be configured for the first cell, or may be a common candidate beam RS list configured for the first cell and the second cell, or the first list of cells, or the second list of cells. In some embodiments, in the MAC CE, the existence of the new beam or RS and the index of the new beam or RS may be the same for the first cell and the second cell, or for the first list of cells, or for the second list of cells.

[0271] In some embodiments, if beam failure is detected / declared in the second beam failure recovery procedure and / or if beam failure is not detected / declared in the first beam failure recovery procedure, the terminal device 120 may monitor at least a UE dedicated PDCCH of the Spcell based on a QCL parameter associated with qnew, for example after a first or second timing. Then, the terminal device 120 may monitor a PDCCH in the corresponding CORESET of the first cell and / or a second list of cells excluding the Spcell based on a QCL parameter associated with qnew, for example after a first or second timing.

[0272] In some embodiments, if a beam failure is detected / declared in the first beam failure recovery procedure (e.g., regardless of whether a beam failure is detected / declared in the second beam failure recovery procedure), the terminal device 120 may monitor a PDCCH in the search space set provided by recoverySearchSpaceId after or starting from the first timing in the Spcell cell. For example, if a beam failure is detected / declared in the Spcell. As another example, after a beam failure recovery request is sent to the network device. In some embodiments, the terminal device 120 may monitor a PDCCH in the corresponding CORESET of the first list of cells excluding the Spcell after or starting from the second timing. In some embodiments, the terminal device 120 may not monitor a PDCCH in the first list of cells excluding the Spcell. For example, until a new TCI state is indicated / activated for the first cell and / or the second cell, or for the first list of cells. For example, after the application timing.

[0273] In some embodiments, if an Spcell is included in the first list of cells, it may be assumed or expected that the Spcell is set as a reference cell for the first list of cells.

[0274] In some embodiments, the terminal device 120 may be configured with a combined TCI mode or a split downlink (DL) / uplink (UL) TCI mode in the Spcell. In some embodiments, if the split DL / UL TCI mode in the Spcell is configured in the terminal device 120 and the indicated / activated / applied DL TCI and the indicated / activated / applied UL TCI are not in the case of beam alignment, the terminal device 120 may perform PUCCH-based BFR when beam failure is detected / declared in the Spcell. For example, otherwise, the terminal device 120 may perform RACH-based BFR when beam failure is detected / declared in the Spcell. In some embodiments, when the terminal device 120 is configured with a combined TCI mode in the Spcell, or when the terminal device 120 is configured with a separated DL / UL TCI in the Spcell, and the indicated / activated / applied DL TCI and the indicated / activated / applied UL TCI are in a beam alignment case, the terminal device 120 may perform PUCCH-based BFR when a beam failure is detected / declared in the Spcell. In some embodiments, the beam alignment case may be at least one of the following: a combined TCI mode, a source RS of qcl-TypeD in the indicated / activated / applied DL TCI is the same as a spatially related source RS in the indicated / activated / applied UL TCI, and a source RS of qcl-TypeD in the indicated / activated / applied DL TCI is quasi-collocated with a spatially related source RS in the indicated / activated / applied UL TCI. For example, quasi-collocated with qcl-typeD.

[0275] In some embodiments, if the mode of separate DL / UL TCI in Spcel is set to the terminal device 120 and the indicated / activated / applied DL TCI and the indicated / activated / applied UL TCI are not a case of beam alignment, the terminal device 120 may transmit a PUCCH based on spatial relationship information corresponding to the previous or latest indicated / activated / applied UL TCI.

[0276] In some embodiments, the candidate beam identifying RS set may include at least an RS that is set to an activated TCI state.

[0277] In some embodiments, the terminal device 120 may be configured with a set of TCI states in the first cell. In some embodiments, the set may include at least one TCI state (e.g., represented as TCI_N), and the source RS configured with the TCI state may be associated with a second physical cell ID or associated with an SSB having a second physical cell ID. In some embodiments, the set may include at least one TCI state (e.g., represented as TCI_S), and the source RS configured with the TCI state may be associated with a first physical cell ID or associated with an SSB having a first physical cell ID.

[0278] In some embodiments, when TCI_N is indicated / activated, TCI_N may be applied to at least UE dedicated channels / RS of the first cell. In some embodiments, when TCI_N is indicated / activated, TCI_N may not be applied to the second cell or second list of cells. For example, the second cell or second list of cells may be suspended, e.g., there may be no monitoring or reception of channels / RS in the second cell or second list of cells, e.g., until a new TCI state associated with the first physical cell ID is indicated. In some embodiments, when TCI_N is indicated / activated, the previous or most recently indicated / activated / applied TCI state associated with the first physical cell ID may be applied to at least UE dedicated channels / RS of the second cell or second list of cells.

[0279] In some embodiments, if qnew is SSB, terminal device 120 may not monitor or receive channels / RS of the second list of cells, for example, the second cell or second list of cells may be suspended, for example, until a new TCI state is indicated / activated and / or after application timing.

[0280] In some embodiments, if an RS associated with the second physical cell ID (having the same index as the RS of the TCI_N) is present in a third cell in the second list of cells, then the TCI_N may be applied to the third cell, e.g., otherwise, the TCI_N may not be applied to the third cell.

[0281] 7A-7C show examples according to some embodiments of the present disclosure.

[0282] As shown in FIG. 7A, the terminal device 120 may be configured with a split DL / UL TCI and a non-beam alignment case.

[0283] As shown in FIG. 7B, a first list of TCI states and a second list of TCI states of a first cell (e.g., CC1) may be configured in the terminal device 120. For example, the first list of TCI states may be associated with a first physical cell ID or associated with a serving cell. For example, the second list of TCI states may be associated with a second physical cell ID or associated with a cell having a different physical cell ID (PCI). Then, a second list of cells (e.g., CC_list) may be configured in the terminal device 120, and the CC_list may be configured to refer to CC1.

[0284] As shown in Figure 7C, the TCI status of the first list may be applicable to the first cell and the second list of cells, and the TCI status of the second list may be applicable to the first cell but not to the second list of cells.

[0285] In some embodiments, the terminal device 120 may be indicated / activated with TCI_N, e.g., after application timing. In some embodiments, the terminal device 120 may not perform a beam failure recovery procedure in the first cell. In some embodiments, the terminal device 120 may perform a first beam failure recovery procedure for the first cell and / or the second cell and / or the second list of cells in accordance with some embodiments of the present disclosure.

[0286] In some embodiments, the parameters of the first beam failure recovery procedure may be based on at least one setting of the first cell, or based on a maximum / minimum between the setting of the first cell and the setting of the second cell, or based on a maximum / minimum of the setting of a first list of cells, or based on a maximum / minimum of the setting of a second list of cells. In some embodiments, the parameters may include at least one of beamFailureInstanceMaxCount, beamFailureDetectionTimer, rsrp-Threshold, candidateBeamRSList.

[0287] In some embodiments, a beam failure detection (BFD) RS set for the first beam failure recovery procedure may be determined based on the qcl-typeD configured RS in the first TCI state of the first cell, or the BFD RS set may be determined based on the RS of the TCI state for each CORESET in the first cell. For example, the terminal device 120 may not expect that the source RS of qcl-typeD of the first TCI state (e.g., CSI-RS of channel state information (CSI) as source RS) is not one port and / or two ports. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the first beam failure recovery (BFR) may be suspended or stopped. For example, if the source RS of qcl-typeD of the first TCI state is not one port and / or two ports, the terminal device 120 may determine the CSI-RS with one port and / or two ports as the BFD RS. The CSI-RS may then be a source RS of qcl-type D for the source RS in the first TCI state and applied to the BFD RS. In some embodiments, the beam failure detection RS is based on a BFD RS set configured for the first cell. In some embodiments, the beam failure detection RS may be determined based on an RS associated with the first physical cell ID.

[0288] In some embodiments, when a beam failure is declared, the value of the beam failure indication field in the MAC CE may be the same for the first cell and the second cell.

[0289] In some embodiments, a new beam or RS may be identified from the candidate beam RS list. For example, the new beam or RS may be for both the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, the candidate beam RS list may be configured for the first cell, or may be a common candidate beam RS list configured for the first cell and the second cell, or for the first list of cells, or for the second list of cells. In some embodiments, in the MAC CE, the existence of the new beam or RS and the index of the new beam or RS may be the same for the first cell and the second cell, or for the first list of cells, or for the second list of cells.

[0290] In some embodiments, the candidate beam identifying RS set may be associated with a first physical cell ID. In some embodiments, the candidate beam identifying RS set may include at least one of a CSI-RS associated with the first physical cell ID and an SSB associated with the first physical cell ID. In some embodiments, the terminal device 120 may transmit a beam failure recovery request to a cell having the first physical cell ID and / or a cell having the second physical cell ID.

[0291] In some embodiments, the candidate beam identification RS set may include at least one of a CSI-RS associated with a first physical cell ID, an SSB associated with the first physical cell ID, a CSI-RS associated with a second physical cell ID, and an SSB associated with the second physical cell ID.

[0292] In some embodiments, the candidate beam identification RS set may include only at least one CSI-RS. For example, the candidate beam identification RS set may not include an SSB. In some embodiments, the candidate beam identification RS set may include at least one of a CSI-RS associated with a first physical cell ID and a CSI-RS associated with a second physical cell ID.

[0293] In some embodiments, if qnew is associated with a second physical cell ID, then qnew may not be applied to the second list of cells.

[0294] In some embodiments, the first cell may have two sets of RSs for candidate beam identification. For example, a first set of RSs and a second set of RSs. In some embodiments, if TCI_N is indicated to the terminal device 120, the beam failure recovery procedure may be performed based on the second set of RSs. In some embodiments, if TCI_S is indicated to the terminal device 120, the beam failure recovery procedure may be performed based on the first set of RSs. In some embodiments, the RSs in the first set of RSs may be associated with a first physical cell ID. In some embodiments, the RSs in the second set of RSs may be associated with a second physical cell ID and / or the first physical cell ID.

[0295] In some embodiments, terminal device 120 may monitor a PDCCH in the first cell and the second cell after the first timing, and the PDCCH may be based on a QCL parameter associated with qnew.

[0296] In some embodiments, after the first beam failure recovery procedure is successful, qnew may replace the source RS set to the first TCI state, or qnew may replace the first TCI state in the corresponding TCI codepoint, e.g., until a new TCI state is indicated / activated for the first cell and the second cell. For example, qnew may be a periodic CSI-RS. For example, the number of ports of qnew may be one or two ports. In some embodiments, if qnew is a synchronization signal (SS) / physical broadcast channel (PBCH), qnew may not replace the source RS set to the first TCI state.

[0297] In some embodiments, the terminal device 120 may receive an indication / activation of the second TCI state. The fields of cell information in the source RS and QCL information of the second TCI state of the second cell may not be present. The terminal device 120 may perform a second beam failure recovery procedure with respect to the second cell. For example, the second beam failure recovery procedure may be separate from the first beam failure recovery procedure. In some embodiments, a beam failure detection RS may be configured for the second cell or may be determined based on the RS of the second cell. For example, the RS may be configured for the second TCI state and for the source RS and QCL information with qcl-TypeD configured. In some embodiments, parameters for the second beam failure recovery procedure may be configured for the second cell. In some embodiments, a candidate beam identification RS set for the second beam failure recovery procedure may be configured for the second cell, or may be configured for the first cell, or may be configured for the first / second list of cells. In some embodiments, multiple TCI states may be configured in the second cell, and at least the source RS or spatial reception parameters of qcl-Type D for different TCI states may refer to different cells, and the RS set for candidate beam identification for the second beam failure recovery procedure may be the RS set configured to the cell with the lowest ID among the different cells.

[0298] In some embodiments, the terminal device 120 may be indicated / activated with TCI_N, for example, after application timing. In some embodiments, the terminal device 120 may not need to monitor paging and short messages based on the QCL parameters corresponding to TCI_N. In some embodiments, the terminal device 120 may monitor paging and short messages in a CSS (e.g., TypeD CSS) or USS based on the QCL parameters corresponding to TCI_N. In some embodiments, if the terminal device 120 receives a modification of the information broadcast channel (BCCH), the terminal device 120 may not need to monitor the PDCCH scrambled with SI-RNTI based on the QCL parameters corresponding to TCI_N, or the terminal device 120 may ignore the information. In some embodiments, the terminal device 120 may monitor the PDCCH at the monitoring occasion based on the index of the SSB associated with the TCI_N. In some embodiments, the terminal device 120 may monitor at the monitoring occasion based on the index of the SSB associated with the previous or latest TCI associated with the first physical cell ID. In some embodiments, the DMRS sequence for the PDCCH may be scrambled based on the value of the second physical cell ID. In some embodiments, the DMRS sequence for the PDCCH may be scrambled based on the value of the first physical cell ID.

[0299] In some embodiments, terminal device 120 may be configured with a mode of non codebook based uplink transmission. In some embodiments, terminal device 120 may be configured with two CSI-RS (e.g., a first CSI-RS and a second CSI-RS) and two SRS resource sets (e.g., a first SRS resource set and a second SRS resource set) for non codebook based uplink transmission. For example, the first CSI-RS may be associated with the first SRS resource set. For example, the second CSI-RS may be associated with the second SRS resource set.

[0300] In some embodiments, both the first SRS resource set and the second SRS resource set are triggered in an overlapping manner in the time domain. For example, the overlapping manner may refer to an overlap of the minimum gap between two pairs of associated NZP-CSI-RS and SRS corresponding to the two SRS resource sets. In some embodiments, the terminal 120 may not be expected to update the SRS precoding information if the gap between the last symbol of reception of the first CSI-RS resource and the first symbol of SRS transmission corresponding to the first SRS resource set is less than 42 OFDM symbols. In some embodiments, the terminal 120 may not be expected to update the SRS precoding information if the gap between the last symbol of reception of the second CSI-RS resource and the first symbol of SRS transmission corresponding to the second SRS resource set is less than 42+d OFDM symbols. For example, d may be a non-negative integer. For example, 0<=d<=42. For example, d may be the number of overlapping symbols of the two pairs of CSI-RS and SRS. In some embodiments, the first symbol of the first CSI-RS resource may be earlier or later than the second CSI-RS resource in the time domain. In some embodiments, the index of the first CSI-RS resource may be lower or not greater than the index of the second CSI-RS resource. In some embodiments, the first symbol of the SRS in the first SRS resource set may be earlier or not later than the SRS in the second SRS resource set in the time domain. In some embodiments, the index of the first SRS resource set may be lower or not greater than the index of the second SRS resource set.

[0301] 8 illustrates a flowchart of an example method 800 according to some embodiments of the present disclosure. For example, the method 800 may be implemented in a terminal device 120 as shown in FIG.

[0302] At block 810, the terminal device 120 receives a configuration from a network device (e.g., the network device 110 as shown in FIG. 1 ) indicating that each of the cell groups serving the terminal device is associated with at least one of a plurality of TRPs (e.g., TRPs 130-1, 130-2 as shown in FIG. 1 ) coupled to the network device.

[0303] In block 820, in response to detecting a beam failure in a cell in the cell group, the terminal device 120 sends a beam failure recovery request to the network device, where the beam failure recovery request comprises TRP information related to the beam failure detected in the cell.

[0304] In some embodiments, each of the multiple TRPs may be represented by at least one of a CORESET pool index, a CORESET group identifier, an identifier of an RS set for beam failure detection, an identifier of an RS set for new / candidate beam identification, spatial relationship information, an SRS resource set, a TCI state, and a QCL parameter set.

[0305] In some embodiments, the multiple TRPs may comprise a first TRP and a second TRP, the cell group may comprise a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells may be configured with a first set of RSs for beam failure detection and a first set of RSs for new / candidate beam identification, and the second subset of cells may be configured with a second set of RSs for beam failure detection and a second set of RSs for new / candidate beam identification.

[0306] In some embodiments, in response to detecting a beam failure based on the first set of RSs, the terminal device 120 may send a first beam failure recovery request to the network device, where the first beam failure recovery request comprises at least an indication of a first TRP or a first subset of cells. In response to detecting a beam failure based on a second set of RSs for beam failure detection, the terminal device 120 may send a second beam failure recovery request to the network device, where the second beam failure recovery request comprises at least an indication of a second TRP or a second subset of cells.

[0307] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may indicate one of the multiple TRPs associated with a beam obstruction detected in the cell.

[0308] In some embodiments, the TRP information may comprise an indication of a TRP index that is common to all cells indicated in the beam failure recovery request.

[0309] In some embodiments, the TRP information may comprise an indication of the TRP index of each of the cells indicated in the beam failure recovery request.

[0310] In some embodiments, a cell may be associated with a plurality of TRPs, and the TRP information may comprise at least one of: first information indicating a number of TRPs associated with a beam failure detected in the cell; second information indicating an index of one of the plurality of TRPs associated with a beam failure detected in the cell; and third information indicating which TRP of the plurality of TRPs a new beam has been identified in.

[0311] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may comprise first information indicating a number of TRPs associated with beam failures detected in the cell, and second information indicating an RS index for a new beam identified in one of the multiple TRPs, where the RS index indicates an index of the one TRP.

[0312] 9 illustrates a flowchart of an example method 900 according to some embodiments of the present disclosure. For example, the method 900 may be implemented in the network device 110 as shown in FIG.

[0313] At block 910, the network device 110 transmits a configuration to the terminal device (e.g., terminal device 120 as shown in FIG. 1 ) indicating that each of the cell groups serving the terminal device is associated with at least one of a plurality of TRPs (e.g., TRPs 130-1, 130-2 as shown in FIG. 1 ) coupled to the network device 110.

[0314] In block 920, in response to detecting a beam failure in a cell in the cell group, the network device 110 receives a beam failure recovery request from the terminal device, where the beam failure recovery request comprises TRP information related to the beam failure detected in the cell.

[0315] In some embodiments, each of the multiple TRPs may be represented by at least one of a CORESET pool index, a CORESET group identifier, an identifier of an RS set for beam failure detection, an identifier of an RS set for new / candidate beam identification, spatial relationship information, an SRS resource set, a TCI state, and a QCL parameter set.

[0316] In some embodiments, the multiple TRPs may comprise a first TRP and a second TRP, the cell group may comprise a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells may be configured with a first set of RSs for beam failure detection and a first set of RSs for new / candidate beam identification, and the second subset of cells may be configured with a second set of RSs for beam failure detection and a second set of RSs for new / candidate beam identification.

[0317] In some embodiments, in response to detecting a beam failure based on the first set of RSs, the network device 110 may receive a first beam failure recovery request from the terminal device, where the first beam failure recovery request comprises at least an indication of a first TRP or a first subset of cells. In response to detecting a beam failure based on a second set of beam failure detection RSs, the network device 110 may receive a second beam failure recovery request from the terminal device, where the second beam failure recovery request comprises at least an indication of a second TRP or a second subset of cells.

[0318] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may indicate one of the multiple TRPs associated with a beam obstruction detected in the cell.

[0319] In some embodiments, the TRP information may comprise an indication of a TRP index that is common to all cells indicated in the beam failure recovery request.

[0320] In some embodiments, the TRP information may comprise an indication of the TRP index of each of the cells indicated in the beam failure recovery request.

[0321] In some embodiments, a cell may be associated with a plurality of TRPs, and the TRP information may comprise at least one of: first information indicating a number of TRPs associated with a beam failure detected in the cell; second information indicating an index of one of the plurality of TRPs associated with a beam failure detected in the cell; and third information indicating which TRP of the plurality of TRPs a new beam has been identified in.

[0322] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may comprise first information indicating a number of TRPs associated with beam failures detected in the cell, and second information indicating an RS index for a new beam identified in one of the multiple TRPs, where the RS index indicates an index of the one TRP.

[0323] In some embodiments, the terminal device comprises circuitry configured to receive a configuration from the network device and, in response to a beam failure being detected in a cell in the cell group, transmit a beam failure recovery request to the network device, where the configuration indicates that each of the cells in the cell group serving the terminal device is associated with at least one of a plurality of transmission and reception points (TRPs) coupled to the network device, and the beam failure recovery request comprises TRP information associated with the beam failure detected in the cell.

[0324] In some embodiments, each of the multiple TRPs is represented by at least one of a control resource set (CORESET) pool index, a CORESET group identifier, an identifier of a reference signal (RS) set for beam failure detection, an identifier of an RS set for new / candidate beam identification, spatial relationship information, a sounding reference signal (SRS) resource set, a transmission configuration indicator (TCI) state, and a quasi-co-location parameter set.

[0325] In some embodiments, the plurality of TRPs comprises a first TRP and a second TRP, and the cell group comprises a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells being configured with a first set of RSs for beam failure detection and a first set of RSs for new / candidate beam identification, and the second subset of cells being configured with a second set of RSs for beam failure detection and a second set of RSs for new / candidate beam identification.

[0326] In some embodiments, the terminal device comprises circuitry configured to send a first beam failure recovery request to the network device in response to a beam failure being detected based on the first set of RSs and to send a second beam failure recovery request to the network device in response to a beam failure being detected based on the second set of RSs for beam failure detection, where the first beam failure recovery request comprises at least an indication of a first TRP or a first subset of cells and the second beam failure recovery request comprises at least an indication of a second TRP or a second subset of cells.

[0327] In some embodiments, a cell is associated with multiple TRPs, and the TRP information indicates one of the multiple TRPs associated with a beam obstruction detected in the cell.

[0328] In some embodiments, the TRP information comprises an indication of a TRP index that is common to all cells indicated in the beam failure recovery request.

[0329] In some embodiments, the TRP information comprises an indication of the TRP index of each of the cells indicated in the beam failure recovery request.

[0330] In some embodiments, the cell is associated with a plurality of TRPs, and the TRP information comprises at least one of first information indicating a number of TRPs associated with a beam failure detected in the cell, second information indicating an index of one of the plurality of TRPs associated with a beam failure detected in the cell, and third information indicating which TRP of the plurality of TRPs a new beam has been identified in.

[0331] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information comprises first information indicating a number of TRPs associated with beam failures detected in the cell, and second information indicating an RS index for a new beam identified in one of the plurality of TRPs, where the RS index indicates an index of the one TRP.

[0332] In some embodiments, the network device comprises circuitry configured to send a configuration to the terminal device and to receive a beam failure recovery request from the terminal device in response to a beam failure being detected in a cell in the cell group, where the configuration indicates that each of the cells in the cell group serving the terminal device is associated with at least one of a plurality of transmission and reception points (TRPs) coupled to the network device, and the beam failure recovery request comprises TRP information associated with the beam failure detected in the cell.

[0333] In some embodiments, each of the multiple TRPs is represented by at least one of a control resource set (CORESET) pool index, a CORESET group identifier, an identifier of a reference signal (RS) set for beam failure detection, an identifier of an RS set for new / candidate beam identification, spatial relationship information, a sounding reference signal (SRS) resource set, a transmission configuration indicator (TCI) state, and a quasi-co-location parameter set.

[0334] In some embodiments, the plurality of TRPs comprises a first TRP and a second TRP, and the cell group comprises a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells being configured with a first set of RSs for beam failure detection and a first set of RSs for new / candidate beam identification, and the second subset of cells being configured with a second set of RSs for beam failure detection and a second set of RSs for new / candidate beam identification.

[0335] In some embodiments, the network device comprises circuitry configured to receive a first beam failure recovery request from the terminal device in response to a beam failure being detected based on a first set of RSs and to receive a second beam failure recovery request from the terminal device in response to a beam failure being detected based on a second set of RSs for beam failure detection, where the first beam failure recovery request comprises at least an indication of a first TRP or a first subset of cells, and the second beam failure recovery request comprises at least an indication of a second TRP or a second subset of cells.

[0336] In some embodiments, a cell is associated with multiple TRPs, and the TRP information indicates one of the multiple TRPs associated with a beam obstruction detected in the cell.

[0337] In some embodiments, the TRP information comprises an indication of a TRP index that is common to all cells indicated in the beam failure recovery request.

[0338] In some embodiments, the TRP information comprises an indication of the TRP index of each of the cells indicated in the beam failure recovery request.

[0339] In some embodiments, the cell is associated with a plurality of TRPs, and the TRP information comprises at least one of first information indicating a number of TRPs associated with a beam failure detected in the cell, second information indicating an index of one of the plurality of TRPs associated with a beam failure detected in the cell, and third information indicating which TRP of the plurality of TRPs a new beam has been identified in.

[0340] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information comprises first information indicating a number of TRPs associated with beam failures detected in the cell, and second information indicating an RS index for a new beam identified in one of the plurality of TRPs, where the RS index indicates an index of the one TRP.

[0341] 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 example implementation of the network apparatus 110, the TRP 130, and / or the terminal apparatus 120 shown in FIG. 1. Thus, the apparatus 1000 may be implemented in or at least as part of the network apparatus 110, the TRP 130, and / or the terminal apparatus 120 shown in FIG.

[0342] As shown in the figure, the device 1000 includes 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 for bidirectional communication. The TX / RX 1040 has at least one antenna to facilitate communication, although in practice, the access nodes described herein may 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, an Un interface for communication between an eNB and a relay node (RN), or an Uu interface for communication between an eNB and a terminal device.

[0343] The program 1030 may be considered to include program instructions that, when executed by an associated processor 1010, enable the device 1000 to operate in accordance with embodiments of the present disclosure, as discussed herein with reference to Figures 1-9. The embodiments of the present disclosure may be implemented by computer software, hardware, or a combination of software and hardware executable by the processor 1010 of the device 1000. The processor 1010 may be configured to implement various embodiments of the present disclosure. The combination of the processor 1010 and the memory 1020 may also constitute a processing means 1050 suitable for implementing embodiments of the present disclosure.

[0344] The memory 1020 may be of any type suitable for the local technology network and may be implemented by any suitable data storage technology, including, but not limited to, computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed and removable memories, etc. Although only one memory 1020 is shown in the device 1000, multiple physically distinct memory modules may be installed in the device 1000. The processor 1010 may be of any type suitable for the local technology network and may include, but is not limited to, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor configurations. The device 1000 may have multiple processors, for example application specific integrated circuit chips time-slaved to a clock synchronous with a master processor.

[0345] In general, various embodiments of the present disclosure may be implemented by hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented by hardware, and other aspects may be implemented by firmware or software that may be executed by a controller, microprocessor, or other computing device. Various aspects of the embodiments of the present disclosure have been shown and described as block diagrams, flow charts, or illustrated by some other pictorial representation, and it will be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented by, for example, but not limited to, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or combinations thereof.

[0346] The present disclosure further provides at least one computer program product tangibly stored in a computer readable non-transitory storage medium. The computer program product includes computer executable instructions, such as instructions included in program modules. The instructions execute on a target real or virtual processor device to perform, for example, the processes or methods described above with reference to Figures 10 and 11. Typically, 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 among program modules as desired. The machine readable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0347] The program codes 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 apparatus, and when the program codes are executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are performed. The program codes 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.

[0348] The above program code may be embodied on a machine-readable medium, which may be any tangible medium that contains or stores a program for use by or in conjunction 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 foregoing. Even more specific examples of machine-readable storage media include one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0349] It should be understood that although operations have been described in a particular order, it is not required that such operations be performed in the particular order or sequence shown, or that all of the operations shown be performed, in order to achieve desired results. In some situations, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes some specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to certain embodiments. Some features that are described in the context of individual embodiments may be implemented in combination in an embodiment. Conversely, various features that are described in the context of an embodiment may be implemented in multiple embodiments separately or in any suitable subcombination.

[0350] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined by 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. A terminal device, means for receiving, from a network device, first downlink control information (DCI) scheduling at least one first physical downlink shared channel (PDSCH); means for receiving the at least one first PDSCH from the network device based on a first transmission configuration indicator (TCI) state applied for downlink transmission, when the first TCI state is associated with a first physical cell identity (ID); means for receiving the at least one first PDSCH from the network device based on at least one first quasi co-location (QCL) parameter associated with the first physical cell ID or at least one second QCL parameter associated with the second physical cell ID when the first TCI state is associated with a second physical cell ID; A terminal device comprising:

2. Means for receiving, from the network device, a second DCI indicating the first TCI state in a first control resource set (CORESET), the first CORESET being configured to have a first CORESET pool index; The terminal device according to claim 1 , further comprising:

3. Means for receiving, from the network device, a radio resource control (RRC) message indicating a list of TCI states including the first TCI state; The terminal device according to claim 1 , further comprising: The first TCI state is applied from a first slot that is at least a first number of symbols after a last symbol of a first positive hybrid automatic repeat request-acknowledge (HARQ-ACK). The terminal device according to claim 2.

5. A method for receiving, from the network device, a third DCI for scheduling at least one second PDSCH; means for receiving, from the network device, the at least one second PDSCH based on a second TCI state applied for downlink transmission, if the second TCI state is associated with the first physical cell ID; means for receiving the at least one second PDSCH from the network device based on at least one third QCL parameter associated with the first physical cell ID or at least one fourth QCL parameter associated with the second physical cell ID when the second TCI state is associated with the second physical cell ID; The terminal device according to claim 4 , further comprising: Means for receiving, from the network device, a fourth DCI in a second CORESET configured to have a second CORESET pool index, the fourth DCI indicating the second TCI state; The terminal device according to claim 5 , further comprising: The second TCI state is applied from a first slot that is at least the first number of symbols after a last symbol of a second positive HARQ-ACK. The terminal device according to claim 5.

8. A method for performing a first beam failure recovery (BFR) procedure for the first CORESET pool index based on a first set of reference signals associated with the first TCI state; and means for performing a second BFR procedure based on a second set of reference signals associated with the second TCI state for the second CORESET pool index; The terminal device according to claim 6 , further comprising:

9. A network device, means for transmitting, to a terminal device, first downlink control information (DCI) scheduling at least one first physical downlink shared channel (PDSCH); means for transmitting the at least one first PDSCH to the terminal device based on a first transmission configuration indicator (TCI) state applied for downlink transmission, when the first TCI state is associated with a first physical cell identity (ID); means for transmitting the at least one first PDSCH to the terminal device based on at least one first quasi co-location (QCL) parameter associated with the first physical cell ID or at least one second QCL parameter associated with the second physical cell ID when the first TCI state is associated with a second physical cell ID; A network device comprising:

10. Means for transmitting a second DCI indicating the first TCI state in a first control resource set (CORESET), the first CORESET being configured to have a first CORESET pool index, in the terminal device; The network device of claim 9 further comprising:

11. A method for transmitting a third DCI to the terminal device, the third DCI scheduling at least one second PDSCH; means for transmitting the at least one second PDSCH to the terminal device based on a second TCI state applied for downlink transmission, if the second TCI state is associated with the first physical cell ID; means for transmitting the at least one second PDSCH to the terminal device based on at least one third QCL parameter associated with the first physical cell ID or at least one fourth QCL parameter associated with the second physical cell ID when the second TCI state is associated with the second physical cell ID; The network device of claim 10 further comprising:

12. Means for transmitting, in the terminal device, a fourth DCI indicating the second TCI state in a second CORESET configured to have a second CORESET pool index; The network device of claim 11 further comprising:

13. A first beam failure recovery (BFR) procedure is performed by the terminal device for the first CORESET pool index based on a first set of reference signals associated with the first TCI state, and a second BFR procedure is performed by the terminal device for the second CORESET pool index based on a second set of reference signals associated with the second TCI state.

13. The network device of claim 12.

14. A method of communication performed by a terminal device, comprising: receiving, from a network device, first downlink control information (DCI) scheduling at least one first physical downlink shared channel (PDSCH); receiving, from the network device, the at least one first PDSCH based on a first transmission configuration indicator (TCI) state applied for downlink transmission, when the first TCI state is associated with a first physical cell identity (ID); receiving, from the network device, the at least one first PDSCH based on at least one first quasi co-location (QCL) parameter associated with the first physical cell ID or at least one second QCL parameter associated with the second physical cell ID when the first TCI state is associated with a second physical cell ID; The method includes:

15. A method of communication performed by a network device, comprising: transmitting, to a terminal device, first downlink control information (DCI) scheduling at least one first physical downlink shared channel (PDSCH); transmitting the at least one first PDSCH to the terminal device based on a first transmission configuration indicator (TCI) state applied for downlink transmission, the first TCI state being associated with a first physical cell identity (ID); transmitting the at least one first PDSCH to the terminal device based on at least one first quasi co-location (QCL) parameter associated with the first physical cell ID or at least one second QCL parameter associated with the second physical cell ID when the first TCI state is associated with a second physical cell ID; The method includes:

Images