Beam fault detection and restoration using multi-TRP and multi-panel transmission

Abstract

In particular, the methods, systems, and devices may support BFD with multiple TRP transmissions or BFR with multiple TRP transmissions. BFD with multiple TRP transmissions may be configured explicitly or implicitly. BFR with multiple TRP transmissions may include: BFR with contention-free PRACH, BFR with PUCCH, BFR with contention-free 2-step RACH, or BFR with PUSCH.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 62 / 887,917, filed on August 16, 2019, entitled “Beam Failure Detection And Recovery With Multi-Trp And Multi-Panel Transmission,” the contents of which are incorporated herein by reference in their entirety. Background Art

[0003] Massive multiple-input, multiple-output (MIMO) systems are expected to improve data throughput and reliability in future 5G systems. Multiple transmission and reception points (multiple TRPs) may be important in 5G to improve reliability, coverage, and capacity performance through flexible deployment scenarios. For example, in order to support the exponential growth of mobile data traffic in 5G and enhance coverage, wireless devices are expected to access a network composed of multiple TRPs (e.g., macro cells, small cells, pico cells, femto cells, remote radio heads, relay nodes, etc.). Summary of the Invention

[0004] Beam Failure Detection (BFD) and Beam Failure Recovery (BFR) can be per-cell rather than per-TRP / panel. BFR can be for SpCell, or BFR can be for SCell. In the case of multiple TRPs (per) cell, whether PCell or Scell, the radio link to one TRP may fail while the link to another TRP may still function. In scenarios with ideal or non-ideal backhaul, it may be preferable to support BFD and BFR for each of the multiple links using multiple TRPs.

[0005] Disclosed herein are methods, systems, and apparatuses that, inter alia, support BFD using multiple TRP transmissions or support BFR using multiple TRP transmissions. For BFD using multiple TRP transmissions, there may be multiple options, such as: 1) an explicit configuration option for a beam failure resource set and a candidate beam reference signal (RS) list set or 2) an implicit configuration option if no explicit beam failure resource set and candidate beam RS list set is provided for the UE. Regarding BFR using multiple TRP transmissions, there may be multiple options, such as: 1) BFR using contention-free PRACH, 2) BFR using PUCCH, 3) BFR using contention-free 2-step RACH, or 4) BFR using PUSCH.

[0006] This summary is provided to introduce some concepts in a simplified form that are further described in the detailed description below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more detailed understanding may be obtained from the following description, which is given by way of example with reference to the accompanying drawings, in which:

[0008] Figure 1 An exemplary multi-TRP transmission is illustrated;

[0009] Figure 2 An exemplary multi-panel transmission is illustrated;

[0010] Figure 3 An exemplary UE using multiple TRPs and multiple panel transmissions is illustrated;

[0011] Figure 4A An exemplary SCell configured with (a) DL only;

[0012] Figure 4B illustrates an exemplary SCell configured with (b) DL and UL transmissions;

[0013] Figure 5 illustrates that an exemplary A TRP may be associated with a CORESET ID;

[0014] Figure 6A Illustrated is an exemplary CC supporting dual TRP transmission (a) ideal backhaul;

[0015] Figure 6B illustrates an exemplary CC supporting dual TRP transmission (b) non-ideal backhaul and a UE with two panels;

[0016] Figure 7A Illustrated is an exemplary two CCs supporting dual TRP transmission (a) ideal backhaul;

[0017] Figure 7B illustrates an exemplary two CCs supporting dual TRP transmission (b) non-ideal backhaul and a UE with two panels;

[0018] Figure 8 illustrates an exemplary failureDetectionResource set mapping relationship between CCs and radio links / multiple TRPs;

[0019] Figure 9 An exemplary method flow for implicit beam failure detection is illustrated;

[0020] Figure 10 An exemplary explicit configuration method for BFD operation is illustrated;

[0021] Figure 11A Illustrated is an example of two CCs (CC 1 has DL and UL, but CC 2 has only DL2) using dual TRP (a) ideal backhaul;

[0022] Figure 11B Illustrated is an exemplary two CCs (CC 1 has DL and UL, but CC 2 has only DL) using dual TRP (b) non-ideal backhaul and two panels;

[0023] Figure 12 An exemplary BFR method is illustrated;

[0024] Figure 13 illustrates an exemplary BFR transmission using CFRA when the CC has both DL and UL;

[0025] Figure 14 illustrates an exemplary BFR transmission using CFRA when multiple CCs have simultaneous DL and UL;

[0026] Figure 15 illustrates an exemplary BFR transmission using CFRA when one CC has both DL and UL but the second CC has only DL;

[0027] Figure 16 illustrates exemplary PUCCH transmission opportunities for BFR at a CC with DL and UL ideal backhaul;

[0028] Figure 17 illustrates exemplary PUCCH transmission opportunities for BFR at multiple (two) CCs with DL and UL ideal backhaul;

[0029] Figure 18 illustrates exemplary PUCCH transmission opportunities for BFR at a CC with DL and UL non-ideal backhaul;

[0030] Figure 19 Illustrated are exemplary PUCCH transmission opportunities for BFR at two CCs (CC 1 with DL and UL, CC 2 with DL only, with non-ideal backhaul between TRP1 and TRP2, and the UE is equipped with 2 panels);

[0031] Figure 20 An exemplary two-step contention-free RACH for SCell DL BFR-only is illustrated;

[0032] Figure 21illustrates an exemplary MAC CE content of Msg A for BFR when the SCell has only DL;

[0033] Figure 22 Figure 1 illustrates an exemplary MAC CE content of Msg A for BFR when the SCell has both UL and DL.

[0034] Figure 23 A BFR MAC CE with a four-octet bitmap (legacy) is illustrated;

[0035] Figure 24 A BFR MAC CE having a four-octet bitmap with an L field is illustrated;

[0036] Figure 25 A BFR MAC CE having a four-octet bitmap with an L field is illustrated;

[0037] Figure 26 Illustrated are exemplary displays (eg, graphical user interfaces) that may be generated based on methods, systems, and apparatus for beam failure detection and restoration using multiple TRPs and multiple panel transmissions.

[0038] Figure 27A An exemplary communication system is illustrated;

[0039] Figure 27B An exemplary system including a RAN and a core network is illustrated;

[0040] Figure 27C An exemplary system including a RAN and a core network is illustrated;

[0041] Figure 27D An exemplary system including a RAN and a core network is illustrated;

[0042] Figure 27E Another example communication system is illustrated;

[0043] Figure 27F is a block diagram of an example apparatus or device, such as a WTRU; and

[0044] Figure 27G is a block diagram of an exemplary computing system. DETAILED DESCRIPTION

[0045] Multiple TRPs and Multi-Panel Transmissions - It should be recognized that increased diversity and robustness can be achieved with both ideal and non-ideal backhaul networks using multiple TRPs and multi-panel transmissions. At least from a PHY perspective, the goal can be to make each TRP-UE link relatively independent. For example, the UE multiplexes the A / N of (one or more) PDSCHs from TRP1 on one PUCCH transmission, splitting the A / N per TRP.

[0046] Note that an ideal backhaul (such as a point-to-point connection using fiber) can allow very high throughput and very low latency between the TRP and the core network. An ideal backhaul can be defined as latency less than 2.5 microseconds and 10 Gbps throughput. Non-ideal backhaul networks such as xDSL, microwave, and trunk networks can have significant latency in the network.

[0047] In a multi-TRP network, a UE can communicate with multiple TRPs, such as Figure 1 As shown in . Typically, UEs access TRPs on different beams. For non-ideal backhaul networks, non-coherent joint transmissions from multiple TRPs can improve performance, especially at the edge of the TRP coverage area. Joint transmission of multiple TRPs can improve PDSCH performance as well as PDCCH performance.

[0048] Multi-panel deployment can be supported in a TRP for multi-beam transmission and reception. As disclosed herein, the term "TRP" may also refer to a network-side panel. Multi-panel deployment can also be supported in a UE. Furthermore, the term "panel" may refer to a panel of a UE (e.g., an antenna array).

[0049] Multi-panel transmission, where a UE can transmit from multiple panels, is known to provide increased spectral efficiency - the transmissions from the panels can be coherent or incoherent. The concept of multi-panel transmission is discussed in Figure 2 As shown in . It can be assumed that each UE panel has a different orientation, so the optimal beam or TRP for reception can be different for each UE panel. The UE can determine the optimal TRP or beam for a given panel based on measurements and can feed the information back to the network; thus, the network can determine which beam(s) or TRP(s) must be used for PUCCH / PUSCH reception. Each panel-TRP link can be treated as an independent link, so no inter-panel calibration is required at the UE.

[0050] Multi-TRP PDSCH Transmission – Conventionally, multi-codeword transmission on multiple layers on the same time-frequency resources can be supported in both DL and UL. Codewords (CWs) can be transmitted from independent beams from different TRPs. Therefore, the DMRS port(s) used for each CW or layer can have different QCL assumptions. However, in non-ideal backhaul networks where latency is an issue, it may be desirable to operate the TRPs as independently as possible, while joint transmission offers lower reliability.

[0051] Thus, a goal for wireless communications is to enable downlink and uplink signaling enhancements for multi-TRP and multi-panel transmissions.

[0052] A procedure to support multi-TRP PDSCH transmission is being considered along with a separate HARQ ACK codebook for each TRP so that the UE can separately acknowledge PDSCH from different TRPs. Figure 3 An example is shown in FIG, where the UE receives PDSCH1 from TRP1 and PDSCH2 from TRP2, and in response, sends Ack1 (for PDSCH1) to TRP1 and Ack2 (for PDSCH2) to TRP2. Note that PDSCH1 and PDSCH2 can correspond to the same or different HARQ processes. The identifier can be used to associate the received PDSCH with the transmitted TRP so that the UE can send the corresponding Ack to the intended TRP.

[0053] SCell configuration in NR - A SCell can be configured with only downlink (DL) transmission. In this case, UL can be transmitted only at the primary cell (PCell) for the UE. Another scenario is that the serving cell (SCell) can have both uplink (UL) and DL used for transmission. Figure 4A In (a), it illustrates the case where the SCell is configured with only DL transmission, while (b) illustrates the case where the SCell is configured with both DL and UL transmission. Figure 4A In , UE transmits PUCCH / PSCCH via PCell. Figure 4B In the SCell, the UE can transmit PUCCH / PSCCH or other physical channels such as PRACH in both the SCell and the PCell.

[0054] Beam Failure Request in Rel-15 - In Rel-15, when beam failure is detected and candidate beams are defined, the UE transmits PRACH of the best identified candidate beam according to the RACH configuration provided by the RRC message PRACH-ResourceDedicatedBFR. In Rel-15, BFR can be accomplished via the Contention Free Random Access (CFRA) procedure.

[0055] In Rel-15, the RRC BeamFailureRecoveryConfig IE in the BWP-UplinkDedicated field can be used to configure the UE with RACH resources and candidate beams for beam failure recovery in the event of beam failure detection. The CORESET can be provided to the UE via a link pointing to the search space set provided by the recoverySearchSpaceId in the RRC IE BeamFailureRecoveryConfig field for monitoring the PDCCH in the CORESET. The RecoverySearchSpaceId can indicate the search space used for the BFR random access response.

[0056] Radio Link Monitoring in Rel-15 - The UE can be configured for each DL BWP of a special cell (SpCell), such as a primary cell (PCell) or a primary secondary cell (PSCell) with a set of resource indices, for radio link monitoring via failureDetectionResources, via the corresponding set of RadioLinkMonitoringRS. The CSI-RS resource configuration index is provided to the UE via csi-RS-Index, or the SS / PBCH block index is provided to the UE via ssb-Index. The UE can be configured with up to N LR_RLM RadioLinkMonitoringRS is used for link recovery process and for radio link monitoring. LR_RLM The maximum number of candidate SS / PBCH blocks per half frame is L. max , up to N can be used RLM A RadioLinkMonitoringRS performs radio link monitoring, and up to two RadioLinkMonitoringRS can be used for the link recovery process.

[0057] If the UE is not provided with RadioLinkMonitoringRS and the UE is provided with a TCI state for PDCCH reception that includes one or more CSI-RS:

[0058] - If the active TCI state for PDCCH reception includes only one RS, the UE uses the RS provided for the active TCI state for PDCCH reception for radio link monitoring

[0059] - If the active TCI state for PDCCH reception includes two RSs, the UE expects one RS to have QCL-Type D [TS 38.214] and the UE uses the RS with QCL-Type D for radio link monitoring; the UE does not expect both RSs to have QCL-Type D

[0060] - UE is not required to use aperiodic or semi-persistent RS for radio link monitoring

[0061] -For L max = 4, the UE selects N provided for the active TCI state received for the PDCCH in the CORESET associated with the search space set in the order starting from the shortest monitoring period. RLM If more than one CORESET is associated with a search space set with the same monitoring periodicity, the UE determines the order of the CORESETs from the highest CORESET index.

[0062] CORESET-TRP Association - If multiple TRPs are transmitted, then one or more CORESETs in the PDCCH configuration correspond to one TRP. Therefore, the CORESET identity (ID) can be tied to a TRP and linked to that TRP via the CORESET's PDSCH grant. The A / N number for that PDSCH is transmitted to that TRP. Per-TRP PUCCH transmission is thus supported. The association between the CORESET ID and the TRP ID in the PDCCH-config is depicted in the figure.

[0063] For NR-PDCCH transmissions that support robustness against beam-pair link blocking, a UE may be configured to monitor NR-PDCCH on M beam-pair links simultaneously from multiple TRPs, where M ≥ 1 and the maximum value of M may depend on the UE capability. A UE may be configured to monitor NR-PDCCH on (one or more) different beam-pair links (BPLs) in the same or different NR-PDCCH slots, depending on n <= N within a single slot. f Frequency Domain Multiplexing (FDM) TCI states or n<=N in a single time slot t Time Domain Multiplexing (TDM) TCI status.

[0064] As an example, the UE may identify reception on CORESET1 with B1 from TRP1 and reception on CORESET2 with B2 from TRP2. As another example, the UE may identify CORESET1 and CORESET2 from TRP1. The maximum number of TRPs M per component carrier (CC) k of the UE kIt may be predefined in the standard or configured by higher layer signaling such as RRC.

[0065] TRP can determine the Tx beam used for downlink transmission based on the UE's measurement of one or more Rx beams of TRP from CSI-RS or SSB.

[0066] Parameters related to UE Rx beam settings for monitoring NR-PDCCH on multiple beam pair links from multiple TRPs are configured by higher layer signaling or MAC CE or considered in the search space design. At least, NR supports spatial QCL hypothesis indication between (one or more) DLRS antenna ports and (one or more) DL RS antenna ports for demodulation of DL control channels. Candidate signaling methods for beam indication of NR-PDCCH (e.g., configuration method for monitoring NR-PDCCH) are MAC CE signaling, RRC signaling, DCI signaling, canonical transparent or implicit methods, and combinations of these signaling methods.

[0067] For receiving unicast DL data channels from multiple TRPs, NR supports the indication of spatial QCL assumptions between (one or more) DL RS antenna ports and (one or more) DM-RS antenna ports of the DL data channel. The information indicating the (one or more) RS antenna ports is indicated via DCI (downlink grant). The information indicates the (one or more) RS antenna ports that perform QCL with the (one or more) DM-RS antenna ports. Different sets of (one or more) DM-RS antenna ports for the DL data channel can be indicated as QCL with different sets of (one or more) RS antenna ports.

[0068] Beam Fault Detection Using Multi-TRP Transmission

[0069] A BFD-UE using multi-TRP transmission at one or more CCs can receive data from multiple TRPs at one or more CCs. Figure 6A and Figure 6B In the present invention, the network (e.g., gNB) can establish multiple (e.g., two) data links, where the UE 200 can simultaneously receive data from TRP1 201 and TRP2 202 of a specific CC (PCell or SCell). However, depending on the ideal or non-ideal backhaul between TRPs (e.g., TRP1 201 or TRP2 202), the network can provide multiple PDSCHs through a single DCI or multiple DCIs, respectively, as shown in FIG. Figure 6A As shown in , or multiple PDSCHs are provided through multiple DCIs, such as Figure 6B As shown in .

[0070] exist Figure 7A and Figure 7BIn the example, the network can establish multiple (eg, two) data links, where the UE 200 can simultaneously receive data from TRP1 201 and TRP2 202 from different CCs (PCell and SCell). CC1 can be PCell and CC2 can be SCell, or vice versa.

[0071] In NR, there are two configuration options by which the UE 200 can be configured for beam failure detection (BFD). In the first option, it is based on an explicit configuration method, when a higher layer (e.g., RRC) provides the UE 200 with reference signal (RS, e.g., CSI-RS) resources to perform BFD. In the second option, it is based on an implicit configuration method, i.e., no explicit RS resources are provided to the UE 200 to perform BFD. Thus, the implicit method can be referred to as the UE determining the RS for BFD based on the TCI state of the corresponding control resource set that the UE uses to monitor the PDCCH for a specific radio link i of CC k. Both implicit and explicit methods have been defined in NR. This is previous, but is extended in this article to multi-link cases, cell aggregation cases, etc.

[0072] Explicit configuration, e.g., higher layer (RRC) configuration of reference signal resources (e.g., CSI-RS) for beam failure detection - In cases with ideal and non-ideal backhaul in one or more CCs (e.g., as shown in Figures 6 and 7), the following explicit configuration method for BFD operation can be applied.

[0073] UE 200 may be explicitly configured with one or more failureDetectionResources sets in the (active) BWP. And explicitly configured with candidateBeamRSList In the radio link quality measurement, it is used to support the component carrier (CC) k, k = 1..., N max Beam Fault Detection (BFD) using multiple TRP transmissions, where M k represents the maximum number of links that can be supported simultaneously at component carrier (CC) k (from different TRPs or the same TRP) and where N max Indicates the maximum number of CCs supported. The quality measurement of a radio link supporting BFD can be a hypothetical block error rate (BLER). Each link can be associated with at least one CORESET. If the UE is not configured with more than N max CCs, the maximum number of radio links can be limited by Restriction. Every set at CC k and It can be independently associated with multiple sets of periodic CSI-RS resource configuration indexes or SS / PBCH block indexes (referred to herein as SSB indexes). UE200 can expect the set Up to Q (eg, two) RS indices are included. For all i=1...M k , UE 200 can expect each set The physical layer in UE 200 can be configured according to the set of resources For M k The threshold Q of the links oyt,LR,i,k (default value of rlmInSyncOutOfSyncThreshold) to evaluate the radio link quality. The UE 200 evaluates the radio link quality based on periodic CSI-RS resource configuration or quasi co-located SS / PBCH blocks, where the DM-RS of PDCCH reception is monitored by the UE 200 .

[0074] If the UE's higher layers do not provide a failureDetectionResource set And M k ≥ 1 (e.g., with multiple links) for multiple TRP transmissions at CC k, then the UE may use the implicit configuration at CC k by default to assume that the other failureDetectionResource sets Therefore, for other links i, UE 200 may assume that the implicit configuration is used for BFD for link i. Unless there is an indication from higher layers, UE 200 may assume that the implicit configuration is used for BFD for all links j≠i, j∈1…M at CC k. k failureDetectionResource set (If configured for link i). Similarly, if higher layers do not provide a candidateBeamRSList set But for the multi-TRP transmission M at CC k k ≥1, then UE 200 may use the implicit configuration at CC k by default to assume that other candidateBeamRSList sets Unless there is an indication from higher layers, UE 200 may assume that all links j≠i, j∈1…M are used for CC k. k failureDetectionResource set (If configured for link i.) Therefore, as disclosed herein, higher layers can copy explicit configuration for one link to other links, so it can reduce explicit configuration work.

[0075] If the higher layer only provides the failureDetectionResource set at the PCell when configuring the Secondary Cell Group (SCG) If not provided at the SCell(s), then the UE 200 may assume that the failureDetectionResource set is used at the PCell if there is a higher layer indication that the UE may apply the same failureDetectionResource set from the PCell to all SCells. to apply to some or all SCells, otherwise the UE may assume that the SCell uses implicit configuration. Similarly, if the higher layer only provides the candidateBeamRSList set at the PCell when configuring the secondary cell group (SCG), the UE may assume that the candidateBeamRSList set at the PCell is implicit. If the UE 200 does not provide the same set of failureDetectionResources from the PCell to all SCells, then the UE 200 may assume that the candidateBeamRSList set at the PCell is used if there is a higher layer indication that the UE may apply the same set of failureDetectionResources from the PCell to all SCells. Therefore, as disclosed herein, higher layers can copy explicit configuration for one CC to other CCs, so it can reduce explicit configuration work.

[0076] exist Figure 8 In the failureDetectionResource set between CC and radio links (from different TRPs) The mapping relationship shows an example of the reference signal (RS) configuration for BFD. Figure 8 In this case, we can assume that N is the total number of CCs and M k is the number of radio links for CCk, k=1…N. Therefore, for UE 200, the number of radio links may be equal to Each radio link may be associated with a TRP, and the TRP may be associated with a CORESET ID. Thus, the TRP ID may be transparent to the UE 200. Each failureDetectionResource set of link i at CC k (e.g., failureDetectionResource set 206) can be independently provided by higher layers, and each It may be associated with a periodic CSI-RS resource configuration index (CRI) or an SSB resource index (SSBRI) (eg, set 208).

[0077] In some cases, N is the number of serving cells or CCs in a frequency band.

[0078] In some cases, N is the number of serving cells or CCs configured in a serving cell or CC (referred to herein as serving cell / CC) list (e.g., a list of serving cells that can be simultaneously updated for TCI relations (e.g., activation or deactivation of one or more TCI states)).

[0079] In some cases, the radio link is applicable to multiple serving cells / CCs, such as serving cells / CCs in a frequency band or a list. For example, if serving cell / CC m is in the same frequency band or in the same list as serving cell / CC k, then the configuration May be applicable to another serving cell / CC m.

[0080] Different links (e.g., corresponding to different TRPs or TRP sets) can be associated with different CORESET pools. These CORESET pools can be distinguished by different CORESET pool indexes, for example, using the RRC parameter coresetPoolIndex-r16.

[0081] In some cases, the number of failureDetectionResources sets M on the BWP on serving cell / CC k is k It may be equal to the number of different CORESET pools in the BWP, for example, the number of different values ​​of CORESETPoolIndex in the ControlResourceSet included in the higher layer parameter PDCCH-Config. This may be useful, for example, in a multi-TRP scenario with non-ideal backhaul. Resource set k may be associated with a CORESET pool index, for example, k=0 is associated with CORESET pool index 0, and k=1 is associated with CORESET pool index 1.

[0082] In some cases, the number of failureDetectionResources sets M on the BWP on cell / CC k k can be greater than the number of different CORESET pools in BWP, for example, even if there is a single CORESET pool on BWP, there are M k =2.

[0083] You can configure multiple sets for BWP by configuring multiple lists (M k>1), each list includes one or more RSs for BFD (e.g., failureDetectionResources). For example, if only a single list is configured in the active DL BWP of CC k, e.g., the old-style list failureDetectionResourcesToAddModList, then M k = 1. If a second list is configured, such as failureDetectionResourcesToAddModList2, then M k =2, and so on.

[0084] The set index i=1…M can be configured for one or more RSs (eg, failureDetectionResources or RadioLinkMonitoringRS) used for BFD. k To configure multiple collections for BWP (m k >1), so that at least one RS is configured with i=M k In some cases, for each i≤M k , at least one RS used for BFD is configured with a set index i. In some cases, an explicit set index value may be optionally configured for the RS used for BFD (eg, RadioLinkMonitoringRS). k In other cases where ≤2, an optional field indicating that the RS belongs to the second set can be configured for the RS used for BFD. If the optional field does not exist, the RS belongs to the first set.

[0085] In some cases, BWP can be explicitly configured with M k , for example in RadioLinkMonitoringConfig.

[0086] If the number of explicitly configured RS sets (e.g., by using multiple lists or by configuring a set index for each RS for BFD) is less than the configured M k , then UE 200 can use both explicitly configured BFD RS and implicitly configured BFD RS. The implicitly configured BFD RS is determined based on the TCI state of the CORESET subset on the BWP, such as the CORESET corresponding to the subset of the CORESET pool index.

[0087] In one example, the first BFD RS set is explicitly configured, but M k=2. For the set of CORESETs used by the UE 200 to monitor the PDCCH, the second BFD RS set is implicitly determined to include an RS index having the same value as the RS index in the RS set indicated by the TCI-State, and if there are two RS indices in the TCI state, then the set includes the RS index having the QCL-Type D configuration for the corresponding TCI state. The set of CORESETs may correspond to a CORESET pool index (e.g., index 0 or index 1, which may be configurable).

[0088] Implicit configuration for beam failure detection - If no failureDetectionResources is provided to UE 200 at CC k (e.g., implicit configuration for BFD), then for the corresponding CORESET that UE 200 uses to monitor PDCCH, UE 200 can determine the failureDetectionResources set at CC k. Includes a periodic CSI-RS resource configuration index with the same value as the RS index in the RS set indicated by TCI-State. In this case, when the UE does not provide any failureDetectionResources from higher layers, CC k is used for Each set (index i) can be associated with a CORESET identity (controlResourceSetId ID, e.g., j) via TCI status to indicate the corresponding CSI-RS or SSB. The mapping rules may depend on different deployment scenarios which will be discussed later.

[0089] In some cases, the set of BFD RSs at CC k is (Index i) is associated with a CORESET pool index (e.g., coresetPoolIndex-r16), for example, if the UE 200 is configured by a higher layer parameter PDCCH-Config including two different values ​​of coresetPoolIndex-r16 in ControlResourceSet. For example, for a corresponding CORESET with coresetPoolIndex-r16 equal to p0 (p0 can be 0 or 1) that the UE 200 uses to monitor PDCCH, the UE 200 determines the set (index i=0) to include the periodic CSI-RS resource configuration index, whose value is the same as the value of the RS index in the RS set configured or indicated by TCI-State (e.g., by RRC or MAC CE), and if there are two RS indices in TCI state, then the set The RS index having the QCL-TypeD configuration for the corresponding TCI state is included. And for the corresponding CORESET with coresetPoolIndex-r16 equal to p1 (p1 (≠p0) can be 1 or 0) used by the UE 200 to monitor the PDCCH, the UE 200 determines the set (index i=1) to include the periodic CSI-RS resource configuration index, whose value is the same as the value of the RS index in the RS set configured or indicated by TCI-State (e.g., by RRC or MAC CE), and if there are two RS indices in TCI state, then the set Contains the RS index with QCL-TypeD configuration for the corresponding TCI state. Figure 9 .

[0090] Figure 9 An exemplary method flow is shown. Figure 9 As shown in , at step 210, the UE 200 may be configured with multiple different CORESET pools (e.g., 2) on the serving cell. At step 211, the UE 200 may be configured or indicated with a TCI state for the CORESET on the serving cell. At step 212, a first BFD RS set may be implicitly determined for (one or more) CORESETs in the first CORESET pool from the RS in the TCI state. At step 213, the UE 200 may perform BFD based on the first BFD RS set. At step 214, a second BFD RS set may be implicitly determined for (one or more) CORESETs in the second CORESET pool from the RS in the TCI state. At step 215, the UE 200 may perform BFD based on the second BFD RS set.

[0091] For respectively Figure 6A and Figure 7A For multi-TRP transmission with ideal backhaul at one or more CCs as shown in , a single DCI or multiple DCIs can be used to schedule multiple PDSCH receptions. In this case, if no (beam) failure detection resources are provided to the UE 200 to monitor CSI-RS or SSB from higher layers, then the UE 200 should use the RS set indicated by the TCI-state for the corresponding (single) CORESET that the UE 200 uses to monitor the PDCCH.

[0092] Single DCI scheduling of multiple TRP PDSCHs may be applicable, for example:

[0093] When the UE 200 is configured by the higher layer parameter RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", "TDMSchemeA", if the UE 200 indicates with two TCI states in the code point of the DCI field "Transmission Configuration Indication" and the DM-RS port(s) within one CDM group in the DCI field "Antenna Port(s)", or,

[0094] When the UE 200 is configured by a higher layer parameter PDSCH-config, PDSCH-config indicates at least one entry in pdsch-TimeDomainAllocationList, including RepNumR16 in PDSCH-TimeDomainResourceAllocation.

[0095] For example, if the UE 200 is configured by a higher layer parameter PDCCH-Config including two different values ​​of CORESETPoolIndex in ControlResourceSet, multi-DCI scheduling of multi-TRP PDSCH may be applicable.

[0096] The following is when a single DCI is used for Figure 6A A CC shown in Figure 7A The options for BFD operation when multiple CCs schedule multiple links are as shown in Table 1 below:

[0097] Table 1

[0098]

[0099] For example, for a single PDCCH / DCI case, assuming Q tci=2, the UE can use the first TCI state configured for the CORESET to receive DCI 1 (link 1) because the PDCCH only supports one DMRS port. Therefore, the second TCI state configured for the CORESET can be used for the second PDCCH (link 2) reception. Note that the second link PDSCH cannot have the same CC ID as the single DCI CC ID. Therefore, if no failureDetectionResources set is provided to the UE 200 from a higher layer, a single DCI is used to schedule (one or more) PDSCHs for multiple links from a multi-TRP transmission, and at least one CORESET that the UE 200 uses to monitor the PDCCH in the serving cell / CC k is associated with multiple TCI states, then for the CORESET with multiple TCI states that the UE 200 uses to monitor the PDCCH, the UE 200 can determine the set (index i=0) to include a periodic CSI-RS resource configuration index having the same value as the RS index in the RS set indicated by the first TCI state. For a CORESET with multiple TCI states for the UE 200 to monitor the PDCCH, the UE 200 may determine the set (index i=1) to include a periodic CSI-RS resource configuration index having the same value as the RS index in the RS set indicated by the second TCI state. In the case where some (one or more) CORESETs have a single TCI state and some CORESETs have multiple TCI states, a periodic CSI-RS resource configuration index having the same value as the RS index in the RS set indicated by the TCI state for the CORESET with a single TCI state is included, for example, in In some cases, it includes or , depending on whether the CORESET is otherwise associated with the first (i=0) or second (i=1) link, for example, by a CORESET pool index.

[0100] For another example of multiple PDCCH / DCI case, two DCIs are transmitted for links 1 and 2, and the corresponding CORESET IDs are denoted as j1 and j2, respectively. For example, without loss of generality, it can be assumed that there are M=2 TRPs, link 1 from TRP1 and link 2 from TRP2 are used for transmission. Therefore, the first TCI state configured for CORESET j1 is the failureDetectionResources set for link 1, and the first TCI state configured for CORESET j2 is the failureDetectionResources set for link 2. Therefore, when UE 200 is not provided with any failureDetectionResources set from higher layers and multiple DCIs are used to schedule (one or more) PDSCHs for multiple links transmitted from multiple TRPs in serving cell / CC k, UE 200 can determine the set (index i=0) is a first set of (one or more) CORESETs for UE 200 to monitor PDCCH. The corresponding CORESET includes a periodic CSI-RS resource configuration index having the same value as the RS index in the RS set indicated by TCI-State, and if there are two RS indices in TCI state, then the set The first set of (one or more) CORESETs may be the CORESET(s) with the same CORESET pool index in the active DL BWP on the serving cell / CC k, for example, CORESETPoolIndex 0. Similarly, for the corresponding CORESET(s) of the second set of (one or more) CORESETs that the UE 200 uses to monitor the PDCCH, the UE 200 may determine the set (index i=1) to include the periodic CSI-RS resource configuration index, which has the same value as the RS index in the RS set indicated by TCI-State, and if there are two RS indices in TCI state, then the set Including the RS index with QCL-TypeD configuration for the corresponding TCI state. For example, the second set of (one or more) CORESETs can be (one or more) CORESETs with the same CORESET pool index in the active DL BWP on the serving cell / CC k but different from the index associated with the first set of (one or more) CORESETs, e.g., CORESETPoolIndex 1.

[0101] For respectively Figure 6B and Figure 7B Multi-TRP transmission with non-ideal backhaul at one or more CCs as shown in , can support multiple PDCCH / DCI or separate PDCCH / DCI to schedule multiple PDSCH receptions. In this case, multiple / separate PDCCHs with multiple links can be provided to UE 200, so that UE 200 can map the DCI in the CORESET independently to each link without ambiguity.

[0102] In this case, BFD operation with implicit configuration can use the same disclosed method as multi-TRP transmission with ideal backhaul at one or more CCs. In addition, it should be clarified which TCI state configured for the CORESET is the default QCL assumption for PDSCH.

[0103] BFD using multiple TRP transmissions in non-DRX or DRX mode - In non-DRX mode operation, the physical layer in the UE 200 may transmit multiple TRPs for each set of The radio link quality of the corresponding resource configuration is provided to the higher layer for UE 200 to evaluate the radio link quality than the threshold Q out,LR,i,k i=1…M k ,k=1…N is a poor indicator. When the radio link quality is lower than the threshold Q out,LR,i,k When the difference is low, the physical layer can inform the higher layers of the set of periodicity used by the UE 200 to evaluate the radio link quality. The maximum value between the shortest periodicity in the CSI-RS configuration or SS / PBCH block and 2 milliseconds is determined.

[0104] In DRX mode operation, when the radio link quality is higher than the threshold Q out,LR,i,k i=1…M k , k = 1 ... N (eg, for all links), the physical layer may provide an indication to a higher layer, whose periodicity is determined as UE 200 determines the BFD periodicity as the set of radio link monitoring resources (eg, for all links). The maximum value between the shortest periodicity of the periodic CSI-RS configuration or SS / PBCH block in the DRX cycle.

[0105] Based on a request from a higher layer, UE 200 may provide the higher layer with Periodic CSI-RS configuration index or SS / PBCH block index (e.g., for all links) and greater than or equal to Q in,LR,i,k (Default value of rlmInSyncOutOfSyncThreshold) threshold corresponding to L1-RSRP measurement.

[0106] In some cases, in non-DRX mode operation, when the UE 200 uses the set of The radio link quality of the corresponding resource configuration is lower than the threshold Q out,LR,i,k When the radio link quality is lower than the threshold Q, the physical layer in the UE 200 may provide an indication to the higher layers for link i and serving cell / CC k. out,LR,i,k When the difference is reached, the physical layer notifies higher layers of the set of values ​​whose periodicity is used by the UE 200 to evaluate the radio link quality (of link i on serving cell / CC k) The maximum value between the shortest periodicity in the CSI-RS configuration or SS / PBCH block and 2 milliseconds is determined. In some cases, when the radio link quality is higher than the threshold Q out,LR,i,k The physical layer notifies higher layers of the set of times that the UE 200 uses to evaluate the radio link quality (on serving cell / CC k) The maximum value between the shortest periodicity in the periodic CSI-RS configuration or SS / PBCH block and 2 milliseconds is determined in the union of the periodic CSI-RS configuration or SS / PBCH block.

[0107] For radio link quality measurement of the BWP of the serving cell, the UE 200 may provide the set Its periodic CSI-RS resource configuration index or SS / PBCH block is indexed by candidateBeamRSList or candidateBeamResourceList. The radio link quality used for candidate beam measurement or new beam identification can be based on RSRP.

[0108] Based on a request from a higher layer, UE 200 may provide the higher layer with a link i and a serving cell / CC k from the set Periodic CSI-RS configuration index or SS / PBCH block index and corresponding L1-RSRP measurement, which are greater than or equal to Q in,LR,i,k (Default value of rlmInSyncOutOfSyncThreshold) Threshold.

[0109] In each case, for all i, Q out,LR,i,k =Q out,LR,k , or for all i, Q in,LR,i,k =Q in,LR,k In each case, for all i and k, Q out,LR,i,k =Q out,LR , or for all i and k, Q in,LR,i,k =Q in,LR .

[0110] For simplicity, an exemplary UE physical layer procedure with two links or TRPs on serving cell k is as follows. Figure 10 , as shown below. It is easy to generalize to more than two links / TRPs: First, for BWP, UE 200 is configured with two sets of RSs for BFD: and The RS in can be transmitted from the first TRP. The RS in can be transmitted from the second TRP. Secondly, for BWP, UE 200 is configured with two sets of RS for new beam identification (candidate beams): and The RS in can be transmitted from the first TRP. The RS in the second TRP can be transmitted from the second TRP. Third, when the BWP is active, the UE 200 can be based on or Perform BFD. When the radio link quality of all RSs in the set is lower than the threshold, the physical layer notifies the higher layer of this (the radio link quality of all RSs in the set is lower than the threshold) with a certain periodicity. When the radio link quality of all RSs in the link is lower than the threshold, the physical layer notifies the higher layer of this with a certain periodicity. Note that the indication to the higher layer can be separate for link 0 and link 1. Therefore, the physical layer can simultaneously notify the higher layer for The radio link quality of all RSs in the network is below the threshold, but no notification is given to higher layers. The radio link quality of all RSs in is below a threshold, e.g., because The radio link quality of one or more RSs in the UE 200 is equal to or higher than the threshold. and One or both of are used to perform new beam identification.

[0111] Keeping in mind the above, Figure 10An exemplary UE physical layer process flow is provided. At step 220, for a BWP, a first RS set and a second RS set for BFD are configured for the UE 200. The first RS in the first RS set is transmitted from the first TRP 201. The second RS in the second RS set is transmitted from the second TRP 202. At step 221, for the BWP, a third RS set and a fourth RS set are configured for new beam identification (e.g., candidate beams) for the UE 200. The third RS in the third RS set is transmitted from the first TRP 201. The fourth RS of the fourth RS set is transmitted from the second TRP 202. At step 222, when the BWP is active, BFD is performed by the UE based on the first RS and the second RS. At step 223, when the radio link quality of some or all RSs in the first set is lower than a threshold, an indication (e.g., a signal or message) is provided by the physical layer, which indicates this periodicity to other layers, where the other layers are layers higher than the physical layer. When the radio link quality of some or all RSs in the second set is below a threshold, the physical layer indicates this to other layers with a certain periodicity. At step 224, based on a request from a layer (e.g., a layer higher than the physical layer), the UE performs new beam identification based on the third RS set or the fourth RS set.

[0112] Continue to refer Figure 10 , the process (beam failure detection and recovery) can be distributed between two layers (PHY and MAC (higher layer)). The process in steps 220-224 can be mainly PHY part. Some of the MAC part may include the following. At step 225, the MAC can receive a PHY indication of the radio link quality of the first or second link (for example, the first and second links correspond to the first and second RS sets). At step 226, after receiving a certain number of PHY indications, the MAC can declare a beam failure of the first or second link. At step 227, after the beam failure of the first link, the MAC requests the PHY to perform a new beam identification for the first link, which corresponds to the third RS set in the PHY. At step 228, after the beam failure of the second link, the MAC can request the PHY to perform a new beam indicator (NBI) for the second link, which corresponds to the fourth RS set in the PHY. Note that indicating sending or receiving indications, etc. in the entire layer is exemplary, and it is expected that other layers can send such indications.

[0113] Corresponding exemplary higher layer procedures are described below and also see Table 2. First, beam failure instance indications for each link from the lower layer may be counted (reset, incremented, etc.), e.g., using BFI_COUNTER, separately for each link, e.g., separately for i=0 and i=1. Second, beam failure detection timer(s) (e.g., beamFailureDetectionTimer) may be maintained, started, or restarted separately for each link, e.g., separately for i=0 and i=1. Third, beam failures may be detected separately for each link based on the corresponding per-link indications from the lower layer. Fourth, the lower layer may be requested to perform a new beam identification (e.g., providing a new beam identification from the set) for link i. =Periodic CSI-RS configuration index or SS / PBCH block index and corresponding L1-RSRP measurement greater than or equal to the threshold), for example, higher layers have detected link i with beam failure. An exemplary MAC layer process is described below in Table 2.

[0114] Table 2

[0115]

[0116]

[0117] Beam failure request using multiple TRP transmissions

[0118] To support multi-TRP transmission, the disclosed subject matter can support beam failure recovery request (BFRQ) transmission using PUCCH or CFRA. During the BFR procedure, the UE 200 can report only one (e.g., best) beam per TRP at a CC, which corresponds to the measured CSI-RS resource index (CRI) or synchronization signal block (SSB) resource index (SSBRI).

[0119] To support BFR using multi-TRP transmission at one CC or multiple CCs, the following options may be disclosed: 1) BFR using contention-free PRACH; 2) BFR using PUCCH; 3) BFR using contention-free 2-step RACH; or 4) BFR using PUSCH.

[0120] This document discloses a method on how to perform BFR via UL signals (PRACH) / channels (PUCCH, PUSCH) at one or more CCs with multi-panel transmission and multi-TRP.

[0121] The disclosed scenarios may be considered for BFR operation using multiple TRPs or multiple panels. In the first scenario, there may be a single CC using multiple TRP transmissions with (a) an ideal backhaul UE with multiple panels or (b) a non-ideal backhaul and UE with multiple panels. In the second scenario, there may be multiple CCs (with both DL and UL) using multiple TRP transmissions with (a) an ideal backhaul with a UE with multiple panels or (b) a non-ideal backhaul and a UE with multiple panels. In the third scenario, there may be multiple CCs (some with both DL and UL, but some CCs with only DL) using multiple TRP transmissions with (a) an ideal backhaul and a UE with multiple panels or (b) a non-ideal backhaul and a UE with multiple panels.

[0122] like Figure 6A and Figure 6B As shown in FIG, CCs (both DL and UL) with multiple TRPs with ideal backhaul and non-ideal backhaul are shown, respectively, and a UE 200 that may be equipped with multiple panels for BFR is shown. In this case, the UE 200 may use a single DCI to schedule multiple links (e.g., from different TRPs) and a single UCI for the joint UCI of the multiple links (e.g., from different panels).

[0123] like Figure 7A and Figure 7B As shown in FIG, multiple CCs (both DL and UL) with multiple TRPs with ideal backhaul and non-ideal backhaul are shown, and the UE 200 can be equipped with multiple panels for BFR. In this case, the UE 200 can use multiple DCIs to schedule multiple links (e.g., from different TRPs) and use multiple UCIs for multiple links (e.g., from different panels).

[0124] If CC 204 (SCell) has only DL, for example, there is no UL transmission for CC 204, such as Figure 14 As shown in , UE 200 can transmit UCI at CCs (e.g., PCells) with both DL and UL. If UE 200 is equipped with multiple panels for UL transmission, the UE's multiple panels can be used to transmit multiple UCIs to the same TRP, as shown in FIG11.

[0125] BFR uses contention-free PRACH - Beam Failure Recovery Request (BFRQ) can use contention-free PRACH (CFRA). If a CC is configured with both DL and UL, then in this case, PRACH transmission for BFR can be performed on the same CC. Depending on the number of links from multiple TRPs that can be supported at the CC, one or more PRACH resources for BFR can be configured by the same CC.

[0126] For a CC with only DL (e.g., SCell), the CC may not have UL transmission. Therefore, BFR using CFRA should be performed on CCs with both DL and UL.

[0127] BFRQ can be categorized in various ways, such as partial beam failure or full beam failure. Referring to partial beam failure, in multi-TRP transmission, UE 200 may be configured with multiple links for simultaneous transmission. Therefore, it can occur in the case of partial beam failure, which means that at least one beam failure occurs among multiple links (from multiple TRPs), but not all. In this case, BFRQ can be performed on those links without beam failure.

[0128] CC with both DL and UL - For CC with both DL and UL (e.g., PCell or SCell configured with both DL and UL), the UE 200 may be configured with multiple M as per CC k configuration(s). k (of which M k (represents the number of supported multi-TRP transmissions for UE 200 at CC k) PRACH-ResourceDedicatedBFR. See Table 3.

[0129] Table 3

[0130]

[0131]

[0132] UE 200 may initiate one or more CFRA transmissions using PRACH for link i of CC k at time slot n (where PRACH resources (e.g., PRACH-ResourceDedicatedBFR) are indicated (e.g., mapped) by beam candidates from periodic CSI-RS or SSB), where i∈{1…M k Therefore, PRACH resource selection can be based on the periodic CSI-RS or the index q of CC k. new,i Quasi-colocation parameters associated with the associated SS / PBCH block, where q at CC k new,i There is a one-to-one mapping with CFRA resources. As further disclosed herein, the link ID (or CORESET ID) can be signaled with a CFRA transmission opportunity. The UE 200 can be configured with one or more CFRA transmission opportunities. See Table 4.

[0133] Table 4

[0134]

[0135] If UE 200 is equipped with M p >1 panel (e.g., the UE is equipped with multiple transmission panels), then the UE 200 may randomly select one panel or multiple panels for multiple contention-free PRACH transmissions, depending on the UE 200 implementation. Depending on the UE 200's capabilities, if the UE 200 supports simultaneous multiple UL transmissions, which may be based on spatial division multiplexing (SDM) or FDM, then the UE 200 may perform simultaneous multiple CFRA for BFR. Due to multiple panels, the UE 200 may report its ability to support simultaneous multiple UL transmissions to the network (e.g., gNB).

[0136] If the UE 200 is equipped with a single transport panel (eg, M p =1) and there are more than one PRACH that needs to be transmitted for BFR (e.g., more than one BFR report), and the corresponding CFRA resources for different links (e.g., from CORESET / TRP i and CORESET / TRP j) are time-frequency overlapping, then UE 200 can postpone one of them to the next available CF-RACH opportunity (RO).

[0137] UE 200 may transmit the panel ID with CFRA. When UE 200 is equipped with more than one panel (M p >1), the panel ID can be signaled to UE 200 in the CFRA resources. If beam failure occurs for all links, in this case, UE 200 can initiate multiple CFRA transmissions simultaneously. Similar to the partial BFR case where more than one CFRA needs to be transmitted, depending on the capabilities of UE 200, if the CFRA resources for links i and j are time-frequency overlapping, UE 200 can simultaneously transmit multiple PRACHs for link i (e.g., from TRP i) and link j (e.g., from TRP j), or defer one of them to the next available RO.

[0138] For example, it can be assumed that two DL and UL links are established for CC 203, and at CCk=1, DL link 1 is from TRP1 201 and DL link 2 is from TRP2 202, respectively. Figure 11A or Figure 11B In addition, the UE 200 may be equipped with 2 panels and each panel may be equipped with a transmit and receive unit (TXRU), for example, UL link 1 to TRP1 201 and UL link 2 to TRP2 202 at CCk=1, respectively. In this scenario, BFR using CFRA is Figure 13 Depicted in.

[0139] For example, it can be assumed that two DL and UL links are established. DL link 1 can come from TRP1 201 at CC 203, and DL link 2 can come from TRP2 202 at CC 204, respectively. Figure 7A or Figure 7B In addition, UE 200 may be equipped with two panels, for example, UL link 1 to TRP1 201 at CC 203 and UL link 2 to TRP2 202 at CC 204. In this case, BFR uses CFRA in Figure 14 Depicted in.

[0140] However, if CC is configured with DL only, e.g. Figure 14 As shown in , then no UL transmission may be configured at the CC, and therefore, CFRA transmission for BFR may be performed at the PCell or those CCs with DL and UL.

[0141] For a CC with only DL and DL (e.g., SCell is configured with DL only), Figure 14 As shown in , there may be no available UL for PRACH transmission of CC. If UE 200 is provided with recoverySearchSpaceIdi∈{1…M k}, then the UE 200 can be at the PCell in a specific time slot n and according to the periodic CSI-RS resource configuration or the index q provided by the higher layer new,i The quasi co-location (QCL) parameter of the antenna port associated with the SS / PBCH (at the SCell) is the link i∈{1…M k Initiate one or more CFRA transmissions (the type of beam associated may be indicated by PRACH-ResourceDedicatedBFR)

[0142] -UE 200 can recoverSearchSpaceIdTRPi∈{1…M k The provided search space focuses on monitoring the PDCCH. The CRC of the monitored DCI format for BFR can be scrambled by the C-RNTI or MCS-C-RNTI starting from time slot n+w (e.g., w=4) within the window configured by BeamFailureRecoveryConfig.

[0143] -Depending on the capabilities of UE 200, for example, the UE may be equipped with multiple panels, denoted as M pIf more than one CFRA must be transmitted simultaneously for the SCell or PCell, and those CFRA resources are time-frequency overlapped in the PCell, the UE 200 may determine to transmit multiple BFRs simultaneously or postpone one of the BFRs using CFRA to the next available contention-free PRACH transmission opportunity (RO).

[0144] -recoverySearchSpaceId can be independent for each SCell in the absence of UL, so there is no need to distinguish the SCell ID where the failure occurs.

[0145] For example, it may be assumed that multiple (eg, 2) DL and UL links are established. DL link 1 is from TRP1 201 at CC 203, and DL link 2 is from TRP2 202 at CC 204, respectively. Figure 14 However, CC 204 can be DL only. In addition, UE 200 is equipped with 2 panels. Therefore, both UL links 1 and 2 go to TRP1 201 located at CC 203. In this scenario, BFR uses CFRA in Figure 15 Depicted in.

[0146] For a link i∈{1…M k}, which is used for corresponding PDSCH reception, UE 200 may assume that the same PDCCH is used for link i∈{1…M k}'s index q new,i The associated antenna port quasi-colocation parameters are the same antenna port quasi-colocation parameters until the UE 200 receives activation of the TCI state or any parameter TCI-StatesPDCCH-ToAddlist or TCI-StatesPDCCH-ToReleaseList from a higher layer. After the UE 200 detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by the recoverySearchSpaceId configured by the CORESET (e.g., j), the UE 200 may continue to monitor PDCCH candidates in the search space set provided by the recoverySearchSpaceId until the UE 200 receives a MAC CE activation command for the TCI state or TCI-StatesPDCCH-ToAddlist or TCI-StatesPDCCH-ToReleaseList for link i (e.g., from TRP i).

[0147] In the case where recoverySearchSpaceId is TRPi∈{1…M k N symbols after the last symbol received by the first PDCCH in the provided search space set rec (for example, N rec =2B) symbols later, where the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI, the UE 200 assumes that the CRC is the same as the index q new,i Or the antenna port quasi-colocation parameter related to PDCCH monitoring configured by the CORESET with index 0 (for example, j) is the same.

[0148] BFR can be transmitted via PUCCH / UCI - For beam failure reporting using multi-TRP transmission at CCs with both DL and UL, the UE 200 can be configured with: 1) PUCCH or PRACH BFR resources; or 2) both PUCCH and PRACH. When both PUCCH and PRACH are available, they can be used simultaneously as long as PUCCH resources for BFR or PRACH resources for BFR are available. When both PUCCH and PRACH are configured, it may depend on the UE implementation which resource is used for BFR.

[0149] A dedicated PUCCH transmission opportunity (UO) at time slot n may be configured for the UE 200 to transmit a beam failure event.

[0150] Dedicated PUCCH resources for PUCCH opportunities can be provided by higher layers (RRC). Configuration parameters may include PUCCH format, starting PRB / PRB offset, frequency hopping (inter-slot, intra-slot), periodicity, first symbol (starting symbol) / startingSymbolIndex, number of symbols / nrofSymbols, initial CS index (initialCyclicShift), number of PRBs / nrofPRBs, time domain OCC (occ-Length, occ-Index), additional DM-RS, maximum code rate, number of slots, pi2BPK and ssb-perPUCCH-Occasion. Figure 11A or Figure 11B As shown in [1], PUCCH can be used to configure dedicated PUCCH transmission opportunities for BFR. When BFR uses PUCCH, the gNB can configure periodic PUCCH resources for BFRQ transmission. However, if there is no BFR at the PUCCH opportunity, then there may be no UCI / PUCCH transmission.

[0151] In case of prioritization, the priority rule for UCI may be defined as: BFR>HARQ-ACK / SR>Periodic CSI (P-CSI).

[0152] If there is a BFR transmitted on a dedicated PUCCH, the UE 200 may monitor the PDCCH at slot n+4 in the search space configured for link i configured by the CORESET (e.g., j), which is associated with the link used for the corresponding beam recovery PDSCH reception (e.g., from TRP i). If the CORESET has configured recoverySearchSpaceId, the UE 200 may perform blind detection on the recovered PDCCH using recoverySearchSpaceId. If recoverySearchSpaceId has not been provided, the UE 200 may assume the search space ID used by COREST for PDCCH reception. Here, in contrast to BFR using CFRA, it may not be necessary to assign a special CORESET to the UE 200 to monitor beam recovery. Instead, the UE 200 may monitor the link of the PFCCH where the BFR occurred.

[0153] UE 200 may assume the same k}'s index q new,i Those same antenna port quasi-colocation parameters associated with the UE 200 until the UE 200 receives activation of the TCI state or any one of the parameters TCI-StatesPDCCH-ToAddlist or TCI-StatesPDCCH-ToReleaseList through a higher layer. After the UE 200 detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set in the CORESET (e.g., j), the UE 200 may continue to monitor the PDCCH candidates in the search space set provided in the CORESET (e.g., j) until the UE 200 receives a MAC CE activation command for the TCI state or TCI-StatesPDCCH-ToAddlist or TCI-StatesPDCCH-ToReleaseList for link / TRP i.

[0154] The TRP i identity (e.g., mapping to CORESET ID i) may be transmitted at the UL DM-RS for PUCCH BFR. For example, without applying UL precoding (e.g., precoding by DFT), the UE 200 may assume a PUCCH demodulation reference signal (DM-RS) sequence r of OFDM symbol number l within a slot. l (mD. Can be the timeslot number within the frame

[0155]

[0156] The pseudo-random sequence generator can be a function of TRP i (e.g., a mapping to CORESET ID i) and can be initialized with

[0157]

[0158] in Given by the higher layer parameter scramblingID0 in the DMRS-UplinkConfig IE if provided, otherwise Given, And M (eg, M=2) is the maximum number of TRPs at a CC. If the UE 200 is configured with dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB, scramblingID0 may be obtained from dmrs-UplinkForPUSCH-MappingTypeB.

[0159] Similar to the use case for BFR using CFRA, BFR using PUCCH resources may depend on one or more of the following deployment scenarios. Figure 6A and Figure 7A As shown in , a single DCI can be used to schedule multiple PDSCH receptions with a multi-TRP transmission with an ideal backhaul at one or more CCs. In this case, a dedicated PUCCH transmission opportunity for multiple links (from multiple TRPs) can be used, and the link / TRP ID can be indicated by the DM-RS for BFRPUCCH.

[0160] In the second deployment scenario, if the UE 200 is equipped with multiple panels M p ≥ 1 for UL transmission, depending on its capabilities, the UE 200 can decide which panel to use for BFR PUCCH transmission or perform multiple BFR UCI / PUCCHs simultaneously. The UE 200 can assume that it uses the panel with the identified q for BFR PUCCH transmission. new,i The panel ID may be transparent to the network, as the network may not need to know the panel ID for BFR PUCCH reception, as the link failure ID may be conveyed by the DM-RS for BFR PUCCH.

[0161] In the third scenario, if the UE 200 is equipped with multiple panels M p ≥1 for UL transmission, then UE 200 can use BFR PUCCH to transmit panel ID.

[0162] In the fourth scenario, for Figure 6B and Figure 7B For multi-TRP transmission with non-ideal backhaul at one or more CCs as shown in , multiple / separate DCIs can be used to schedule multiple PDSCH receptions. In this case, UE 200 can be configured with separate dedicated PUCCH transmission opportunities for BFR in CCs. Those separate dedicated PUCCH transmission opportunities can be based on TDM, FDM, or time-frequency overlap via SDM.

[0163] In the fifth scenario, if the SCell has only DL, then BFR PUCCH can be configured at the PCell. BFR PUCCH resources can be configured based on ideal or non-ideal backhaul between TRPs.

[0164] The difference between BFR using PUCCH and CFRA is that multiple BFR requests can be reported in a dedicated PUCCH opportunity instead of using multiple CFRA resources. For example, it can be assumed that multiple DL and UL links are established for CC 203, and at CCk=1, DL link 1 comes from TRP1 201 and DL link 2 comes from TRP2 202. The ideal backhaul between TRP1 201 and TRP2 202 is as follows: Figure 6A In addition, the UE may be equipped with 2 panels, for example, UL link 1 to TRP1 201 and UL link 2 to TRP2 202 with CCk=1. In this scenario, BFR uses PUCCH in Figure 16 Depicted in.

[0165] For example, it can be assumed that multiple DL and UL links are established. DL link 1 comes from TRP1 201 at CC 203, DL link 2 comes from TRP2 202 at CC 204, and the ideal backhaul between TRP1 201 and TRP2 202 is as follows: Figure 7A In addition, UE 200 is equipped with 2 panels, such as UL link 1 to TRP1 201 at CC 203 and UL link 2 to TRP2 202 at CC 204. For this scenario, BFR uses PUCCH in Figure 17In this case, BFR transmission using PUCCH can be transmitted at UL CC 203, and the link / TRP ID can be distinguished by the DM-RS used for BFR PUCCH. Therefore, only CC 203 can be configured with PUCCH for BFR.

[0166] For example, it can be assumed that multiple DL and UL links are established for CC 203, and at CCk=1, DL link 1 comes from TRP1 201, DL link 2 comes from TRP2 202, and the non-ideal backhaul between TRP1 201 and TRP2 202 is as follows: Figure 6B In addition, UE 200 may be equipped with two panels, for example, UL link 1 to TRP1 201 at CCk=1 and UL link 2 to TRP2 202. In this example, BFR using PUCCH is used in Figure 18 As shown in FIG. BFR PUCCH 1 and BFR PUCCH 2 can be separated. In this case, it can be assumed that multiple BFR PUCCH 1 and BFR PUCCH 2 are based on TDM.

[0167] For example, it can be assumed that multiple CCs 203 are configured, and at CC 204, DL link 1 is from TRP1 201 and DL link 2 is from TRP2 202, with non-ideal backhauls between TRP1 201 and TRP2 202 as shown in Figure B. However, CC 204 only has DL. In addition, UE 200 can be equipped with two panels, such as UL link 1 to TRP1 201 at CC 203 and UL link 2 to TRP2 202 at CC 204. In this example, BFR using PUCCH is used in Figure 19 As shown in FIG. BFR PUCCH 1 and BFR PUCCH 2 are separated. In this case, it can be assumed that BFR PUCCH 1 and BFR PUCCH 2 are based on TDM.

[0168] During the BFR process, the UE 200 may report the best measured quality (e.g., RSRP) of the CRI or SSBRI from the configured CSI-RS or SSB index set for each CC (Note: the CSI-RS or SSB index may be based on explicit or implicit configuration). The uplink control information (UCI) carrying the CRI for BFR is depicted in Table 5 (an exemplary mapping order for one reported CSI field for CRI or an exemplary mapping order for SSBRI for BFR).

[0169] UCI conveying CRI / SSBRI for BSR can be used for the following use cases: 1) Single CC using multiple TRP / panel transmission, e.g. Figure 6A or Figure 6B or 2) using multiple CCs with multiple TRPs / panels, as shown in Figure 7A or Figure 7B As shown in .

[0170] Table 5

[0171]

[0172] The actual number of bits used for CRI or SSBRI transmission in a dedicated PUCCH transmission opportunity may depend on or bits, of which It can be the number of CSI-RS resources in the corresponding resource set, and It can be the configured number of SS / PBCH blocks in the corresponding resource set used to report "ssb-Index".

[0173] BFR using 2-step RACH - When SCell is configured with DL only, UE 200 can use contention-free 2-step RACH for BFR at PCell. For SCell with downlink only, UE can report new / identified q new,i The new / identified q may be selected from the explicit or implicit configuration of the reference signal (e.g., CSI-RS or SSB) for link i. new .

[0174] The following method may be used for contention-free 2-step RACH for BFR at the PCell.

[0175] Figure 12 An exemplary BFR method is illustrated. In the first step (e.g., step 282), the UE 200 may transmit a beam failure event (e.g., one or more beam failures occurring at one or more CCs) via a PRACH preamble transmission at a contention-free PRACH opportunity (RO). In the second step (e.g., step 283), a MAC-CE transmitted by a PUSCH reports the CC index (s), CORESET ID, or new / identified candidate beam / RSq where the failure occurred. new,i (if present). The new / identified q can be selected from the explicit or implicit configuration of the reference signal (e.g., CSI-RS or SSB) new,i In this case, the PRACH RO does not need to be associated with the SSB block resource index (SSBRI) because the new beam information q new,i It can be carried via Msg A (PUSCH).

[0176] When BFR uses contention-free 2-step RACH for SCells with only DL, there can be a one-to-one mapping between the contention-free PRACH preamble and the PUSCH resource unit (PRU). When performing MsgA transmission, the DMRS port or DMRS sequence can be implicitly indicated to the physical layer. Alternatively, the DMRS port or DMRS sequence can be implicitly determined by the physical layer based on the selected RA preamble.

[0177] For example, it can be assumed that multiple DL and UL links can be established for CC 203, and at CC 204 DL link 1 is from TRP1 201 and DL link 2 is from TRP2 202, and the non-ideal backhaul between TRP1 201 and TRP2 202 is as follows: Figure 11B However, CC 204 may only have DL. In addition, UE 200 may be equipped with two panels, for example, UL link 1 to TRP1 201 at CC 203 and UL link 2 to TRP2 202 at CC 204, respectively.

[0178] Figure 11B Example setup for contention-free 2-step RACH in BFR Figure 20 In this example, UE 200 can configure the timing offset between the PRACH preamble and Msg A. Note that this timing offset can be set to zero, for example, so that the PRACH preamble and PUSCH can be transmitted in the same time slot as TDM or FDM. To transmit contention-free 2-step RACH for BFR at the PCell, UE 200 automatically determines PRACH and PUSCH transmission based on UL spatial relationship factors, for example, the TCI state is the same as the lowest CORESET ID that UE 200 can monitor at the PCell.

[0179] UE 200 can monitor the link i∈{1…M k} (e.g., PDCCH from TRP i). This can be because each CC can be configured with at least DL. While UE 200 can initiate one or more contention-free PRACH transmissions at PCell in slot n for those SCells without UL for the preamble and MsgA PUSCH at slot n+k. Based on the periodic CSI-RS resource configuration or the index q provided by higher layers, new,iThe antenna port quasi-colocation parameters associated with the associated SS / PBCH block (in the SCell) can be used by the UE 200 to recoverSearchSpaceId TRP i (i∈{1…M k}) focuses on monitoring the PDCCH in the search space provided by the UE 200, which may depend on the configuration. The CRC of the monitored DCI format for BFR may be scrambled by the C-RNTI or MCS-C-RNTI starting from slot n+k+4 within the window configured by BeamFailureRecoveryConfig. Depending on the capabilities of the UE 200, if more than one PRACH must be transmitted and their PRACH resources are time-frequency overlapping at the PCell, the UE 200 may decide to transmit multiple PRACHs simultaneously or to postpone one of them to the next available PRACH transmission opportunity (RO). In addition, the PRACH preamble may carry the UL panel ID or use DM-RS for Msg A PUSCH.

[0180] The failed CC(s) index can be from up to N for SCells with DL-only BFR. max Therefore, the maximum number of BFRs can be expressed as N max ×M, where M can be the maximum number of TRPs supported by each CC.

[0181] MAC CE can be used to report the failed CC index(es), CORESET ID, new beam IDq for MsgA new,i The example of MAC CE is in Figure 21 The fields are described below. The first field, "FailedCC ID," indicates the identity of the CC with the failed beam. The second field, "NBI," indicates the new beam indicator. If NBI = 1, the new beam ID (CRI / SSBRI) is reported. The third field, "CI," indicates the persistence indicator. If CI = 1, there is another failed CC to report. The fourth field, "R," indicates a reserved bit.

[0182] For 2-step contention-free RACH for BFR method, this is a useful case for SCell with DL only. The MAC-CE payload may include CC ID, CORESET ID or new beam ID (e.g., q new,i ). Therefore, the mapping of CC, TRP or panel ID can be explicitly signaled via MAC-CE payload, such as Figure 21 As shown in .

[0183] However, 2-step RACH can be beneficial for the use case when the SCell is configured with DL only. When the SCell is configured with both DL and UL, this SCell can transmit those failed links without the help of other cells. Therefore, the index of those failed links (one or more) can be omitted in the MAC CE payload. Therefore, the MAC CE content can be reduced, such as Figure 22 As shown in .

[0184] BFR uses PUSCH - (one or more) failed CC indexes, new beam information (if present), or beam failure events to be reported by a single report of MAC CE. In this case, the resources used for MAC CE may not be used for dedicated PUCCH or PRACH triggering for BFR. Since (one or more) failed CC indexes, new beam information, or CORESET ID can be reported by a single report of MAC-CE without dedicated PUCCH or PRACH for BFR, the latency of SCell-BFR can be large and not controlled by the gNB. This can be because when a normal SR is received, the gNB cannot immediately schedule PUSCH transmission as in the typical case. In this case, there can be use cases such as the following:

[0185] In the first use case, for BFR with only some SCells with DL, if there is BFR at the PCell and available resources for PUSCH transmission, then the public Msg A content can be carried by regular PUSCH without using contention-free RACH or 2-step RACH method for BFR.

[0186] In the second use case, for BFR with both DL and UL CCs, if BFR is present, then there may be contention-free RACH or dedicated PUCCH opportunities and available resources at the CC for PUSCH transmission, then it may piggyback the failed CC index(es), CORESET ID, new beam IDq indicated by contention-free RACH to regular PUSCH new,i .

[0187] MAC CE can be used to report as Msg A when SCell has only DL, e.g. failed CC index(es), CORESET ID, new beam ID for Msg A new,i An example of a PUSCH MAC CE data payload is shown in Figure 21 Shown in.

[0188] MAC CE can be used to report as Msg A, e.g., CORESET ID, new beam ID for Msg A, when SCell has only both DL and UL new,i An example of a MAC CE data payload for PUSCH is given in Figure 22 Shown in.

[0189] For UL panel ID indication, the UL panel ID may be transmitted via using DM-RS for PUSCH, or it may be explicitly signaled in the PUSCH payload.

[0190] In some cases, MAC CE may be used to indicate beam failure on one or more serving cells or on one or more links on those one or more serving cells (also applicable to RACH-based BFR as described above, e.g., 2-step RACH).

[0191] For example, consider Figure 23 MAC CE in with an exemplary four-byte bitmap to indicate beam failure or no beam failure on a cell or link.

[0192] C m The field indicates beam failure detection and the presence of an octet including, for example, the AC field for the serving cell with ServCellIndex m. m The field indicates that a beam failure is detected and for the serving cell with ServCellIndex m, the octet including the AC field is present. m The field indicates that no beam failure is detected and the octets including the AC field are not present for the serving cell with ServCellIndex m. The octets including the AC field appear in ascending order based on ServCellIndex;

[0193] In this example, 32 serving cells or links may be indicated. For example, consider a case where there are 16 serving cells, each with two links.

[0194] In one example, C0 and C1 indicate the first (e.g., i=0) and second (e.g., i=1) links of the first cell, e.g., the serving cell with the lowest index (ServCellIndex 0), respectively. The following fields C2 and C3 indicate the first and second links of the second cell, respectively, and so on.

[0195] In various examples, different serving cells have different numbers of configured links. If the sum of the number of links with lower link index in serving cell k and the number of links with lower link index in serving cell k is m-1, then C mmay indicate link i of cell k. C0 may indicate the first link with the lowest index of the serving cell.

[0196] In another example, C0, C1, ..., C 15 Indicates the first links of serving cells 0, ..., 15 respectively. 16 ,C 17 ,…,C 31 Indicate the second links of serving cells 0, ..., 15 respectively.

[0197] In various examples, different serving cells have different numbers of configured links. If m≤M, then C m The first link cell m can be indicated, where M is the highest serving cell index of this MAC entity. If m is greater than M, then C m A second link between cells configured with more than one link may be indicated, and so on.

[0198] The AC field indicates, for example, the presence of the Candidate RS ID field in this octet. If the SSB in candidateBeamRSSCellList has an SS-RSRP higher than rsrp-ThresholdBFR or the CSI-RS in candidateBeamRSSCellList has a CSI-RSRP higher than rsrp-ThresholdBFR (e.g., for the corresponding link i, e.g., The AC field is set to 1 when at least one of the SSB / CSI-RS in the selected signal is available; otherwise, it is set to 0. If the AC field is set to 1, the Candidate RS ID field is present. If the AC field is set to 0, the R bit is present instead.

[0199] For which C m An example of a field indicating beam failure detection and the presence of an octet including an AC field for a serving cell with ServCellIndex m. The octet including the AC field may also include a link field (L), such as Figure 24 For example, if the corresponding serving cell is configured with a single link, the AC octet includes a 1-bit R (reserved, set to 0) field, also as shown in FIG. Figure 23As shown in . On the other hand, if the corresponding serving cell is configured with multiple links, for example two links, the L field can indicate whether the next AC octet also corresponds to the same cell but a different link. For example, if L=0, then the next AC octet corresponds to the next serving cell with a beam failure indicated by its C field. If L=1, then the next AC octet corresponds to another link on the same serving cell where a beam failure is detected. Note that if different links are associated with different sets of candidate RSs, the network can infer the index of the failed link from the candidate RSID. In some cases, the AC bytes corresponding to different links of the serving cell are placed in the order of the link index. If so, even if the AC field is set to 0, if one or more links of the same serving cell fail and are also included in the MAC CE, the network can infer which link failed. In one example, one or more of the reserved bits (otherwise used for the candidate RS ID) are used to indicate the corresponding link index if the AC field is set to 0, for example, the corresponding candidate RS ID does not exist. If the corresponding candidate RS ID does not exist, this can resolve the ambiguity of which link failed.

[0200] For which C m As another example of a field indicating beam failure detection and the presence of an octet including an AC field for a serving cell with ServCellIndex m, the octet including the AC field may also include a link index field (L), such as Figure 25 For example, if the corresponding serving cell is configured with a single link, the AC octet includes an R (reserved, set to 0) field, as shown in FIG. Figure 23 On the other hand, if the corresponding serving cell is configured with multiple links, for example, four links, then the L field may indicate the link index of the link that has failed. In this case, the candidate RS IDs may be indexed within the set for the link. For example, candidate RS ID 0 may refer to An RS in In some cases, the beam failure of a single link per serving cell may be transmitted per MAC CE. In some cases, the AC octet of each link of the serving cell where the failure occurred is always included, e.g., if the corresponding C m The field indicates beam failure detection. In such cases, a certain L value (eg, highest) or a certain candidate RS ID (eg, highest) may indicate that no beam failure was detected for that link.

[0201] Table 6 includes exemplary abbreviations or definitions for the subject matter disclosed herein.

[0202] Table 6 - Abbreviations and definitions

[0203]

[0204]

[0205]

[0206] It should be understood that the entities that perform the steps shown herein (such as Figures 1-20 ), which can be logical entities. These steps can be stored in Figure 27C-27G The exemplary methods disclosed herein may be skipped, combined, or added to the memory of the device, server, or computer system shown in FIG.

[0207] Figure 26 An exemplary display (e.g., a graphical user interface) is illustrated that may be generated based on the methods, systems, and apparatus for beam fault detection and restoration with multiple TRPs and multiple panels as discussed herein. Display interface 901 (e.g., a touch screen display) may provide text associated with beam fault detection and restoration with multiple TRPs and multiple panels in block 902, such as BFD or BFR related parameters, method flow, and associated current conditions. Progress of any step discussed herein (e.g., messages sent or success of a step) may be displayed in block 902. Additionally, graphical output 902 may be displayed on display interface 901. Graphical output 903 may be a topology of devices implementing the methods, systems, and apparatus for beam fault detection and restoration with multiple TRPs and multiple panels, graphical output of the progress of any method or system discussed herein, and the like.

[0208] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced standards, and New Radio (NR), also known as "5G." Development of the 3GPP NR standards is expected to continue and include the definition of next-generation radio access technologies (New RATs), which are expected to include the provision of new flexible radio access below 7 GHz, and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to include new, non-backwards-compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with different requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for, for example, indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with sub-7 GHz flexible radio access, with cmWave- and mmWave-specific design optimizations.

[0209] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide range of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine-type communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy conservation), and enhanced vehicle-to-everything (eV2X) communications (which can include any of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and vehicle communications with other entities). Specific services and applications within these categories include, for example, monitoring sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car emergency calls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics, and aerial drones, among others. All of these and other use cases are contemplated herein.

[0210] Figure 27A An example communication system 100 is illustrated in which methods and apparatus for beam failure detection and recovery with multi-TRP and multi-panel transmissions, such as those described and claimed herein, may be used. Figures 1 to 20The communication system 100 may include a wireless transmit / receive unit (WTRU) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (generally or collectively referred to as one WTRU 102 or multiple WTRUs 102). The communication system 100 may include a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. The network services 113 may include, for example, a V2X server, a V2X function, a ProSe server, a ProSe function, IoT services, video streaming, or edge computing.

[0211] It will be appreciated that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of apparatus or device configured to operate or communicate in a wireless environment. Figure 27A 、 Figure 27B 、 Figure 27C 、 Figure 27D 、 Figure 27E or Figure 27F Each WTRU 102a, 102b, 102c, 102d, 102e, 102f or 102g is depicted as a handheld wireless communication device, but it should be understood that for the various use cases expected for 5G wireless communications, each WTRU may include or be implemented in any type of device or apparatus configured to transmit or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronic product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, bus, truck, train or airplane), etc.

[0212] The communication system 100 may also include a base station 114a and a base station 114b. Figure 27AIn the example shown, each base station 114a and 114b is depicted as a single element. In practice, the base stations 114a and 114b may include any number of interconnected base stations or network elements. The base station 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, network services 113, or other networks 112. Similarly, the base station 114b may be any type of device configured to wirelessly interface with at least one of the remote radio heads (RRHs) 118a, 118b, the transmission and reception points (TRPs) 119a, 119b, or the roadside units (RSUs) 120a and 120b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, other networks 112, or network services 113. The RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102 (e.g., WTRU 102c) to facilitate access to one or more communication networks, such as the core networks 106 / 107 / 109, the Internet 110, network services 113, or other networks 112.

[0213] The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, network services 113, or other networks 112. The RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102e or 102f to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, other networks 112, or network services 113. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a next generation Node B (gNodeB), a satellite, a site controller, an access point (AP), a wireless router, and the like.

[0214] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Similarly, base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations or network elements (not shown), such as a BSC, an RNC, relay nodes, etc. Base station 114a may be configured to transmit or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown) for methods, systems, and apparatus for beam failure detection and recovery using multiple TRPs and multiple template transmissions, as disclosed herein. Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an example, the base station 114a may include three transceivers, e.g., one transceiver for each sector of the cell. In an example, the base station 114a may employ multiple-input multiple-output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0215] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c, or 102g over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0216] The base station 114b can communicate with one or more of the RRHs 118a, 118b, the TRPs 119a, 119b, or the RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which can be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b can be established using any suitable radio access technology (RAT).

[0217] The RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f over the air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).

[0218] The WTRUs 102a, 102b, 102c, 102d, 102e, or 102f may communicate with each other, such as sidelink communications, over the air interface 115d / 116d / 117d, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d / 116d / 117d may be established using any suitable radio access technology (RAT).

[0219] The communication system 100 may be a multiple-access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, TRPs 119a, 119b and RSUs 120a, 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, 102f may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) or High Speed ​​Uplink Packet Access (HSUPA).

[0220] In an example, the base station 114a and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) or LTE-Advanced (LTE-A) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. In the future, the air interface 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and V2X technologies and interfaces (such as sidelink communications). Similarly, 3GPP NR technology includes NR V2X technology and interfaces (such as sidelink communication, etc.).

[0221] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, and 102g, or the RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b, may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN) etc.

[0222] For example, Figure 27AThe base station 114c in the example may be a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area (such as a business location, a house, a vehicle, a train, an antenna, a satellite, a factory, a campus, etc.) for implementing the methods, systems, and apparatus for beam failure detection and recovery using multiple TRPs and multi-panel transmissions, as disclosed herein. In an example, the base station 114c and the WTRU 102 (e.g., WTRU 102e) may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, the base station 114c and the WTRU 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, the base station 114c and the WTRU 102 (e.g., WTRU 102e) may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a picocell or femtocell. Figure 27A As shown in FIG, the base station 114c may have a direct connection to the Internet 110. Therefore, the base station 114c may not be required to access the Internet 110 via the core network 106 / 107 / 109.

[0223] The RAN 103 / 104 / 105 or RAN 103b / 104b / 105b may be in communication with the core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or perform high-level security functions (such as user authentication).

[0224] Although not in Figure 27AAlthough not shown in the figures, it will be appreciated that the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b, which may utilize an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs a GSM or NR radio technology.

[0225] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP internet protocol suite. The networks 112 may include wired or wireless communication networks owned or operated by other service providers. For example, the networks 112 may include any type of packet data network (e.g., an IEEE 802.3 Ethernet network) or another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or a different RAT.

[0226] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capabilities. For example, the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different wireless links to implement the methods, systems, and apparatuses for beam failure detection and recovery with multi-TRP and multi-panel transmission as disclosed herein. For example, Figure 27A The WTRU 102g shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[0227] Although Figure 27A

[0026] Not shown, but as will be appreciated, the user equipment may establish a wired connection to a gateway. The gateway may be a residential gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. It will be appreciated that many of the subject matter included herein is equally applicable to a UE that is a WTRU and a UE that connects to a network using a wired connection. For example, the concepts applicable to wireless interfaces 115, 116, 117, and 115c / 116c / 117c are equally applicable to wired connections.

[0228] Figure 27B 1 is a system diagram of an example RAN 103 and core network 106 that may implement the methods, systems, and apparatus for beam failure detection and recovery with multi-TRP and multi-panel transmission as disclosed herein. As described above, the RAN 103 may employ UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also communicate with the core network 106. Figure 27B As shown in FIG, the RAN 103 may include Node-Bs 140a, 140b, and 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. The Node-Bs 140a, 140b, and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a and 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and radio network controllers (RNCs).

[0229] like Figure 27B As shown in FIG, Node Bs 140a and 140b can communicate with RNC 142a. Additionally, Node B 140c can communicate with RNC 142b. Node Bs 140a, 140b, and 140c can communicate with respective RNCs 142a and 142b via an Iub interface. RNCs 142a and 142b can communicate with each other via an Iur interface. Each of RNCs 142a and 142b can be configured to control the respective Node Bs 140a, 140b, and 140c to which it is connected. Additionally, each of RNCs 142a and 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, and the like.

[0230] Figure 27BThe core network 106 shown in FIG may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements is depicted as part of the core network 106, it will be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.

[0231] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices.

[0232] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0233] The core network 106 may also be connected to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0234] Figure 27C 1 is a system diagram of an example RAN 104 and core network 107 that may implement the methods, systems, and apparatus for beam failure detection and recovery with multiple TRPs and multi-panel transmission as disclosed herein. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.

[0235] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, although it will be appreciated that the RAN 104 may include any number of eNode-Bs. The eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. For example, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0236] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink or downlink, etc. Figure 27C As shown in FIG, eNode-Bs 160a, 160b, and 160c may communicate with each other via an X2 interface.

[0237] Figure 27C The core network 107 shown in FIG may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the aforementioned elements is depicted as part of the core network 107, it should be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.

[0238] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, and 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0239] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, and 102c, managing and storing the context of the WTRUs 102a, 102b, and 102c, and the like.

[0240] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0241] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices. For example, the core network 107 may include, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0242] Figure 27D 1 is a system diagram of an example RAN 105 and core network 109 that may implement the methods, systems, and apparatus for beam failure detection and recovery with multiple TRPs and multi-panel transmissions as disclosed herein. The RAN 105 may employ NR radio technology to communicate with the WTRUs 102a and 102b over the air interface 117. The RAN 105 may also be in communication with the core network 109. The Non-3GPP Interworking Function (N3IWF) 199 may employ non-3GPP radio technology to communicate with the WTRU 102c over the air interface 198. The N3IWF 199 may also be in communication with the core network 109.

[0243] The RAN 105 may include gNode-Bs 180a and 180b. It will be appreciated that the RAN 105 may include any number of gNode-Bs. The gNode-Bs 180a and 180b may each include one or more transceivers for communicating with the WTRUs 102a and 102b over the air interface 117. When integrated access and backhaul connectivity is used, the same air interface may be used between the WTRUs and the gNode-Bs, which may be the core network 109 via one or more gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU-MIMO, or digital beamforming techniques. Thus, for example, the gNode-B 180a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. It will be appreciated that the RAN 105 may employ other types of base stations, such as eNode-Bs. It will also be appreciated that the RAN 105 may employ more than one type of base station. For example, RAN may employ eNode-B and gNode-B.

[0244] The N3IWF 199 may include a non-3GPP access point 180c. It will be appreciated that the N3IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c may include one or more transceivers for communicating with the WTRU 102c over the air interface 198. The non-3GPP access point 180c may communicate with the WTRU 102c over the air interface 198 using the 802.11 protocol.

[0245] Each of the gNode-Bs 180a and 180b may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink or downlink, etc. Figure 27D As shown in FIG, for example, gNode-Bs 180a and 180b may communicate with each other via an Xn interface.

[0246] Figure 27D The core network 109 shown in FIG may be a 5G core network (5GC). The core network 109 may provide a variety of communication services to customers interconnected by a radio access network. The core network 109 includes multiple entities that perform the functions of the core network. As used herein, the term "core network entity" or "network function" refers to any entity that performs one or more functions of the core network. It should be understood that such a core network entity may be a device or computer system (such as a computer system) stored in a computer configured for wireless or network communications. Figure 27G A logical entity implemented in the form of computer-executable instructions (software) stored in a memory of the system 90 shown in FIG. 1 and executed on a processor thereof.

[0247] exist Figure 27D In the example of FIG, 5G core network 109 may include access and mobility management function (AMF) 172, session management function (SMF) 174, user plane function (UPF) 176a and 176b, user data management function (UDM) 197, authentication server function (AUSF) 190, network exposure function (NEF) 196, policy control function (PCF) 184, non-3GPP interworking function (N3IWF) 199, user data repository (UDR) 178. Although each of the aforementioned elements is depicted as part of the 5G core network 109, it should be appreciated that any of these elements may be owned or operated by an entity other than the core network operator. It will also be appreciated that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Figure 27D The network functions are shown connected directly to each other, however, it will be appreciated that they may communicate via a routing agent such as the diameter routing agent or a message bus.

[0248] exist Figure 27D In the example of FIG, connectivity between network functions is achieved via interfaces or reference points. It will be appreciated that network functions can be modeled, described, or implemented as a collection of services that are referenced (invoked) or called (called) by other network functions or services. The reference of network function services can be achieved via direct connections between network functions, the exchange of messages on a message bus, calling software functions, etc.

[0249] The AMF 172 may be connected to the RAN 105 via the N2 interface and may serve as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability management, access authentication, and access authorization. The AMF may be responsible for forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 may generally route and forward NAS packets to / from the WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface is not Figure 27D Shown in.

[0250] The SMF 174 may be connected to the AMF 172 via the N11 interface. Similarly, the SMF may be connected to the PCF 184 via the N7 interface and to the UPFs 176a and 176b via the N4 interface. The SMF 174 may serve as a control node. For example, the SMF 174 may be responsible for session management, IP address allocation for the WTRUs 102a, 102b, and 102c, management and configuration of traffic steering rules in the UPFs 176a and 176b, and generation of downlink data notifications to the AMF 172.

[0251]

[0046] The UPF 176a and UPF 176b may provide the WTRUs 102a, 102b, and 102c with access to a packet data network (PDN), such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and UPF 176b may also provide the WTRUs 102a, 102b, and 102c with access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or any other type of network that exchanges packets of data. The UPF 176a and UPF 176b may receive traffic steering rules from the SMF 174 via the N4 interface. The UPF 176a and UPF 176b may provide access to the packet data network by connecting the packet data network with the N6 interface or by connecting to each other and to other UPFs via the N9 interface. In addition to providing access to the packet data network, UPF 176 may also be responsible for packet routing and forwarding, policy rule enforcement, quality of service handling of user plane traffic, and downlink packet buffering.

[0252] The AMF 172 may also connect to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates connectivity between the WTRU 102c and the 5G core network 170, for example, via a 3GPP-undefined radio interface technology. The AMF may interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0253] PCF 184 may be connected to SMF 174 via an N7 interface, to AMF 172 via an N15 interface, and to Application Function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not Figure 27D. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, thereby allowing the control plane nodes to enforce these rules. The PCF 184 may send policies for the WTRUs 102a, 102b, and 102c to the AMF 172 so that the AMF may deliver the policies to the WTRUs 102a, 102b, and 102c via the N1 interface. The policies may then be enforced or applied at the WTRUs 102a, 102b, and 102c.

[0254] UDR 178 can act as a repository for authentication credentials and subscription information. The UDR can connect to network functions so that the network functions can add data to the repository, read, and modify data in the repository. For example, UDR 178 can connect to PCF 184 via the N36 interface. Similarly, UDR 178 can connect to NEF 196 via the N37 interface, and UDR 178 can connect to UDM 197 via the N35 interface.

[0255] The UDM 197 can serve as an interface between the UDR 178 and other network functions. The UDM 197 can authorize network functions to access the UDR 178. For example, the UDM 197 can connect to the AMF 172 via the N8 interface, and the UDM 197 can connect to the SMF 174 via the N10 interface. Similarly, the UDM 197 can connect to the AUSF 190 via the N13 interface. The UDR 178 and the UDM 197 can be tightly integrated.

[0256] The AUSF 190 performs operations related to authentication and is connected to the UDM 178 via the N13 interface and to the AMF 172 via the N12 interface.

[0257] NEF 196 exposes the capabilities and services in the 5G core network 109 to the application function (AF) 188. The exposure can occur over the N33 API interface. The NEF can connect to the AF 188 via the N33 interface and it can connect to other network functions to expose the capabilities and services of the 5G core network 109.

[0258] The application functions 188 may interact with network functions in the 5G core network 109. The interaction between the application functions 188 and the network functions may occur via a direct interface or may occur via the NEF 196. The application functions 188 may be considered part of the 5G core network 109 or may be external to the 5G core network 109 and deployed by an enterprise that has a business relationship with the mobile network operator.

[0259] Network slicing is a mechanism that mobile network operators can use to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types running across a single RAN. Network slicing enables operators to create networks that are customized to provide optimized solutions for different market scenarios with different requirements (for example, in terms of functionality, performance, and isolation).

[0260] 3GPP has designed the 5G core network to support network slicing. Network slicing is a promising tool for network operators to support a diverse set of 5G use cases (e.g., massive IoT, critical communications, V2X, and enhanced mobile broadband), which have very diverse and sometimes extreme requirements. Without network slicing, the network architecture may not be flexible and scalable enough to efficiently support a wide range of use case requirements, each with its own specific set of performance, scalability, and availability requirements. Furthermore, the introduction of new network services should be made more efficient.

[0261] Reference again Figure 27D In a network slicing scenario, the WTRU 102a, 102b, or 102c may connect to the AMF 172 via the N1 interface. The AMF may logically be part of one or more slices. The AMF may coordinate the connection or communication between the WTRU 102a, 102b, or 102c and one or more UPFs 176a and 176b, the SMF 174, and other network functions. Each of the UPFs 176a and 176b, the SMF 174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may utilize different computing resources, security credentials, etc.

[0262] The core network 109 may facilitate communications with other networks. For example, the core network 109 may include, or may communicate with, an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that serves as an interface between the 5G core network 109 and the PSTN 108. For example, the core network 109 may include, or may communicate with, a Short Message Service (SMS) service center that facilitates communications via the Short Message Service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, and 102c and servers or application functions 188. In addition, the core network 170 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0263] This article describes and Figure 27A 、 Figure 27C 、 Figure 27D or Figure 27E The core network entities shown in FIG are identified by names given to those entities in certain existing 3GPP specifications, but it will be appreciated that those entities and functions may be identified by other names in the future, and that certain entities or functions may be combined in future specifications released by 3GPP (including future 3GPP NR specifications). Figure 27A 、 Figure 27B 、 Figure 27C 、 Figure 27D or Figure 27E The specific network entities and functionality described and illustrated in the present disclosure are presented, and it should be understood that the subject matter disclosed and claimed herein may be implemented or realized in any similar communication system, whether currently defined or defined in the future.

[0264] Figure 27E An example communication system 111 is illustrated in which the systems, methods, and apparatus described herein for beam failure detection and recovery with multi-TRP and multi-panel transmissions may be implemented. The communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied to any number of WTRUs, base station gNBs, V2X networks, or other network elements. One, some, or all of the WTRUs A, B, C, D, E, and F may be outside the range of access network coverage 131. WTRUs A, B, and C form a V2X group, with WTRU A being the group leader and WTRUs B and C being group members.

[0265] If WTRUs A, B, C, D, E, and F are within access network coverage 131, they may communicate with each other via gNB 121 over the Uu interface 129. Figure 27E In the example of FIG, WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate directly to each other via a sidelink interface (e.g., PC5 or NR PC5) such as interface 125a, 125b, or 128 whether they are within access network coverage 131 or outside access network coverage 131. For example, in Figure 27E In the example of , WTRU D outside the access network coverage 131 communicates with WTRU F inside the coverage 131.

[0266] WTRUs A, B, C, D, E, and F may communicate with the RSU 123a or 123b via the vehicle-to-network (V2N) interface 133 or the sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate with the V2X server 124 via the vehicle-to-infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate with another UE via the vehicle-to-person (V2P) interface 128.

[0267] Figure 27F is a block diagram of an example apparatus or device WTRU 102 that may be configured for wireless communications and operations in accordance with the systems, methods, and apparatus described herein for beam failure detection and recovery with multiple TRPs and multiple panel transmissions, such as Figure 27A 、 Figure 27B 、 Figure 27C 、 Figure 27D or Figure 27E or Figures 1-20 WTRU 102 (e.g., UE). Figure 27F As shown in FIG, the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements, and that the base stations 114a and 114b, or the nodes that the base stations 114a and 114b may represent, such as, but not limited to, a transceiver station (BTS), a Node-B, a site controller, an access point (AP), a Home Node-B, an evolved Home Node-B (eNodeB), a Home evolved Node-B (HeNB), a Home evolved Node-B gateway, a next generation Node-B (gNode-B), and a proxy node, among others, may include. Figure 27F Some or all of the elements depicted in and may be exemplary embodiments of implementing the disclosed systems and methods for beam fault detection and restoration with multi-TRP and multi-panel transmission as described herein.

[0268] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 27F The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0269] The transmit / receive element 122 of the UE may be configured to transmit data to a base station (e.g., Figure 27A The transmit / receive element 122 may transmit or receive signals to or from a base station 114a) or transmit or receive signals to or from another UE via the air interface 115d / 116d / 117d. For example, the transmit / receive element 122 may be an antenna configured to transmit or receive RF signals. The transmit / receive element 122 may be an emitter / detector configured to transmit or receive IR, UV, or visible light signals, for example. The transmit / receive element 122 may be configured to transmit and receive both RF and optical signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit or receive any combination of wireless or wired signals.

[0270] Furthermore, although the transmit / receive element 122 Figure 27F Although depicted as a single element in FIG, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0271] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11 or NR and E-UTRA), or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.

[0272] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 or removable memory 132. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. The processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server hosted in the cloud or an edge computing platform, or in a home computer (not shown). The processor 118 may be configured to control an illumination pattern, image, or color on the display or indicator 128 in response to whether the setup of beam failure detection and restoration with multiple TRPs and multiple panel transmissions is successful or failed in some examples described herein, or to otherwise indicate the status and associated components of beam failure detection and restoration with multiple TRPs and multiple panel transmissions. The controlled illumination pattern, image, or color on the display or indicator 128 may reflect the diagrams illustrated or discussed herein (e.g., Figure 1-Figure 25 , etc.). Disclosed herein are messages and procedures for beam failure detection and restoration using multiple TRPs and multiple panel transmissions. The messages and procedures can be extended to provide an interface / API for a user to request resources via an input source (e.g., speaker / microphone 124, keypad 126, or display / touchpad / indicator 128) and, among other things, request, configure, or query information related to beam failure detection and restoration using multiple TRPs and multiple panel transmissions, which can be displayed on display 128.

[0273] The processor 118 may receive power from the power source 134 and may be configured to distribute or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0274] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method.

[0275] The processor 118 may also be coupled to other peripherals 138, which may include one or more software or hardware modules that provide additional features, functionality, or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.

[0276] The WTRU 102 may be included in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health equipment, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains, or airplanes), etc. The WTRU 102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as an interconnect interface that may include one of the peripheral devices 138.

[0277] Figure 27G is a block diagram of an exemplary computing system 90 in which Figure 27A 、 Figure 27C 、 Figure 27D and Figure 27E One or more devices of a communication network as shown in and beam failure detection and restoration with multi-TRP and multi-panel transmission, such as described and claimed herein Figures 1 to 20The systems and methods shown herein may include nodes or functional entities within RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, other networks 112, or network services 113. Computing system 90 may comprise a computer or server and may be primarily controlled by computer-readable instructions, which may be in the form of software, regardless of when, where, or by any means such software is stored or accessed. Such computer-readable instructions may be executed within processor 91 to enable computing system 90 to operate. Processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, or the like. Processor 91 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables computing system 90 to operate within a communications network. The coprocessor 81 is an optional processor different from the main processor 91 that can perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 can receive, generate and process data related to the method and apparatus for beam failure detection and recovery with multi-TRP and multi-panel transmission disclosed herein, such as RRC IE.

[0278] In operation, processor 91 retrieves, decodes, and executes instructions, and transfers information to and from other resources via the computing system's primary data transfer path, system bus 80. Such a system bus connects components within computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and for operating the bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.

[0279] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. This memory includes circuitry that allows information to be stored and retrieved. ROM 93 generally contains stored data that is not easily modified. Data stored in RAM 82 can be read or changed by processor 91 or other hardware devices. Access to RAM 82 or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that translates virtual addresses into physical addresses when executing instructions. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.

[0280] In addition, the computing system 90 may include a peripheral device controller 83 that is responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94 , a keyboard 84 , a mouse 95 , and a disk drive 85 .

[0281] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.

[0282] Additionally, the computing system 90 may include communication circuitry, such as, for example, a wireless or wired network adapter 97, which may be used to connect the computing system 90 to external communication networks or devices (such as the RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, the Internet 110, WTRU 102, or Figure 27A 、 Figure 27B 、 Figure 27C 、 Figure 27D or Figure 27E Other networks 112) to enable computing system 90 to communicate with other nodes or functional entities of those networks. Alone or in combination with processor 91, communication circuitry can be used to perform the transmission and reception steps of certain devices, nodes or functional entities described herein.

[0283] It should be understood that any or all of the devices, systems, methods, and processes described herein can be implemented in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to perform or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein can be implemented in the form of such computer-executable instructions executed on a processor of a device or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile, removable, and non-removable media implemented in any non-transient (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other tangible or physical media that can be used to store desired information and can be accessed by a computing system.

[0284] In describing the preferred methods, systems, or apparatus of the presently disclosed subject matter (Beam Fault Detection and Restoration with Multi-TRP and Multi-Panel Transmission) as shown in the figures, specific terminology is employed for the sake of clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose.

[0285] The various techniques described herein can be implemented in conjunction with hardware, firmware, software, or, where appropriate, a combination thereof. Such hardware, firmware, and software can reside in a device located at each node of a communication network. The device can operate individually or in combination with one another to implement the methods described herein. As used herein, the terms "device," "network device," "node," "equipment," "network node," etc., can be used interchangeably. In addition, unless otherwise provided herein, the use of the word "or" is generally used inclusively.

[0286] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any device or system and performing any combined method. The patentable scope of the invention is defined by the claims and may include other examples that occur to those skilled in the art (for example, skipping steps, combining steps, or adding steps between the exemplary methods disclosed herein). If such other examples have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ substantially from the literal language of the claims, then it is intended that these other examples be included within the scope of the claims.

[0287] The methods, systems, and apparatus described herein may, among other things, provide means for supporting BFD using multiple TRP transmissions or supporting BFR using multiple TRP transmissions, such as Figure 1-Figure 25 The apparatus may be a base station or a user equipment. The system may include one or more processors connected to a memory for implementing operations. The methods, systems, and apparatuses described herein may, in particular, provide explicit configuration options for beam failure resource sets and candidate beam RS list sets. The explicit configuration options may include: explicitly configuring one or more failureDetectionResources sets for the UE in the (active) BWP. And explicitly configure the candidateBeamRSList for UE to use for radio link quality measurement To support in component cells (CC) k, k = 1..., N max Beam Fault Detection (BFD) using multiple TRP transmissions, where M k represents the maximum number of links supported simultaneously on component carrier (CC) k (from different TRPs or the same TRP), where N max Indicates the maximum number of CCs supported. Each set of CCs at k and It may be independently associated with multiple sets of periodic CSI-RS resource configuration indices or SS / PBCH block indices. It may be determined that no explicit beam failure resource set or candidate beam RS list set is provided to the UE 200; and based on the determination that no explicit beam failure resource set or candidate beam RS list set is provided to the UE 200, an implicit configuration option is configured. The implicit configuration option may include: for the corresponding CORESET used by the UE 200 to monitor the PDCCH, the UE configures the failureDetectionResources set at CC k. To include a periodic CSI-RS resource configuration index that has the same value as the RS index in the RS set indicated by the TCI-state. A single DCI can be used to schedule multiple links, and a single UCI can be used for the joint UCI of the multiple links. The methods, systems, and apparatus as described herein may, in particular, provide BFR that supports the use of multiple TRP transmissions, which may include using BFR using contention-free PRACH, BFR using PUCCH, BFR using contention-free 2-step RACH, or BFR using PUSCH. All combinations (including removal or addition of steps) in this paragraph and the next paragraph are considered in a manner consistent with other parts of the detailed description.

[0288] The methods, systems, and apparatus described herein may, among other things, provide for determining that a beam failure event has occurred; based on determining that a beam failure event has occurred, transmitting an indication of the beam failure event, wherein the indication is transmitted during a contention-free physical random access channel (PRACH) opportunity; and reporting an index of a component carrier where the failure occurred via a physical uplink shared channel (PUSCH). The report may include (one or more) failed CC indices, CORESET IDs, or new beam information. new . The new beam information may be carried by Msg A. The method, system, or apparatus may provide for implicitly indicating a demodulation reference signal (DMRS) port or DMRS sequence to the physical layer when performing Msg A transmission. The method, system, or apparatus may provide for implicit determination of a demodulation reference signal (DMRS) port or DMRS sequence by the physical layer based on detection of a selected RA preamble. All combinations in this paragraph and the next paragraph (including removal or addition of steps) are considered in a manner consistent with other parts of the detailed description.

[0289] The methods, systems, and apparatuses described herein may, in particular, provide for configuring (or detecting) a first reference signal (RS) set and a second RS set for beam failure detection (BFD); configuring (or detecting) a third RS set and a fourth RS set for new beam identification; and performing BFD based on the radio link quality of the first RS set or the radio link quality of the second RS set when a bandwidth part (BWP) is active. The methods, systems, and apparatuses described herein may, in particular, provide for receiving a first RS from a first RS set from a first TRP; and receiving a second RS from a second RS set from a second TRP. The radio link quality of the first RS set or the radio link quality of the second RS set may be based on a reference signal received power (RSRP) or a reference signal received quality (RSRQ). The radio link quality of the first RS set may be from the first TRP; the radio link quality of the second RS set may be from the second TRP. The methods, systems, and apparatuses described herein may, in particular, provide for receiving the radio link quality of one or more RSs in the first RS set; and providing an indication to other layers of the radio link quality of at least the RSs in the first RS set based on the radio link quality of a first threshold number of one or more RSs in the first set being below a radio link quality threshold. The indication may be provided by the physical layer. The methods, systems, and apparatuses described herein may, in particular, provide for receiving the radio link quality of one or more RSs in a first RS set; and based on the radio link quality of a second threshold number of one or more RSs in a second set being lower than a radio link quality threshold, provide an indication to other layers of the radio link quality of at least the RSs in the second RS set. The methods, systems, and apparatuses described herein may, in particular, provide for receiving a third RS in a third RS set from a first TRP; and receiving a fourth RS in a fourth RS set from a second TRP. The methods, systems, and apparatuses described herein may, in particular, provide for receiving the radio link quality of the third RS set from a first TRP; and receiving the radio link quality of the fourth RS set from a second TRP. The methods, systems, and apparatuses described herein may, in particular, provide for performing new beam identification based on a request (e.g., in response to a request) based on the radio link quality of the third RS set or the radio link quality of the fourth RS set reaching one or more thresholds. The methods, systems, and apparatuses described herein may, in particular, provide for providing an indication of a beam failure based on a first link (e.g., based on the NBI of the third set), and the MAC layer may request the PHY layer to perform new beam identification on the first link, which corresponds to the third RS set in the PHY. The request for beam failure recovery may be received via a physical random access channel, a physical uplink control channel, or a physical uplink shared channel. If a higher layer determines a beam failure based on an indication associated with the first set, the higher layer may request a new beam identification based on a third set. Similarly, the second set may be associated with a fourth set.All combinations in this paragraph and the next (including removal or addition of steps) are contemplated in a manner consistent with the rest of the detailed description.

[0290] The methods, systems and apparatus as described herein may, in particular, provide for measuring the radio link quality of one or more RSs in a third RS set from a first TRP. The methods, systems and apparatus as described herein may, in particular, provide for measuring the radio link quality of a fourth RS set from a second TRP. The methods, systems and apparatus as described herein may, in particular, provide for performing new beam identification based on the radio link quality of the third RS set and the radio link quality of the fourth RS set, wherein the radio link quality (e.g., the third or fourth set) may be based on RSRP. The methods, systems and apparatus as described herein may, in particular, provide for evaluating the measured radio link quality of one or more RSs in a first RS set; determining that the measured radio link quality of one or more RSs in the first RS set is below a threshold; and providing an indication to another layer that the radio link quality of one or more RSs in the first set is below the threshold. The radio link quality of the first RS set may be from a first TRP. The second RS set may be from a second TRP. The radio link quality of the first RS set or the radio link quality of the second RS set may be based on an assumed block error rate. All combinations of this paragraph and the above paragraphs (including removal or addition of steps) are considered in a manner consistent with other parts of the detailed description.

Claims

1. A user equipment comprising: The processor is configured to: a receive beam failure detection (BFD) configuration, wherein the BFD configuration indicates a first reference signal (RS) set and a second RS set, the first RS set being associated with a first transmit reception point (TRP) and the second RS set being associated with a second TRP, wherein the first TRP is associated with a first cell and the second TRP is associated with a second cell; determining whether a measurement associated with a first set of RSs associated with a first TRP is below a threshold associated with BFD; determining whether a measurement associated with a second set of RSs associated with a second TRP is below a threshold associated with BFD; as well as BFD is performed for the first TRP based on measurements associated with the first set of RSs being below a threshold associated with BFD, and BFD is performed for the second TRP based on measurements associated with the second set of RSs being below a threshold associated with BFD. 2 . The user equipment of claim 1 , wherein the processor is configured to measure radio link quality of the one or more RSs.

3. The user equipment of claim 1, wherein the processor is configured to request, by a medium access control layer, a physical layer to perform new beam identification based on the first RS set and the second RS set, wherein the physical layer periodically reports to the medium access control layer. 4 . The user equipment of claim 3 , wherein the processor is configured to count beam failure instance indications from the physical layer separately for each radio link. The user equipment of claim 1 , wherein the first cell and the second cell are the same. The user equipment of claim 1 , wherein the first cell is different from the second cell.

7. The user equipment of claim 1 , wherein the processor is configured to: A receive beam failure recovery (BFR) configuration is provided, wherein the BFR configuration includes one or more physical random access channel (PRACH) resources, and the one or more PRACH resources are associated with a third TRP.

8. The user equipment of claim 7, wherein the processor is configured to: One or more recovery search space identifiers are received, where the one or more recovery search space identifiers are configured by a control resource set (CORESET).

9. The user equipment of claim 7, wherein the processor is configured to: Based on detecting BFD for the first TRP or the second TRP, one or more contention free random access (CFRA) transmissions are initiated.

10. A method performed by a user equipment, the method comprising: a receive beam failure detection (BFD) configuration, wherein the BFD configuration indicates a first reference signal (RS) set and a second RS set, the first RS set being associated with a first transmit reception point (TRP) and the second RS set being associated with a second TRP, wherein the first TRP is associated with a first cell and the second TRP is associated with a second cell; determining whether a measurement associated with a first set of RSs associated with a first TRP is below a threshold associated with BFD; determining whether a measurement associated with a second set of RSs associated with a second TRP is below a threshold associated with BFD; as well as BFD is performed for the first TRP based on measurements associated with the first set of RSs being below a threshold associated with BFD, and BFD is performed for the second TRP based on measurements associated with the second set of RSs being below a threshold associated with BFD. The method of claim 10 , further comprising measuring radio link quality of the one or more RSs. 12 . The method of claim 10 , further comprising requesting, by a medium access control layer, a physical layer to perform new beam identification based on the first RS set and the second RS set, wherein the physical layer periodically reports to the medium access control layer.

13. The method of claim 12, further comprising counting beam failure instance indications from the physical layer separately for each radio link. The method of claim 10 , wherein the first cell and the second cell are the same. The method of claim 10 , wherein the first cell is different from the second cell.

16. The method of claim 10, further comprising: A receive beam failure recovery (BFR) configuration is provided, wherein the BFR configuration includes one or more physical random access channel (PRACH) resources, and the one or more PRACH resources are associated with a third TRP.

17. The method of claim 16, further comprising: One or more recovery search space identifiers are received, where the one or more recovery search space identifiers are configured by a control resource set (CORESET).

18. The method of claim 17, further comprising: Based on detecting BFD for the first TRP or the second TRP, one or more contention free random access (CFRA) transmissions are initiated.

Images