Terminal device and method executed on the terminal device

Abstract

The purpose of this disclosure is to provide methods, apparatus, and computer-readable media for communication. [Solution] The terminal device receives an indication from the network device of at least one transmit setting indicator (TCI) state in the detected downlink control information (DCI) within the first physical downlink control channel (PDCCH). The terminal device also receives a downlink transmission from the network device based on at least one TCI state based on the first condition. Furthermore, the terminal device applies at least one TCI state to at least one RS in a first set of reference signals (RS) applied for beam fault detection, based on the first condition. Furthermore, the terminal device determines an estimate of the radio link quality between the terminal device and the network device based on the first set of RS. This enables proper beam fault detection.

Description

[Technical Field]

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

[0002] At the 3rd Generation Partnership Project (3GPP®) meeting RAN#86, it was agreed to support enhanced multi-beam operations, primarily targeting frequency band 2 (FR2), but also applicable to frequency band 1 (FR1). It was agreed to identify and define features to facilitate more efficient beam management (low latency, low overhead) for both downlink (DL) and uplink (UL). For example, it was proposed to support a common beam for transmitting and receiving data and control information for both DL and UL. It was also proposed to support a unified Transmission Configuration Indication (TCI) framework for DL ​​and UL beam direction. Furthermore, MIMO (Multi-input multi-output) was proposed, which includes features to facilitate the use of multiple antenna elements at base stations for both sub-6GHz and above-6GHz frequency bands. Therefore, enhancing multi-beam operations is worthwhile. [Overview of the Initiative] [Problems that the invention aims to solve]

[0003] Generally, embodiments of this disclosure provide methods, apparatus, and computer storage media for communication. [Means for solving the problem]

[0004] In a first embodiment, a method for communication is provided. The method includes, in a terminal device, receiving from a network device an indication of at least one transmit setting indicator (TCI) state in detected downlink control information (DCI) in a first physical downlink control channel (PDCCH); receiving a downlink transmission from the network device based on at least one TCI state based on a first condition; applying at least one TCI state to at least one RS in a first set of reference signals (RS) applied for beam fault detection, or including a third RS indicated by at least one TCI state in the first set of RSs based on the first condition; and determining an estimate of radio link quality between the terminal device and the network device based on the first set of RSs.

[0005] In a second embodiment, a method for communication is provided. The method includes, in a terminal device, determining an estimate of radio link quality according to a first reference signal (RS) and a second RS; transmitting a request to a network device for an indication of the transmit setting indicator (TCI) status in an uplink resource based on a first condition; and monitoring one or more physical downlink control channels (PDCCH) in one or more control resource sets (CORESET).

[0006] In a third embodiment, a method for communication is provided. The method includes, in a network device, transmitting to a terminal device an indication of at least one transmit setting indicator (TCI) state in downlink control information (DCI) in a first physical downlink control channel (PDCCH); transmitting a downlink transmission from the network device to the terminal device based on at least one TCI state based on a first condition; and transmitting at least one RS in a first set of reference signals (RS) applied for beam fault detection based on a first condition.

[0007] In a fourth aspect, a method for communication is provided. The method includes, in a network device, transmitting a first reference signal (RS) and a second RS to a terminal device; transmitting a first set of physical downlink control channels (PDCCHs) in one or more control resource sets (CORESETs) in a third state to the terminal device; receiving a request from the terminal device for an indication of a transmit setting indicator (TCI) state in an uplink resource; and, based on the receipt of the request, transmitting a second set of PDCCHs in one or more CORESETs to the terminal device in a fourth TCI state.

[0008] In a fifth aspect, a terminal device is provided. The terminal device includes a processor and memory coupled to the processor. Instructions are stored in the memory, which, when executed by the processor, cause the terminal device to perform the method according to the first aspect of the present disclosure.

[0009] In a sixth aspect, a terminal device is provided. The terminal device includes a processor and memory coupled to the processor. Instructions are stored in the memory, and when executed by the processor, the instructions cause the terminal device to perform the method according to the second aspect of the present disclosure.

[0010] In a seventh aspect, a network device is provided. The network device includes a processor and memory coupled to the processor. Instructions are stored in the memory, which, when executed by the processor, cause the network device to perform the method according to the third aspect of this disclosure.

[0011] In the eighth aspect, a network device is provided. The network device includes a processor and memory coupled to the processor. Instructions are stored in the memory, and when executed by the processor, the instructions cause the network device to perform the method according to the fourth aspect of the present disclosure.

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

[0013] Other features of the present disclosure should be readily understood through the following description.

Brief Description of Drawings

[0014] Through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, the above and other objects, features, and advantages of the present disclosure should become clearer. [Figure 1] An exemplary communication system capable of implementing embodiments of the present disclosure is shown. [Figure 2] A signaling flow of communication according to some exemplary embodiments of the present disclosure is shown. [Figure 3] An example of beam application setting in a terminal device according to some embodiments of the present disclosure is shown. [Figure 4] An example of beam application setting in a terminal device according to some embodiments of the present disclosure is shown. [Figure 5] An example of beam application setting in a terminal device according to some embodiments of the present disclosure is shown. [Figure 6] An example of beam application setting in a terminal device according to some embodiments of the present disclosure is shown. [Figure 7] An example of beam application setting in a terminal device according to some embodiments of the present disclosure is shown. [Figure 8] A signaling flow of communication according to some exemplary embodiments of the present disclosure is shown. [Figure 9] An example of beam application setting in a terminal device according to some embodiments of the present disclosure is shown. [Figure 10] An example of beam obstacle detection according to some embodiments of the present disclosure is shown. [Figure 11]A flowchart of an exemplary communication method implemented by a terminal device according to some embodiments of the present disclosure is shown. [Figure 12] A flowchart of an exemplary communication method implemented by a terminal device according to some embodiments of the present disclosure is shown. [Figure 13] A flowchart of an exemplary communication method implemented by a network device according to some embodiments of the present disclosure is shown. [Figure 14] A flowchart of an exemplary communication method implemented by a network device according to some embodiments of the present disclosure is shown. [Figure 15] It is a schematic block diagram of a device suitable for implementing embodiments of the present disclosure. Throughout all the drawings, the same or similar reference numerals represent the same or similar elements.

Embodiments for Carrying Out the Invention

[0015] The principles of the present disclosure will be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and are helpful for those skilled in the art to understand and implement the present disclosure, without suggesting any limitation to the scope of the present disclosure. The present disclosure described in this specification can be implemented in various ways other than those described below.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used have the same meaning as commonly understood by those skilled in the art to which the present disclosure pertains.

[0017] 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 terminals (UEs), personal computers, desktops, mobile phones, cell phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, IoT (Internet of Things) devices, IoE (Internet of Everything) devices, machine-type communication (MTC) equipment, vehicle-mounted equipment for V2X communication (where X means pedestrian, vehicle, or infrastructure / network), imaging devices such as digital cameras, game consoles, music storage and playback devices, and internet devices that enable wireless / wired internet access and browsing. The term “terminal device” can be used interchangeably with UE, mobile station, subscriber equipment, mobile terminal, user terminal, or wireless device. The term “network device” refers to a device capable of providing or hosting a cell or coverage from which terminal devices can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), Evolved Node B (eNodeB or eNB), Next Generation Node B (gNB), Transmit / Receive Point (TRP), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), Femtonode, piconode, and other low-power nodes.

[0018] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first and second network devices may be a master node and the other a secondary node. The first and second network devices 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 is an eNB, and the second RAT device is a gNB. Information related to different RATs may be transmitted to the terminal device from at least one of the first and second network devices. In one embodiment, first information may be transmitted from the first network device to the terminal device, and second information may be transmitted directly from the second network device to the terminal device or via the first network device. In one embodiment, information related to the configuration of the terminal device set 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 transmitted directly from the second network device to the terminal device or via the first network device.

[0019] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural unless otherwise clearly indicated in the context. The term “including” and its variations are interpreted as an open term meaning “including but not limited to.” The term “based on” is interpreted as “based on at least partially.” The terms “one embodiment” and “one embodiment” are interpreted as “at least one embodiment.” The term “another embodiment” is interpreted as “at least one other embodiment.” Terms such as “first,” “second,” etc., may refer to different or the same subject. The following may include other explicit and implicit definitions.

[0020] In some examples, values, processes, or devices are referred to as "optimal," "lowest," "highest," "minimum," "maximum," etc. It is understood that such descriptions are intended to indicate that a choice is available from among several functional alternatives, and that such a choice does not necessarily have to be better, smaller, more expensive, or more preferable than the others.

[0021] As used herein, the term “circuit” may mean a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of an analog hardware circuit and / or a digital hardware circuit and software / firmware. As a further example, a circuit may be any part of a software-equipped hardware processor, such as a digital signal processor, software, and memory, which work together to enable a device such as a terminal or network device to perform various functions. In yet another example, a circuit may be a hardware circuit and / or processor, such as a microprocessor or a part of a microprocessor, which requires software / firmware for operation but may not have software when not needed for operation. As used herein, the term “circuit” also encompasses a mere hardware circuit or processor, or a part of a hardware circuit or processor, and the implementation of its (or their) accompanying software and / or firmware.

[0022] In this specification, the term "TRP" refers to an antenna array (having one or more antenna elements) available to network equipment at a specific geographic location. While some embodiments of this disclosure are described with reference to, for example, multiple TRPs, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation to the scope of this disclosure. It should be understood that the disclosure described herein can be implemented in various ways other than those described below.

[0023] Generally, in uplink (UL) transmissions, one TRP typically 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 an associated transmission (such as a push transmission), and the term "multiple TRPs for UL" refers to the use of multiple SRS resource sets to perform an associated transmission (such as a push transmission).

[0024] As described above, to enhance multibeam operations, primarily targeting FR2 but also applicable to FR1, the following features are identified and defined to facilitate more efficient beam management (low latency, low overhead) of DL / UL in order to support higher intra-cell and L1 / L2-centered inter-cell mobility, and / or more configured TCI states: i. A common beam for DL ​​and UL data and control transmission and reception, especially for in-band CA; ii. A unified TCI framework for DL ​​and UL beam indication; iii. Improved latency and efficiency by enhancing the signaling mechanism for the above features and increasing the use of dynamic control signaling (as opposed to RRC).

[0025] To indicate DL / UL beam indications of coupling or separation from an active TCI state, it has been proposed to support L1-based beam indications using at least UE-specific (unicast) DCI. Existing DCI formats 1_1 and 1_2 are reused for beam indications, and a mechanism is supported for the UE to confirm successful decoding of the beam indication. ACK / NAK of the Physical Downlink Shared Channel (PDSCH) scheduled by the DCI transmitting the beam indication can also be used as an ACK to the DCI.

[0026] It has also been proposed to support the activation of one or more TCI states via a media access control (MAC) control element (CE) similar to that in Release.15 / 16. At a minimum, in the case of a single activated TCI state, the activated TCI state is applied.

[0027] Rel-17's unified TCI beam designation supports DCI formats 1_1 / 1_2 without DL assignment, and the acknowledgment / negation (ACK / NACK) mechanism is used as in the case of PDSCH releases of semi-persistent scheduling (SPS) with type-1 and type-2 HARQ-ACK codebooks. Upon successful reception of the beam designation DCI, the UE reports an ACK.

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

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

[0030] The TCI field can be used for signals in the following states: 1) coupled DL / UL TCI state, 2) DL-only TCI state (in the case of isolated DL / UL TCI), and 3) UL-only TCI state (in the case of isolated DL / UL TCI).

[0031] Furthermore, Rel-16 utilizes the DCI fields for the DCI format identifier, carrier indicator, bandwidth sub-indicator, time-domain resource allocation (TDRA), downlink allocation index (if configured), scheduled PUCCH transmit power control (TPC) instruction, PUCCH resource indicator, and PDSCH-to-HARQ_feedback timing indicator (if present). The remaining unused DCI fields and code points are reserved for Release 17.

[0032] It has also been proposed to support UEs in reporting whether they support TCI updates using DCI format 1_1 / 1_2. For UEs that support TCI updates using DCI format 1_1 / 1_2, TCI updates must be supported by using DCI 1_1 / 1_2 with DL assignments, and support for the above functionality for TCI updates using DCI format 1_1 / 1_2 without DL assignments is optional for the UE.

[0033] In DCI-based beam designation for Rel-17, the application time of the beam designation is the first slot or first sub-slot which is at least Xms or Y symbols from the last symbol of the acknowledgment response for the coupled or separated DL / UL beam designation.

[0034] In some embodiments, one slot contains 14 or 12 orthogonal frequency division multiplexing (OFDM) symbols. In some embodiments, a sub-slot contains at least one of {2, 4, 7} OFDM symbols.

[0035] According to format 1_1 of section 7.3.1.2.2 of TS38.212, the transmit configuration instruction is 0 bits if the upper layer parameter tci-PresentInDCI is not enabled, and 3 bits otherwise, as defined in section 5.1.5 of [6, TS38.214]. According to format 1_2 of section 7.3.1.2.3 of TS38.212, the transmit configuration instruction is 0 bits if the upper layer parameter tci-PresentDCI-1-2 is not set, and otherwise, 1, 2, or 3 bits determined by the upper layer parameter tci-PresentDCI-1-2 as defined in section 5.1.5 of [6, TS38.214].

[0036] The UE receives an activation instruction used to map up to eight TCI states to the code points of the DCI field “Transmit Setup Instruction” of one CC / DL BWP or one set of CC / DL BWPs, as described in section 6.1.3.14 of [10, TS38.321]. Once the set of TCI state IDs is activated for the set of CC / DL BWPs and the CCs indicated in the activation instruction determine the applicable list of CCs, the same set of TCI state IDs is applied to all DL BWPs in the indicated CCs.

[0037] If the UE supports two TCI states in the code point of the DCI field “Send Setup Instruction”, the UE may receive an activation instruction, as described in section 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 code point of the DCI field “Send Setup Instruction”. The UE is not expected to receive more than eight TCI states in the activation instruction.

[0038] If the DCI format 1_2 contains a DCI field "Transmit Setup Instruction," and the number of code points S in the DCI field "Transmit Setup Instruction" of DCI format 1_2 is less than the number of TCI code points activated by the activation instruction, as described in sections 6.1.3.14 and 6.1.3.24 of [10,TS38.321], then only the first S activated code points are applied for DCI format 1_2. For example, if the number of bits in the DCI field "Transmit Setup Instruction" of DCI format 1_2, or the number of bits in the upper layer parameter tci-PresentDCI-1-2, is 1 bit, then S=2. As another example, if the number of bits in the DCI field "Transmit Setup Instruction" of DCI format 1_2, or the number of bits in the upper layer parameter tci-PresentDCI-1-2, is 2 bits, then S=4. As another example, if the number of bits in the DCI field "Transmit Settings Instruction" in DCI format 1_2, or the number of bits in the upper layer parameter tci-PresentDCI-1-2, is 3, then S=8.

[0039] Furthermore, DCI formats 1_1 / 1_2 can be used for dynamic beam designation regardless of whether DL assignment is present. When beam designation is indicated in DCI format with DL scheduling, the ACK / NACK of the PDSCH can be used to indicate the ACK of the beam designation, and the designated beam can be applied after a certain time.

[0040] However, if there is a mismatch between the beam / TCI state of the Beam Fault Detection (BFD) reference signal (RS) and the indicated common beam / TCI state, beam fault detection using BFD RS is not suitable for monitoring link quality. Furthermore, if there is a mismatch between the beam / TCI state of BFD RS and the indicated common beam / TCI state, beam fault detection using BFD RS is not suitable for monitoring link quality. Also, if the indicated beam / TCI state fails / blocks, the UE cannot obtain indication of other beam / TCI states unless a Beam Fault Recovery (BFR) is performed. After a BFR, the newly identified beam will be used for PDCCH(CORESET), which can be considered a new common beam. However, it is necessary to define how the TCI field is handled in PDCCH(CORESET). PDCCH has a TCI field that indicates the TCI state, but the activated TCI state that can be indicated may already be inappropriate (e.g., already failed), which can lead to unnecessary / inappropriate beam updates.

[0041] To address at least some of the problems described above, we propose a beam indication solution. The terminal device receives an indication of at least one transmit setting indicator (TCI) state in the detected downlink control information (DCI) within a first physical downlink control channel (PDCCH). The terminal device also receives a downlink transmission from the network device based on at least one TCI state based on a first condition. The terminal device further applies at least one TCI state to at least one reference signal (RS) in a first RS set applied for beam fault detection, based on the first condition. Furthermore, the terminal device determines an estimate of the radio link quality between the terminal device and the network device based on the first RS set. This enables proper beam fault detection.

[0042] Figure 1 shows a schematic diagram of a communication system that can implement an embodiment of the present disclosure. The communication system 100, which is part of a communication network, includes terminal devices 110-1, 110-2, ..., 110-N, which can be collectively referred to as "terminal device 110". The number N can be any appropriate integer. For illustrative purposes only, an embodiment of the present disclosure will be described with reference to terminal device 110-1.

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

[0044] Communication in the communication system 100 may be carried out in accordance with any suitable communication protocol. Communication protocols include, but are not limited to, cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication may utilize any suitable wireless communication technology. Wireless communication technologies include, but are not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), MIMO (Multiple-Input Multiple-Output), orthogonal frequency division multiple access (OFDMA), and / or any other technologies currently known or to be developed in the future.

[0045] Embodiments of the present disclosure can be applied to any preferred scenario. For example, embodiments of the present disclosure can be implemented in low-capacity NR devices. Alternatively, embodiments of the present disclosure can be implemented in any of the following: New Wireless (NR) MIMO (multiple-input and multiple-output), NR Sidelink Enhancements, NR systems at frequencies above 52.6 GHz, NR operation extension up to 71 GHz, Narrow Band IoT (NB-IoT) / Enhanced Machine Type Communication (eMTC) on non-terrestrial networks (NTN), NTN, UE power saving function enhancements, NR coverage extensions, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB), NR multicast / broadcast services, or multi-wireless dual connectivity enhancements.

[0046] The number of network devices, terminal devices, and / or TRPs is for illustrative purposes only and should not be interpreted as implying any limitation to this disclosure. The communication system 100 may include any appropriate number of network devices, terminal devices, and / or TRPs suitable for implementing the disclosure.

[0047] In some embodiments, a TRP may be explicitly associated with a different higher-layer configuration identity. 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 transmit configuration instruction (TCI) state, or a group of TCI states, which are used to distinguish transmissions between different TRPs and terminal device 110-1. If terminal device 110-1 receives two DCIs from two CORESETs associated with different higher-layer configuration identities, the two DCIs will be 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 from different TRPs to terminal device 110. For example, if terminal device 110-1 receives a DCI from a dedicated CORESET, that DCI will be indicated from the associated TRP dedicated to that CORESET. In some embodiments, RS may be at least one of CSI-RS, SRS, positioning RS, uplink DMRS, downlink DMRS, uplink PTRS, and downlink PTRS.

[0048] In repeated transmission or reception via two TRPs, the network device 120 may select a repetition method from among several available repetition methods. The repetition method may define the transmission method for the network device 120 to use the two TRPs cooperatively, such as the multiplexing method between the two TRPs and the respective resource allocation to the two TRPs.

[0049] Figure 2 shows the signaling flow of communication between a network device and a terminal device according to some embodiments of the present disclosure. For discussion purposes, process 200 will be described with reference to Figure 1. Process 200 may involve the network device 120 and terminal device 110-1 in Figure 1.

[0050] The network device 120 transmits an instruction for at least one TCI state in the DCI within the first PDCCH to the terminal device 110-1 (2010). Furthermore, before transmitting data to the terminal device 110, the network device 120 may transmit control information associated with the data transmission. For example, the control information may schedule a resource set for the data transmission and indicate various transmission parameters related to the data transmission, such as one or more TCI states, frequency domain resource allocation (FDRA), time domain resource allocation (TDRA) which may include slot offset and start / length indicator values, demodulation reference signal (DMRS) groups, redundant versions (RV), etc. It should be understood that the transmission parameters indicated in the control information are not limited to those listed above. Embodiments of this disclosure are equally applicable to control information that includes arbitrary transmission parameters.

[0051] In the following, the terms “transmit opportunity,” “receive opportunity,” “repeat,” “transmit,” “receive,” “PDSCH transmit opportunity,” “PDSCH repeat,” “PUSCH transmit opportunity,” “PUSCH repeat,” “PUCCH opportunity,” “PUCCH repeat,” “repeat transmit,” “repeat receive,” “PDSCH transmit,” “PDSCH receive,” “PUSCH transmit,” “PUSCH receive,” “PUCCH transmit,” “PUCCH receive,” “RS transmit,” “RS receive,” “communication,” “transmit,” and “receive” can be used interchangeably. The terms “TCI status,” “QCL ​​parameter set,” “QCL ​​parameter,” “QCL ​​assumption,” and “QCL ​​setting” can be used interchangeably. The terms “TCI field,” “TCI status field,” and “transmit setting instruction” can be used interchangeably. The terms “transmit opportunity,” “transmit,” “repeat,” “receive,” “receive opportunity,” “monitoring opportunity,” “PDCCH monitoring opportunity,” “PDCCH transmit opportunity,” “PDCCH transmit,” “PDCCH candidate,” “PDCCH receive opportunity,” “PDCCH receive,” “search space,” “CORESET,” “multi-chance,” and “PDCCH repeat” can be used interchangeably. Hereinafter, the terms “PDCCH repeat,” “repeating PDCCH,” “repeating PDCCH signal,” “PDCCH candidate configured for the same scheduling,” “PDCCH,” “PDCCH candidate,” and “linked PDCCH candidate” can be used interchangeably. The terms “DCI” and “DCI format” can be used interchangeably. In some embodiments, embodiments of the present disclosure can be applied to scheduling PDSCH and PUSCH, and below, PDSCH scheduling will be described as an example. For example, embodiments of the present disclosure can be applied to PUSCH by replacing “transmit” with “receive” and / or “receive” with “transmit.” The terms “PDSCH” and “PUSCH” can be used interchangeably. The terms “transmit” and “receive” can be used interchangeably.

[0052] As specified in the 3GPP specification (TS38.214), a UE may have a list of up to M TCI-State settings within the upper-layer parameter PDSCH-Config to decode a PDSCH according to a detected PDCCH with a DCI intended for the UE and a given serving cell, where M depends on the UE's capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State includes one or two downlink reference signals and parameters that establish a pseudo-collocation relationship between the DMRS port of the PDSCH, the DMRS port of the PDCCH, or the CSI-RS port of a Channel State Information Reference Signal (CSI-RS) resource. The pseudo-collocation relationship is established by the upper-layer parameter qcl-Type1 for the first downlink (DL) RS and qcl-Type2 (if set) for the second DL RS. In the case of two DL RSs, the QCL types must not be the same, regardless of whether they refer to the same DL RS or different DL RSs. The pseudo-collocation type corresponding to each DL RS is given by the parameter qcl-Type in the higher layer of QCL-Info, and can take one of the following values. - "QCL-TypeA": {Doppler shift, Doppler diffusion, mean delay, delay diffusion} - "QCL-TypeB": {Doppler shift, Doppler diffusion} - "QCL-TypeC": {Doppler shift, mean delay} - "QCL-TypeD": {Spatial Rx parameter}

[0053] The UE receives an activation instruction as described in the section "Activating / Deactivating TCI States of UE-Specific PDSCH MAC CE" in [TS38.321] (e.g., section 6.1.3.14) or the section "Extended Activation / Deactivation of TCI States of UE-Specific PDSCH MAC CE" in [TS38.321] (e.g., section 6.1.3). The activation instruction is used to map up to eight TCI states to the code points of the DCI field "Transmit Setup Instruction" of one CC / DL BWP or one set of CC / DL BWPs. Once a set of TCI state IDs is activated for a set of CC / DL BWPs, and the CC indicated in the activation instruction determines the applicable list of CCs, the same set of TCI state IDs is applied to all DL BWPs in the indicated CC.

[0054] If the UE supports two TCI states in the code point of the DCI field “Transmit Setup Instruction”, the UE may receive an activation instruction as described in the section “Activating / Deactivating UE-Specific PDSCH MAC CE TCI States” or “Activating / Deactivating UE-Specific PDSCH MAC CE Extended TCI States” in [TS38.321] (for example, the items in section 6.1.3.14 or 6.1.3), which is used to map up to eight combinations of one or two TCI states to the code point of the DCI field “Transmit Setup Instruction”. The UE is not expected to receive more than eight TCI states in an activation instruction.

[0055] If a DCI field "Transmit Setup Instruction" exists in DCI format 1_2, and the number of code points S in the DCI field "Transmit Setup Instruction" of DCI format 1_2 is less than the number of TCI code points activated by the activation instruction, as described in sections 6.1.3.14 and 6.1.3.24 of [10,TS38.321], then only the first S activated code points are applied for DCI format 1_2.

[0056] When the UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH that transmits the activation instruction, the indicated mapping between the TCI state and the code point of the DCI field "Transmit Setup Instruction" is in the slot

number

[0057] In some embodiments, if the UE has set the upper-layer parameter tci-PresentInDCI or tci-PresentInDCI-ForFormat1_2 to "enabled" for the CORESET that schedules the PDSCH, the UE assumes that the DCI of the PDCCH sent by the CORESET (e.g., DCI format 1_1 or DCI format 1_2) has a TCI field. If the CORESET that schedules the PDSCH does not have tci-PresentInDCI or tci-PresentInDCI-ForFormat1_2 set, or if the PDSCH is scheduled by DCI (e.g., DCI format 1_0), the UE assumes that the DCI of the PDCCH sent by the CORESET (e.g., DCI format 1_1 or DCI format 1_2 or DCI format 1_0) does not have a TCI field. If the PDSCH is scheduled by a DCI format without a TCI field, and the time offset between the reception of the DL DCI and the corresponding PDSCH on the serving cell is greater than or equal to the threshold timeDurationForQCL, where applicable, and the threshold is based on the reported capabilities of the UE ([13, ​​TS38.306]), then in order to determine the pseudo-collocation of the PDSCH antenna port, the UE assumes that the TCI state or QCL assumption of the PDSCH is the same as the TCI state or QCL assumption applied for the CORESET used for PDCCH transmission within the serving cell's active BWP.

[0058] For a CORESET scheduling a PDSCH, if tci-PresentInDCI is set to "Enabled" or tci-PresentInDCI-ForFormat1_2 is set, and the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to timeDurationForQCL, where applicable, then after the UE receives the initial upper-layer setting of the TCI state and before receiving the activation instruction, the UE may assume that the DMRS port of the serving cell's PDSCH is pseudo-collocated with the SS / PBCH block determined in the initial access procedure, with respect to "QCL-typeA" and, where applicable, "QCL-typeD". The value of timeDurationForQCL is based on the reported capabilities of the UE.

[0059] If the UE has the upper-layer parameter tci-PresentInDCI set to "enabled" for the CORESET that schedules the PDSCH, the UE assumes that the DCI of the PDCCH sent by the CORESET (e.g., DCI format 1_1) contains a TCI field. If the UE has the upper-layer parameter tci-PresentInDCI-ForFormat1_2 set for the CORESET that schedules the PDSCH, the UE assumes that the DCI of the PDCCH sent by the CORESET (e.g., DCI format 1_2) contains a TCI field with the DCI field size indicated by tci-PresentInDCI-ForFormat1_2. If a PDSCH is scheduled by 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 is greater than or equal to the threshold timeDurationForQCL, where applicable, and the threshold is based on the reported UE capability ([TS38.306]), then in order to determine the pseudo-collocation of the PDSCH antenna port, the UE assumes that the TCI state or QCL assumption of the PDSCH is the same as the TCI state or QCL assumption applied for the CORESET used for PDCCH transmission within the serving cell's active BWP.

[0060] 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 the activated TCI state of the scheduled component carrier or DL ​​BWP, the UE must use the TCI-State according to the value of the "Transmit Setting Instruction" field in the detected PDCCH with DCI to determine the pseudo-collocation of the PDSCH antenna port. If the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationForQCL, and the threshold is based on the reported capabilities of the UE ([TS38.306]), the UE assumes that the DM-RS port of the serving cell's PDSCH is pseudo-collocated with the RS in the TCI state with respect to the QCL type parameter given by the indicated TCI state. If a single-slot PDSCH is configured in the UE, the indicated TCI state should be based on the activated TCI state in the slot having the scheduled PDSCH. When a multi-slot PDSCH is configured on the UE, the indicated TCI state should be based on the activated TCI state in the first slot or sub-slot having the scheduled PDSCH, and the UE should expect the activated TCI state to be the same across all slots having the scheduled PDSCH.If a UE has a CORESET associated with a search space set for cross-carrier scheduling, and a PDCCH transmitting a scheduling DCI and a PDSCH scheduled by that DCI are transmitted on the same carrier, the UE expects that tci-PresentInDCI is set to "Enabled" or that tci-PresentInDCI-ForFormat1_2 is set for the CORESET, and if one or more TCI states set for a serving cell scheduled by the search space set include "QCL-TypeD", the UE expects that the time offset between the reception of the PDCCH detected by the search space set and the corresponding PDSCH is greater than or equal to the threshold timeDurationForQCL.

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

[0062] - The UE may assume that the DM-RS port of the serving cell's PDSCH is pseudo-collocated with RS with respect to the QCL parameter used for the pseudo-collocation indication of the PDCCH of the CORESET having the lowest controlResourceSetId associated with the monitored search space in the most recent slot where one or more CORESETs in the serving cell's active BWP are being monitored by the UE. In this case, if the qcl-Type is set to "typeD" for the PDSCH DM-RS and differs from that of a PDCCH DM-RS that overlaps in at least one symbol, the UE is expected to prioritize receiving the PDCCH associated with that CORESET. This also applies to the case of in-band CA (where the PDSCH and CORESET are on different component carriers).

[0063] - If the UE has enableDefaultTCIStatePerCoresetPoolIndex set and the UE is configured by a higher-layer parameter PDCCH-Config which contains two different values ​​for coresetPoolIndex in different ControlResourceSets, then the following will occur:

[0064] - In the most recent slot monitored by the UE, one or more CORESETs associated with the same coresetPoolIndex value as the PDCCH scheduling a PDSCH within the serving cell's active BWP may assume that the DM / RS port of that PDSCH, associated with the serving cell's coresetPoolIndex value, is pseudo-collocated with the RS, with respect to the QCL parameter used for the PDCCH pseudo-collocation instruction of the CORESET having the lowest controlResourceSetId associated with the monitored search space, among the CORESETs set to the same coresetPoolIndex value as the PDCCH scheduling that PDSCH. In this case, if the "QCL-TypeD" of the PDSCH DM-RS differs from that of the PDCCH DM-RS, which overlap in at least one symbol, and they are associated with the same coresetPoolIndex, the UE is expected to prioritize receiving the PDCCH associated with that CORESET. This also applies to the in-band CA case (where the PDSCH and CORESET are on different component carriers).

[0065] - If enableTwoDefaultTCI-States is set in the UE and at least one TCI code point indicates two TCI states, the UE may assume that the DM-RS port of the serving cell's PDSCH or PDSCH transmit opportunity is pseudo-collocated with RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest code point among the TCI code points containing two different TCI states. If the UE is set by the upper layer parameter repetitionScheme set in "tdmSchemeA" or if the UE is set by the upper layer parameter repetitionNumber, the mapping of TCI states to PDSCH transmit opportunities is determined in accordance with Section 5.1.2.1, based on the activated TCI state in the slot having the first PDSCH transmit opportunity, by replacing the indicated TCI state with the TCI state corresponding to the lowest code point among the TCI code points containing two different TCI states. In this case, if the "QCL-TypeD" of both TCI states corresponding to the lowest code point among two different TCI code points is different from that of the PDCCH DM-RS which overlap by at least one symbol, the UE is expected to prioritize receiving the PDCCH associated with its CORESET. This also applies to the case of in-band CA (where the PDCCH and CORESET are on different component carriers).

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

[0067] If a PDCCH transmitting 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 set on the UE, then the following occurs:

[0068] - timeDurationForQCL is determined based on the subcarrier interval of the scheduled PDSCH. μ PDCCH <μ PDSCH In this case, an additional timing delay is added to timeDurationForQCL.

number

[0069] - In either case, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and the DL DCI does not have a TCI field, the UE obtains the QCL assumption for the scheduled PDSCH from the lowest ID activated TCI state applicable to the PDSCH in the active BWP of the scheduled cell.

[0070] For periodic CSI-RS resources in an NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, the UE should expect the TCI-State to indicate one of the following pseudo-collocation types:

[0071] - "type C" having an SS / PBCH block, and, if applicable, "type D" having the same SS / PBCH block, or

[0072] - "typeC" which has an SS / PBCH block, and "typeD" which has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter repetition set, or

[0073] For non-periodic CSI-RS resources in an NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, the UE should expect that the TCI-State will indicate the qcl-Type set to "typeA" which has periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and, if applicable, the qcl-Type set to "typeD" which has the same periodic CSI-RS resources.

[0074] For CSI-RS resources in an NZP-CSI-RS-ResourceSet configured without the upper layer parameter trs-Info and the upper layer parameter repetition, the UE should expect the TCI-State to indicate one of the following pseudo-collocation types:

[0075] - "typeA" which has a CSI-RS resource in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and, if applicable, "typeD" which has the same CSI-RS resource, or

[0076] - "typeA" which has a CSI-RS resource in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and "typeD" which has an SS / PBCH block if applicable, or

[0077] - "typeA" which has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and "typeD" which, if applicable, has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter repetition set, or

[0078] - If "typeD" is not applicable, "typeB" is used, which has a CSI-RS resource in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set.

[0079] For CSI-RS resources in an NZP-CSI-RS-ResourceSet with the upper layer parameter repetition set, the UE should expect the TCI-State to indicate one of the following pseudo-collocation types:

[0080] - "typeA" which has a CSI-RS resource in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and, if applicable, "typeD" which has the same CSI-RS resource, or

[0081] - "typeA" which has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and "typeD" which, if applicable, has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter repetition set, or

[0082] - "Type C" having an SS / PBCH block, and "Type D" having the same SS / PBCH block, where applicable.

[0083] For DM-RS in PDCCH, the UE should expect the TCI-State to exhibit one of the following pseudo-collocation types:

[0084] - "typeA" which has a CSI-RS resource in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and, if applicable, "typeD" which has the same CSI-RS resource, or

[0085] - "typeA" which has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and "typeD" which, if applicable, has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter repetition set, or

[0086] - "typeA" has CSI-RS resources in NZP-CSI-RS-ResourceSet configured without the upper layer parameters trs-Info and repetition, and "typeD" has the same CSI-RS resources, if applicable.

[0087] For DM-RS in PDSCH, the UE should expect the TCI-State to exhibit one of the following pseudo-collocation types:

[0088] - "typeA" which has a CSI-RS resource in the NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and, if applicable, "typeD" which has the same CSI-RS resource, or

[0089] - "typeA" which has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter trs-Info set, and "typeD" which, if applicable, has a CSI-RS resource in an NZP-CSI-RS-ResourceSet with the upper layer parameter repetition set, or

[0090] - "typeA" which has CSI-RS resources in NZP-CSI-RS-ResourceSet configured without the upper layer parameter trs-Info and the upper layer parameter repetition, and "typeD" which has the same CSI-RS resources, if applicable.

[0091] If a PDCCH transmitting a scheduling DCI is received on one component carrier, and the PDSCH scheduled by that DCI is on another component carrier, timeDurationForQCL is determined based on the subcarrier interval 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 interval is 15 kHz, 8 symbols if the PDCCH subcarrier interval is 30 kHz, and 14 symbols if the PDCCH subcarrier interval is 60 kHz. For example, if the symbol is a PDCCH symbol, or if the symbol is based on the subcarrier interval of a PDCCH (for example, as defined in Table 5.2.1.5.1a-1 of TS38.214), and 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 in any case where tci-PresentInDCI is not set, the UE obtains the QCL assumption for the scheduled PDSCH from the lowest ID activated TCI state applicable to the PDSCH in the active BWP of the scheduled cell.

[0092] If the UE is configured by the upper-layer parameter RepSchemeEnabler set to one of “FDMSchemeA”, “FDMSchemeB”, or “TDMSchemeA”, as specified in the 3GPP specification (TS38.214), then two TCI states in the code point of the DCI field “Transmit Setting Instructions” and a DMRS port in one CDM (Code Domain Multiplexing) group in the DCI field “Antenna Ports”. If two TCI states are indicated in DCI and the UE is set to “FDMSchemeA”, then the UE must receive a single PDSCH transmit opportunity for TB with each TCI state associated with non-overlapping frequency domain resource allocation, as described in the “Physical Resource Block (PRB) Bundling)” section of TS38.214 (e.g., section 5.1.2.3). If two TCI states are shown in DCI and the UE is set to "FDMSchemeB", the UE must receive two PDSCH transmit opportunities of the same TB in each TCI state associated with a PDSCH transmit opportunity that has non-overlapping frequency-domain resource allocations with respect to other PDSCH transmit opportunities, as described in the "Physical Resource Block (PRB) Bundling" section of TS38.214 (e.g., section 5.1.2.3). If two TCI states are shown in DCI and the UE is set to "TDMSchemeA", the UE must receive two PDSCH transmit opportunities of the same TB in each TCI state associated with a PDSCH transmit opportunity that has non-overlapping time-domain resource allocations with respect to other PDSCH transmit opportunities, as described in the "Time-Domain Resource Allocation" section of TS38.214 (e.g., section 5.1.2.1), and both PDSCH transmit opportunities must be received within a given slot.

[0093] If the UE is configured by the higher-layer parameter PDSCH-config which indicates at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 of PDSCH-TimeDomainResourceAllocation, the UE may expect one or two TCI states to be indicated in the DCI field "Time Domain Resource Allocation" and one or two TCI states in the DCI field "Transmit Setting Instructions" code point, along with the DCI field "Time Domain Resource Allocation" and the DM-RS port in one CDM group of the DCI field "Antenna Port". "Time Domain Resource Allocation" indicates an entry in pdsch-TimeDomainAllocationList containing RepNum16 of PDSCH-TimeDomainResourceAllocation. If two TCI states are indicated in the DCI having the "Transmit Setting Instructions" field, the UE may expect to receive multiple slot-level PDSCH transmit opportunities of the same TB with two TCI states used across multiple PDSCH transmit opportunities, as defined in the "Resource Allocation in the Time Domain" section of TS38.214 (e.g., section 5.1.2.1). If a DCI with a “Transmit Settings Instruction” field indicates one TCI state, the UE may expect to receive multiple slot-level PDSCH transmit opportunities for the same TB with that single TCI state used across multiple PDSCH transmit opportunities, as defined in the “Resource Allocation in the Time Domain” section of TS38.214 (e.g., section 5.1.2.1).

[0094] If the DCI field "Time Domain Resource Allocation" does not show the UE one entry in pdsch-TimeDomainAllocationList containing RepNumR16 of PDSCH-TimeDomainResourceAllocation, and the UE is shown two TCI states for the code point in the DCI field "Transmit Setting Instructions" and two DM-RS ports in the CDM groups in the DCI field "Antenna Port", the UE may expect to receive a single PDSCH. Here, the association between DM-RS ports and TCI states is as defined in the "DMRS Receiving Procedure" section of TS38.214 (e.g., section 5.1.6.2).

[0095] If the UE is shown the DCI field "Time Domain Resource Allocation" which indicates one entry in pdsch-TimeDomainAllocationList containing RepNumR16 of PDSCH-TimeDomainResourceAllocation, and if the UE is shown one TCI state for a code point in the DCI field "Transmit Configuration Instruction", then the UE procedure for receiving the PDSCH upon PDCCH detection follows the section "UE Procedure for Receiving a Physical Downlink Shared Channel" in TS38.214 (e.g., section 5.1).

[0096] 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.

[0097] As specified in the 3GPP specification (TS38.214), when the UE is configured by the upper-layer parameter RepSchemeEnabler set to "TDMSchemeA" and a DM-RS port in one CDM group is indicated to the UE in the DCI field "Antenna Ports", the number of PDSCH transmit opportunities is derived from the number of TCI states indicated by the DCI field "Transmit Setting Instructions" of the scheduling DCI. If two TCI states are indicated by the DCI field "Transmit Setting Instructions", the UE is expected to receive two PDSCH transmit opportunities. Here, the first TCI state applies to the first PDSCH transmit opportunity, and the time-domain resource allocation for the first PDSCH transmit opportunity follows the "Time-Domain Resource Allocation" section of TS38.214 (e.g., section 5.1.2.1). The second TCI state applies to the second PDSCH transmit opportunity, and the second PDSCH transmit opportunity must have the same number of symbols as the first PDSCH transmit opportunity. The value of StartingSymbolOffsetK is assigned to the UE by the upper layer.

number

number

number

number

[0098] If the UE is configured by the higher-layer parameter PDSCH-config, which indicates at least one entry in pdsch-TimeDomainAllocationList, including RepNumR16 of PDSCH-TimeDomainResourceAllocation, as specified in the 3GPP specification (TS38.214), then the same SLIV (start and length indicator value) applies to all PDSCH transmit opportunities, the first TCI state applies to the first PDSCH transmit opportunity, and the time-domain resource allocation for the first PDSCH transmit opportunity follows the section "Time-Domain Resource Allocation" in TS38.214 (e.g., section 5.1.2.1). If the value indicated by RepNumR16 of PDSCH-TimeDomainResourceAllocation is equal to 2, the second TCI state is applied to the second PDSCH transmission opportunity. If the value indicated by RepNumR16 of PDSCH-TimeDomainResourceAllocation is greater than 2, the UE may further configure RepTCIMapping to enable CycMapping or SeqMapping. 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 that each PDSCH transmission opportunity is limited to two transmission layers.For all PDSCH transmission opportunities associated with the first TCI state, the applicable redundant 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 redundant 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 each redundant version rv. s The additional shift operation for is set by the parameter RVSeqOffset of the upper layer, and n is counted considering only PDSCH transmit opportunities associated with the second TCI state. If one TCI state is indicated by the DCI field "Transmit Setting Instructions" along with the DCI field "Time Domain Resource Allocation" which shows one entry in pdsch-TimeDomainAllocationList including RepNumR16 of PDSCH-TimeDomainResourceAllocation, and the DCI field "Antenna Port" which shows a DM-RS port in one CDM group, then the same SLIV applies to all PDSCH transmit opportunities, and the same TCI state applies to all PDSCH transmit opportunities according to the section "Resource Allocation in the Time Domain" of TS38.214 (e.g., section 5.1.2.1). The UE may expect that each PDSCH transmit opportunity is limited to two transmit layers. For all PDSCH transmission opportunities, the applicable redundant version is derived according to Table 5.1.2.1-2 of [TS38.214], where n is counted taking PDSCH transmission opportunities into account. Otherwise, the UE is expected to receive a single PDSCH transmission opportunity, and the resource allocation in the time domain follows the “Resource Allocation in the Time Domain” section of TS38.214 (e.g., section 5.1.2.1).

[0099] Table 5.1.2.1-2 Redundant version applied when pdsch-AggregationFactor exists [Table 1]

[0100] Table 5.1.2.1-3 A redundant version applied to the second TCI state when an RVSeqOffset exists. [Table 2]

[0101] As specified in the 3GPP specification (TS38.214), if the UE is configured by the upper-layer parameter RepSchemeEnabler set to "FDMSchemeA" or "FDMSchemeB", then the UE is shown two TCI states for the code point in the DCI field "Transmit Settings Instruction" and a DMRS port in one CDM group in the DCI field "Antenna Port".

number

number

number

number

[0102] For a UE configured by the upper-layer parameter RepSchemeEnabler set in "FDMSchemeB", when the UE is shown two TCI states in the code point of the DCI field "Transmit Setting Instruction" and a DM-RS port in one CDM group in the DCI field "Antenna Port", each PDSCH transmit opportunity must follow the "Physical Downlink Shared Channel" section (e.g., section 7.3.1) of [TS38.211] for mapping to resource elements determined by the PRB assigned to the corresponding TCI state of the PDSCH transmit opportunity. Furthermore, the UE should expect a maximum of two code blocks per PDSCH transmit opportunity when a single transmit layer is scheduled, and a single code block per PDSCH transmit opportunity when two transmit layers are scheduled. For two PDSCH transmit opportunities, the applicable redundant versions are 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.

[0103] In some embodiments, there is an application timing for beam indication or TCI status indication. In some embodiments, the application timing may be the first slot or first subslot at least Xms or Y symbols after the last symbol of confirmation of coupled or separated DL / UL beam indication. For example, Y may be an integer, such that 1 <= Y <= 336. In some embodiments, a slot may contain 12 or 14 symbols. In some embodiments, a subslot may contain S symbols, such that S is an integer, such that 1 <= S <= 14. For example, S may be at least one of {2, 4, 7}. In some embodiments, beam indication is indicated by the DCI of the PDCCH. For example, the DCI of the PDCCH may or may not schedule a PDSCH. In some embodiments, the gap between the last symbol of the DCI and the first slot or first subslot must be commensurate with the capabilities of the terminal device. In some embodiments, confirmation of coupled or separated DL / UL beam indication may be confirmation of a PDSCH scheduled by the DCI, for example, when the DCI schedules a PDSCH. In some embodiments, confirmation of the coupling or separation of DL / UL beam indication may be a confirmation of the DCI, for example, when the DCI does not schedule the PDSCH.

[0104] In some embodiments, a terminal device may receive or detect a DCI (e.g., represented as "DCI_t") in the PDCCH. The DCI indicates a coupled DL / UL TCI state, or a separated DL / UL TCI state, or a DL TCI state, or an UL TCI state, or a pair of DL / UL TCI states. In some embodiments, a second time threshold H2 may indicate a predetermined / set 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 coupled DL / UL TCI state, or separated 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 the application timing or the second time threshold H2. For example, if a coupled DL / UL TCI state is indicated in DCI, the coupled DL / UL TCI state may be applied to PDSCH and / or CORESET and / or PUSCH and / or PUCCH and / or uplink RS and / or downlink RS after the application timing or a second time threshold H2. As another example, if a DL TCI state is indicated in DCI, the DL TCI state may be applied to PDSCH and / or CORESET and / or downlink RS after the application timing or a second time threshold H2. As yet another example, if a UL TCI state is indicated in DCI, the UL TCI state may be applied to PUSCH and / or PUCCH and / or uplink RS after the application timing or a second time threshold H2. As another example, if a pair of DL / UL TCI states are shown in DCI, the DL TCI state may be applied to PDSCH and / or CORESET and / or downlink RS after the application timing or a second time threshold H2, and the UL TCI state may be applied to PUSCH and / or PUCCH and / or uplink RS after the application timing or a second time threshold H2.

[0105] In some embodiments, the terminal device 110 may receive an indication of the downlink TCI status (or beam or QCL parameter set), and the source reference signal of the TCI status provides QCL information for reception at all CORESETs of at least the PDSCH and component carrier (CC). For example, the PDSCH is dedicated or UE-specific.

[0106] In some embodiments, the terminal device 110 may receive an indication of the uplink TCI status (or beam or spatial relationship), and the source reference signal of the TCI status provides a criterion for determining the uplink transmission spatial filter for at least all PUCCH resources in the CC, based on dynamic grants or set grants. For example, the PUCCH may be dedicated or UE-specific.

[0107] In some embodiments, the terminal device 110 may receive an instruction indicating a coupled TCI state (or beam or QCL parameter set), the TCI state referring to at least a common source reference signal used to determine both downlink QCL information and uplink transmit space filters.

[0108] In some embodiments, the terminal device 110 may receive indications of downlink TCI status (or beam or QCL parameter set) and uplink TCI status (or beam or spatial relationship), and the source reference signal in the DL TCI status provides QCL information for reception at least in all CORESETs of the PDSCH and component carrier (CC). The source reference signal in the TCI status also provides a criterion for determining the uplink transmit spatial filter for at least all PUCCH resources in the CC, based on dynamic grants or set grants. For example, the PUCCH is dedicated or UE-specific. As another example, the PDSCH is dedicated or UE-specific.

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

[0110] In some embodiments, the terminal device 110 may be configured with a plurality of uplink TCI states (for example, represented as N, where N is a positive integer, for example N may be 2, 3, or 4), and / or the terminal device 110 may receive an instruction indicating one of the N TCI states, and the source reference signal in one of the N TCI states or the indicated TCI state provides a criterion for determining the uplink transmit space filter for at least a subset of PUSCH and / or PUCCH in CC based on dynamic grants or set grants. For example, PUCCH may be dedicated or UE-specific.

[0111] In some embodiments, the terminal device 110 may be configured with a plurality of coupled DL / UL TCI states (for example, represented as M, where M is a positive integer, for example M may be 2, 3, or 4), and / or the terminal device 110 may receive an instruction indicating one of the M coupled TCI states, each of the M TCI states or the indicated TCI state pointing to at least a common source reference signal used to determine both downlink QCL information and uplink transmit space filters.

[0112] In some embodiments, the terminal device 110 may be configured with a plurality of downlink TCI states (for example, represented as M, where M is a positive integer, e.g., M may be 2, 3, or 4), and the terminal device 110 may be configured with a plurality of uplink TCI states (for example, represented as N, where N is a positive integer, e.g., N may be 2, 3, or 4), and / or the terminal device 110 may receive an instruction indicating one of the M downlink TCI states and one of the N uplink TCI states, wherein the source reference signal in each of the M DL TCI states or one indicated DL TCI state provides QCL information for reception in at least a subset of PDSCH and / or component carrier (CC) CORESETs, and the source reference signal in each of the N TCI states or one indicated UL TCI state provides a criterion for determining the uplink transmit space filter for at least a subset of PUSCH and / or PUCCH in CC based on dynamic grants or set grants. For example, PUCCH is dedicated or UE-specific. Another example is PDSCH, which is dedicated or UE-specific.

[0113] In the following, DCI_t may be used to describe DCIs for combined DL / UL TCI status indicators or isolated DL / UL TCI status indicators. In the following, the terms "DCI", "PDCCH", "DCI_t", "DCI for combined DL / UL TCI status indicators", "DCI for isolated DL / UL TCI status indicators", "DCI for DL ​​TCI status indicators", "DCI for UL TCI status indicators", "PDCCH for combined DL / UL TCI status indicators", "PDCCH for isolated DL / UL TCI status indicators", "PDCCH for DL ​​TCI status indicators", "PDCCH for UL TCI status indicators", "DCI for TCI status indicators", and "PDCCH for TCI status indicators" may be used interchangeably.

[0114] In some embodiments, DCI may be used to indicate the TCI state of a coupled DL / UL TCI state indicator or a separated DL / UL TCI state indicator. DCI may also schedule PDSCHs (e.g., DCI format 1_1 and format 1_2). In some embodiments, the HARQ of the PDSCH scheduled by DCI can be used as an ACK to DCI. For example, DCI may be DCI_t.

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

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

[0117] In some embodiments, a DCI (e.g., DCI_t) may be used to indicate one or more TCI states. For example, one or more TCI states may be for coupled DL / UL TCI state indications or isolated DL / UL TCI state indications. 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 110-1 may report an ACK. In some embodiments, if the reception / decoding of the DCI fails, the terminal device 110-1 may report a NACK. For example, the ACK and / or NACK may be reported on the physical uplink control channel (PUCCH) or the physical uplink sharing channel (PUSCH). In some embodiments, the terminal device 110-1 may be configured with a HARQ codebook type. For example, the type may be at least one of type 1 (e.g., semistatic), 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, DCI is received / detected by PDCCH.

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

[0119] Network device 120 transmits a downlink transmission to terminal device 110-1 based on the last TCI (2020) according to the first condition. For example, network device 120 may transmit downlink data to terminal device 110-1. Network device 120 may transmit a downlink transmission on a beam corresponding to at least one TCI. The first condition can be after a first timing, or starting from a first timing. The first timing can be a beam application timing. Alternatively, or additionally, the first condition can include an acknowledgment (HARQ-ACK) of a hybrid auto-retransmission request corresponding to a detected DCI, or a physical downlink shared channel (PDSCH) scheduled by a DCI, being an ACK. In some embodiments, the first PDCCH does not have to start or end earlier than a second PDCCH in the PDCCH set. In other words, the first PDCCH may start or end later than any other PDCCH in the PDCCH set. In some embodiments, the HARQ-ACK corresponding to the detected DCI in the first PDCCH, or the PDSCH scheduled by the detected DCI in the first PDCCH, and the HARQ-ACK corresponding to the detected DCI in the second PDCCH are reported to the network device 120 using the same resource.

[0120] The terminal device 110-1 applies at least one TCI state to at least one reference signal (RS) in the first RS set (2030) based on the first condition. The first RS set is applied for beam fault detection. For example, the terminal device 110-1 may receive the first RS set on a beam corresponding to at least one TCI. The first RS set may include any appropriate number of reference signals.

[0121] In some embodiments, at least one TCI state can be applied to a first RS in a first RS set based on a first condition. Alternatively, or additionally, a second TCI state can be applied to a second RS in the first RS set, where the first RS set includes a first RS and a second RS. In this case, the first RS can be an RS with a low or high index value in the first RS set. The second TCI state may be a default or fallback TCI state, or a TCI state corresponding to the lowest code point from a set of code points activated via MAC CE. In some embodiments, the second TCI state can be the first TCI state.

[0122] In an exemplary embodiment, the first RS set can be configured by higher-layer parameters from the network device 120. Alternatively, the terminal device 110-1 can determine the first RS set based on the TCI state of one or more control resource sets (CORESETs).

[0123] The terminal device 110-1 determines an estimate of the wireless link quality between the terminal device 110-1 and the network device 120 based on the first RS set (2040). For example, the terminal device 110-1 can measure the first RS set. In this case, the terminal device 110-1 can estimate the wireless link quality based on the measurement result of the first RS set.

[0124] In some embodiments, terminal device 110-1 may stop the first procedure based on a second condition and restart the second procedure based on the first condition. In some embodiments, the second condition may be after a second timing or starting from a second timing. For example, the second timing may not be later than or earlier than the first timing. In some embodiments, the second timing may be the timing at which a DCI is detected in the first PDCCH. Alternatively, or additionally, the second timing may be the timing at which the PDSCH scheduled by the detected DCI is successfully decoded. Alternatively, or additionally, the second timing may be the timing at which a HARQ-ACK corresponding to the DCI, or a HARQ-ACK corresponding to the PDSCH scheduled by the detected DCI, is generated in the terminal device.

[0125] In other embodiments, the second condition may include that at least one TCI state is different from the first TCI state. The first TCI state applies to the PDCCH of the detected DCI and / or to at least one RS in the first RS set. Alternatively, or additionally, the second condition may include that the acknowledgment of a hybrid auto-retransmission request (HARQ-ACK) corresponding to the detected DCI, or the PDSCH scheduled by the DCI, is an ACK. In some embodiments, the first PDCCH cannot start or end earlier than the second PDCCH in the PDCCH set. The HARQ-ACK corresponding to the detected DCI in the first PDCCH, or the PDSCH scheduled by the detected DCI in the first PDCCH, and the HARQ-ACK corresponding to the detected DCI in any other PDCCH may be reported to the network device on the same resource. In some embodiments, the value of the beam fault indicator counter may be set to 0 based on the second condition. In other embodiments, terminal device 110-1 may ignore TCI fields in detected DCIs within the PDCCH after a third timing and / or until a fourth timing. In this case, the third timing may be when beam fault recovery is successfully completed. The fourth timing may be when one or more TCI states are activated (or until the UE receives activation of a TCI state or one of the parameters tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList from a higher layer).

[0126] Figures 3 to 7 show examples of beam application settings in terminal device 110. Figures 3 to 7 will be explained with reference to Figure 1.

[0127] In some embodiments, the terminal device may receive at least one setting of a first RS set for beam fault detection. In some embodiments, the first RS set may include at least one of a first RS and a second RS. In some embodiments, the first RS set may include at least one of the indices of the first RS and the second RS. For example, the terminal device may receive at least one setting via at least one of RRC and MAC CE.

[0128] In some embodiments, the terminal device may determine the first RS set to include at least one of a first RS index and a second RS index having the same value as the RS index in the RS set indicated by the TCI state of CORESET, where CORESET is used to monitor PDCCH. For example, when the first RS set is not set in the terminal device. In some embodiments, the first RS and / or the second RS are set to qcl-Type set to "typeD" in the TCI state.

[0129] In some embodiments, a single port is configured for the first RS and / or the second RS. In some embodiments, the first RS and / or the second RS is a CSI-RS.

[0130] In some embodiments, a terminal device may receive, detect, or monitor a first PDCCH in a TCI (e.g., represented as TCI_1), where TCI_1 may be any one of a first coupled TCI state, a first downlink TCI state, or a first downlink TCI state in a first pair of downlink and uplink TCI states. In some embodiments, the first PDCCH may be in a first CORESET, which is set to or indicates TCI_1.

[0131] In some embodiments, the terminal device may receive an instruction for a TCI (e.g., represented as TCI_2) in a detected DCI within a first PDCCH, where TCI_2 may be one of a second coupled TCI state, a second downlink TCI state, or a second pair of downlink TCI states and uplink TCI states. In some embodiments, the terminal device may receive a downlink transmission in TCI_2 (e.g., a second coupled TCI state, or a second downlink TCI state, or a second downlink TCI state in a second pair of downlink TCI states and uplink TCI states) based on the first condition, where the downlink transmission may be all or at least one of a subset of the PDSCH and CORESET. In some embodiments, the terminal device may, based on the first condition, apply TCI_2 (e.g., a second coupled TCI state, or a second downlink TCI state, or a second downlink TCI state in a second pair of downlink and uplink TCI states) to at least one RS in the first RS set. In some embodiments, the terminal device may, based on the first condition, include a third RS or an index of the third RS in the first RS set. In some embodiments, the terminal device may, based on the first condition, replace a first RS or an index of the first RS in the first RS set with a third RS or an index of the third RS. In some embodiments, the index of the third RS is set to the same value as the RS index of the RS set indicated by TCI_2. In some embodiments, the third RS is set to qcl-Type, which is set to "typeD" in TCI_2. In some embodiments, the third RS is set to a single port. In some embodiments, the third RS is a CSI-RS. In some embodiments, the RS set represented by TCI_2 may include one or two RSs.In some embodiments, if one or two RSs in the RS set indicated by TCI_2 do not have a qcl-Type set to "typeD", or if one or two RSs in the RS set indicated by TCI_2 are not CSI-RSs, or if an RS in an RS set where a qcl-Type set to "typeD" is set is not a CSI-RS, or if an RS in an RS set where a qcl-Type set to "typeD" is set does not have a single port, the terminal device may, based on the first condition, include a fourth RS or an index of the fourth RS in the first RS set. In some embodiments, the terminal device may, based on the first condition, replace the first RS or an index of the first RS in the first RS set with a fourth RS or an index of the fourth RS. In some embodiments, the fourth RS is an RS that is pseudo-collocated with one or two RSs in the RS set indicated by TCI_2 of "typeD". In some embodiments, the fourth RS is an RS in an RS set where the qcl-Type set to "typeD" is configured, and an RS that is pseudo-collocated in "typeD". In some embodiments, the fourth RS is a CSI-RS. In some embodiments, the fourth RS is configured with a single port.

[0132] In some embodiments, the first RS set may be used for beam fault detection. In some embodiments, the terminal device may evaluate the radio link quality (e.g., reference signal received power (RSRP)) based on the first RS set.

[0133] In some embodiments, the first RS set includes a first RS and a second RS. In some embodiments, the first RS set includes the index of the first RS and the index of the second RS. In some embodiments, the index of the first RS is lower than the index of the second RS. In some embodiments, the index of the first RS is higher than the index of the second RS.

[0134] In some embodiments, the terminal device may apply TCI_2 (e.g., a second coupled TCI state, or a second downlink TCI state, or a second downlink TCI state in a second pair of downlink and uplink TCI states) to a first RS in a first RS set based on a first condition. In some embodiments, the second TCI state may be applied to a second RS. In some embodiments, the second TCI state can be the default TCI state. In some embodiments, the second TCI state may be a fallback TCI state. In other embodiments, the second TCI state may be a downlink TCI state, or a coupled TCI state, or a downlink TCI state in a pair of downlink and uplink TCI states, corresponding to the lowest code point from the set of code points activated via MAC CE. In some embodiments, the second TCI state may be a preceding TCI state that is applied to all or a subset of the CORESET before the first TCI state is applied (e.g., a downlink TCI state, or a coupled TCI state, or a downlink TCI state in a pair of downlink and uplink TCI states), and may be a different TCI state from the first TCI state.

[0135] In some embodiments, the index of the second RS is set to the same value as the RS index in the RS set indicated by the downlink TCI state, combined TCI state, or downlink TCI state of a pair of downlink and uplink TCI states, corresponding to the lowest code point from the set of code points activated via MAC CE.

[0136] In some embodiments, the index of the second RS is an RS having a setting index that has the same value as the RS index in the RS set indicated by a downlink TCI state, or a combined TCI state, or a downlink TCI state of a pair of downlink and uplink TCI states, corresponding to the lowest code point from the set of code points activated via MAC CE.

[0137] In some embodiments, the first condition is that it is after a first timing (the first timing may be a beam application timing, or a first slot or first subslot which is at least a first value of milliseconds or a second value of symbol from the last symbol of the uplink resource with an acknowledgment of the detected DCI or DCI-scheduled PDSCH), that it starts from the first timing, that the acknowledgment of the hybrid auto retransmission request (HARQ-ACK) corresponding to the detected DCI or DCI-scheduled physical downlink shared channel (PDSCH) is an ACK, and that the first PDCCH is a PDC At least one of the following may be: the first PDCCH starts or ends earlier or later than the second PDCCH in the CH set; or the first PDCCH is the latest of the second PDCCH group, and the HARQ-ACK corresponding to a detected DCI in the first PDCCH or a PDSCH scheduled by a detected DCI in the first PDCCH is an ACK, and the HARQ-ACK corresponding to a detected DCI in the first PDCCH or a PDSCH scheduled by a detected DCI in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH are reported to the network device using the same resource.

[0138] In some embodiments, the uplink resource may be a PUSCH resource or a PUCCH resource. In some embodiments, the terminal device transmits the uplink resource to the network device.

[0139] In some embodiments, the terminal device may stop or abandon the first procedure based on a second condition. In some embodiments, the first procedure may be a beam failure recovery procedure. In some embodiments, the first procedure may include a beam failure detection procedure and / or a new beam candidate identification procedure. In some embodiments, the terminal device may set the value of beam failure indication_counter (e.g., BFI_counter) to 0 based on a second condition. In some embodiments, the terminal device may stop a beam failure recovery timer (e.g., beamFailureRecoveryTimer set by RRC) based on a second condition. In some embodiments, the beam failure indication counter is a non-negative integer.

[0140] In some embodiments, the second condition is that it occurs after the second timing, starts from the second timing, TCI_1 is different from TCI_2, the second coupled TCI state is different from the first coupled TCI state, the second downlink TCI state is different from the first downlink TCI state, the second pair of downlink TCI states and uplink TCI states is different from the first pair of downlink TCI states and uplink TCI states, the detected DCI, or the acknowledgment of the hybrid auto-retransmission request corresponding to the PDSCH scheduled by the DCI (HARQ-ACK) is an ACK, and the first PDCCH is a PDCCH At least one of the following may occur: the first PDCCH starts or ends earlier or later than the second PDCCH in the set; the first PDCCH is the most recent in the second PDCCH group; the HARQ-ACK corresponding to a detected DCI in the first PDCCH or a PDSCH scheduled by a detected DCI in the first PDCCH is an ACK; and the HARQ-ACK corresponding to a detected DCI in the first PDCCH or a PDSCH scheduled by a detected DCI in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH are reported to the network device using the same resource.

[0141] In some embodiments, the second timing is neither later nor earlier than the first timing. In some embodiments, the second timing may be at least one of the following: the timing at which a DCI is detected in the first PDCCH; the timing at which the PDSCH scheduled by the detected DCI is successfully decoded; the timing at which a HARQ-ACK corresponding to the DCI or a HARQ-ACK corresponding to the PDSCH scheduled by the detected DCI is encoded; and the timing at which a HARQ-ACK corresponding to the DCI or a HARQ-ACK corresponding to the PDSCH scheduled by the detected DCI is generated in the terminal device.

[0142] In some embodiments, even if beam fault instance indications are received from lower layers of the terminal device during a certain period of time, the beam fault indication counter (e.g., BFI_counter) does not increase by one.

[0143] In some embodiments, in the case of dynamic beam instruction, the beam / TCI state of at least one RS in the BFD RS set q0 can be updated after the beam application timing. Alternatively, if the HARQ-ACK corresponding to the DCI or PDSCH scheduled by the DCI is an ACK, the dynamically indicated beam / TCI state (DL TCI or coupled TCI) can be updated for the RS in the BFD RS set after the beam application timing and / or monitored for beam fault detection. For example, as shown in Figure 3, the PDCCH 310 may indicate TCI state 1, and the TCI state of the BFD RS may be TCI state 2. After the beam application timing 311, TCI state 1 can be applied to the CORESET. Furthermore, after the beam application timing 311, the TCI state of the BFD RS can be updated from TCI state 2 to TCI state 1 (305).

[0144] In other embodiments, the current BFR procedure (e.g., beam fault detection and / or identification of a new beam) can be stopped after a second timing. The second timing may be, at least for DL ​​TCI, when a DCI is detected in the PDCCH or when the PDSCH scheduled by the DCI is successfully decoded, if the indicated TCI state is different from the current TCI state. Then, after the first timing (i.e., beam application timing), the BFR procedure is restarted regardless of whether a new TCI state is applied. For example, as shown in Figure 4, the PDCCH 410 may indicate TCI state 1, and the TCI state of the BFD RS may be TCI state 2. The current BFR procedure can be stopped after the second timing 412. After the first timing 411, TCI state 1 can be applied to the CORESET and the BFR procedure can be restarted. In some embodiments, the TCI state of the BFD RS can be updated from TCI state 2 to TCI state 1 (405).

[0145] In exemplary embodiments, if a set of periodic CSI-RS resource setting indices q0 is provided, the TCI state of the PDCCH (e.g., DL TCI or combined TCI) can be applied to the TCI state of at least one CSI-RS resource after beam application timing. For example, in some embodiments, a dynamically indicated beam / TCI state (e.g., DL TCI or combined TCI) can be applied to the entire BFD RS set. For example, if q0 is provided to terminal device 110-1, only one RS index is sufficient, and the beam / TCI state of the RS follows the dynamically indicated beam / TCI state (DL TCI or combined TCI).

[0146] Alternatively, a dynamically indicated beam / TCI state (e.g., DL TCI or coupled TCI) can be applied to one RS in the BFD RS set. For example, if q0 is provided and q0 contains two RS indices, the dynamically indicated beam / TCI state can be applied to the RS with the lower or higher index. In another embodiment, if q0 is provided and q0 contains two RC indices, the dynamically indicated beam / TCI state can be applied to one of the RSs (e.g., RS A), and the beam / TCI state of RS B is the fallback / default beam (e.g., the TCI state of the lowest code point). For example, as shown in Figure 5, PDCCH510 may indicate TCI state 1, and the TCI states of the BFD RS may be TCI states 2 and TCI states 3. After the first timing 511, TCI state 1 can be applied to the CORESET. The TCI state 2 of the BFD RS can be maintained, and the other TCI states of the BFD RS can be updated from TCI state 3 to TCI state 1 (505). In other words, a dynamically represented TCI state (i.e., TCI state 1) can be applied to one of the RSs (e.g., RS A), and the beam / TCI state of RS B is the fallback / default beam, which in this case is TCI state 2.

[0147] In other embodiments, dynamically represented beam / TCI states (e.g., DL TCI or coupled TCI) can be selectively applied to one of the RSs in the BFD RS set. For example, given q0, if q0 contains two RS indices (e.g., RS A and RS B), after the application timing, the nth dynamically represented beam / TCI state can be applied to RS A and the (n+1)th dynamically represented beam / TCI state can be applied to RS B. For example, as shown in Figure 6, PDCCH 610 can represent TCI state 1, and the TCI states of the BFD RS can be TCI states 2 and TCI states 3. After beam application timing 611, TCI state 1 can be applied to the CORESET. The BFD RS can maintain TCI state 2, and the other TCI states of the BFD RS can be updated from TCI state 3 to TCI state 1 (615). PDCCH 620 can represent TCI state 4. After beam application timing 621, TCI state 4 can be applied to the CORESET. The BFD RS can maintain TCI state 1 and update other TCI states of the BFD RS from TCI state 2 to TCI state 4 (625). In other words, after the application timing, the nth dynamically revealed beam / TCI state (i.e., TCI 1) can be applied to RS A and the (n+1)th dynamically revealed beam / TCI state (i.e., TCI 4) can be applied to RS B.

[0148] Alternatively, if a set of periodic CSI-RS resource setting indices q0 is not provided, the beam / TCI state of the BFD RS will at least follow the dynamically indicated beam / TCI state. For example, terminal device 110-1 may determine the BFD RS set to include a CSI-RS with a QCL TypeD set corresponding to the indicated TCI state (DL TCI or combined TCI). In some embodiments, terminal device 110-1 may use failureDetectionResourceToAddModList for the bandwidth portion (BWP) of a serving cell

number

number

number

number

number

number

[0149] In some embodiments, if a set of periodic CSI-RS resource setting indices q0 is not provided, the beam / TCI state of the BFD RS will at least follow dynamically indicated beam / TCI states. For example, terminal device 110-1 may determine the BFD RS set to include up to two CSI-RS with QCL TypeD set, one RS corresponding to an indicated TCI state (e.g., DL TCI or combined TCI), and another RS ​​corresponding to a default / fallback TCI state (e.g., DL TCI or combined TCI). For example, as shown in Figure 7, PDCCH 710 may indicate TCI state 1, and the TCI states of the BFD RS may be TCI states 2 and 3. After a first timing 711, TCI state 1 can be applied to the CORESET. The BFD RS can maintain TCI state 2, and the other TCI states of the BFD RS can be updated from TCI state 3 to TCI state 1 (715). In other words, a dynamically represented TCI state (i.e., TCI state 1) can be applied to one of the RSs (e.g., RS A), and the beam / TCI state of RS B is the fallback / default beam, which in this case is TCI state 2.

[0150] In another embodiment, after MAC CE activates the TCI state, the dynamically indicated beam / TCI state can be replaced with the TCI state of the lowest code point before the beam application timing of the TCI state indicated in DCI. This enables proper beam fault detection.

[0151] In some embodiments, BFI_counter can be set to 0 if the beam / TCI state of at least one BFD RS is updated based on the dynamically indicated beam / TCI state in the TCI field of a PDCCH (e.g., PDCCH 310, PDCCH 410, PDCCH 510, or PDCCH 710). For example, BFI_counter can be set to 0 if the TCI state of any of the reference signals used for beam fault detection is indicated / updated by the DCI / physical layer of the condition associated with this serving cell. In some embodiments, the condition may be that the HARQ-ACK corresponding to the DCI, or the PDSCH scheduled by the DCI, is an ACK. Alternatively, in the case of HARQ-ACK multiplexing, the condition may be that the PDCCH with the DCI is up-to-date. In other embodiments, the condition may be after a certain timing, such as the beam application timing, or the timing when the DCI is detected, the PDSCH scheduled by the DCI is successfully decoded, or the HARQ-ACK codebook is generated.

[0152] In some embodiments, the terminal device may be configured with two RS sets (e.g., RS_s1 and RS_s2) for beam fault detection, or the terminal device may determine them. In some embodiments, RS_s1 may include one or two RSs, or include indices for one or two RSs. In some embodiments, RS_s2 may include one or two RSs, or include indices for one or two RSs. In some embodiments, the terminal device may be configured for multi-TRP transmission (e.g., a first TRP and a second TRP). In some embodiments, RS_s1 may be applied for beam fault detection of the first TRP. In some embodiments, RS_s2 may be applied for beam fault detection of the second TRP. In some embodiments, a first beam fault recovery procedure may exist for the first TRP. In some embodiments, a second beam fault recovery procedure may exist for the second TRP. In some embodiments, a third beam fault recovery procedure may exist for the cells of the first and second TRPs. In some embodiments, if the value of either the beam failure indicator counter in the first beam failure recovery procedure or the second beam failure recovery procedure is set to 0, the value of the beam failure indicator counter in the third beam failure recovery procedure is set to 0. In some embodiments, if either the beam failure recovery timer (e.g., beamFailureRecoveryTimer set by RRC) in the first beam failure recovery procedure or the second beam failure recovery procedure is stopped, the beam failure recovery timer (e.g., beamFailureRecoveryTimer set by RRC) in the third beam failure recovery procedure is stopped.

[0153] Figure 8 shows the signaling flow of communication between a network device and a terminal device according to some embodiments of the present disclosure. For discussion purposes, process 800 will be described with reference to Figure 1. Process 800 may involve the network device 120 and terminal device 110-1 in Figure 1.

[0154] The terminal device 110-1 determines the estimated wireless link quality between the terminal device 110-1 and the network device 120 according to the first RS and the second RS (8010). For example, the terminal device 110-1 can measure a first set of RS. In this case, the terminal device 110-1 can estimate the wireless link quality based on the measurement results of the first set of RS.

[0155] Terminal device 110-1 sends a request to network device 120 (8020) for an indication of at least one TCI state in the uplink resource. The request may not include an RS index. In this case, terminal device 110 may receive a DCI in a first PDCCH from network device 120. The DCI may include an indication of at least one TCI state. Terminal device 110-1 may further apply at least one TCI state to a first RS based on the first condition. In some embodiments, at least one TCI state or a second TCI state can be applied for transmission of the uplink resource. For example, in some embodiments, up to two RS indices (e.g., RS A and RS B) are included in q0, and a dynamically indicated beam / TCI state can be applied to RS A and a default / fallback beam / TCI state can be applied to RS B. If a fault (e.g., represented as a first fault or a single fault) is detected based on RS A and no beam fault is detected based on RS A+RS B (e.g., no beam fault recovery request is triggered), the terminal device 110-1 may report a beam instruction request to the network device 120 (e.g., via PUCCH / PRACH / PUSCH; beam or spatial relation information may follow the default / fallback UL TCI).

[0156] The network device 120 transmits one or more PDCCHs in one or more CORESETs to the terminal device 110-1 (8030). The terminal device 110-1 monitors one or more PDCCHs in one or more CORESETs based on conditions (8040). In some embodiments, the conditions may include that a fault has been detected based on a first RS. Alternatively, or additionally, the conditions may include that no fault has been detected based on a second RS. In some embodiments, the terminal device 110-1 may monitor the PDCCHs in the CORESETs in a default / fallback beam / TCI state after a request (e.g., until the beam / TCI state is indicated in the PDCCH and after the application timing).

[0157] In some embodiments, a second TCI state may be applied to a second RS. For example, the second TCI may be the default TCI state. Alternatively, the second TCI may be a fallback TCI state. In other embodiments, the second TCI may be the TCI state corresponding to the lowest code point from a set of code points activated via MAC CE. Alternatively, the second TCI may be the TCI state applied to the first PDCCH. In this case, the terminal device 110-1 may receive / monitor one or more PDCCHs in one or more CORESETs in the second TCI state. After a request, the terminal device 110-1 may transmit a PUSCH / PUCCH using the same spatial domain filter as that corresponding to RS B. For example, as shown in Figure 9, PDCCH 910 may indicate TCI state 1. TCI state 1 may be applied to RS A after beam application timing 911. TCI state 2, which is the default / fallback TCI state, may be applied to RS B. If a fault is detected based on RS A (in other words, TCI state 1 is not active) and no beam fault is detected based on RS A + RS B (for example, no beam fault recovery request is triggered), terminal device 110-1 may report a beam instruction request to network device 120 at timing 921. In this case, terminal device 110-1 may receive / monitor one or more PDCCHs in one or more CORESETs in TCI state 2.

[0158] In some embodiments, terminal device 110-1 can transmit a request in a certain beam / TCI state. In some embodiments, the beam / TCI state can be a default / fallback beam / TCI state (e.g., coupled or UL TCI) or a indicated (currently applied) UL TCI. Alternatively, if terminal device 110-1 has a separate TCI configured, terminal device 110-1 can transmit a request in a indicated (i.e., currently applied) UL TCI. In some embodiments, if coupled TCI is configured on terminal device 110-1, terminal device 110-1 may transmit a request in a default / fallback beam / (coupled) TCI state.

[0159] In some embodiments, the request may include an instruction for a beam update / instruction request. For example, the request may include a single bit indicating a beam update / instruction request. In this case, when the network device 120 receives the request, it can know that the terminal device 110-1 needs to indicate a (new / different) beam / perform an update with a (new / different) beam. It is not necessary to report a new beam candidate in the request. In some embodiments, the terminal device 110-1 does not need to search for a new beam candidate after a beam fault is detected in the RSA.

[0160] In other embodiments, separate procedures and / or sets of parameters (e.g., at least one of beamFailureDetectionTimer_1, BFI_COUNTER_1, beamFailureInstanceMaxCount_1, beamFailureRecoveryTimer_1 (or beamUpdateRequestTimer)) may be proposed for beam fault detection in RS A and for beam change / update requests based on that detection. For example, as shown in Figure 10, a first beam fault is detected in RS A. Table 1 shows an example of a first procedure for fault detection in the MAC entity of terminal device 110-1.

[0161] Table 1 [Table 3]

[0162] Furthermore, as shown in Figure 10, the terminal device 110-1 may perform beam fault detection in RS A and RS B. Table 2 shows an example of fault detection and recovery procedures in the MAC entity of the terminal device 110-1.

[0163] Table 2 [Table 4]

[0164] In some embodiments, after BFR, a newly identified beam can be applied to PDCCH monitoring and / or PUCCH transmission in CORESET, and the TCI field of PDCCH can be ignored. For PCell or PSCell, the terminal device 110-1 can be provided with settings for PRACH transmission. For PRACH transmission of slot n, a periodic CSI-RS resource setting or an index q provided by the upper layer is used. new In accordance with the antenna port pseudo-collocation parameters associated with the synchronization signal / physical broadcast channel (SS / PBCH) block associated with the terminal device 110-1 may monitor the PDCCH in a set of search spaces provided by recoverySearchSpaceId for detecting a DCI format in which the CRC is scrambled by a Cell Radio Network Temporary Identifier (C-RNTI) or Modulation Coding Scheme Cell-RNTI (MCS-C-RNTI), starting from slot n+4, within a window set by BeamFailureRecoveryConfig. For PDCCH monitoring in the set of search spaces provided by recoverySearchSpaceId, and for corresponding PDSCH reception, the terminal device 110-1 may use index q newThe same antenna port pseudo-collocation parameters as those associated with the DCI may be assumed. If a TCI field is present in the detected DCI and dynamic beam instruction is set, the TCI field is ignored until the UE receives either a TCI state activation instruction or the parameters tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList from a higher layer. After terminal device 110-1 detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, terminal device 110-1 may continue to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until terminal device 110-1 receives a MAC CE activation instruction for the TCI state or tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList.

[0165] For PCell or PSCell, 28 symbols after the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId for terminal device 110-1 to detect a DCI format with the CRC scrambled by C-RNTI or MCS-C-RNTI, if a TCI field exists in the detected DCI, and if dynamic beam instruction is set, the TCI field is ignored, and terminal device 110-1 transmits PUCCH in the same cell as the PRACH transmission using the following until terminal device 110-1 receives an activation command for PUCCH-SpatialRelationInfo ([11,TS38.321]), or is provided with PUCCH-SpatialRelationInfo for a PUCCH resource, or receives an activation command for the TCI state if dynamic beam instruction is set. - Same spatial filter as the previous PRACH transmission - As described in Section 7.2.1, q u = 0, q d = q new and the power determined by l = 0

[0166] For a PCell or PSCell, 28 symbols after the last symbol of the first PDCCH reception in the search space set provided by the recoverySearchSpaceId that the terminal device 110-1 detects a DCI format in which the CRC is scrambled by a C-RNTI or MCS-C-RNTI, the terminal device 110-1, for PDCCH monitoring in CORESET with index 0, assumes the same antenna port quasi-collocation parameters associated with index q new and, if the detected DCI format has a TCI field and a dynamic beam indication is set, the TCI field is ignored.

[0167] For a PCell or PSCell, when a BFR MAC CE ([11, TS38.321]) is transmitted in Msg3 or MsgA of a contention-based random access procedure and a PUCCH resource is provided by PUCCH-SpatialRelationInfo, 28 symbols after the last symbol of the PDCCH reception that determines the completion of the contention-based random access procedure described in Section 5.1.5 of [11, TS38.321], the terminal device 110-1 transmits a PUCCH in the same cell as the PRACH transmission using the following: - The same spatial filter as the previous PRACH transmission - As described in Section 7.2.1, q u = 0, q d = q new and the power determined by l = 0. Here, q new is the SS / PBCH block index selected for the last PRACH transmission.

[0168] Terminal device 110-1 can provide settings for PUCCH transmission with Link Recovery Request (LRR) by schedulingRequestID-BFR-SCell, as described in Section 9.2.4. Terminal device 110-1 provides an index of at least the corresponding SCell where the radio link quality is worse than Qout in a first PUSCH MAC CE, where LR, q for the corresponding SCell new The indication of the presence of, and the index q of the SS / PBCH block provided by the periodic CSI-RS setting or the upper layer. new If any, it can be sent for the corresponding SCell as described in [11, TS38.321]. Twenty-eight symbols after the last symbol of the PDCCH reception with DCI format scheduling a PUSCH transmission with a toggled NDI field value of the same HARQ process number as the first PUSCH transmission, the terminal device 110-1 may do the following: - In all CORESETs in SCells shown by MAC CE, if there is a corresponding index q new Monitor the PDCCH using the same antenna port pseudo-collocation parameters associated with it. - In the cases listed below, to receive periodic CSI-RS or SS / PBCH blocks as described in Section 9.2.2, if q new Using the same spatial domain filter as the one corresponding to q, as described in Section 7.2.1, u =0, q d =q new Then, using the power determined at l=0, a PUCCH transmission is sent in the PUCCH-SCell. - PUCCH's PUCCH-SpatialRelationInfo is provided to terminal device 110-1. - PUCCH with LRR is not transmitted, or is transmitted on PCell or PSCell. - PUCCH-SCell is included in the SCell indicated by MAC-CE. - If dynamic beam indication is set, the TCI field is ignored if dynamic beam indication is set, if a TCI field is present in the detected DCI, until the UE receives an activation command for the TCI state at a higher layer. The 28 symbol SCS setting is the minimum of the SCS settings for the active DL BWP for PDCCH reception and the active DL BWP for at least one SCell.

[0169] In some embodiments, in the case of cross-component carrier (CC) instructions (for example, terminal device 110-1 receives a PDCCH at CC1, and the detected DCI indicates the TCI state and cross-carrier scheduling / instruction at CC2), if the indicated TCI state is a combined TCI or a DL TCI + UL TCI pair, and CC2 is a downlink CC without uplink transmissions, then either the combined TCI applies only to downlink transmissions (CORESET, PDSCH, and RS), or only the DL TCI applies to downlink transmissions (CORESET, PDSCH, and RS). A pool of TCI states across CCs can be applied to a set of CCs, and if a CC in the set is a downlink-only CC (no uplink), then if the TCI state is a combined TCI, it applies only to the downlink transmissions of that CC, and if the TCI state is a DL TCI + UL TCI pair, only the DL TCI applies to the CC. For example, terminal device 110-1 does not expect only UL TCI to be indicated for a CC. Alternatively, if the UL TCI for CC is indicated on terminal device 110-1, the current or default DL TCI applies to CC.

[0170] Figure 11 shows a flowchart of an exemplary method 1100 according to an embodiment of the present disclosure. For illustrative purposes only, method 1100 can be performed using the terminal device 110-1 shown in Figure 1.

[0171] In block 1110, terminal device 110-1 receives from network device 120 an indication of at least one transmit setting indicator (TCI) state in the detected downlink control information (DCI) within the first physical downlink control channel (PDCCH).

[0172] In block 1120, terminal device 110-1 receives a downlink transmission from network device 120 based on at least one TCI state based on a first condition. In some embodiments, the first condition includes one or more of the following: being after a first timing; starting from the first timing; the acknowledgment of a hybrid auto-retransmission request (HARQ-ACK) corresponding to a detected DCI or a physical downlink shared channel (PDSCH) scheduled by a DCI being an ACK; the first PDCCH not starting or ending earlier than a second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to a detected DCI or a PDSCH scheduled by a detected DCI in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH being reported to the network device on the same resource. In some embodiments, the first timing is the beam application timing.

[0173] In block 1130, terminal device 110-1 applies at least one TCI state to at least one reference signal (RS) in the first RS set based on a first condition, or includes a third RS indicated by at least one TCI state in the first RS set based on a first condition. The first RS set is applied for beam fault detection. In some embodiments, terminal device 110-1 may stop the first procedure based on a second condition. Terminal device 110-1 may restart the second procedure based on the first condition. In this case, the second condition includes at least one of the following: it is after the second timing; it starts from the second timing; at least one TCI state is different from a first TCI state that applies to the PDCCH of the detected DCI and / or to at least one RS in the first RS set; the acknowledgment of the hybrid auto retransmission request (HARQ-ACK) corresponding to the detected DCI or the PDSCH scheduled by the DCI is an ACK; and the first PDCCH does not start or end earlier than the second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to the detected DCI in the first PDCCH or the PDSCH scheduled by the detected DCI in the first PDCCH and the HARQ-ACK corresponding to the detected DCI in any other PDCCH are reported to the network device on the same resource.

[0174] In some embodiments, the terminal device 110-1 may transmit an uplink resource with an acknowledgment to the network device, the uplink resource being a resource of a physical uplink shared channel (PUSCH) or a resource of a physical uplink controlled channel (PUCCH).

[0175] In exemplary embodiments, the second timing is not later than or earlier than the first timing. The second timing may include at least one of the timing at which a DCI is detected in the first PDCCH, the timing at which the PDSCH scheduled by the detected DCI is successfully decoded, and the timing at which a HARQ-ACK corresponding to the DCI or a HARQ-ACK corresponding to the PDSCH scheduled by the detected DCI is generated in the terminal device. In some embodiments, the first RS set includes one or two RSs.

[0176] In some embodiments, the terminal device 110-1 may apply at least one TCI state to a first RS in the first RS set and a second TCI state to a second RS in the first RS set based on a first condition. The first RS set includes a first RS and a second RS.

[0177] In an exemplary embodiment, the first RS is an RS with a low or high index value in the first RS set. In another exemplary embodiment, the second TCI state is a default or fallback TCI state, or a TCI state corresponding to the lowest code point from a set of code points activated via a media access control element (MAC CE).

[0178] In some embodiments, the second TCI state is the first TCI state. In some embodiments, the first RS set may be set by a network device. In some embodiments, the first RS set is determined by a terminal device based on the TCI states of one or more control resource sets (CORESETs).

[0179] In an exemplary embodiment, the value of the beam fault indicator counter is set to 0 based on a second condition. The second condition may include at least one of the following: it is after a second timing; it starts from the second timing; at least one TCI state is different from a first TCI state applied to the PDCCH of the detected DCI and / or applied to at least one RS in the first RS set; the acknowledgment of a hybrid auto-retransmission request (HARQ-ACK) corresponding to the detected DCI or the PDSCH scheduled by the DCI is an ACK; and the first PDCCH does not start or end earlier than the second PDCCH in the PDCCH set, and the HARQ-ACK corresponding to the detected DCI in the first PDCCH or the PDSCH scheduled by the detected DCI in the first PDCCH and the HARQ-ACK corresponding to the detected DCI in any other PDCCH are reported to the network device on the same resource.

[0180] In some embodiments, terminal device 110-1 may ignore the TCI field of another detected DCI in another PDCCH after a third timing and / or until a fourth timing. In this case, the third timing is when beam fault recovery is successfully completed, and the fourth timing is when one or more TCI states are activated or when the indicated mapping between TCI states and code points is applied.

[0181] In some embodiments, the terminal device 110-1 may, based on the first condition, replace the first RS with a third RS in the first RS set and apply the second TCI state to the second RS in the first RS set. In this case, the first RS set includes the first RS and the second RS.

[0182] In block 1140, terminal device 110-1 determines an estimate of the wireless link quality between the terminal device and the network device based on the first RS set.

[0183] Figure 12 shows a flowchart of an exemplary method 1200 according to an embodiment of the present disclosure. For illustrative purposes only, method 1200 can be performed using the terminal device 110-1 shown in Figure 1.

[0184] In block 1210, terminal device 110-1 determines the estimate of radio link quality according to the first reference signal (RS) and the second RS.

[0185] In block 1220, terminal device 110-1 sends a request to network device 120 for an indication of the Transmit Setting Indicator (TCI) status on the first uplink resource, based on a first condition. In some embodiments, the first condition includes at least one of a fault detected based on a first RS and no fault detected based on a second RS. In some embodiments, the request does not include an RS index.

[0186] In an exemplary embodiment, terminal device 110-1 receives an instruction from network device 120 for the TCI state in the downlink control information (DCI) within the first PDCCH. Terminal device 110-1 may also apply the TCI state to the first RS based on a first condition, which includes at least one of the following: it is after a first timing; it starts from the first timing; the acknowledgment of a hybrid auto retransmission request (HARQ-ACK) corresponding to a detected DCI or a physical downlink shared channel (PDSCH) scheduled by a DCI is an ACK; and the first PDCCH does not start or end earlier than a second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to a detected DCI or a PDSCH scheduled by a detected DCI within the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH are reported to the network device on the same resource. Here, the first timing is the beam application timing, or the first slot or first subslot which is at least a first value of milliseconds or a second value of symbol from the last symbol of the second uplink resource with an acknowledgment of the detected DCI or PDSCH scheduled by the DCI. Terminal device 110-1 can apply a second TCI state to the second RS. The second TCI state may include one of the following: the default TCI state, a fallback TCI state, the TCI state corresponding to the lowest code point from a set of code points activated via the Media Access Control Element (MAC CE), or the TCI state applied to the first PDCCH.

[0187] In block 1230, terminal device 110-1 monitors one or more physical downlink control channels (PDCCHs) in one or more control resource sets (CORESETs). In some embodiments, terminal device 110-1 may monitor one or more PDCCHs in one or more CORESETs in a second TCI state. The TCI state can be applied for uplink resource transmission. In some embodiments, the second TCI state or uplink TCI state is applied for the transmission of a first uplink resource, and the uplink TCI state is the TCI state applied for uplink transmission when transmitting a first uplink resource.

[0188] Figure 13 shows a flowchart of an exemplary method 1300 according to an embodiment of the present disclosure. For illustrative purposes only, method 1300 can be implemented using the network device 120 shown in Figure 1.

[0189] In block 1310, the network device 120 transmits an instruction to the terminal device 110-1 indicating the state of at least one transmit setting indicator (TCI) in the downlink control information (DCI) within the first physical downlink control channel (PDCCH).

[0190] In block 1320, the network device 120 transmits a downlink transmission from the network device to the terminal device 110-1 based on at least one TCI state based on a first condition. In some embodiments, the first condition may include at least one of the following: it is after a first timing; it starts from the first timing; the acknowledgment of a hybrid auto retransmission request (HARQ-ACK) corresponding to a detected DCI or a physical downlink shared channel (PDSCH) scheduled by a DCI is an ACK; and the first PDCCH does not start or end earlier than a second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to a detected DCI in the first PDCCH or a PDSCH scheduled by a detected DCI in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH are reported to the network device on the same resource. Here, the first timing is the beam application timing, or the first slot which is at least a first value of milliseconds or a second value of symbols from the last symbol of the uplink resource with an acknowledgment of the detected DCI or PDSCH scheduled by the DCI.

[0191] In block 1330, the network device 120 transmits at least one RS in a first set of reference signals (RS) based on a first condition. The first set of RS can be applied for beam fault detection.

[0192] In some embodiments, the first timing may be the beam application timing. The first RS set includes one or two RSs. In some embodiments, the first RS set is configured in the terminal device. In some exemplary embodiments, the first RS set is determined in the terminal device based on the TCI state of one or more control resource sets (CORESETs).

[0193] In some embodiments, the network device 120 may receive an uplink resource accompanied by an acknowledgment to the network device. In this case, the uplink resource may be a resource of a physical uplink shared channel (PUSCH) or a resource of a physical uplink controlled channel (PUCCH).

[0194] Figure 14 shows a flowchart of an exemplary method 1400 according to an embodiment of the present disclosure. For illustrative purposes only, method 1400 can be implemented using the network device 120 shown in Figure 1.

[0195] In block 1410, the network device 120 transmits a first reference signal (RS) and a second RS to the terminal device 110-1.

[0196] In block 1420, the network device 120 transmits the first PDCCH set from one or more control resource sets (CORESET) in the third TCI state to the terminal device 110-1.

[0197] In block 1430, the network device 120 receives a request from terminal device 110-1 for an instruction regarding the Transmit Setting Indicator (TCI) status in the uplink resource.

[0198] In block 1440, the network device 120 transmits a second PDCCH set in one or more CORESETs in a fourth TCI state to the terminal device 110-1 based on the receipt of the request. In some embodiments, the fourth TCI state is one of the following: the default TCI state, a fallback TCI state, the TCI state corresponding to the lowest code point from a set of code points activated via the Media Access Control Element (MAC CE), a preceding TCI state applied to one or more CORESETs before the third TCI state is applied, or a TCI state different from the third TCI state.

[0199] In some embodiments, the network device 120 may transmit an instruction for a fifth TCI state in the second PDCCH set to the terminal device 110-1. In other embodiments, the network device 120 may transmit the second PDCCH set in a fourth TCI state to the terminal device 110-1 after a time period starting from the first or last symbol of the uplink resource. In this case, the second TCI state can be one of the following: the default TCI state, a fallback TCI state, the TCI state corresponding to the lowest code point from the set of code points activated via the Media Access Control Element (MAC CE), or the TCI state applied to the first PDCCH. In some embodiments, the third and fifth TCI states correspond to different code points in the set of code points activated via the Media Access Control Element (MAC CE). In some embodiments, the third or fourth TCI state can be applied for the transmission of the uplink resource. In exemplary embodiments, the request does not include an RS index.

[0200] In some embodiments, the terminal device includes circuitry configured to receive from a network device an indication of at least one transmit setting indicator (TCI) state in detected downlink control information (DCI) in a first physical downlink control channel (PDCCH), receive a downlink transmission from the network device based on at least one TCI state based on a first condition, apply at least one TCI state to at least one reference signal (RS) in a first RS set applied for beam fault detection based on the first condition, or include a third RS indicated by at least one TCI state in the first RS set based on the first condition, and determine an estimate of radio link quality between the terminal device and the network device based on the first RS set.

[0201] In some embodiments, the first condition includes at least one of the following: being after a first timing; starting from the first timing; the acknowledgment of a hybrid auto-retransmission request (HARQ-ACK) corresponding to a detected DCI or a DCI-scheduled physical downlink shared channel (PDSCH) being an ACK; and the first PDCCH not starting or ending earlier than a second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to a detected DCI or a DCI-scheduled PDSCH in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH being reported to the network device for the same resource, where the first timing is a beam application timing, or a first slot or first subslot that is at least a first value of milliseconds or a second value of a symbol from the last symbol of the uplink resource with an acknowledgment of a detected DCI or a DCI-scheduled PDSCH.

[0202] In some embodiments, the terminal device includes circuitry configured to send an uplink resource with an acknowledgment to the network device. The uplink resource is either a resource on a physical uplink shared channel (PUSCH) or a resource on a physical uplink controlled channel (PUCCH).

[0203] In some embodiments, the terminal device includes a circuit configured to stop the first procedure based on a second condition and to resume the second procedure based on the first condition.

[0204] In some embodiments, the second condition includes at least one of the following: being after the second timing; starting from the second timing; at least one TCI state being different from a first TCI state applied to the PDCCH of the detected DCI and / or applied to at least one RS in the first RS set; the Hybrid Auto Retransmission Request Acknowledgment (HARQ-ACK) corresponding to the detected DCI or the PDSCH scheduled by the DCI being an ACK; and the first PDCCH not starting or ending earlier than the second PDCCH in the PDCCH set, and the HARQ-ACK corresponding to the detected DCI in the first PDCCH or the PDSCH scheduled by the detected DCI in the first PDCCH and the HARQ-ACK corresponding to the detected DCI in any other PDCCH being reported to the network device on the same resource.

[0205] In some embodiments, the second timing is neither later nor earlier than the first timing.

[0206] In some embodiments, the second timing includes at least one of the following: the timing at which a DCI is detected in the first PDCCH; the timing at which the PDSCH scheduled by the detected DCI is successfully decoded; and the timing at which a HARQ-ACK corresponding to the DCI or a HARQ-ACK corresponding to the PDSCH scheduled by the detected DCI is generated in the terminal device.

[0207] In some embodiments, the first RS set includes one or two RSs, or the first RS set includes one or two indices of the RS resource settings of one or two RSs.

[0208] In some embodiments, the terminal device includes a circuit configured to apply at least one TCI state to a first RS in a first RS set and a second TCI state to a second RS in the first RS set, based on a first condition. The first RS set includes a first RS and a second RS.

[0209] In some embodiments, the terminal device includes a circuit configured to replace a first RS with a third RS in a first RS set and to apply a second TCI state to a second RS in the first RS set, based on a first condition. The first RS set includes a first RS and a second RS.

[0210] In some embodiments, the first RS is an RS with a low or high index value in the first RS set.

[0211] In some embodiments, the second TCI state is a default or fallback TCI state, or a TCI state corresponding to the lowest code point from a set of code points activated via a media access control element (MAC CE).

[0212] In some embodiments, the second TCI state is the first TCI state.

[0213] In some embodiments, the first RS set is configured by a network device, or the first RS set is determined by a terminal device based on the TCI state of one or more control resource sets (CORESETs).

[0214] In some embodiments, the value of a beam fault indicator counter is set to 0 based on a second condition, the second condition being after a second timing, starting from the second timing, at least one TCI state being different from a first TCI state applied to the PDCCH of a detected DCI and / or applied to at least one RS in the first RS set, the acknowledgment of a hybrid auto-retransmission request (HARQ-ACK) corresponding to the detected DCI or the PDSCH scheduled by the DCI being an ACK, and the first PDCCH not starting or ending earlier than the second PDCCH in the PDCCH set, and the HARQ-ACK corresponding to the detected DCI in the first PDCCH or the PDSCH scheduled by the detected DCI in the first PDCCH and the HARQ-ACK corresponding to the detected DCI in any other PDCCH being reported to the network device on the same resource.

[0215] In some embodiments, the terminal device includes circuitry configured to ignore the TCI field of another detected DCI in another PDCCH after a third timing and / or until a fourth timing.

[0216] In some embodiments, a third timing is when beam fault recovery is successfully completed, and a fourth timing is when one or more TCI states are activated or when the specified mapping between TCI states and code points is applied.

[0217] In some embodiments, the terminal device includes circuitry configured to determine an estimate of radio link quality according to a first reference signal (RS) and a second RS, to send a request to the network device for an indication of the transmit setting indicator (TCI) status in a first uplink resource based on a first condition, and to monitor one or more physical downlink control channels (PDCCH) in one or more control resource sets (CORESET).

[0218] In some embodiments, the first situation includes at least one of a fault detected based on a first RS and a fault not detected based on a second RS.

[0219] In some embodiments, the terminal device includes a circuit configured to receive an indication of the TCI state in detected downlink control information (DCI) in a first PDCCH from a network device and to apply the TCI state to a first RS based on a first condition. The first condition includes at least one of the following: it is after a first timing; it starts from a first timing; the acknowledgment of a hybrid auto retransmission request (HARQ-ACK) corresponding to a detected DCI or a physical downlink shared channel (PDSCH) scheduled by the DCI is an ACK; and the first PDCCH does not start or end earlier than a second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to a detected DCI in the first PDCCH or a PDSCH scheduled by the detected DCI in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH are reported to the network device on the same resource. Here, the first timing is the beam application timing, or the first slot or first subslot which is at least a first value of milliseconds or a second value of symbols from the last symbol of the second uplink resource with an acknowledgment of the detected DCI or PDSCH scheduled by the DCI.

[0220] In some embodiments, the terminal device includes circuitry configured to apply a second TCI state to a second RS. The second TCI state is one of the following: a default TCI state, a fallback TCI state, a TCI state corresponding to the lowest code point from a set of code points activated via a media access control element (MAC CE), or a TCI state applied to a first PDCCH.

[0221] In some embodiments, the terminal device includes circuitry configured to monitor one or more PDCCHs within one or more CORESETs in a second TCI state.

[0222] In some embodiments, a second TCI state or uplink TCI state is applied for transmission of a first uplink resource, and the uplink TCI state is a TCI state applied for uplink transmission when transmitting the first uplink resource.

[0223] In some embodiments, the request does not include an RS index.

[0224] In some embodiments, the network device includes circuitry configured to transmit an indication of at least one transmit setting indicator (TCI) state in downlink control information (DCI) within a first physical downlink control channel (PDCCH), transmit downlink transmissions from the network device to terminal devices based on at least one TCI state based on a first condition, and transmit at least one RS in a first set of reference signals (RS) applied for beam fault detection based on a first condition.

[0225] In some embodiments, the first condition includes at least one of the following: being after a first timing; starting from the first timing; the acknowledgment of a hybrid auto-retransmission request (HARQ-ACK) corresponding to a detected DCI or a DCI-scheduled physical downlink shared channel (PDSCH) being an ACK; and the first PDCCH not starting or ending earlier than a second PDCCH in the PDCCH set; and the HARQ-ACK corresponding to a detected DCI or a DCI-scheduled PDSCH in the first PDCCH and the HARQ-ACK corresponding to a detected DCI in the second PDCCH being reported to the network device for the same resource, where the first timing is a beam application timing or a first slot which is at least a first value of milliseconds or a second value of a symbol from the last symbol of the uplink resource with the acknowledgment of a detected DCI or a DCI-scheduled PDSCH.

[0226] In some embodiments, the network device includes circuitry configured to receive uplink resources from terminal devices accompanied by acknowledgments to the network device. The uplink resources may be resources of a physical uplink shared channel (PUSCH) or resources of a physical uplink controlled channel (PUCCH).

[0227] In some embodiments, the first RS set includes one or two RSs, or the first RS set includes one or two indices of the RS resource settings of one or two RSs.

[0228] In some embodiments, the first RS set is configured in the terminal device.

[0229] In some embodiments, the first RS set is determined by the terminal device based on the TCI state of one or more control resource sets (CORESETs).

[0230] In some embodiments, the network device includes circuitry configured to transmit a first reference signal (RS) and a second RS to a terminal device, transmit a first set of physical downlink control channels (PDCCHs) in one or more control resource sets (CORESETs) to the terminal device in a third TCI state, receive a request from the terminal device for an indication of a transmit setting indicator (TCI) state in an uplink resource, and, based on the receipt of the request, transmit a second set of PDCCHs in one or more CORESETs to the terminal device in a fourth TCI state.

[0231] In some embodiments, the fourth TCI state is one of the following: the default TCI state, a fallback TCI state, the TCI state corresponding to the lowest code point from a set of code points activated via a Media Access Control element (MAC CE), a preceding TCI state applied to one or more CORESETs before the third TCI state is applied, or a TCI state different from the third TCI state.

[0232] In some embodiments, the network device includes circuitry configured to transmit an instruction for a fifth TCI state in a second PDCCH set to a terminal device.

[0233] In some embodiments, the network device includes circuitry configured to transmit a second PDCCH set in a fourth TCI state upon receipt of a request, by transmitting a second PDCCH set in a fourth TCI state after a time period starting from the first or last symbol of the uplink resource.

[0234] In some embodiments, the third TCI state and the fifth TCI state correspond to different code points in a set of code points activated via a media access control element (MAC CE).

[0235] In some embodiments, a third TCI state or a fourth TCI state is applied for the transmission of uplink resources.

[0236] In some embodiments, the request does not include an RS index.

[0237] Figure 15 is a schematic block diagram of a device 1500 suitable for carrying out embodiments of the present disclosure. The device 1500 can be considered a further exemplary implementation of the network device 120 or terminal device 110 shown in Figure 1. Therefore, the device 1500 can be implemented in, or at least as part of, the terminal device 110 or network device 120.

[0238] As shown in the figure, the device 1500 includes a processor 1510, a memory 1520 coupled to the processor 1510, a suitable transmitter (TX) and receiver (RX) 1540 coupled to the processor 1510, and a communication interface connected to the TX / RX 1540. The memory 1520 stores at least a portion of the program 1530. The TX / RX 1540 is for bidirectional communication. The TX / RX 1540 has at least one antenna to facilitate communication, although in practice the access node described herein may have multiple antennas. The communication interface may represent any interface required for communication with other network elements, for example, 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 a Uu interface for communication between an eNB and a terminal device.

[0239] Program 1530 is considered to include program instructions, and when the program is executed by an associated processor 1510, it enables the apparatus 1500 to operate in accordance with the embodiments of the present disclosure as discussed herein with reference to FIGS. 2-14. Embodiments herein may be implemented by computer software, hardware, or a combination of software and hardware that is executable by the processor 1510 of the apparatus 1500. The processor 1510 may be configured to implement various embodiments of the present disclosure. Also, the combination of the processor 1510 and the memory 1520 may constitute processing means suitable for implementing each embodiment of the present disclosure.

[0240] The memory 1520 may be of any type suitable for a local technical network and may be implemented by any suitable data storage technology (examples include, but are not limited to, computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory). Although only one memory 1520 is shown for the apparatus 1500, a plurality of physically different memory modules may be installed in the apparatus 1500. The processor 1510 may be of any type suitable for a local technical network and may include, for example, one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration, but is not limited thereto. The apparatus 1500 may have a plurality of processors, for example, an application-specific integrated circuit chip that is temporally dependent on a clock synchronized with a master processor.

[0241] Generally, various embodiments of the present disclosure may be implemented by hardware or dedicated 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 can be executed by a controller, a microprocessor, or other computing devices. Various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or by some other pictorial representation, and the blocks, devices, systems, techniques, or methods described herein may be implemented, for example, by hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or combinations thereof, but it will be understood that they are not limited thereto.

[0242] The present disclosure further provides at least one computer program product tangibly stored in a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules. The instructions are executed on a device on a target physical processor or virtual processor, for example, to execute the processes or methods described above with reference to FIGS. 2 to 14. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules may be combined or divided among program modules as needed. The machine-readable instructions of program modules may be executed within a local or distributed device. In a distributed device, program modules may be located on either local or remote storage media.

[0243] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when the program code is executed by the processor or controller, the functions / operations defined in the flowcharts and / or block diagrams are performed. The program code may run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0244] The program code described above may be implemented on a machine-readable medium, which may be any tangible medium containing or storing a program used by an instruction execution system, apparatus, or device, or a program used in conjunction with such a system 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 thereof. More specific examples of machine-readable storage media include one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable and writable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0245] While the operations have been described in a specific order, it should not be understood that, in order to obtain the desired results, these operations must be performed in a specific order or sequence, or that all of the operations shown must be performed. In some situations, multitasking and parallel processing may be advantageous. Similarly, the above discussion includes some specific implementation details, which should be interpreted not as limitations on the scope of this disclosure, but as descriptions of features that may be specific to particular embodiments. Some features described in the context of individual embodiments may be implemented in combination in one embodiment. Conversely, various features described in the context of one embodiment may be implemented separately or in any suitable secondary combination in multiple embodiments.

[0246] While this disclosure has been described using terminology specific to structural features and / or methodological behavior, it should be understood that this disclosure, as defined by the attached claims, is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and behaviors described above are disclosed as exemplary forms for implementing the claims.

Claims

1. In the downlink control information (DCI) within the first physical downlink control channel (PDCCH), means for receiving an instruction on the state of the first transmit setting indicator (TCI) from a network device, When the first TCI state is different from a previously indicated TCI state, and the hybrid automatic repeat request acknowledgedgement (HARQ-ACK) corresponding to the physical downlink shared channel (PDSCH) scheduled by the DCI is ACK, means for receiving a downlink transmission from the network device that starts after the beam application timing and to which the first TCI state is applied, As it is determined that the first TCI state is different from a previously shown TCI state, means for setting Beam Failure Indication (BFI)_COUNTER to 0, Equipped with, Terminal device.

2. The system further comprises means for determining the first set such that it includes one or more indices of a second RS having the same value as the respective RS index in the RS set corresponding to the first TCI state of each control resource set (CORESET). The terminal device according to claim 1.

3. The means for detecting beam interference further comprises means for evaluating downlink radio link quality based on the first set, The terminal device according to claim 2.

4. A method performed by a terminal device, Receiving an instruction from a network device regarding the state of the first transmit setting indicator (TCI) in the downlink control information (DCI) within the first physical downlink control channel (PDCCH), If the first TCI state is different from a previously indicated TCI state, and the hybrid automatic repeat request acknowledgedgement (HARQ-ACK) corresponding to the physical downlink shared channel (PDSCH) scheduled by the DCI is ACK, then a downlink transmission is received from the network device that starts after the beam application timing and to which the first TCI state is applied, Since it has been determined that the first TCI state is different from the previously shown TCI state, Beam Failure Indication (BFI)_COUNTER is set to 0, including, method.

5. The first set further includes determining the first set to include one or more indices of a second RS having the same value as the respective RS index in the RS set corresponding to the first TCI state of each control resource set (CORESET), The method according to claim 4.

6. To detect beam faults, further comprising evaluating the downlink radio link quality based on the first set, The method according to claim 5.

Images