Terminal device, network device, and method

Abstract

The embodiments of the present disclosure relate to a communication method, an apparatus, and a computer storage medium. The method includes, in a terminal device, receiving from a network device a first set of reference signals (RSs) and a second set of RSs, receiving one or more settings of a first timer and a second timer, performing beam failure detection associated with a first procedure based on the first set and the first timer, performing beam failure detection associated with a second procedure based on the second set and the second timer, and performing a third procedure based on a first condition and / or a first parameter associated with at least one of the first procedure and the second procedure.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to methods, apparatuses, and computer storage media for communication.

Background Art

[0002] In recent years, enhancing support for the deployment of multi-transmission reception points (multi-TRPs) has been under consideration. For example, for physical channels other than the physical downlink shared channel (PDSCH) (such as the physical downlink control channel (PDCCH), the physical uplink shared channel (PUSCH), and / or the physical uplink control channel (PUCCH), etc.), it has been proposed to identify and define functions for improving reliability and robustness based on the reliability functions of Release 16 using multi-TRPs and / or multi-panels. Assuming multi-PDSCH reception based on multi-downlink control information (multi-DCI), it has been proposed to identify and define enhancements related to quasi-collocation (QCL) / transmission configuration indicator (TCI) to enable inter-cell multi-TRP operation. Furthermore, it has also been proposed to evaluate and, if necessary, define enhancements related to beam management for multi-TRP simultaneous transmission involving multi-panel reception.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Generally, exemplary embodiments of the present disclosure provide methods, apparatuses, and computer storage media for communication.

Means for Solving the Problems

[0004] In a first aspect, a communication method is provided. The method includes, at a terminal device, receiving, from a network device, a first set of reference signals (RSs) and a second set of RSs, receiving one or more settings of a first timer and a second timer, performing beam failure detection related to a first procedure based on the first set and the first timer, performing beam failure detection related to a second procedure based on the second set and the second timer, and performing a third procedure based on a first condition and / or a first parameter related to at least one of the first procedure and the second procedure.

[0005] In a second aspect, a communication method is provided. The method includes, at a network device, transmitting, to a terminal device, a first set of reference signals (RSs) for a first procedure and a second set of RSs for a second procedure, transmitting one or more settings of a first timer and a second timer for the first procedure and the second procedure, and receiving, from the terminal device, a beam failure recovery request or a random access preamble.

[0006] In a third aspect, a terminal device is provided. The terminal device includes circuitry configured to execute the method according to the first aspect of the present disclosure described above.

[0007] In a fourth aspect, a network device is provided. The network device includes circuitry configured to execute the method according to the second aspect of the present disclosure described above.

[0008] In a fifth aspect, a computer program product including machine-readable instructions is provided. The machine-readable instructions, when executed, cause a machine to execute the method according to the first aspect or the second aspect of the present disclosure described above.

[0009] In a sixth aspect, a computer-readable medium storing instructions is provided. The instructions, when executed by at least one processor, cause the at least one processor to execute the method according to the first aspect or the second aspect of the present disclosure described above.

[0010] It should be understood that the summary part of the invention is not intended to identify the important features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure should be easily understood through the following description.

Brief Description of the Drawings

[0011] Through the 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 more apparent.

[0012]

Figure 1

[0013]

Figure 2

[0014]

Figure 3A

Figure 3B

Figure 3C

[0015]

Figure 4A

Figure 4B

[0016]

Figure 5

[0017]

Figure 6A

Figure 6B

Figure 6C

Figure 6D

[0018]

Figure 7A

Figure 7B

[0019]

Figure 8

[0020]

Figure 9

[0021]

Figure 10

[0022] Throughout all the drawings, the same or similar reference numerals represent the same or similar elements.

Embodiments for Carrying Out the Invention

[0023] The principles of the present disclosure will be described with reference to some exemplary embodiments. These embodiments are described for illustrative purposes only and are intended to be helpful to those skilled in the art in understanding and implementing the present disclosure, and it should be understood that they do not imply any limitation to the scope of the present disclosure. The present disclosure described herein can be implemented in various ways other than those described below.

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

[0025] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "comprising" and variations thereof are to be construed as an open-ended term meaning "including but not limited to". The term "based on" is to be construed as "at least partially based on". The terms "some embodiments" and "one embodiment" are to be construed as "at least some embodiments". The term "another embodiment" is to be construed as "at least one other embodiment". The terms "first", "second", etc. may refer to different objects or the same object. There may be other explicit and implicit definitions included in the following content.

[0026] In some instances, 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 selection can be made from among a plurality of functional alternatives that are available, and that such a selection need not be better, smaller, higher, or more preferred than other selections.

[0027] 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 portion of a hardware processor with software, such as a digital signal processor, software, and memory that cooperate to perform various functions in a device such as a terminal device or a network device. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation but may not have software present when not required for operation. As used herein, the term circuit encompasses merely a hardware circuit or processor, or a portion of a hardware circuit or processor, and the implementation of its (or their) associated software and / or firmware.

[0028] As described above, for multi-TRP simultaneous transmission involving multi-panel reception, it has been proposed to evaluate and, if necessary, define enhancements related to beam management. However, how to solve beam outage recovery based on multi-TRP is a major issue for reliable communication.

[0029] Embodiments of the present disclosure provide solutions for solving the above problems and / or one or more other potential problems. According to this solution, in response to a beam failure being detected in a cell within a cell group by a terminal device, the terminal device may send a Beam Failure Recovery Request (BFRQ) to a network device. Here, the BFRQ includes TRP information related to the beam failure detected in the cell. For example, the TRP information may indicate at least one of the number of TRPs related to the beam failure detected in the cell, the TRP index related to the beam failure detected in the cell, whether a new candidate beam is identified at the failed TRP, and information about the new candidate beam if a new candidate beam is identified at the failed TRP. In this way, this solution can support multi-TRP based BFRQ.

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

[0031] As used herein, the term "terminal device" refers to any device having a wireless or wired communication function. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, vehicle-mounted devices for V2X communication (where X means pedestrian, vehicle, or infrastructure / network), imaging devices such as digital cameras, gaming devices, music storage and playback devices, Internet devices enabling wireless / wired Internet access and browsing, etc., but are not limited thereto. Hereinafter, for the purpose of discussion, some embodiments will be described with reference to a UE as an example of the terminal device 120.

[0032] As used in this specification, the term "network device" or "base station" (BS) refers to a device capable of providing or hosting a cell or coverage with which a terminal device can communicate. Examples of network devices include Node B (NodeB or NB), Evolved NodeB (eNodeB or eNB), next-generation NodeB (gNB), remote radio unit (RRU), radio head (RH), remote radio head (RRH), femto node, low-power nodes such as pico nodes, etc., but are not limited thereto.

[0033] In some scenarios, network 100 can support Carrier Aggregation (CA) that aggregates two or more CCs to support a wider bandwidth. For example, in FIG. 1, network device 110 may provide a plurality of serving cells including one Primary Cell (Pcell) 101 corresponding to a primary CC and at least one Secondary Cell (Scell) 102 corresponding to at least one secondary CC to terminal device 120. It should be understood that the number of network devices, terminal devices, and / or serving cells is for illustrative purposes only and does not imply any limitation to the present disclosure. Network 100 can include any suitable number of network devices, terminal devices, and / or serving cells that are compatible with the implementation of the present disclosure.

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

[0035] In one embodiment, the terminal device 120 may be connected to a first network device and a second network device (not shown in FIG. 1). One of the first network device and the second network device may be a master node, and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device may be an eNB, and the second RAT device may be a gNB. Information related to different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device 120. In one embodiment, the first information may be transmitted from the first network device to the terminal device 120, and the second information may be directly transmitted from the second network device to the terminal device 120 or transmitted via the first network device. In one embodiment, information related to the settings 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 re - settings of the terminal device set by the second network device may be directly transmitted from the second network device to the terminal device or transmitted via the first network device. The information may be transmitted via any one of radio resource control (RRC) signaling, media access control (MAC) control element (CE), or downlink control information (DCI).

[0036] In the communication network 100 shown in FIG. 1, the network device 110 can communicate data and control information to the terminal device 120, and the terminal device 120 can also communicate data and control information to the network device 110. The link from the network device 110 to the terminal device 120 is referred to as a downlink (DL), and the link from the terminal device 120 to the network device 110 is referred to as an uplink (UL).

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

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

[0039] Communication in network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Further, the communication may be performed according to any generation of communication protocol known currently or developed in the future. Examples of communication protocols include, but are not limited to, the communication protocols of the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, and the fifth generation (5G).

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

[0041] It should be understood that the TRP is also a panel, and the panel can also refer to an antenna array (having one or more antenna elements). Although some embodiments of the present disclosure are described with reference to a plurality of TRPs, for example, these embodiments are for illustrative purposes only and are helpful for those skilled in the art to understand and implement the present disclosure, and do not imply any limitation to the scope of the present disclosure. It should be understood that the present disclosure described in this specification can be implemented in various ways other than those described below.

[0042] As an enhancement of multi-beam operation mainly targeting FR2 but also applicable to FR1, the following functions are identified and defined to facilitate more efficient beam management (low latency, low overhead) for DL / UL to support higher in-cell and L1 / L2 centered inter-cell mobility, and / or more configured TCI states. i. Common beams for DL and UL data and control transmission and reception, especially for intra-band CA. ii. Unified TCI framework for DL and UL beam indication. iii. Enhancement of the signaling mechanism of the above functions to improve latency and efficiency by increasing the use of dynamic control signaling (as opposed to RRC).

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

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

[0045] In the beam indication by the unified TCI in Rel-17, DCI format 1_1 / 1_2 without DL allocation is supported, and the acknowledgement / negative acknowledgement (ACK / NACK) mechanism is used in the same way as in the case of the semi-persistent scheduling (SPS) PDSCH release by type-1 and type-2 HARQ-ACK codebooks. When the reception of the beam indication DCI is successful, the UE reports an ACK.

[0046] For the type-1 HARQ-ACK codebook, the position of the ACK information in the HARQ-ACK codebook is determined based on the virtual PDSCH indicated by the TDRA field in the beam indication DCI, based on the time domain allocation list set for the PDSCH. For the type-2 HARQ-ACK codebook, the position of the ACK information in the HARQ-ACK codebook is determined according to the same rules as for SPS release. The ACK is reported in k slots of the PUCCH after the reception of the PDCCH is completed. Here, k is indicated by the PDSCH-to-HARQ_feedback timing indicator field of the DCI format, or provided by dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCI-Format1-2-r16 when the PDSCH-to-HARQ_feedback timing indicator field does not exist in the DCI.

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

[0048] The TCI field can be used for signals of 1) the TCI state of the connected DL / UL, 2) the TCI state of DL only (in the case of separated DL / UL TCI), and 3) the TCI state of UL only (in the case of separated DL / UL TCI).

[0049] Furthermore, in Rel-16, the DCI field of the DCI format identifier, carrier indicator, bandwidth part indicator, time domain resource allocation (TDRA), downlink allocation index (if configured), transmission power control (TPC) command for the scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator (if present) is used. The remaining unused DCI fields and code points are reserved for Release 17.

[0050] It is also proposed to support the UE to report whether it supports TCI updates by DCI format 1_1 / 1_2. For a UE that supports TCI updates by DCI format 1_1 / 1_2, TCI updates must be supported by using DCI 1_1 / 1_2 with a DL allocation, and the support of the above functions for TCI updates by DCI format 1_1 / 1_2 without a DL allocation is optional for the UE.

[0051] In the DCI-based beam indication of Rel-17, the application time of the beam indication is the first slot that is at least X ms or Y symbols from the last symbol of the acknowledgment response of the connected or separated DL / UL beam indication.

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

[0053] FIG. 2 shows a signaling chart 200 according to an embodiment of the present disclosure. As shown in FIG. 2, the network device 110 may transmit settings to the terminal device 120 (210). In some embodiments, the settings may indicate that each within a cell group that provides services to the terminal device 120 is associated with at least one of the TRPs 130 connected to the network device 110. For example, the settings may be transmitted from the network device 110 to the terminal device 120 via at least one of radio resource control (RRC) signaling, media access control (MAC) control element (CE), or downlink control information (DCI). The terminal device 120 may perform beam failure detection (220). In response to a beam failure being detected in a cell within the cell group, the terminal device 120 may transmit a BFRQ to the network device 110 based on the settings. In some embodiments, the BFRQ may include TRP information related to the beam failure detected in the cell.

[0054] In some embodiments, M TRPs may be configured in a cell's bandwidth part (BWP). Here, M is a positive integer. For example, 1 ≤ M ≤ 4. In another example, M = 2. In some embodiments, each of the M TRPs may be represented by at least one of a control resource set (CORESET) pool index, CORESET group identifier (ID), CORESET group, CORESET set ID, CORESET set, sounding reference signal (SRS) resource set, SRS resource set ID, transmit configuration indicator (TCI) state, TCI state group, reference signal (RS) set ID for beam obstruction detection, RS set ID for new / candidate beam identification, spatial relation information, spatial relation information group, quasi-collinear (QCL) parameter set, RS group for beam obstruction detection, RS group for new / candidate beam identification, etc., or may be associated with at least one of them. In the example shown in FIG. 1B, M = 2. In some embodiments, the first TRP 130-1 may be the first CORESET pool index (e.g., the one with a value of 0; in another example, a CORESET without a setting for the parameter "CORESET pool index"), the ID of the first CORESET group / set / subset, the first group / set / subset of the CORESET (e.g., the CORESET with the first CORESET pool index or the ID of the first CORESET group / set / subset set; in another example, a CORESET without the parameter "CORESET pool index" or the parameter "CORESET group / set / subset ID" set), the first SRS resource set, the ID of the first SRS resource set, the first TCI state, the first group of TCI states, the ID of the first set of reference signals (RS) for beam obstruction detection, the first set of reference signals (RS) for beam obstruction detection, the ID of the first set of RSs for new / candidate beam identification, the first set of RSs for new / candidate beam identification, the first spatial relation information, the first group of spatial relation information, the first set of QCL parameters, the first group of RSs for beam obstruction detection, the first group of RSs for new / candidate beam identification, etc., or may be associated with at least one of them.The second TRP 130-2 may be represented by at least one of the following: a second CORESET pool index (e.g., value 1), an ID of a second CORESET group / set / subset, a second group / set / subset of a CORESET (e.g., a CORESET with the second CORESET pool index or the ID of the second CORESET group / set / subset set), a second SRS resource set, an ID of the second SRS resource set, a second TCI state, a second group of TCI states, an ID of a second set of reference signals (RSs) for beam failure detection, the second set of reference signals (RSs) for beam failure detection, an ID of a second set of RSs for new / candidate beam identification, the second set of RSs for new / candidate beam identification, second spatial relation information, a second group of spatial relation information, a second set of QCL parameters, a second group of RSs for beam failure detection, a second group of RSs for new / candidate beam identification, etc.

[0055] In some embodiments, a first TRP (e.g., the first TRP 130-1) and a second TRP (e.g., the second TRP 130-2) may be set in the BWP of the cell for the terminal device 120.

[0056] In some embodiments, a first procedure, a second procedure, and a third procedure may be set for the terminal device 120 for the cell and / or BWP. For example, the first procedure is a beam failure detection and recovery procedure specific to the TRP associated with the first TRP. In another example, the second procedure is a beam failure detection and recovery procedure specific to the TRP associated with the second TRP. For example, the third procedure is a cell-specific beam failure detection and recovery procedure, or a random access procedure related to the BWP and / or cell. It is necessary to design the relationship between the first procedure, the second procedure, and the third procedure. For example, when beam failure recovery is triggered for the first TRP or the second TRP, it may include whether to increment the beam failure detection counter related to the third procedure.

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

[0058] Hereinafter, the terms "TRP", "CORESET pool index", "CORESET group / set / subset ID", "CORESET group / set / subset", "SRS resource set", "SRS resource set ID", "TCI state", "group of TCI states", "ID of RS set for beam obstruction detection", "ID of RS set for new / candidate beam identification", "spatial relation information", "group of spatial relation information", "QCL parameter set", "group of RS for beam obstruction detection", and "group of RS for new / candidate beam identification" can be used interchangeably. The terms "first TRP", "first CORESET pool index", "ID of first CORESET group / set / subset", "first CORESET group / set / subset", "first SRS resource set", "ID of first SRS resource set", "first TCI state", "first TCI state out of two TCI states corresponding to a TCI code point", "first group of TCI states", "ID of first set of RS for beam obstruction detection", "first set of RS for beam obstruction detection", "ID of first set of RS for new / candidate beam identification", "first set of RS for new / candidate beam identification", "first spatial relation information", "first group of spatial relation information", "first set of QCL parameters", "first group of RS for beam obstruction detection", and "first group of RS for new / candidate beam identification" can be used interchangeably.The terms "second TRP", "second CORESET pool index", "ID of the second CORESET group / set / subset", "second CORESET group / set / subset", "second SRS resource set", "ID of the second SRS resource set", "second TCI state", "second TCI state out of two TCI states corresponding to the TCI code point", "second group of TCI states", "ID of the second set of RSs for beam obstacle detection", "second set of RSs for beam obstacle detection", "ID of the second set of RSs for new / candidate beam identification", "second set of RSs for new / candidate beam identification", "second spatial relation information", "second group of spatial relation information", "second set of QCL parameters", "second group of RSs for beam obstacle detection", and "second group of RSs for new / candidate beam identification" can be used interchangeably. The terms "PUSCH" and "PUSCH MAC CE" can be used interchangeably.

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

[0060] As shown in Figure 3A, a terminal device 120 may be configured with a set of RSs for beam obstacle detection (RS 0_0 , RS 0_1 ) and a set of RSs for new / candidate beam identification (RS 1_0 , RS 1_1 ). If there is an obstacle in RS 0_0 and RS 0_1 , the terminal device may search for a new beam based on RS 1_0 and RS 1_1 .

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

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

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

[0064] As shown in FIG. 4A, the terminal device 120 may be set with a first TRP (TRP 1) and a second TRP (TRP 2) for communicating with the network device 110. For example, a first set of RSs for beam failure detection (BFD_set_1) may be set for beam failure detection. For example, it is for the first TRP. In another example, a second set of RSs for beam failure detection (BFD_set_2) may be set for beam failure detection. For example, it is for the second TRP. For example, when a beam failure is declared based on BFD_set_1, the terminal device 120 may search for or select a new beam. For example, based on a set of RSs for new / candidate beam identification. In this case, new / candidate beam identification may be set. For example, it is associated with the first TRP.

[0065] As shown in FIG. 4B, when the value of BFI_COUNTER_1 is greater than or equal to the first maximum value (for example, beamFailureInstanceMaxCount_1), the beam failure recovery procedure is triggered. For example, it is related to the first procedure. For example, if the beam failure recovery is successfully completed in relation to the first procedure, the third procedure may be resumed, or the value of the third counter (for example, BFI_COUNTER_0) may be set to 0.

[0066] FIG. 5 shows an example according to some embodiments of the present disclosure.

[0067] As shown in FIG. 5, a first timer (Time_1) may be set in the terminal device 120 in the first procedure (beam failure procedure 1). For example, the first procedure is for the first TRP (TRP 1). The beam failure detection is based on the first set of beam failure detection reference signals (BFD_set_1). For example, when a beam failure indication 1 is received from a lower layer of the terminal device, the value of the first counter (BFI_COUNTER_1) is incremented by one. For example, when BFI_COUNTER_1 is greater than or equal to the first maximum value (beamFailureInstanceMaxCount_1), a BFR is triggered for the first procedure. For example, there is a failure in the first TRP (TRP 1). Also, in the terminal device 120, a second timer (Time_2) may be set in the second procedure (beam failure procedure 2). For example, the second procedure is for the second TRP (TRP 2). The beam failure detection is based on the second set of beam failure detection reference signals (BFD_set_2). For example, when a beam failure indication 2 is received from a lower layer of the terminal device, the value of the second counter (BFI_COUNTER_2) is incremented by one. For example, when BFI_COUNTER_2 is greater than or equal to the second maximum value (beamFailureInstanceMaxCount_2), a BFR is triggered for the second procedure. For example, there is a failure in the second TRP (TRP 2). For example, it may be difficult to cope with a situation where failures occur simultaneously or in a short period in both the first TRP and the second TRP. For example, it is necessary to design how to trigger a third procedure in order to fully utilize the cell-specific BFR.

[0068] In some embodiments, a first procedure may be set in the terminal device 120. For example, the first procedure is a beam failure detection and recovery procedure. In another example, the first procedure is a beam failure detection and recovery procedure specific to a TRP. In another example, the first procedure is related to a first TRP. In some embodiments, a second procedure may be set in the terminal device 120. For example, the second procedure is a beam failure detection and recovery procedure. In another example, the second procedure is a beam failure detection and recovery procedure specific to a TRP. In another example, the second procedure is related to a second TRP. In some embodiments, a third procedure may be set in the terminal device 120. For example, the third procedure is a beam failure detection and recovery procedure. In another example, the third procedure is a cell-specific or random access channel (RACH)-based beam failure detection and recovery procedure. In another example, the third procedure is related to a cell. For example, the first TRP and the second TRP are set in the BWP of the cell. In some embodiments, the first procedure, the second procedure, and the third procedure are executed in the same BWP and / or the same cell.

[0069] In some embodiments, the terminal device 120 may receive at least one setting. Here, the at least one setting may include at least one of a first maximum value (for example, the first maximum value may be for counting beam failure instances. In another example, the first maximum value may be beamFailureInstanceMaxCount_1), a first timer (for example, the first timer may be a beam failure detection timer. In another example, the first timer may be beamFailureDetectionTimer_1), a first set of RSs for beam failure detection, a first set of RSs for new / candidate beam identification (for example, candidateBeamRSList_1), and a first threshold value (for example, the first threshold value may be an RSRP threshold value. In another example, the first threshold value may be rsrp_Threshold_1). In some embodiments, the at least one setting may be for the first procedure.

[0070] In some embodiments, the terminal device 120 may receive at least one setting. Here, the at least one setting may include at least one of a second maximum value (for example, the second maximum value may be for counting beam failure instances; in another example, the second maximum value may be beamFailureInstanceMaxCount_2), a second timer (for example, the second timer may be a beam failure detection timer; in another example, the second timer may be beamFailureDetectionTimer_2), a second set of new / candidate beam identification reference signals (for example, candidateBeamRSList_2), and a second threshold value (for example, the second threshold value may be an RSRP threshold value; in another example, the second threshold value may be rsrp_Threshold_2). In some embodiments, the at least one setting may be for a second procedure.

[0071] In some embodiments, the terminal device 120 may receive at least one setting. Here, the at least one setting may include at least one of a third maximum value (for example, the third maximum value may be for counting beam failure instances; in another example, the third maximum value may be beamFailureInstanceMaxCount_3), a third timer (for example, the third timer may be a beam failure detection timer; in another example, the third timer may be beamFailureDetectionTimer_0), a third set of new / candidate beam identification reference signals (for example, candidateBeamRSList_3), and a third threshold value (for example, the third threshold value may be an RSRP threshold value; in another example, the third threshold value may be rsrp_Threshold_0). In some embodiments, the at least one setting may be for a third procedure.

[0072] In some embodiments, the terminal device 120 may receive a first set of RSs for beam obstacle detection and a second set of RSs for beam obstacle detection. In some embodiments, the RSs may be CSI-RSs. In some embodiments, the terminal device 120 may receive the configuration of the first set of RSs. In some embodiments, the terminal device 120 may determine the first set of RSs based on one or more RSs indicated by one or more TCI states for the first CORESET set. In some embodiments, the terminal device 120 may receive the configuration of the second set of RSs. In some embodiments, the terminal device 120 may determine the second set of RSs based on one or more RSs indicated by one or more TCI states for the second CORESET set. In some embodiments, the terminal device 120 may receive one or more configurations of the first CORESET set and the second CORESET set for the cell's BWP. In some embodiments, the first CORESET set is associated with a first TRP. In some embodiments, the second CORESET set is associated with a second TRP.

[0073] In some embodiments, the terminal device 120 may perform beam obstacle detection related to a first procedure based on the first set of RSs and a first timer. In some embodiments, the terminal device 120 may perform beam obstacle detection related to a second procedure based on the second set of RSs and a second timer.

[0074] In some embodiments, the terminal device 120 may perform a third procedure based on a first condition and / or a first parameter related to at least one of the first procedure and the second procedure.

[0075] In some embodiments, there may be a first counter for beam failure detection related to the first procedure, and the first counter may be incremented by one when there is a beam failure instance indication related to the first procedure. For example, the beam failure instance indication may be received from a lower layer in an upper layer of the terminal device 120. In another example, the beam failure instance indication may be based on a first set of RSs. In some embodiments, there may be a second counter for beam failure detection related to the first procedure, and the second counter may be incremented by one when there is a beam failure instance indication related to the second procedure. For example, the beam failure instance indication may be received from a lower layer in an upper layer of the terminal device 120. In another example, the beam failure instance indication may be based on a second set of RSs.

[0076] In some embodiments, the terminal device 120 may perform beam failure detection related to the third procedure based on a third set of RSs and a third timer.

[0077] In some embodiments, the RS may be CSI-RS. In some embodiments, the terminal device 120 may receive the configuration of the third set of RSs from the network device. In some embodiments, the terminal device 120 may determine the third set of RSs based on the first set of RSs and the second set of RSs. In some embodiments, the third set of RSs may be an integrated set of the first set of RSs and the second set of RSs. In some embodiments, the third set of RSs may include at least one RS from the first set of RSs and at least one RS from the second set of RSs. In some embodiments, at least one RS from the first set of RSs and / or at least one RS from the second set of RSs may not be included in the third set of RSs. In some embodiments, the terminal device 120 may determine the third set of RSs based on one or more RSs indicated by one or more TCI states for the first CORESET set and / or one or more RSs indicated by one or more TCI states for the second CORESET set.

[0078] In some embodiments, the third timer may be determined based on the first timer and the second timer. In some embodiments, the value of the third timer may be the larger value or the maximum value of the value of the first timer and the value of the second timer. For example, the third timer may be max(the first timer, the second timer). In another example, the value of the third timer may be max(value of the first timer, value of the second timer). In another example, when the value of the first timer is greater than or equal to the value of the second timer, the value of the third timer may be the same as the value of the first timer. In another example, when the value of the first timer is less than or equal to the value of the second timer, the value of the third timer may be the same as the value of the second timer. In another example, when the value of the first timer is greater than or equal to the value of the second timer, the third timer may be the same as the first timer. In another example, when the value of the first timer is less than or equal to the value of the second timer, the third timer may be the same as the second timer. In some embodiments, the terminal device 120 may receive the configuration of the third timer from the network device.

[0079] In some embodiments, there may be a third counter for beam obstruction detection related to the third procedure. In some embodiments, the third counter may be incremented by one when there is a beam obstruction instance indication related to the third procedure. For example, the beam obstruction instance indication may be received from a lower layer in an upper layer of the terminal device 120. In another example, the beam obstruction instance indication may be based on a third set of RSs. In some embodiments, the third counter may be incremented by one based on at least one of the first counter, the second counter, the first timer, the second timer, the third timer, and the first period.

[0080] In some embodiments, the terminal device 120 may set a third counter to 0 based on a first condition. In some embodiments, the first condition may include that beam failure recovery (BFR) related to a first procedure is triggered, BFR related to a second procedure is triggered, a first counter for beam failure detection related to the first procedure is greater than or equal to a first maximum value, a second counter for beam failure detection related to the second procedure is greater than or equal to a second maximum value, a first timer expires, a second timer expires, the first timer is reset, the second timer is reset, the first maximum value is reset, the second maximum value is reset, any one of the reference signals (RS) in a first set of RS is reset or changed or replaced or updated, any one of the RS in a second set of RS is reset or changed or replaced or updated, a transmission configuration indicator (TCI) state for any one of the RS in the first set of RS is reset or changed or updated, a TCI state for any one of the RS in the second set of RS is reset or changed or updated, BFR related to the first procedure is completed normally, BFR related to the second procedure is completed normally, the first counter for beam failure detection related to the first procedure is set to 0, the second counter for beam failure detection related to the second procedure is set to 0, the cell is deactivated, the first transmission and reception point (TRP) is deactivated, the second TRP is deactivated, all triggered BFRs related to the first procedure are cancelled, and all triggered BFRs related to the second procedure are cancelled, or at least one of the above.

[0081] In some embodiments, when a second condition is satisfied, the terminal device 120 may perform beam failure detection related to a third procedure based on a first set of RS and / or a first timer. In some embodiments, when the second condition is not satisfied, the terminal device 120 may perform beam failure detection related to the third procedure based on a third set of RS and / or a third timer.

[0082] In some embodiments, the second condition may include at least one of: the BFR associated with the second procedure is triggered; the BFR associated with the second procedure is triggered and the BFR associated with the first procedure is not triggered; the period between the triggering of the BFR associated with the second procedure and the normal completion of the BFR associated with the second procedure; the period from when the BFR associated with the second procedure is triggered until the BFR associated with the second procedure is normally completed; the period from when the BFR associated with the second procedure is triggered until the BFR associated with the first procedure or the BFR associated with the third procedure is triggered; and the period between the triggering of the BFR associated with the second procedure and the triggering of the BFR associated with the first procedure or the BFR associated with the third procedure.

[0083] In some embodiments, the value of the third timer for beam failure detection associated with the third procedure may be determined based on the first counter for beam failure detection associated with the first procedure, the second counter for beam failure detection associated with the second procedure, and the third timer.

[0084] In some embodiments, the terminal device 120 may start or resume a third timer when a beam failure instance indication related to the first procedure is indicated or received. For example, from a lower layer of the terminal device. In some embodiments, the beam failure instance indication may be based on a first set of RSs. In some embodiments, the terminal device 120 may start or resume a third timer when a first counter is incremented by one. In some embodiments, the terminal device 120 may increment a third counter by one when a beam failure instance indication related to the second procedure is indicated or received within a period before the third timer expires (or when the third timer has not expired). For example, from a lower layer of the terminal device. In some embodiments, the beam failure instance indication may be based on a second set of RSs. In some embodiments, the terminal device 120 may increment a third counter by one when a second counter is incremented by one within a period before the third timer expires (or when the third timer has not expired). In some embodiments, the third timer may be set to 0 when the third timer expires.

[0085] In some embodiments, the terminal device 120 may start or resume a third timer when a beam failure instance indication related to the second procedure is indicated or received. For example, from a lower layer of the terminal device. In some embodiments, the beam failure instance indication may be based on a second set of RSs. In some embodiments, the terminal device 120 may start or resume a third timer when a second counter is incremented by one. In some embodiments, within a period before the third timer expires (or the third timer has not expired), when a beam failure instance indication related to the first procedure is indicated or received, the terminal device 120 may increment a third counter by one. For example, from a lower layer of the terminal device. In some embodiments, the beam failure instance indication may be based on a first set of RSs. In some embodiments, within a period before the third timer expires (or the third timer has not expired), when a first counter is incremented by one, the terminal device 120 may increment a third counter by one. In some embodiments, the third timer may be set to 0 when the third timer expires.

[0086] In some embodiments, the third timer may be started or resumed based on at least one of: when a beam failure instance indication related to either the first procedure or the second procedure is indicated or received when the value of the first counter is 0 and the value of the second counter is 0; and whether the smaller value of the first timer and the second timer is set, or whether a beam failure instance indication related to one of the first procedure or the second procedure with a higher priority is indicated or received.

[0087] In some embodiments, when a BFR or random access procedure related to the third procedure is triggered or started, the terminal device 120 may cancel all triggered BFRs related to either the first procedure or the second procedure.

[0088] In some embodiments, when a BFR or a random access procedure related to the third procedure is triggered or started, the terminal device 120 may stop the first procedure and the second procedure.

[0089] In some embodiments, a BFR or a random access procedure related to the third procedure is triggered or started before a certain timing. The timing includes at least one of the fact that beam failure recovery related to the first procedure is successfully completed and the fact that beam failure recovery related to the second procedure is successfully completed.

[0090] In some embodiments, the triggering of the BFR related to the third procedure is the same as the starting of the random access procedure.

[0091] In some embodiments, when the random access procedure related to the third procedure is started, or when beam failure recovery related to the third procedure is triggered, the terminal device 120 may send a random access preamble to the network device.

[0092] In some embodiments, the terminal device 120 may determine the power for sending the random access preamble related to the third procedure based on at least one of the power parameters and the number of beam failure recovery request transmissions related to at least one of the first procedure and the second procedure.

[0093] In some embodiments, the terminal device 120 may communicate with the network device 110 based on the first TRP and the second TRP of the cell. In some embodiments, the terminal device 120 may communicate with the network device 110 based on a single TRP of the cell after a certain timing. The timing may be at least one of the fact that the BFR related to the third procedure is triggered, the fact that the random access procedure related to the third procedure is started, and the fact that the beam failure recovery related to the third procedure is successfully completed.

[0094] In some embodiments, there may be a third set of RSs for identifying new / candidate beams related to the third procedure (e.g., NBI_set_0). In some embodiments, the terminal device 120 may receive one or more configurations of the third set of RSs for identifying new / candidate beams from the network device 110. In some embodiments, the terminal device 120 may determine the third set of RSs for identifying new / candidate beams based on the first set of RSs for identifying new / candidate beams and the second set of RSs for identifying new / candidate beams. In some embodiments, the third set of RSs for identifying new / candidate beams may be an integrated set of the first set of RSs for identifying new / candidate beams and the second set of RSs for identifying new / candidate beams. For example, NBI_set_0 = candidateBeamRSList_1 ∪ candidateBeamRSList_2. In some embodiments, at least one RS in the third set of RSs for identifying new / candidate beams is different from any one of the RSs in the first set of RSs for identifying new / candidate beams and the second set of RSs for identifying new / candidate beams.

[0095] FIG. 6-6D shows an example according to some embodiments of the present disclosure.

[0096] As shown in FIG. 6A, a first timer (Time_1) may be set in the terminal device 120 in the first procedure (beam failure procedure 1). For example, the first procedure is for the first TRP (TRP 1). And the beam failure detection is based on the first set of beam failure detection reference signals (BFD_set_1). For example, when a beam failure indication 1 is received from the lower layer of the terminal device, the value of the first counter (BFI_COUNTER_1) is incremented by one. For example, when BFI_COUNTER_1 is greater than or equal to the first maximum value (beamFailureInstanceMaxCount_1), a BFR is triggered for the first procedure. For example, there is a failure in the first TRP (TRP 1). Also, in the terminal device 120, a second timer (Time_2) may be set in the second procedure (beam failure procedure 2). For example, the second procedure is for the second TRP (TRP 2). And the beam failure detection is based on the second set of beam failure detection reference signals (BFD_set_2). For example, when a beam failure indication 2 is received from the lower layer of the terminal device, the value of the second counter (BFI_COUNTER_2) is incremented by one. For example, when BFI_COUNTER_2 is greater than or equal to the second maximum value (beamFailureInstanceMaxCount_2), a BFR is triggered for the second procedure. For example, there is a failure in the second TRP (TRP 2). For example, in the terminal device 120, a third timer (Time_0) may be set in the third procedure (beam failure procedure 0). For example, the third procedure is for the cell, and the first TRP and the second TRP are set in the cell. For example, when a beam failure indication 0 is received from the lower layer of the terminal device, the value of the third counter (BFI_COUNTER_0) is incremented by one. For example, when BFI_COUNTER_0 is greater than or equal to the third maximum value (beamFailureInstanceMaxCount_0), a BFR is triggered for the third procedure. For example, there is a failure in the cell.

[0097] In some embodiments, the set of RSs for beam obstacle detection and / or the timer for beam obstacle detection associated with the third procedure may depend on the first condition in the first procedure and / or the second procedure. In some embodiments, the first condition may be at least one of: the BFR is triggered in the first procedure; the BFR is triggered in the second procedure; it is before the beam obstacle recovery is successfully completed in the first procedure; it is before the beam obstacle recovery is successfully completed in the second procedure.

[0098] In some embodiments, when the first condition is satisfied (for example, the BFR is triggered in the first procedure and / or it is before the beam obstacle recovery is successfully completed in the first procedure), the beam obstacle detection associated with the third procedure may be based on the second set of RSs for beam obstacle detection and / or the second timer. For example, when the first condition is satisfied and a beam obstacle instance indication is indicated or received from a lower layer of the terminal device, the terminal device may start or restart the second timer.

[0099] In some embodiments, when the first condition is not satisfied (for example, the BFR is not triggered in the first procedure and / or the second procedure, and / or the beam obstacle recovery is successfully completed in the first procedure and / or the second procedure), the beam obstacle detection associated with the third procedure may be based on the third set of RSs for beam obstacle detection and / or the third timer. For example, when the first condition is not satisfied and a beam obstacle instance indication is indicated or received from a lower layer of the terminal device, the terminal device may start or restart the third timer.

[0100] As shown in FIG. 6B, a first timer (Time_1) may be set in the terminal device 120 in the first procedure (beam failure procedure 1). For example, the first procedure is for the first TRP (TRP 1). And the beam failure detection is based on the first set of beam failure detection reference signals (BFD_set_1). For example, when a beam failure indication 1 is received from a lower layer of the terminal device, the value of the first counter (BFI_COUNTER_1) is incremented by one. For example, when BFI_COUNTER_1 is greater than or equal to the first maximum value (beamFailureInstanceMaxCount_1), a BFR is triggered for the first procedure. For example, there is a failure in the first TRP (TRP 1). For example, a second timer (Time_2) may be set in the terminal device 120 in the second procedure (beam failure procedure 2). For example, the second procedure is for the second TRP (TRP 2). And the beam failure detection is based on the second set of beam failure detection reference signals (BFD_set_2). For example, when a beam failure indication 2 is received from a lower layer of the terminal device, the value of the second counter (BFI_COUNTER_2) is incremented by one. For example, when BFI_COUNTER_2 is greater than or equal to the second maximum value (beamFailureInstanceMaxCount_2), a BFR is triggered for the second procedure. For example, there is a failure in the second TRP (TRP 2). For example, a third timer (Time_0) may be set in the terminal device 120 in the third procedure (beam failure procedure 0). For example, the third procedure is for the cell, and the first TRP and the second TRP are set in the cell. For example, when BFI_COUNTER_1 is greater than or equal to beamFailureInstanceMaxCount_1, or when there is a failure in the first TRP, the beam failure detection in the third procedure may be based on the second set of beam failure detection reference signals (BFD_set_2). In another example, when BFI_COUNTER_1 is less than beamFailureInstanceMaxCount_1, or when there is no failure in the first TRP, the beam failure detection in the third procedure may be based on the third set of beam failure detection reference signals (BFD_set_0).In another example, when a beam failure indication 0 is received from the lower layer of the terminal device, the value of the third counter (BFI_COUNTER_0) is incremented by one. In another example, when BFI_COUNTER_1 is greater than or equal to beamFailureInstanceMaxCount_1, or when there is a failure in the first TRP, when a beam failure indication 0 is received from the lower layer of the terminal device, the terminal device may start or restart the second timer (Timer_2). In another example, when BFI_COUNTER_1 is less than beamFailureInstanceMaxCount_1, or when there is no failure in the first TRP, when a beam failure indication 0 is received from the lower layer of the terminal device, the terminal device may start or restart the third timer (Timer_0).

[0101] In some embodiments, at least one of the following terminal device variables may be used for the beam failure detection procedure. - BFI_COUNTER_0 (per serving cell): A counter for beam failure instance indication with an initial value set to 0 - BFI_COUNTER_1 (when a TRP-specific BFR is set and for TRP 1 of the serving cell): A counter for beam failure instance indication with an initial value set to 0 - BFI_COUNTER_2 (when a TRP-specific BFR is set and for TRP 2 of the serving cell): A counter for beam failure instance indication with an initial value set to 0

[0102] In some embodiments, the MAC entity of the terminal device is set for beam failure detection per serving cell, and a TRP-specific BFR and a cell-specific BFR must be set. (For example, related to the first procedure) 1> When a beam failure instance indication detected based on the first set of beam failure detection reference signals is received from the lower layer 2> Start or restart beamFailureDetectionTimer_1 2> Increment BFI_COUNTER_1 by one 2> When BFI_COUNTER_1 >= beamFailureInstanceMaxCount_1 3> Trigger BFR for the first TRP of this serving cell 1> When beamFailureDetectionTimer_1 expires, or 1> Any of beamFailureDetectionTimer_1, beamFailureInstanceMaxCount_1, or the beam failure detection reference signal is reset (e.g., by a higher layer or a lower layer or a physical layer) and is associated with the first TRP of this serving cell 2> Set BFI_COUNTER_1 to 0 2> Set BFI_COUNTER_0 to 0 1> When receiving a PDCCH addressed to C-RNTI indicating an uplink grant for a new transmission for the HARQ process used for transmitting a BFR MAC CE or a Truncated BFR MAC CE containing beam failure recovery information of the first TRP of this serving cell 2> Set BFI_COUNTER_1 to 0 2> Set BFI_COUNTER_0 to 0 2> Consider that the beam failure recovery procedure of the first TRP is successfully completed and cancel all triggered BFRs related to the first TRP of this serving cell (e.g., related to the second procedure) 1> When receiving a beam failure instance indication detected based on the second set of beam failure detection RSs from a lower layer 2> Start or resume beamFailureDetectionTimer_2 2> Increment BFI_COUNTER_2 by 1 2> When BFI_COUNTER_2 >= beamFailureInstanceMaxCount_2 3> Trigger BFR for the second TRP of this serving cell 1> If beamFailureDetectionTimer_2 expires, or 1> For the second TRP of this serving cell, if any of beamFailureDetectionTimer_2, beamFailureInstanceMaxCount_2, or the reference signal for beam failure detection is reset (e.g., by a higher layer or a lower layer or the physical layer) 2> Set BFI_COUNTER_2 to 0 2> Set BFI_COUNTER_0 to 0 1> If a PDCCH addressed to C-RNTI indicating an uplink grant for a new transmission is received for the HARQ process used for transmitting a BFR MAC CE or Truncated BFR MAC CE containing beam failure recovery information for the second TRP of this serving cell 2> Set BFI_COUNTER_2 to 0 2> Set BFI_COUNTER_0 to 0 2> Consider that the beam failure recovery procedure for the second TRP has completed successfully, and cancel all triggered BFRs related to the second TRP of this serving cell (e.g., related to the third procedure) 1> If a beam failure instance indication detected for the cell is received from the lower layer 2> Start or resume beamFailureDetectionTimer_0 2> Increment BFI_COUNTER_0 by 1 2> If BFI_COUNTER_0 >= beamFailureInstanceMaxCount_0 3> If the serving cell is an SCell 4> Trigger a BFR for this serving cell 4> Stop the P1 and P2 procedures if set 3> Otherwise 4> Start a random access procedure in the SpCell 4> Stop the P1 and P2 procedures if set 1> If beamFailureDetectionTimer_0 expires, or 1> For this serving cell, if any of beamFailureDetectionTimer_0, beamFailureInstanceMaxCount_0, or the reference signal for beam failure detection is reset (e.g., by a higher layer or a lower layer or the physical layer) 2> Set BFI_COUNTER_0 to 0 1> If the serving cell is a SpCell and the random access procedure started for SpCell beam failure recovery has completed successfully 2> Set BFI_COUNTER_0 to 0 2> If set, stop beamFailureRecoveryTimer_0 2> Consider the beam failure recovery procedure to have completed successfully 1> Otherwise, if the serving cell is an SCell and a PDCCH addressed to the C-RNTI indicating an uplink grant for a new transmission is received for the HARQ process used for transmitting a BFR MAC CE or Truncated BFR MAC CE containing the beam failure recovery information of this serving cell, or 1> If the SCell is deactivated as defined in Section 5.9 2> Set BFI_COUNTER_0 to 0 2> Consider the beam failure recovery procedure to have completed successfully and cancel all triggered BFRs (including P1 and P2) for this serving cell

[0103] In some embodiments, all or a subset of the steps as disclosed in Embodiment

[0081] may be applied to at least one of the first procedure, the second procedure, and the third procedure.

[0104] As shown in FIG. 6C, a first timer (Time_1) may be set in the terminal device 120 in the first procedure (beam failure procedure 1). For example, the first procedure is for the first TRP (TRP 1). And the beam failure detection is based on the first set of beam failure detection reference signals (BFD_set_1). For example, when a beam failure indication 1 is received from the lower layer of the terminal device, the value of the first counter (BFI_COUNTER_1) is incremented by one. For example, when BFI_COUNTER_1 is greater than or equal to the first maximum value (beamFailureInstanceMaxCount_1), a BFR is triggered for the first procedure. For example, there is a failure in the first TRP (TRP 1). For example, a third timer (Time_0) may be set in the terminal device 120 in the third procedure (beam failure procedure 0). For example, the third procedure is for a cell, and the first TRP and the second TRP are set in the cell. For example, when BFI_COUNTER_1 is greater than or equal to beamFailureInstanceMaxCount_1, or when there is a failure in the first TRP, a beam failure recovery procedure 1 is executed. In another example, when the beam failure recovery related to the first procedure is completed normally, the value of BFI_COUNTER_0 may be set to 0 related to the third procedure.

[0105] In some embodiments, when a BFR is triggered in relation to either one of the first procedure or the second procedure, if within the first period, a BFR or a random access procedure is triggered in relation to the third procedure, the first procedure or the second procedure is cancelled, or the value of BFI_COUNTER_0 is set to 0, or the value of BFI_COUNTER_1 is set to 0. For example, the terminal device may perform a beam failure recovery related to the third procedure. For example, the terminal device may select a new candidate RS from the third set of new / candidate beam identification reference signals.

[0106] In some embodiments, when the BFR is triggered in relation to either the first procedure or the second procedure, within the first period, if the value of BFI_COUNTER_0 is greater than or equal to the third maximum value, a BFR or a random access procedure may be triggered in relation to the third procedure. In some embodiments, the first procedure or the second procedure is cancelled, or the value of BFI_COUNTER_1 is set to 0, or the value of BFI_COUNTER_2 is set to 0. For example, the terminal device may perform beam failure recovery related to the third procedure. For example, the terminal device may select a new candidate RS from the third set of new / candidate beam identification RSs. In some embodiments, within the first period, if the BFR or the random access procedure is not triggered in relation to the third procedure, or if the value of BFI_COUNTER_0 is less than the third maximum value, the value of BFI_COUNTER_0 is set to 0.

[0107] In some embodiments, when the BFR is triggered in relation to either the first procedure or the second procedure, the terminal device may start or resume the third timer, and if the BFR or the random access procedure is triggered in relation to the third procedure before the third timer expires, the first procedure or the second procedure is cancelled, or the value of BFI_COUNTER_1 is set to 0, or the value of BFI_COUNTER_2 is set to 0. For example, the terminal device may perform beam failure recovery related to the third procedure. For example, the terminal device may select a new candidate RS from the third set of new / candidate beam identification RSs.

[0108] In some embodiments, the terminal device 120 may receive the setting of the first period from the network device 110. In some embodiments, the first period may be between the timing when the BFR is triggered in relation to either the first procedure or the second procedure and the timing when the beam failure recovery procedure is successfully completed in relation to either the first procedure or the second procedure. In some embodiments, the first period may be from the timing when the BFR is triggered in relation to either the first procedure or the second procedure to the timing when the beam failure recovery procedure is successfully completed in relation to either the first procedure or the second procedure.

[0109] In some embodiments, when the BFR is triggered in relation to either the first procedure or the second procedure, the terminal device may start or resume the third timer. Before the third timer expires, if the value of BFI_COUNTER_0 is greater than or equal to the third maximum value, a BFR or a random access procedure may be triggered in relation to the third procedure. In some embodiments, either the first procedure or the second procedure is cancelled, or the value of BFI_COUNTER_0 is set to 0, or the value of BFI_COUNTER_1 is set to 0. For example, the terminal device may perform beam failure recovery related to the third procedure. For example, the terminal device may select a new candidate RS from the third set of the new / candidate beam identification RS. In some embodiments, if the third timer expires and the BFR or the random access procedure is not triggered in relation to the third procedure, or if the value of BFI_COUNTER_0 is less than the third maximum value, the value of BFI_COUNTER_0 is set to 0. In some embodiments, before the third timer expires, if the BFR or the random access procedure is not triggered in relation to the third procedure, or if the value of BFI_COUNTER_0 is less than the third maximum value, the value of BFI_COUNTER_0 is set to 0.

[0110] As shown in FIG. 6D, a first timer (Time_1) may be set in the terminal device 120 in the first procedure (beam failure procedure 1). For example, the first procedure is for the first TRP (TRP 1). And the beam failure detection is based on the first set of beam failure detection reference signals (BFD_set_1). For example, when a beam failure indication 1 is received from the lower layer of the terminal device, the value of the first counter (BFI_COUNTER_1) increases by one. For example, when BFI_COUNTER_1 is greater than or equal to the first maximum value (beamFailureInstanceMaxCount_1), a BFR is triggered for the first procedure. For example, there is a failure in the first TRP (TRP 1). For example, a second timer (Time_2) may be set in the terminal device 120 in the second procedure (beam failure procedure 2). For example, the second procedure is for the second TRP (TRP 2). And the beam failure detection is based on the second set of beam failure detection reference signals (BFD_set_2). For example, when a beam failure indication 2 is received from the lower layer of the terminal device, the value of the second counter (BFI_COUNTER_2) increases by one. For example, when BFI_COUNTER_2 is greater than or equal to the second maximum value (beamFailureInstanceMaxCount_2), a BFR is triggered for the second procedure. For example, there is a failure in the second TRP (TRP 2). For example, a third timer (Time_0) may be set in the terminal device 120 in the third procedure (beam failure procedure 0). For example, the third procedure is for the cell, and the first TRP and the second TRP are set in the cell. For example, when a beam failure indication 1 related to the first procedure is received from the lower layer of the terminal device, the value of the first counter (BFI_COUNTER_1) increases by one, and the terminal device 120 may start or restart the third timer (Timer_0). For example, if a beam failure instance indication 2 related to the second procedure is shown or received within the period before the third timer (Timer_0) expires, the value of BFI_COUNTER_0 increases by one. In another example, when the third timer (Timer_0) expires, the value of BFI_COUNTER_0 is set to 0.

[0111] In some embodiments, the first timer associated with the first procedure may be shorter than or equal to the second timer associated with the second procedure. In some embodiments, the terminal device may receive one or more settings of the priority of at least one of the first procedure and the second procedure. In some embodiments, a higher priority may be set for the first procedure than for the second procedure. In some embodiments, a lower priority may be set for the first procedure than for the second procedure.

[0112] In some embodiments, when the BFR is triggered in relation to the second procedure, or when the value of the second counter is greater than or equal to the second maximum value associated with the second procedure, the terminal device may execute a BFR procedure specific to the TRP. For example, the BFR is not triggered in relation to the first procedure. In some embodiments, when the BFR is triggered in relation to the first procedure, or when the value of the first counter is greater than or equal to the first maximum value associated with the first procedure, the terminal device may execute a random access procedure or a BFR procedure specific to the cell. In some embodiments, the first procedure and the second procedure for the BWP of the cell may be set in the terminal device. For example, the first procedure may be a BFR procedure specific to the cell or a procedure based on random access. For example, the second procedure may be a BFR procedure specific to the TRP. In some embodiments, a higher priority may be set for the first procedure than for the second procedure.

[0113] In some embodiments, when the value of the first counter is greater than or equal to the first maximum value associated with the first procedure, the terminal device may start executing the second procedure. For example, within a period, when the value of the second counter is greater than or equal to the second maximum value associated with the second procedure, a random access procedure may be started, or a cell-specific BFR associated with the third procedure may be triggered, otherwise, a BFR associated with the first procedure may be triggered.

[0114] In some embodiments, when the value of the first counter is greater than or equal to the first maximum value associated with the first procedure, the terminal device may start or resume the third timer, the value of the second counter may be set to 0, and the beam obstruction detection may be based on the second set of beam obstruction detection reference signals (RS) associated with the second procedure. In some embodiments, before the third timer expires, or during a period before the third timer expires, if the value of the second counter is greater than or equal to the second maximum value, the terminal device may start a random access procedure or a cell-specific beam failure recovery (BFR) procedure; otherwise, the terminal device may trigger the BFR associated with the first procedure.

[0115] In some embodiments, the new candidate beam / RS for the random access procedure or the cell-specific BFR procedure is the same as the new candidate beam / RS associated with the first procedure. In some embodiments, the new candidate beam / RS for the random access procedure or the cell-specific BFR procedure is selected based on the first set of new / candidate beam identification RS.

[0116] In some embodiments, when a BFR is triggered or a random access procedure is triggered in relation to the third procedure, then, thereafter, multi-TRP transmission (based on the first TRP and the second TRP) falls back to single-TRP transmission between the network device and the terminal device. In some embodiments, when a BFR is triggered or a random access procedure is triggered in relation to the third procedure, then, thereafter, the communication between the network device and the terminal device is changed from being based on the first TRP and the second TRP to being based on a single TRP.

[0117] In some embodiments, the power for transmitting the random access preamble associated with the third procedure may be determined based on one or more power parameters and / or the number of beam failure recovery request (BFRQ) transmissions associated with at least one of the first procedure and the second procedure.

[0118] In some embodiments, the initial power for transmitting the random access preamble related to the third procedure may be determined based on the maximum one of the reference power for the scheduling request (SR) or beam failure request (BFR) or BFRQ transmission in the first and second procedures.

[0119] In some embodiments, there may be a parameter (e.g., BfrqTrans_COUNTER_1) for counting the number of BFRQ transmissions within the period related to the first procedure. In some embodiments, BfrqTrans_COUNTER_1 may be a non - negative integer. For example, 0 <= BfrqTrans_COUNTER_1 <= BfrqTrans_MaxCount_1. For example, BfrqTrans_MaxCount_1 is a positive integer. In another example, 1 <= BfrqTrans_MaxCount_1 <= 100. In another example, BfrqTrans_MaxCount_1 may be set by the network device.

[0120] In some embodiments, there may be a parameter (e.g., BfrqTrans_COUNTER_2) for counting the number of BFRQ transmissions within the period related to the second procedure. In some embodiments, BfrqTrans_COUNTER_2 may be a non - negative integer. For example, 0 <= BfrqTrans_COUNTER_2 <= BfrqTrans_MaxCount_2. For example, BfrqTrans_MaxCount_2 is a positive integer. In another example, 1 <= BfrqTrans_MaxCount_2 <= 100. In another example, BfrqTrans_MaxCount_2 may be set by the network device.

[0121] In some embodiments, the period may be between the timing when the BFR is triggered in the first procedure or the second procedure and the timing when the beam failure recovery procedure is successfully completed in the first procedure or the second procedure. In some embodiments, the period may be between the timing when the BFR is triggered in the first procedure or the second procedure and the timing when the BFR is triggered in relation to the third procedure or the random access procedure is started. For example, the timing when the BFR is triggered in relation to the third procedure or the random access procedure is started is neither earlier nor later than the timing when the beam failure recovery is successfully completed in the first procedure or the second procedure. In some embodiments, the period may be between the first BFRQ transmission and the BFRQ transmission having an index of BfrqTrans_COUNTER_1 or BfrqTrans_COUNTER_2 related to the first procedure or the second procedure.

[0122] In some embodiments, the power of the transmission of the random access preamble related to the third procedure may be determined based on BfrqTrans_COUNTER_1 and / or BfrqTrans_COUNTER_2.

[0123] In some embodiments, when the random access procedure related to the third procedure is triggered or started, the value of PREAMBLE_POWER_RAMPING_COUNTER may be set to the maximum value of BfrqTrans_COUNTER_1 and BfrqTrans_COUNTER_2. For example, PREAMBLE_POWER_RAMPING_COUNTER = max(BfrqTrans_COUNTER_1, BfrqTrans_COUNTER_2) or max(BfrqTrans_MaxCount_1, BfrqTrans_MaxCount_2). For example, this is the case for the transmission of the first random access preamble.

[0124] In some embodiments, when the random access procedure related to the third procedure is triggered or started, PREAMBLE_RECIEVED_TARGET_POWER may be determined based on (PREAMBLE_POWER_RAMPING_COUNTER + max(BfrqTrans_COUNTER_1, BfrqTrans_COUNTER_2) - 1) × PREAMBLE_POWER_RAMPING_STEP or (PREAMBLE_POWER_RAMPING_COUNTER + max(BfrqTrans_MaxCount_1, BfrqTrans_MaxCount_2) - 1) × PREAMBLE_POWER_RAMPING_STEP. For example, in the case of transmitting the first random access preamble.

[0125] In some embodiments, the power for transmitting the random access preamble related to the third procedure may be determined based on a power offset (e.g., POWER_OFFSET_BFRQ), and the power offset may be determined based on BFRQ transmission in the first procedure and / or the second procedure.

[0126] In some embodiments, when the random access procedure related to the third procedure is triggered or started, PREAMBLE_RECEIVED_TARGET_POWER may be determined based on preambleReceivedTargetPower + POWER_OFFSET_BFRQ. For example, in the case of transmitting the first random access preamble.

[0127] In some embodiments, the power offset may be determined based on the offset between the power for the first BFRQ transmission and the maximum value of the power for BFRQ transmission within the period related to the first procedure and / or the second procedure.

[0128] In some embodiments, the power offset may be determined based on the offset between the power by transmission power control (TPC) for the first BFRQ transmission and the maximum / peak value of (accumulated) TPC within the period related to the first procedure and / or the second procedure. For example, the power offset may be max(TPC_1, TPC_2) or max(max(TPC_1, TPC_2), 0). For example, TPC_1 may be related to the first procedure. In another example, TPC_2 may be related to the second procedure.

[0129] In some embodiments, the first procedure, the second procedure, and the third procedure may be set together for the cell. In some embodiments, the first procedure and the second procedure may be set together for the BWP of the cell. In some embodiments, the first procedure / second procedure and the third procedure may not be set together for the same BWP of the cell. For example, the first procedure and the second procedure may be set for the first BWP. For example, the first TRP and the second TRP are set for the first BWP. In another example, the third procedure may not be set for the first BWP. In another example, the third procedure may be set for the second BWP. For example, a single TRP may be set for the second BWP.

[0130] In some embodiments, when the active BWP is changed or switched from the first BWP to the second BWP, the first procedure and the second procedure may be stopped or canceled, and the third procedure may be executed. In some embodiments, the beam blockage detection related to the third procedure may be based on the first set of RSs and / or the first timer for beam blockage detection. In some embodiments, when the active BWP is changed or switched from the first BWP to the second BWP, the first procedure may be stopped or canceled, and the third procedure and the second procedure may be executed. Also, when a BFR is triggered in relation to the second procedure, a BFRQ is transmitted, and PDCCH monitoring based on the beam / RS related to the second procedure is not performed.

[0131] In some embodiments, when the active BWP is changed or switched from the second BWP to the first BWP, the third procedure may be stopped or canceled, and the first and second procedures may be executed. In some embodiments, when the active BWP is changed or switched from the second BWP to the first BWP, the execution of the first and second procedures may be started.

[0132] In some embodiments, the terminal device 120 may receive the detected downlink control information (DCI), and the detected DCI may indicate BWP switching and TCI state. Then, the detected DCI may schedule PDSCH transmission. After BWP switching, the terminal device may apply the indicated TCI state to the scheduled PDSCH.

[0133] In some embodiments, the terminal device may receive the first detected DCI in the first BWP, where the first detected DCI may indicate the second BWP. In some embodiments, the terminal device may receive an indication of a combination of the first TCI state and the second TCI state. In some embodiments, the terminal device may discard the second TCI state for communication between the terminal device and the network device based on the configuration of the second BWP. For example, the communication may be the reception of a set of CORESET, PDSCH, and RS from the network device. In another example, the communication may be the transmission of a set of PUCCH, PUSCH, and RS to the network device. In some embodiments, the indication of the combination may be received in the first detected DCI or the second detected DCI. For example, the second detected DCI may be received after or subsequent to the first detected DCI.

[0134] In some embodiments, the terminal device may receive the first CORESET set in the first TCI state after a certain timing in the second BWP. Then, the terminal device may transmit the first PUCCH set in the first TCI state after the timing in the first uplink BWP. Further, the terminal device may transmit the second PUCCH set in the second TCI state after the timing in the first uplink BWP. For example, the second TCI state may not be applied to downlink reception in the second BWP. For example, the second BWP is a downlink BWP.

[0135] In some embodiments, the terminal device may receive the configuration of the first CORESET set for the second BWP. Here, the second BWP is a downlink BWP. In some embodiments, the terminal device may receive one or more configurations of the first PUCCH set and the second PUCCH set for the first uplink BWP.

[0136] In some embodiments, the terminal device may receive the second CORESET set in the first TCI state after a certain timing in the first BWP. Then, the terminal device may receive the third CORESET set in the second TCI state after the timing. Further, the terminal device may transmit the third PUCCH set in the first TCI state after the timing in the second BWP. For example, the second TCI state may not be applied to uplink transmission in the second BWP. Here, the second BWP may be an uplink BWP.

[0137] In some embodiments, the terminal device 120 may receive the configuration of the third PUCCH set for the second BWP. Here, the second BWP is an uplink BWP.

[0138] In some embodiments, the terminal device may receive one or more settings of the first BWP and the second BWP of the cell. In some embodiments, the terminal device may receive the setting of the first uplink BWP of the cell.

[0139] In some embodiments, the terminal device may receive an activation command. Here, the activation command is used to map a set of combinations of one or two TCI states to a code point set. Here, the set includes a combination of a first TCI state and a second TCI state.

[0140] In some embodiments, a first downlink BWP may be set for the terminal device, and two TRPs may be set for the first downlink BWP. For example, a first TRP and a second TRP. In some embodiments, a first uplink BWP may be set for the terminal device. Here, two TRPs may be set for the first uplink BWP. For example, a first TRP and a second TRP. In some embodiments, a first subset of the CORESET and a second subset of the CORESET in the first downlink BWP may be set for the terminal device. For example, a first TCI state (e.g., a first connected TCI) may be applied to the first subset of the CORESET. In another example, a second TCI state (e.g., a second connected TCI) may be applied to the second subset of the CORESET. In some embodiments, a third subset of the CORESET in the second downlink BWP may be set for the terminal device. For example, a single TRP may be set for the second downlink BWP. For example, a first TRP. In another example, a third TCI state (e.g., a third connected TCI) may be indicated or applied to the third subset of the CORESET. For example, the third subset of the CORESET may be the same as either the first subset of the CORESET or the second subset of the CORESET.

[0141] In some embodiments, the terminal device may receive the first detected DCI, where the first detected DCI may indicate a downlink BWP switch. For example, it is a switch from the first downlink BWP to the second downlink BWP. In some embodiments, the terminal device may receive an indication of a combination of the third TCI state and the fourth TCI state. In some embodiments, only one of the third TCI state and the fourth TCI state associated with the third subset of CORESET is applied to downlink reception and / or uplink transmission. For example, it is applied to the third subset of CORESET.

[0142] In some embodiments, the third TCI state is applied to downlink reception in the second downlink BWP (e.g., applied to the third subset of CORESET), and the fourth TCI state is not applied to downlink reception in the second downlink BWP (e.g., not applied to either CORESET or PDSCH). In some embodiments, both the third TCI state and the fourth TCI state may be applied to uplink transmission in the first uplink BWP.

[0143] FIGS. 7A - 7B show examples according to some embodiments of the present disclosure.

[0144] As shown in FIG. 7A, a first downlink BWP (DL BWP 1) and an uplink BWP (UL BWP 1) may be configured for the terminal device 120. For example, a second downlink BWP (DL BWP 2) may be configured for the terminal device 120. For example, two TRPs (TRP 1 and TRP 2) may be configured for DL BWP 1 and UL BWP 1. For example, one TRP (TRP 1) may be configured for the second downlink BWP. For example, connection TCI 1 may be applied to the uplink communication and downlink communication between the terminal device and the network device by TRP 1. In another example, connection TCI 2 may be applied to the uplink communication and downlink communication between the terminal device and the network device by TRP 2. For example, the terminal device may receive a downlink BWP switch (from DL BWP1 to DL BWP2). For example, the terminal device may receive TCI code points corresponding to connection TCI 3 and connection TCI 4. For example, after the BWP switch, connection TCI 4 may be ignored or discarded for the uplink communication and downlink communication between the terminal device and the network device. For example, based on TRP 2.

[0145] As shown in FIG. 7B, a first downlink BWP (DL BWP 1) and an uplink BWP (UL BWP 1) may be configured for the terminal device 120. For example, a second downlink BWP (DL BWP 2) may be configured for the terminal device 120. For example, two TRPs (TRP 1 and TRP 2) may be configured for DL BWP 1 and UL BWP 1. For example, one TRP (TRP 1) may be configured for the second downlink BWP. For example, connection TCI 1 may be applied to the uplink communication and downlink communication between the terminal device and the network device by TRP 1. In another example, connection TCI 2 may be applied to the uplink communication and downlink communication between the terminal device and the network device by TRP 2. For example, the terminal device may receive a downlink BWP switch (from DL BWP1 to DL BWP2). For example, the terminal device may receive TCI code points corresponding to connection TCI 3 and connection TCI 4. For example, after the BWP switch, connection TCI 4 may be ignored or discarded for the downlink communication between the terminal device and the network device. For example, based on TRP 2. In another example, after the BWP switch, connection TCI 4 may be applied to the uplink communication between the terminal device and the network device. For example, based on TRP 2.

[0146] In some embodiments, the timing may be beam application timing. For example, the timing may be in the first slot or the first sub-slot that is at least X ms or Y symbols from the last symbol of the confirmation of the first detected DCI or the second detected DCI.

[0147] In some embodiments, the network device 110 may transmit, in the first BWP, a first DCI indicating the second BWP to the terminal device 120 and transmit an indication of a combination of the first TCI state and the second TCI state. The network device 110 may discard the second TCI state for the communication between the network device 110 and the terminal device 120 based on the configuration of the second BWP.

[0148] In some embodiments, the network device 110 may transmit a combination instruction in the first DCI or the second DCI. For example, the second DCI is transmitted after or subsequent to the first DCI.

[0149] In some embodiments, in the second BWP, after a certain timing, the network device 110 transmits a first control resource set (CORESET) set in the first TCI state, and in the first uplink BWP, after the timing, receives a first physical uplink control channel (PUCCH) set in the first TCI state, and in the first uplink BWP, after the timing, may receive a second PUCCH set in the second TCI state. The second TCI state is not applicable to downlink transmissions in the second BWP which is a downlink BWP.

[0150] In some embodiments, the network device 110 may transmit a setting of a first CORESET set for the second BWP which is a downlink BWP, and may transmit one or more settings of a first PUCCH set and a second PUCCH set for the first uplink BWP.

[0151] In some embodiments, the network device 110 may transmit one or more settings of a second CORESET set and a third CORESET set for the first BWP which is a downlink BWP.

[0152] In some embodiments, in the first BWP, after the timing, the network device 110 transmits a second CORESET set in the first TCI state, and in the first BWP, after the timing, transmits a third CORESET set in the second TCI state, and in the second BWP, after the timing, may receive a third physical uplink control channel (PUCCH) set in the first TCI state. The second TCI state is not applicable to uplink receptions in the second BWP which is an uplink BWP.

[0153] In some embodiments, the network device 110 may transmit a configuration of a third PUCCH set for a second BWP that is an uplink BWP.

[0154] In some embodiments, the network device 110 may transmit one or more configurations of a first BWP and a second BWP of a cell.

[0155] In some embodiments, the network device 110 may transmit a configuration of a first uplink BWP of a cell.

[0156] In some embodiments, the network device 110 may transmit an activation command for mapping a set of combinations of one or two TCI states to a code point set. Here, the set includes a combination of a first TCI state and a second TCI state.

[0157] FIG. 8 shows a flowchart of an exemplary method 800 according to some embodiments of the present disclosure. For example, the method 800 can be implemented by the terminal device 120 as shown in FIG. 1.

[0158] In block 810, the terminal device 120 receives a configuration from a network device (e.g., the network device 110 as shown in FIG. 1). Here, the configuration indicates that each in a cell group that provides services to the terminal device is associated with at least one of a plurality of TRPs (e.g., TRP130-1, 130-2 as shown in FIG. 1) connected to the network device.

[0159] In block 820, in response to detecting a beam failure in a cell within the cell group, the terminal device 120 transmits a beam failure recovery request to the network device. Here, the beam failure recovery request includes TRP information related to the beam failure detected in the cell.

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

[0161] In some embodiments, the plurality of TRPs may include a first TRP and a second TRP, the cell group may include a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, a first set of RSs for beam obstacle detection and a first set of RSs for new / candidate beam identification may be set in the first subset of cells, and a second set of RSs for beam obstacle detection and a second set of RSs for new / candidate beam identification may be set in the second subset of cells.

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

[0163] In some embodiments, a cell may be associated with a plurality of TRPs, and the TRP information may indicate one of the plurality of TRPs related to a beam obstacle detected in the cell.

[0164] In some embodiments, the TRP information may include an indication of a TRP index common to all cells indicated in the beam obstacle recovery request.

[0165] In some embodiments, the TRP information may include an indication of the respective TRP index of each cell indicated by the beam failure recovery request.

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

[0167] In some embodiments, a cell may be associated with a plurality of TRPs, and the TRP information may include first information indicating the number of TRPs associated with the beam failure detected in the cell and second information indicating an RS index for a new beam identified at one of the plurality of TRPs. Here, the RS index indicates the index of the one TRP.

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

[0169] In block 910, network device 110 transmits a configuration to a terminal device (e.g., terminal device 120 as shown in FIG. 1). Here, the configuration indicates that each in a cell group that provides a service to the terminal device is associated with at least one of a plurality of TRPs (e.g., TRP130-1, 130-2 as shown in FIG. 1) connected to network device 110.

[0170] In block 920, in response to detecting a beam failure in a cell within the cell group, network device 110 receives a beam failure recovery request from the terminal device. Here, the beam failure recovery request includes TRP information associated with the beam failure detected in the cell.

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

[0172] In some embodiments, the plurality of TRPs may include a first TRP and a second TRP, the cell group may include a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells may be set with a first set of RSs for beam obstruction detection and a first set of RSs for new / candidate beam identification, and the second subset of cells may be set with a second set of RSs for beam obstruction detection and a second set of RSs for new / candidate beam identification.

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

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

[0175] In some embodiments, the TRP information may include an indication of a TRP index common to all cells indicated in the beam obstruction recovery request.

[0176] In some embodiments, the TRP information may include an indication of each TRP index of each cell indicated by the beam failure recovery request.

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

[0178] In some embodiments, a cell may be associated with a plurality of TRPs, and the TRP information may include first information indicating the number of TRPs associated with the beam failure detected in the cell and second information indicating an RS index for a new beam identified at one of the plurality of TRPs. Here, the RS index indicates the index of the one TRP.

[0179] In some embodiments, the terminal device includes a circuit configured to receive a setting from the network device and transmit a beam failure recovery request to the network device in response to detecting a beam failure in a cell within a cell group. Here, the setting indicates that each cell within the cell group that provides a service to the terminal device is associated with at least one of a plurality of transmit and receive points (TRPs) connected to the network device, and the beam failure recovery request includes TRP information related to the beam failure detected in the cell.

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

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

[0182] In some embodiments, the terminal device includes a circuit configured to transmit a first beam failure recovery request to the network device in response to detecting a beam failure based on the first set of RSs, and transmit a second beam failure recovery request to the network device in response to detecting a beam failure based on the second set of RSs for beam failure detection. Here, the first beam failure recovery request includes at least an indication of the first TRP or the first subset of cells, and the second beam failure recovery request includes at least an indication of the second TRP or the second subset of cells.

[0183] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information indicates one of the plurality of TRPs related to the beam failure detected in the cell.

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

[0185] In some embodiments, the TRP information includes an indication of the respective TRP index of each cell indicated in the beam failure recovery request.

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

[0187] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information includes: first information indicating the number of TRPs associated with a beam obstruction detected in the cell; and second information indicating an RS index for a new beam identified at one of the plurality of TRPs. Here, the RS index indicates the index of the one TRP.

[0188] In some embodiments, a network device includes a circuit configured to transmit a configuration to a terminal device and receive, from the terminal device, a beam obstruction recovery request in response to a beam obstruction being detected in a cell within a cell group. Here, the configuration indicates that each cell within the cell group that provides a service to the terminal device is associated with at least one of a plurality of transmit and receive points (TRPs) connected to the network device, and the beam obstruction recovery request includes TRP information associated with the beam obstruction detected in the cell.

[0189] In some embodiments, each of the plurality of TRPs is represented by at least one of: a control resource set (CORESET) pool index, a CORESET group identifier, an identifier of a reference signal (RS) set for beam obstruction detection, an identifier of an RS set for new / candidate beam identification, spatial relation information, a sounding reference signal (SRS) resource set, a transmit configuration indicator (TCI) state, and a quasi-collocation parameter set.

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

[0191] In some embodiments, the network device includes a circuit configured to receive, from a terminal device, a first beam failure recovery request in response to detecting a beam failure based on the first set of RSs, and to receive, from the terminal device, a second beam failure recovery request in response to detecting a beam failure based on the second set of RSs for beam failure detection. Here, the first beam failure recovery request includes at least an indication of the first TRP or the first subset of cells, and the second beam failure recovery request includes at least an indication of the second TRP or the second subset of cells.

[0192] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information indicates one of the plurality of TRPs related to a beam failure detected in the cell.

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

[0194] In some embodiments, the TRP information includes an indication of the respective TRP index of each cell indicated in the beam failure recovery request.

[0195] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information includes at least one of first information indicating the number of TRPs associated with a beam obstruction detected in the cell, second information indicating an index of one of the plurality of TRPs associated with the beam obstruction detected in the cell, and third information indicating which of the plurality of TRPs a new beam was identified at.

[0196] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information includes first information indicating the number of TRPs associated with a beam obstruction detected in the cell and second information indicating an RS index for a new beam identified at one of the plurality of TRPs. Here, the RS index indicates the index of the one TRP.

[0197] FIG. 10 is a schematic block diagram of an apparatus 1000 suitable for implementing embodiments of the present disclosure. The apparatus 1000 can be regarded as another exemplary implementation of the network apparatus 110, the TRP 130, and / or the terminal apparatus 120 shown in FIG. 1. Therefore, the apparatus 1000 can be implemented in, or at least as a part of, the network apparatus 110, the TRP 130, and / or the terminal apparatus 120 shown in FIG. 1.

[0198] As shown in the figure, the apparatus 1000 includes a processor 1010, a memory 1020 connected to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 connected to the processor 1010, and a communication interface connected to the TX / RX 1040. The memory 1010 stores at least a part of the program 1030. The TX / RX 1040 is for bidirectional communication. The TX / RX 1040 has at least one antenna for facilitating communication, but in fact, the access node described in the present application may have a plurality of antennas. The communication interface may represent any interface necessary for communicating 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, a Un interface for communication between an eNB and a Relay Node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0199] The program 1030 is considered to include program instructions, and when the program is executed by the associated processor 1010, it enables the apparatus 1000 to operate according to the embodiments of the present disclosure as discussed with reference to FIGS. 1 to 9 herein. The embodiments herein may be implemented by computer software, hardware, or a combination of software and hardware executable by the processor 1010 of the apparatus 1000. The processor 1010 may be configured to implement various embodiments of the present disclosure. Also, the combination of the processor 1010 and the memory 1020 may constitute a processing means 1050 suitable for implementing each embodiment of the present disclosure.

[0200] Memory 1020 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, etc.). Although only one memory 1020 is shown for device 1000, a plurality of physically different memory modules may be installed in device 1000. Processor 1010 may be of any type suitable for a local technical network and may include, for example, but not be limited to, a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration, one or more of which may be included. Device 1000 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.

[0201] In general, the 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 in hardware, and other aspects may be implemented by firmware or software that can be executed by a controller, a microprocessor, or other computing device. The various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or shown 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 a controller or other computing device, or a combination thereof, but it will be understood that they are not limited thereto.

[0202] The present disclosure further provides at least one computer program product tangibly stored on a computer-readable non-transitory 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, and execute the processes or methods described above with reference to FIGS. 10 and 11, for example. Usually, 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.

[0203] The program code for executing the method of the present disclosure may be described by any combination of one or more programming languages. The 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 flowchart and / or block diagram are implemented. The program code may be executed entirely on a machine, partially on a machine, as an independent software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0204] The above program code may be embodied on a machine-readable medium, which may be any tangible medium that includes or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium may include one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0205] Note that although the operations have been described in a particular order, it should not be understood that such operations must be performed in the particular order shown or sequentially in order to obtain the desired result, and all the operations shown may not be required in some situations. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes some specific implementation details, these are not limitations on the scope of the present disclosure and should be construed as descriptions of features specific to a particular embodiment. Some features described in the context of individual embodiments may be implemented in combination in one embodiment. Conversely, the various features described in the context of one embodiment may be implemented separately in multiple embodiments or in any suitable sub-combination.

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

Claims

1. A terminal device, means for receiving from a network device a first set of reference signals (RS) for a serving cell and a second set of RS for beam obstacle detection; means for performing a beam failure recovery (BFR) procedure when a beam obstacle is detected in at least one of the first set of the RS or the second set of the RS; wherein the serving cell is a primary cell, a first BFR is triggered for the first set of the RS, a second BFR is triggered for the second set of the RS, and when the BFR procedure has not been successfully completed for either the first set of the RS or the second set of the RS, means for performing a random access procedure in the serving cell for beam failure recovery; comprising when BFR is triggered for only one of the first set of the RS and the second set of the RS, a procedure other than the random access procedure is performed for beam failure recovery, wherein when the serving cell is a secondary cell (SCell) and the SCell is deactivated, means for setting a beam failure indication counter to 0, considering that the first BFR and the second BFR have been successfully completed, and cancelling all triggered BFRs for the serving cell; a terminal device.

2. a beam failure indication for at least one of the first set of the RS or the second set of the RS is received from a lower layer, a beam failure indication counter for at least one of the first set of the RS or the second set of the RS is incremented by one, when the beam failure indication counter is greater than or equal to a maximum value of the beam failure indication counter for at least one of the first set of the RS or the second set of the RS, the beam failure is detected; The terminal device according to claim 1.

3. The means for performing the BFR procedure comprises means for triggering BFR for the first set of the RS or the second set of the RS, means for transmitting a BFR medium access control (MAC) control element (CE) including BFR information for the serving cell; The terminal device according to claim 1.

4. Beam failure recovery information is transmitted to the network device, The beam failure recovery information includes the number of sets of RS related to the beam failure detected in the serving cell. The terminal device according to claim 1.

5. The beam failure indication counter is associated with a first beam failure indication counter for the first set of the RSs and a second beam failure indication counter for the second set of the RSs, The terminal device according to claim 4.

6. A network device, means for transmitting a first set of reference signals (RSs) for a serving cell and a second set of RSs to a terminal device for beam failure detection; means for performing a beam failure recovery (BFR) procedure when a beam failure occurs in at least one of the first set of the RSs or the second set of the RSs; wherein the serving cell is a primary cell, a first BFR is triggered for the first set of the RSs, a second BFR is triggered for the second set of the RSs, and when the BFR procedure has not been successfully completed for either the first set of the RSs or the second set of the RSs, means for performing a random access procedure in the serving cell for beam failure recovery; comprising when a BFR is triggered for only one of the first set of the RSs and the second set of the RSs, a procedure other than the random access procedure is performed for beam failure recovery, wherein when the serving cell is a secondary cell (SCell) and the SCell is deactivated, the beam failure indication counter is set to 0, the first BFR and the second BFR are considered to have been successfully completed, and all triggered BFRs for the serving cell are cancelled; A network device.

7. When the beam failure indication counter is greater than or equal to the maximum value of the beam failure indication counter for at least one of the first set of the RSs or the second set of the RSs, the beam failure is detected, The network device according to claim 6.

8. The means for performing the BFR procedure comprises means for receiving a BFR trigger for the first set of the RSs or the second set of the RSs, and means for receiving a BFR medium access control (MAC) control element (CE) including BFR information for the serving cell The network device according to claim 6.

9. Beam failure recovery information is received from the terminal device, The beam failure recovery information includes the number of sets of RSs related to the beam failure detected in the serving cell, The network device according to claim 6.

10. The beam failure indication counter is associated with a first beam failure indication counter for the first set of the RSs and a second beam failure indication counter for the second set of the RSs. The network device according to claim 9.

11. A method executed by a terminal device, comprising: receiving, from a network device, a first set of reference signals (RSs) for a serving cell and a second set of RSs for beam failure detection; performing a beam failure recovery (BFR) procedure when a beam failure is detected in at least one of the first set of the RSs or the second set of the RSs; when the serving cell is a primary cell, a first BFR is triggered for the first set of the RSs, a second BFR is triggered for the second set of the RSs, and when the BFR procedure has not been successfully completed for either the first set of the RSs or the second set of the RSs, performing a random access procedure in the serving cell for beam failure recovery; when a BFR is triggered for only one of the first set of the RSs and the second set of the RSs, performing a procedure other than the random access procedure for beam failure recovery; when the serving cell is a secondary cell (SCell) and the SCell is deactivated, setting a beam failure indication counter to 0, assuming that the first BFR and the second BFR have been successfully completed, and canceling all triggered BFRs for the serving cell; A method comprising the above.

12. Beam failure recovery information is transmitted to the network device, The beam failure recovery information includes the number of sets of RSs related to the beam failure detected in the serving cell, the method according to claim 11.

13. The beam failure indication counter is associated with a first beam failure indication counter for the first set of the RSs and a second beam failure indication counter for the second set of the RSs. The method according to claim 12.

14. A method executed by a network device, comprising: transmitting, to a terminal device, a first set of reference signals (RSs) for a serving cell and a second set of RSs for beam failure detection; Execute a beam failure recovery (BFR) procedure when a beam failure occurs in at least one of the first set of the RSs or the second set of the RSs. When the serving cell is a primary cell, a first BFR is triggered for the first set of the RSs, a second BFR is triggered for the second set of the RSs, and when the BFR procedure has not been successfully completed for either the first set of the RSs or the second set of the RSs, execute a random access procedure in the serving cell for beam failure recovery. including When BFR is triggered for only one of the first set of the RSs and the second set of the RSs, a procedure other than the random access procedure is executed for beam failure recovery. When the serving cell is a secondary cell (SCell) and the SCell is deactivated, a beam failure indication counter is set to 0, the first BFR and the second BFR are considered to have been successfully completed, and all triggered BFRs for the serving cell are cancelled. Method. **Claim 15**: Beam failure recovery information is received from the terminal device. The method according to claim 14, wherein the beam failure recovery information includes the number of sets of RSs associated with the beam failure detected in the serving cell.

Images