Beam Fault Detection and Recovery Using Multi-TRP and Multi-Panel Transmissions

Abstract

The method, system, and device may support BFD with multi-TRP transmission or BFR with multi-TRP transmission. For BFD with multi-TRP transmission, there may be explicit or implicit configuration. For BFR with multi-TRP transmission, there may be BFR with contention-free PRACH, BFR with PUCCH, BFR with contention-free 2-step RACH, or BFR with PUSCH.

Description

[Technical Field]

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 887,917, filed August 16, 2019, entitled "Beam Fault Detection and Recovery Using Multi-Trp and Multi-Panel Transmission," which is incorporated herein by reference in its entirety. [Background technology]

[0002] Massive Multiple Input Multiple Output (MIMO) systems are expected to enhance data throughput and reliability in future 5G systems. Multiple transmit / receive points (multiple TRPs) are crucial in 5G to improve reliability, coverage, and throughput through flexible deployment scenarios. For example, to support the exponential growth of mobile data traffic in 5G and enable coverage expansion, wireless devices are expected to access networks consisting of multiple TRPs (e.g., macrocells, small cells, picocells, femtocells, remote radio heads, relay nodes, etc.). Summary of the Invention [Problem to be solved by the invention]

[0003] Beam Failure Detection (BFD) and Beam Failure Recovery (BFR) may be on a per-cell basis, but not on a per-TRP / panel basis. BFR may be for an SpCell or BFR may be for an SCell. In the case of multi-TRP (per cell), even if the radio link to one TRP fails, the link to another TRP may still work, regardless of PCell or Scell. In scenarios with ideal or non-ideal backhaul, it may be preferable to support BFD and BFR on each of the multiple links with multi-TRP. [Means for solving the problem]

[0004] Specifically, methods, systems, and devices are disclosed herein that support BFD with multiple TRP transmission or BFR with multiple TRP transmission. For BFD with multiple TRP transmission, multiple options may exist, such as 1) explicit configuration of a beam-impairment resource set and a candidate beam Reference Signal (RS) list set, or 2) implicit configuration if the UE is not provided with an explicit beam-impairment resource set and a candidate beam RS list set. For BFR with multiple TRP transmission, multiple options may exist, such as 1) contention-free PRACH-based BFR, 2) PUCCH-based BFR, 3) contention-free 2-step RACH-based BFR, or 4) PUSCH-based BFR.

[0005] This Summary is presented to introduce a selection of concepts in a simplified form of the Detailed Description, which is further described below. This Summary is not intended to identify key or substantial features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Moreover, the claimed subject matter is not bound by any limitations, such as that it solves any or all of the disadvantages noted in any part of this disclosure. [Brief explanation of the drawings]

[0006] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which: [Figure 1] FIG. 1 illustrates an exemplary multi-TRP transmission. [Figure 2] FIG. 1 illustrates an exemplary multi-panel transmission. [Figure 3] FIG. 1 illustrates an exemplary UE using multi-TRP and multi-panel transmission. [Figure 4A]FIG. 1(a) illustrates an exemplary SCell configured with only DL. [Figure 4B] (b) An exemplary SCell configured for DL ​​and UL transmission. [Figure 5] FIG. 1 illustrates an exemplary TRP with which a CORESET ID may be associated. [Figure 6A] 1 illustrates an exemplary CC supporting two TRP transmissions; (a) an ideal backhaul; [Figure 6B] (b) An example CC supporting non-ideal backhaul and a UE with two TRP transmissions. [Figure 7A] FIG. 1 illustrates two exemplary CCs supporting two TRP transmissions; (a) an ideal backhaul; [Figure 7B] (b) A diagram showing a UE with two exemplary CCs supporting a non-ideal backhaul and two panels showing two TRP transmissions. [Figure 8] A diagram showing an exemplary failureDetectionResource set mapping relationship between CC and radio link / multi-TRP. [Figure 9] FIG. 1 illustrates an example method flow for implicit beam obstruction detection. [Figure 10] FIG. 1 illustrates an exemplary, well-defined configuration method for BFD operations. [Figure 11A] FIG. 1 illustrates two exemplary CCs (CC1 has DL and UL, while CC2 has only DL) using two TRP(a) ideal backhauls. [Figure 11B] FIG. 10 shows two exemplary CCs (CC1 has DL and UL, while CC2 has only DL) using two TRP (b) non-ideal backhauls and two panels. [Figure 12] FIG. 1 illustrates an exemplary BFR method. [Figure 13] A diagram showing an example CFRA transmission using BFR when the CC has both DL and UL. [Figure 14]A diagram showing an example CFRA transmission using BFR when multiple CCs have both DL and UL. [Figure 15] A diagram showing an example CFRA transmission using BFR when one CC has both DL and UL, but the other CC has only DL. [Figure 16] FIG. 1 illustrates exemplary PUCCH transmission opportunities for BFR when CC uses DL and UL ideal backhaul. [Figure 17] FIG. 10 illustrates exemplary PUCCH transmission opportunities for BFR when multiple (two) CCs use DL and UL ideal backhaul. [Figure 18] FIG. 1 illustrates exemplary PUCCH transmission opportunities for BFR when CC uses DL and UL non-ideal backhaul. [Figure 19] 1 illustrates exemplary PUCCH transmission opportunities for BFR when two CCs, CC1 with DL and UL and CC2 with only DL, use non-ideal backhaul between TRP1 and TRP2. The UE is equipped with two panels. [Figure 20] FIG. 10 illustrates an example two-step contention-free RACH for BFR of an SCell with DL only. [Figure 21] FIG. 10 illustrates exemplary MAC CE content of MsgA for BFR when SCell has only DL. [Figure 22] A diagram showing exemplary MAC CE contents of MsgA for BFR when SCell has both UL and DL. [Figure 23] FIG. 1 illustrates a BFR MAC CE using a 4-octet bitmap (legacy). [Figure 24] A diagram showing BFR MAC CE using a 4-octet bitmap including an L field. [Figure 25] A diagram showing BFR MAC CE using a 4-octet bitmap including an L field. [Figure 26]10A-10C illustrate example displays (e.g., graphical user interfaces) that may be generated based on methods, systems, and devices for beam failure detection and recovery using multi-TRP and multi-panel transmission. [Figure 27A] FIG. 1 illustrates an exemplary communication system. [Figure 27B] FIG. 1 illustrates an example system including a RAN and a core network. [Figure 27C] FIG. 1 illustrates an example system including a RAN and a core network. [Figure 27D] FIG. 1 illustrates an example system including a RAN and a core network. [Figure 27E] FIG. 10 illustrates another example of a communication system. [Figure 27F] 1 is a block diagram of an example apparatus or device such as a WTRU. [Figure 27G] FIG. 1 is a block diagram of an exemplary computing system. DETAILED DESCRIPTION OF THE INVENTION

[0007] Multi-TRP and Multi-Panel Transmission—It is recognized that improved diversity and robustness may be achieved through both ideal and non-ideal backhaul networks using multi-TRP and multi-panel transmission. A goal may be to make the TRP-UE links relatively independent, at least from a PHY perspective. For example, the UE multiplexes the A / N of the PDSCH from TRP1 for one PUCCH transmission, with the A / N being split per TRP.

[0008] Note that an ideal backhaul, such as a point-to-point connection using optical fiber, can enable very high throughput and very low latency between the TRP and the core network. An ideal backhaul is sometimes defined as latency of less than 2.5 microseconds and a throughput of 10 Gbps. Non-ideal backhauls, such as xDSL, microwave, and trunk networks, can result in significantly longer latency times in the network.

[0009] In a multi-TRP network, as shown in Figure 1, a UE may communicate with multiple TRPs. Typically, the TRPs are accessed by the UE on different beams. For non-ideal backhaul networks, non-coherent simultaneous transmissions from multiple TRPs may improve performance, especially at the edge of a TRP's coverage area. Simultaneous transmissions by multiple TRPs may improve both PDSCH and PDCCH performance.

[0010] Multi-panel deployments may 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 deployments may also be supported in a UE. Additionally, the term "panel" may refer to a panel (e.g., an antenna array) of a UE.

[0011] It is known that multi-panel transmission, in which a UE may transmit from multiple panels (transmissions from panels may be coherent or non-coherent), improves spectral efficiency. The concept of multi-panel transmission is shown in Figure 2. Because each UE panel may be assumed to have a different directionality, the best beam or TRP for reception may be different for each UE panel. The UE may determine the best TRP or beam for a given panel based on measurements and feed that information back to the network, which can then determine which beam or TRP should be used for PUCCH / PUSCH reception. Each panel-TRP link can be considered an independent link, so no coordination between UE panels is required.

[0012] Multi-TRP PDSCH Transmission - Traditionally, codeword transmission over multiple layers over the same time-frequency resources may be supported in DL and UL. Codewords (CWs) may be transmitted from different TRPs via independent beams. Therefore, the CW or DMRS ports per layer may have different QCL assumptions. However, in non-ideal backhaul networks where latency is a concern, it may be desirable to operate TRPs independently whenever possible, rather than relying on simultaneous transmissions.

[0013] Therefore, a goal of wireless communications is to enable extension of downlink and uplink signaling for multi-TRP and multi-panel transmissions.

[0014] A procedure to support multi-TRP PDSCH transmissions is considered, along with individual HARQ ACK codebooks per TRP, so that the UE can separately recognize PDSCHs from different TRPs. Figure 3 shows an example in which a 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 may correspond to the same or different HARQ processes. An identifier may be used to associate the received PDSCH with the TRP that transmitted it, so that the UE can send an Ack corresponding to the desired TRP.

[0015] SCell configuration in NR - An SCell may be configured for downlink (DL) transmission only. In this case, UL may be transmitted only on the primary cell (PCell) for the UE. In another scenario, a serving cell (SCell) may have both uplink (UL) and DL for transmission. Figure 4A shows the case where only DL transmission is configured on the SCell, and (b) shows the case where both DL and UL transmissions are configured on the SCell. In Figure 4A, the UE transmits PUCCH / PSCCH via the PCell. In Figure 4B, the UE may transmit PUCCH / PSCCH or other physical channels, such as PRACH, on both the SCell and PCell.

[0016] 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 identified best candidate beam according to the RACH configuration provided by the RRC message PRACH-ResourceDedicatedBFR. In Rel-15, BFR may be done via a Contention-Free Random Access (CFRA) procedure.

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

[0018] JPEG0007745536000001.jpg68170

[0019] JPEG0007745536000002.jpg89170

[0020] CORESET associated with a TRP - Multi-TRP transmission, where one or more CORESETs in the PDCCH configuration correspond to one TRP. Thus, a CORESET Identification (ID) is bound to the TRP, and a PDSCH grant via the CORESET may be associated with that TRP. The A / N for that PDSCH is transmitted to that TRP. In this way, PUCCH transmission per TRP is supported. The association between CORESET ID and TRP ID in the PDCCH configuration is as depicted.

[0021] JPEG0007745536000003.jpg54170

[0022] JPEG0007745536000004.jpg37170

[0023] The TRP may determine a Tx beam for downlink transmission based on UE measurements on one or more Rx beams of the TRP via CSI-RS or SSB.

[0024] Parameters for UE Rx beam configuration for monitoring NR-PDCCH on multiple beam-pair links from multiple TRPs are configured by higher layer signaling, MAC CE, or considered in search space design. At a minimum, NR supports indication of spatial QCL assumptions between DL RS antenna ports and DL RS antenna ports for demodulation of DL control channels. Candidate signaling methods for beam indication for NR-PDCCH (e.g., configuration methods for monitoring NR-PDCCH) include MAC CE signaling, RRC signaling, DCI signaling, transparent or implicit methods according to specifications, and combinations of these signaling methods.

[0025] For reception of unicast DL data channels from multiple TRPs, NR supports indication of spatial QCL assumptions between DL RS antenna ports and DM-RS antenna ports of the DL data channel. Information indicating the RS antenna ports is indicated via DCI (downlink grant). The information indicates the DM-RS antenna ports and the RS antenna ports that are QCLs. Different sets of DM-RS antenna ports for the DL data channel may be indicated as QCLs with different sets of RS antenna ports.

[0026] (Beam obstruction detection using multi-TRP transmission) A BFD-UE using multiple TRP transmission for a CC or multiple CCs may receive data from multiple TRPs for a CC or multiple CCs. In Figures 6A and 6B, a network (e.g., a gNB) may set up multiple (e.g., two) data links, and UE 200 may simultaneously receive data from a specific CC (PCell or SCell) through TRP1 201 and TRP2 202. However, depending on ideal or non-ideal backhaul between TRPs (e.g., TRP1 201 or TRP2 202), the network may provide multiple PDSCHs through a single DCI or multiple DCIs, as shown in Figure 6A, or multiple PDSCHs through multiple DCIs, as shown in Figure 6B.

[0027] 7A and 7B, the network may set up multiple (e.g., two) data links, where the UE 200 may simultaneously receive data from different CCs (PCells or SCells) through TRP1 201 and TRP2 202. CC1 may be a PCell and CC2 may be an SCell, or vice versa.

[0028] JPEG0007745536000005.jpg57170

[0029] Explicit configuration, e.g., higher layers (RRC) configure reference signal resources (e.g., CSI-RS) for beam failure detection. In the case of a CC or multiple CCs with ideal and non-ideal backhaul (e.g., as shown in Figures 6 and 7), the following explicit configuration method for BFD operation can be applied.

[0030] JPEG0007745536000006.jpg116170

[0031] JPEG0007745536000007.jpg88170

[0032] JPEG0007745536000008.jpg80170

[0033] JPEG0007745536000009.jpg68170

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

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

[0036] JPEG0007745536000010.jpg29170

[0037] Different links (e.g., corresponding to different TRPs or sets of TRPs) may be associated with different CORESET pools, which can be distinguished by different CORESET pool indices, for example using the RRC parameter coresetPoolIndex-r16.

[0038] JPEG0007745536000011.jpg42170

[0039] JPEG0007745536000012.jpg22170

[0040] JPEG0007745536000013.jpg39170

[0041] JPEG0007745536000014.jpg53170

[0042] JPEG0007745536000015.jpg18170

[0043] JPEG0007745536000016.jpg36170

[0044] JPEG0007745536000017.jpg48170

[0045] JPEG0007745536000018.jpg65170

[0046] JPEG0007745536000019.jpg98170

[0047] 9 illustrates an exemplary method flow. As shown in FIG. 9, in step 210, multiple different CORESET pools (e.g., two) of serving cells may be configured in UE 200. In step 211, TCI descriptions of the CORESETs of the serving cells may be configured or indicated to UE 200. In step 212, a first set of BFD RSs may be implicitly determined from the RSs in the TCI descriptions of the CORESETs in the first CORESET pool. In step 213, UE 200 may implement BFD based on the first set of BFD RSs. In step 214, a second set of BFD RSs may be implicitly determined from the RSs in the TCI descriptions of the CORESETs in the second CORESET pool. In step 215, UE 200 may implement BFD based on the second set of BFD RSs.

[0048] In the case of multi-TRP transmission with CC or multi-CC ideal backhaul as shown in Figures 6A and 7A, respectively, a single DCI or multiple DCIs may be used to schedule multiple PDSCH receptions. In this case, if UE 200 is not provided with any (beam) failure detection resources from higher layers to monitor CSI-RS or SSB, UE 200 should use the RS set indicated by the TCI-state of each (single) CORESET used by UE 200 for monitoring PDCCH.

[0049] Single DCI scheduling for multi-TRP PDSCH is applicable, for example, in the following cases: · If the UE200 is configured with the higher layer parameter RepSchemeEnabler set to "FDMSchemeA", "FDMSchemeB", "TDMSchemeA", if the UE200 is indicated two TCI descriptions in the code position of the DCI field "Transmission Configuration Indication" and one DM-RS port in a CDM group in the DCI field "Antenna Port(s)". · If the UE 200 is configured by the higher layer parameter PDSCH-config indicating at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation.

[0050] For example, if the UE 200 is configured with the higher layer parameter PDCCH-Config indicating two different values ​​of CORESETPoolIndex in the ControlResourceSet, then multiple DCI scheduling of multi-TRP PDSCHs may be applicable.

[0051] The following description relates to BFD operation options when a single DCI is used to schedule multiple links of the CC shown in Figure 6A or multiple CCs shown in Figure 7A and is described in Table 1 below. [Table 1]

[0052] JPEG0007745536000021.jpg124170

[0053] JPEG0007745536000022.jpg139170

[0054] In the case of multi-TRP transmission with CC or multi-CC non-ideal backhaul as shown in Figures 6B and 7B, respectively, multiple PDCCHs / DCIs or separate PDCCHs / DCIs may be supported to schedule multiple PDSCH receptions. In this case, UE 200 may be provided with multiple / separate PDCCHs with multiple links, so that UE 200 can independently map DCIs in the CORESET to each link without ambiguity.

[0055] In this case, BFD operation with implicit configuration can use the same disclosed approach as multi-TRP transmission with CC or multi-CC ideal backhaul. Furthermore, it is necessary to clarify which TCI description configured in CORESET is the default QCL assumption for PDSCH.

[0056] JPEG0007745536000023.jpg48170

[0057] JPEG0007745536000024.jpg32170

[0058] JPEG0007745536000025.jpg33170

[0059] JPEG0007745536000026.jpg69170

[0060] JPEG0007745536000027.jpg31170

[0061] JPEG0007745536000028.jpg28170

[0062] JPEG0007745536000029.jpg24170

[0063] JPEG0007745536000030.jpg99170

[0064] With the foregoing in mind, FIG. 10 presents an exemplary UE physical layer procedure flow. In step 220, for BWP, a first set of RSs and a second set of RSs for BFD are configured in the UE 200. A first RS of the first set of RSs is transmitted from the first TRP 201. A second RS of the second set of RSs is transmitted from the second TRP 202. In step 221, for BWP, a third set of RSs and a fourth set of RSs for new beam identification (e.g., candidate beam) are configured in the UE 200. A third RS of the third set of RSs is transmitted from the first TRP 201. A fourth RS of the fourth set of RSs is transmitted from the second TRP 202. In step 222, if BWP is active, BFD is performed by the UE based on the first RS and the second RS. In step 223, if the radio link quality of some or all of the RSs in the first set is below a threshold, the physical layer provides an indication (e.g., a signal or message) of this to other layers, where the other layers are layers higher than the physical layer. If the radio link quality of some or all of the RSs in the second set is below a threshold, the physical layer indicates this to other layers at a specific period. In step 224, new beam identification is performed by the UE based on the third set of RSs or the fourth set of RSs, in response to a request from a layer (e.g., a layer higher than the physical layer).

[0065] Continuing to refer to FIG. 10 , the procedure (beam failure detection and recovery) may be distributed between two layers: PHY and MAC (higher layer). The procedure from step 220 to step 224 may be dominated by the PHY portion. Part of the MAC portion may include the following: In step 225, the MAC may receive PHY indications of radio link quality for the first or second link (e.g., the first and second links corresponding to the first and second sets of RSs). In step 226, based on receiving a certain number of PHY indications, the MAC may declare beam failure for the first or second link. In step 227, based on beam failure for the first link, the MAC may request the PHY to perform a new beam identification for the first link corresponding to the third set of RSs for the PHY. In step 228, based on beam failure for the second link, the MAC may request the PHY to perform a new beam indicator (NBI) for the second link corresponding to the fourth set of RSs for the PHY. It should be noted that although each layer is illustrated throughout as sending or receiving indications, etc., it is contemplated that other layers may send such indications.

[0066] JPEG0007745536000031.jpg68170 [Table 2-1] [Table 2-2]

[0067] (Beam obstruction request using multi-TRP transmission) To support multi-TRP transmission, the disclosed subject matter may support the use of PUCCH or CFRA for Beam Failure Recovery Request (BFRQ) transmission. During a BFR procedure, UE 200 may report only one (e.g., best) beam corresponding to a measured CSI-RS resource index (CRI) or synchronization signal block (SSB) resource index (SSBRI) only per TRP of a CC.

[0068] To support BFR with multi-TRP transmission for a CC or multiple CCs, the following options are possible: 1) BFR with contention-free PRACH, 2) BFR with PUCCH, 3) BFR with contention-free 2-step RACH, or 4) BFR with PUSCH.

[0069] The methods disclosed herein relate to methods for implementing BFR over UL signals (PRACH) / channels (PUCCH, PUSCH) using multi-panel transmission of a CC or multiple CCs and multi-TRP.

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

[0071] 6A and 6B, a UE 200 is shown that can be equipped with CC (with both DL and UL) using multiple TRPs with ideal and non-ideal backhauls, and multiple panels for BFR. In this case, the UE 200 may use a single DCI to schedule multiple links (e.g., from different TRPs) and a single UCI to concatenate UCIs to the multiple links (e.g., from different panels).

[0072] 7A and 7B, a UE 200 is shown that can be equipped with multiple CCs (with both DL and UL) using multiple TRPs with ideal and non-ideal backhauls, and multiple panels for BFR. In this case, the UE 200 may use multiple DCIs to schedule multiple links (e.g., from different TRPs) and multiple UCIs for multiple links (e.g., from different panels).

[0073] In the case where there is no UL transmission on a CC 204 (SCell) having only DL, for example, as shown in Figure 14, the UE 200 may transmit UCI on a CC having DL and UL (for example, a PCell). If the UE 200 is equipped with multiple panels for UL transmission, the multiple panels of the UE may be used to transmit multiple UCIs to the same TRP, as shown in Figure 11.

[0074] Contention-Free PRACH Using BFR - A Contention-Free PRACH (CFRA) may be used for Beam Failure Recovery Request (BFRQ). If DL and UL are configured on a CC, in this case PRACH transmission for BFR may be performed on the same CC. Depending on the number of links from multiple TRPs that may be supported on a CC, one or more PRACH resources may be configured by the same CC for BFR.

[0075] In the case of a CC that has only DL (e.g., an SCell), the CC cannot perform UL transmission, so CFRA-enabled BFR needs to be implemented in a CC that has both DL and UL.

[0076] BFRQ can be classified into several schemes, such as partial beam obstruction or complete beam obstruction. Regarding partial beam obstruction, in a multi-TRP transmission, the UE 200 may be configured with multiple links for simultaneous transmission. Therefore, in the case of partial beam obstruction, beam obstruction may occur, meaning that beam obstruction occurs among at least one, but not all, of the multiple links (from the multi-TRP). In this case, BFRQ may be implemented on the link without beam obstruction.

[0077] JPEG0007745536000034.jpg33170 [Table 3]

[0078] JPEG0007745536000036.jpg58170 [Table 4]

[0079] JPEG0007745536000038.jpg46170

[0080] JPEG0007745536000039.jpg38170

[0081] JPEG0007745536000040.jpg53170

[0082] JPEG0007745536000041.jpg46170

[0083] For example, it may be assumed that two DL and UL links are configured. For example, DL link 1 may be from TRP1 201 of CC 203, and DL link 2 may be from TRP2 202 of CC 204, as shown in Figure 7A or 7B, respectively. In addition, UE 200 may be equipped with two panels, for example, UL link 1 to TRP1 201 of CC 203 and UL link 2 to TRP2 202 of CC 204, respectively. CFRA-based BFR in this scenario is depicted in Figure 14.

[0084] However, if only DL is configured on a CC as shown in Figure 14, it may not be possible to configure UL transmission on the CC, and therefore CFRA transmission for BFR may be performed on PCells with DL and UL or their CCs.

[0085] JPEG0007745536000042.jpg130170

[0086] For example, it may be assumed that multiple (e.g., two) DL and UL links are configured. As shown in Figure 14, DL link 1 is from TRP1 201 of CC 203, and DL link 2 is from TRP2 202 of CC 204, respectively. However, CC 204 may be DL-only. In addition, UE 200 is equipped with two panels. Therefore, both UL links 1 and 2 are to TRP1 201 of CC 203. CFRA-based BFR in this scenario is depicted in Figure 15.

[0087] JPEG0007745536000043.jpg74170

[0088] JPEG0007745536000044.jpg38170

[0089] For beam failure reporting with multi-TRP transmission for CCs with both BFR-DL and UL, which may be transmitted via PUCCH / UCI, UE 200 may be configured with 1) PUCCH or PRACH BFR resources, or 2) both PUCCH and PRACH. In the case of both PUCCH and PRACH, if both PUCCH and PRACH are configured, both PUCCH resources for BFR or PRACH resources for BFR may be used whenever possible, and which resources to use for BFR may be up to the UE implementation.

[0090] JPEG0007745536000045.jpg16170

[0091] Dedicated PUCCH resources for PUCCH opportunities may 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, starting 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. As shown in Figures 11A or 11B, dedicated PUCCH transmission opportunities may be configured for BFR with PUCCH. For BFR with PUCCH, the gNB may configure periodic PUCCH resources for BFRQ transmission. However, if there is no BFR in a PUCCH opportunity, UCI / PUCCH transmission may not occur.

[0092] In the case of prioritization, the priority rule of UCI may be specified as BFR>HARQ-ACK / SR>Periodical CSI (P-CSI).

[0093] JPEG0007745536000046.jpg59170

[0094] JPEG0007745536000047.jpg57170

[0095] JPEG0007745536000048.jpg37170

number

[0096] JPEG0007745536000050.jpg17170

number

[0097] JPEG0007745536000052.jpg39170

[0098] Like the BFR use case with CFRA, BFR with PUCCH resources may rely on one or more of the following deployment cases: For the first deployment case of multi-TRP transmission with CC or multi-CC ideal backhaul as shown in Figures 6A and 7A, respectively, a single DCI may be used to schedule multiple PDSCH receptions. In this case, dedicated PUCCH transmission opportunities for multiple links (from multiple TRPs) may be used, and the link / TRP ID may be indicated by the DM-RS for the BFR PUCCH.

[0099] JPEG0007745536000053.jpg47170

[0100] JPEG0007745536000054.jpg18170

[0101] In a fourth scenario for multi-TRP transmission with CC or multi-CC non-ideal backhaul as shown in Figures 6B and 7B, respectively, multi / dedicated DCI may be used to schedule multiple PDSCH receptions. In this case, separate dedicated PUCCH transmission opportunities for BFR on the CC may be configured in the UE 200. These separate dedicated PUCCH transmission opportunities may be based on overlapping time-frequency via TDM, FDM, or SDM.

[0102] In a fifth scenario, if the SCell has only DL, the BFR PUCCH may be configured on the PCell. The BFR PUCCH resources may be configured based on ideal or non-ideal backhaul during the TRP.

[0103] JPEG0007745536000055.jpg52170

[0104] For example, it may be assumed that multiple DL and UL links are configured. As shown in FIG. 7A, DL link 1 is from TRP1 201 of CC 203, and DL link 2 is from TRP2 202 of CC 204, respectively, with an ideal backhaul between TRP1 201 and TRP2 202. In addition, UE 200 is equipped with two panels, e.g., UL link 1 to TRP1 201 of CC 203 and UL link 2 to TRP2 202 of CC 204, respectively. For this scenario, PUCCH-using BFR is depicted in FIG. 17. In this case, BFR transmission using PUCCH may be transmitted on UL CC 203, and the link / TRP ID may be distinguished by the DM-RS for BFR PUCCH. Therefore, only CC 203 may be configured to use PUCCH for BFR.

[0105] JPEG0007745536000056.jpg53170

[0106] For example, as shown in Figure B, CC203 is configured with multiple PUCCHs, and CC204's DL link 1 is from TRP1 201 and DL link 2 is from TRP2 202, and it may be assumed that there is a non-ideal backhaul between TRP1 201 and TRP2 202. However, CC204 only has DL. In addition, UE 200 may be equipped with two PUCCHs, for example, UL link 1 of CC203 to TRP1 201 and UL link 2 of CC204 to TRP2 202, respectively. BFR using PUCCH in this example is shown in Figure 19. BFR PUCCH1 and BFR PUCCH2 are separate. In this case, it may be assumed that BFR PUCCH1 and BFR PUCCH2 are based on TDM.

[0107] During the BFR procedure, the UE 200 may report the best measured quality (e.g., RSRP) of the CRI or SSBRI from a set of configured CSI-RS or SSB indices per CC (note that the CSI-RS or SSB indices may be based on explicit or implicit configuration). The uplink control information (UCI) carrying the CRI for BFR is presented in Table 5 (order of an example mapping of CSI fields for a report with CRI or SSBRI for BFR).

[0108] The UCI carrying the CRI / SSBRI for BSR may be used in use cases such as 1) a single CC with multi-TRP / panel transmission as shown in Figure 6A or 6B, or 2) multiple CCs with multi-TRP / panel transmission as shown in Figure 7A or 7B. [Table 5]

[0109] JPEG0007745536000058.jpg32170

[0110] JPEG0007745536000059.jpg42170

[0111] The following method may be used for contention-free two-step RACH for BFR on the PCell.

[0112] JPEG0007745536000060.jpg58170

[0113] For contention-free two-step RACH using BFR on an SCell with only DL, there may be a one-to-one mapping between contention-free PRACH preambles and PUSCH resource unit (PRU) units. When MsgA transmission is performed, the DMRS port or DMRS sequence may be implicitly indicated to the physical layer. Alternatively, the DMRS port or DMRS sequence may be implicitly determined by the physical layer based on the selected RA preamble.

[0114] For example, as shown in Figure 11B, multiple DL and UL links may be configured for CC203, and DL link 1 of CC204 may be from TRP1 201 and DL link 2 may be from TRP2 202, and it may be assumed that there is a non-ideal backhaul between TRP1 201 and TRP2 202. However, CC204 may only have DL. In addition, UE200 may be equipped with two panels, for example, UL link 1 of CC203 to TRP1 201 and UL link 2 of CC204 to TRP2 202, respectively.

[0115] An example of the configuration of FIG. 11B, a contention-free two-step RACH for BFR, is depicted in FIG. 20. In this example, UE 200 may configure a timing offset between the PRACH preamble and MsgA. Note that this timing offset may be set to zero, e.g., the PRACH preamble and PUSCH may be transmitted in the same slot for TDM or FDM. To transmit the contention-free two-step RACH for BFR on the PCell, UE 200 automatically determines the UL spatial relationship of the PRACH and PUSCH transmissions, e.g., based on the factor that the TCI description is the same as the lowest CORESET ID that UE 200 can monitor on the PCell.

[0116] JPEG0007745536000061.jpg109170

[0117] JPEG0007745536000062.jpg24170

[0118] JPEG0007745536000063.jpg48170

[0119] JPEG0007745536000064.jpg33170

[0120] However, a two-step RACH may be beneficial for use cases where an SCell is configured for only DL. If an SCell is configured for both DL and UL, it can transmit those failed links without the assistance of other cells. Therefore, those failed link indexes may be omitted in the MAC CE payload. Therefore, the MAC CE content can be reduced as shown in Figure 22.

[0121] The failed CC index, new beam information (if any), or beam failure event will be reported by a single report by the PUSCH-using BFR-MAC CE. In this case, the MAC CE's resources may be triggered by a dedicated PUCCH or PRACH for BFR. Since the failed CC index, new beam information, or CORESET ID may be reported by a single report by the MAC-CE without a dedicated PUCCH or PRACH for BFR, the SCell-BFR delay may be large and uncontrollable by the gNB. This may be because the gNB may not schedule a PUSCH transmission immediately when a normal SR is received, as is typically the case. In this case, for example, the following use cases may be considered:

[0122] The first use case is BFR on some SCells with only DL: If there are available resources for BFR and PUSCH transmission on the PCell, the disclosed MsgA content may be carried by a regular PUSCH without using a contention-free RACH or a two-step RACH approach for BFR.

[0123] JPEG0007745536000065.jpg33170

[0124] JPEG0007745536000066.jpg25170

[0125] JPEG0007745536000067.jpg22170

[0126] Regarding UL Panel ID indication, the UL Panel ID may be conveyed via the DM-RS for the PUSCH or explicitly signaled in the PUSCH payload.

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

[0128] For example, consider the MAC CE of FIG. 23, which includes an exemplary 4-octet bitmap indicating beam or non-beam failure of a cell or link.

[0129] C m The field indicates beam failure detection and the presence of an octet containing the AC field for the serving cell with, for example, ServCellIndex m. C set to 1 m The AC field indicates that a beam failure has been detected and that an octet containing the AC field is present for the serving cell with ServCellIndex m. m The field indicates that no beam obstruction is detected and that the octet containing the AC field is not present for the serving cell with ServCellIndex m. The octets containing the AC field are present in ascending order based on ServCellIndex.

[0130] In this example, 32 serving cells or links may be shown, e.g., with 16 serving cells, each cell may be considered to have two links.

[0131] In one example, C0 and C1 indicate the first link (e.g., i=0) and the second link (e.g., i=1), respectively, of the first cell (e.g., the serving cell with the lowest index ServCellIndex 0). The next fields C2 and C3 indicate the first link and the second link, respectively, of the second cell, etc.

[0132] In various examples, different serving cells have different numbers of configured links. If the total number of links with low serving cell indices and the number of links with low link indices of serving cell k is m-1, then C m may denote link i of cell k. C0 may denote the first link of the serving cell with the lowest index.

[0133] In another example, C0, C1, ..., C 15 indicate the first links of serving cells 0, ..., 15, respectively. C 16 , C 17 ,...C 31 indicate the secondary links of serving cells 0, ..., 15, respectively.

[0134] In various examples, different serving cells have different numbers of configured links. If m is less than M (where M is the highest serving cell index for this MAC entity), then C m may denote the first link cell m. If m is greater than M, then C m may indicate the second link in a cell that has more than one link configured.

[0135] JPEG0007745536000068.jpg49170

[0136] C mIn an example where the field indicates beam failure detection and the presence of an octet including an AC field for the serving cell with ServCellIndex m, the octet including the AC field may also include a link field (L) as shown in FIG. 24. For example, if a single link is configured for the corresponding serving cell, the AC octet includes a 1-bit R (reserved, set to 0) field, as shown in FIG. 23. On the other hand, if multiple links, e.g., two links, are configured for the corresponding serving cell, the L field may indicate whether the next AC octet corresponds to the same cell but a different link. For example, if L=0, the next AC octet corresponds to the next serving cell with a beam failure indicated by its C field. If L=1, the next AC octet corresponds to another link with a beam failure detected for the same serving cell. Note that if different links are associated with different sets of candidate RSs, the index of the failed link may be removed from the candidate RS ID by the network. In some cases, AC octets corresponding to different links of a serving cell are arranged in link index order. In that case, even if the AC field is set to 0 and one or more links of the same serving cell fail and are included in the MAC CE, the network may remove the failed link. In one example, when the AC field is set to 0 (e.g., there is no corresponding candidate RS ID), one or more of the reserved bits (otherwise used for the candidate RS ID) are used to indicate the corresponding link index. This can resolve ambiguity about the failed link when there is no corresponding candidate RS ID.

[0137] JPEG0007745536000069.jpg83170

[0138] Table 6 contains exemplary abbreviations and definitions for the subject matter disclosed herein. [Table 6-1] [Table 6-2] [Table 6-3]

[0139] It should be understood that the entities performing the steps set forth herein may be logical entities, such as those shown in Figures 1-20. These steps may be stored in a memory of, and executed by, a processor of, a device, server, or computer system, such as those shown in Figures 27C-27G. Omission of steps, combination of steps, or addition of steps is contemplated among the example methods disclosed herein.

[0140] 26 illustrates an example display (e.g., a graphical user interface) that may be generated based on the methods, systems, and devices for beam failure detection and recovery using multi-TRP and multi-panel transmission as discussed herein. A display interface 901 (e.g., a touchscreen display) may provide text related to beam failure detection and recovery using multi-TRP and multi-panel transmission in block 902, such as BFD- or BFR-related parameters, method flow, and associated current status. Progress of any of the steps discussed herein (e.g., message transmission or step success) may be displayed in block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be the geometry of a device implementing the methods, systems, and devices for beam failure detection and recovery using multi-TRP and multi-panel transmission, a graphical output of the progress of any method or system discussed herein, etc.

[0141] The 3rd Generation Partnership Project (3GPP®) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities (including those affecting coding / decoding, 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, and New Radio (NR), also referred to as "5G." 3GPP NR standard development continues and is expected to include the specification of next-generation radio access technologies (new RATs), which are expected to include new flexible radio access provisions below 7 GHz and new ultra-mobile broadband radio access provisions above 7 GHz. Flexible radio access is envisioned to consist of new, non-backward compatible radio access in new frequency bands below 6 GHz and to include different operating modes that may be multiplexed together in the same frequency band to address a broad set of 3GPP NR use cases with diverse requirements. Ultra mobile broadband is envisioned to include cmWave and mmWave frequency bands, offering opportunities for ultra mobile broadband access, for example, for indoor applications and hotspots. In particular, ultra mobile broadband is envisioned to share a common design framework with flexible radio access below 7 GHz, with cmWave and mmWave specific design optimizations.

[0142] 3GPP has identified various use cases that NR is expected to support, resulting in different user experience requirements for data rate, latency, and mobility. Broad categories of use cases include enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low-Latency Communications (URLLC), Massive Machine-Type Communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy efficiency), and enhanced Vehicle-To-Everything (eV2X) communications, which may include any of the following: Vehicle-to-Vehicle Communications (V2V), Vehicle-to-Infrastructure Communications (V2I), Vehicle-to-Network Communications (V2N), Vehicle-to-Pedestrian Communications (V2P), and vehicle communications with other entities. Specific services and applications in these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based office, emergency responder connectivity, automotive e-calls, disaster alerts, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics, and aerial drones, to name a few. All of these use cases and others are contemplated herein.

[0143] 27A illustrates an example of a communication system 100 in which methods and apparatus for beam failure detection and recovery using multi-TRP and multi-panel transmission, such as the systems and methods described and claimed herein and shown in FIGS. 1-20, may be used. The communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (which may refer generally or collectively to one or more 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, an IoT service, video streaming, or edge computing.

[0144] 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. Although each WTRU 102a, 102b, 102c, 102d, 102e, 102f, or 102g is depicted in Figures 27A, 27B, 27C, 27D, 27E, and 27F as a handheld wireless communication device, it will be understood that in various possible use cases for 5G wireless communication, each WTRU may comprise or be implemented in any type of apparatus or device 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 telephone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronics product, a wearable device such as a smart watch or smart clothing, a medical or e-health device, a robot, industrial equipment, a drone, or a vehicle such as a car, bus, truck, train, or airplane.

[0145] The communications system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 27A, 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 interconnecting 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 and facilitate access to one or more communications networks, such as the core network 106 / 107 / 109, the Internet 110, the network services 113, or other networks 112. Similarly, the base station 114b may be any type of device configured to interface wired or wirelessly with at least one of the remote radio heads (RRHs) 118a, 118b, the transmit / receive points (TRPs) 119a, 119b, or the roadside units (RSUs) 120a and 120b and facilitate access to one or more communication networks, such as the core networks 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 interface wirelessly with at least one of the WTRUs 102, e.g., the WTRU 102c, and facilitate access to one or more communication networks, such as the core networks 106 / 107 / 109, the Internet 110, the network services 113, or other networks 112.

[0146] The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d and facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the 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 and facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, or the 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 (gNode B), a satellite, a site controller, an Access Point (AP), a wireless router, etc.

[0147] The base station 114a may be part of the 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), or a relay node. Similarly, the base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations or network elements (not shown), such as a BSC, an RNC, or a relay node. The base station 114a may be configured to transmit or receive wireless signals within a particular geographic area (not shown), which may also be referred to as a cell. Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a particular geographic area (not shown), which may also be referred to as a cell (not shown) for the beam failure detection and recovery methods, systems, and devices using multi-TRP and multi-panel transmission as disclosed herein. Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a particular geographic area (not shown), which may also be referred to as a cell. 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 one example, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In one example, the base station 114a may employ multiple-input multiple-output (MIMO) technology and thus utilize multiple transceivers for each sector of the cell.

[0148] 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, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0149] The base station 114b may communicate with one or more of the RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b through a wired or air interface 115b / 116b / 117b, which may 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, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).

[0150] 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 an 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, centimeter wave, millimeter wave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).

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

[0152] The communications 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, and so on. For example, the base station 114a and WTRUs 102a, 102b, and 102c in the RAN 103 / 104 / 105, or the RRHs 118a, 118b, TRPs 119a, 119b and RSUs 120a, 120b and WTRUs 102c, 102d, 102e, and 102f in the RAN 103b / 104b / 105b, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS), Universal Terrestrial Radio Access (UTRA), or the like, thereby enabling Wideband CDMA (WCDMA) to be used 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).

[0153] In one example, the base station 114a and the WTRUs 102a, 102b, and 102c, or the RRHs 118a, 118b, TRPs 119a, 119b, or the RSUs 120a, 120b and the WTRUs 102c, 102d in the RANs 103b / 104b / 105b, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), thereby establishing the air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively, using Long Term Evolution (LTE) or LTE-Advanced (LTE-A). In the future, the air interfaces 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 (e.g., sidelink communications). Similarly, 3GPP NR technologies may include NR V2X technologies and interfaces (e.g., sidelink communications).

[0154] The base station 114a and the WTRUs 102a, 102b, 102c, and 102g in the RANs 103 / 104 / 105, or the RRHs 118a, 118b, TRPs 119a, 119b, and RSUs 120a, 120b, and the WTRUs 102c, 102d, 102e, and 102f in the RANs 103b / 104b / 105b, may be connected to a wireless LAN (WAN) or a wireless LAN (LAN) using a standard such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, or Interim Standard 2000. Wireless technologies such as IS-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), and GSM EDGE (GERAN) may be implemented.

[0155] 27A may be a wireless router, a Home Node B, a Home eNode B, or an access point and may utilize any suitable RAT for implementing the beam failure detection and recovery methods, systems, and devices using multi-TRP and multi-panel transmissions as disclosed herein to facilitate wireless connectivity within a local area, such as a business, home, vehicle, train, aircraft, satellite, manufacturing plant, campus, etc. In one example, the base station 114c and the WTRU 102, e.g., the WTRU 102e, may implement a wireless 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 wireless 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., the WTRU 102e, may establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.). As shown in FIG. 27A, the base station 114c may have a direct connection to the Internet 110. Thus, the base station 114c may not need to access the Internet 110 through the core network 106 / 107 / 109.

[0156] The RAN 103 / 104 / 105 or RAN 103b / 104b / 105b may communicate with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, application, 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, prepaid calling, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or perform high-level security functions such as user authentication.

[0157] 27A, it will be understood that the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or core network 106 / 107 / 109 may communicate directly or indirectly with other RANs employing 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 E-UTRA radio technology, the core network 106 / 107 / 109 may also communicate with another RAN (not shown) employing GSM or NR radio technology.

[0158] 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 providing 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), the User Datagram Protocol (UDP), and the Internet Protocol (IP) of 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, network 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 that may employ the same RAT as RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or a different RAT.

[0159] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may have multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers that communicate with different wireless networks over different wireless links to implement the beam failure detection and recovery methods, systems, and devices using multi-TRP and multi-panel transmissions disclosed herein. For example, the WTRU 102g shown in FIG. 27A may be configured to communicate with a base station 114a, which may employ a cellular-based wireless technology, and with a base station 114c, which may employ an IEEE 802.11 wireless technology.

[0160] Although not shown in FIG. 27A , it will be understood that the user terminal may make 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 should be understood that much of the subject matter contained herein may equally apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, ideas applied to the air interfaces 115, 116, 117 and 115c / 116c / 117c may equally apply to wired connections.

[0161] FIG. 27B is a system diagram of an example RAN 103 and core network 106 that may implement the methods, systems, and devices for beam failure detection and recovery using multi-TRP and multi-panel transmission 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. As shown in FIG. 27B, the RAN 103 may include Node-Bs 140a, 140b, and 140c, each of which may include one or more transceivers, for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. Each of the Node-Bs 140a, 140b, and 140c may 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).

[0162] As shown in Figure 27B, Node-Bs 140a and 140b may communicate with RNC 142a. Additionally, Node-B 140c may communicate with RNC 142b. Node-Bs 140a, 140b, and 140c may communicate with corresponding RNCs 142a and 142b via an Iub interface. RNCs 142a and 142b may communicate with each other via an Iur interface. Each of RNCs 142a and 142b may be configured to control its respective connected Node-Bs 140a, 140b, and 140c. Additionally, each of RNCs 142a and 142b may 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, etc.

[0163] The core network 106 shown in Figure 27B 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. Although each of the above elements is depicted as part of the core network 106, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator.

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

[0165] The RNC 142a in the RAN 103 may also be connected to an SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to a GGSN 150. The SGSN 148 and 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.

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

[0167] 27C is a system diagram of an example RAN 104 and core network 107 that may implement the beam failure detection and recovery methods, systems, and devices using multi-TRP and multi-panel transmission disclosed herein. As described above, the RAN 104 may employ E-UTRA radio technology and communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also communicate with the core network 107.

[0168] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, although it will be understood 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, the eNode-B 160a may use multiple antennas to transmit wireless signals to and receive wireless signals from the WTRU 102a, for example.

[0169] 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, scheduling of users on the uplink or downlink, etc. As shown in FIG. 27C, the eNode-Bs 160a, 160b, and 160c may communicate with each other over an X2 interface.

[0170] The core network 107 shown in Figure 27C may include a Mobility Management Gateway (MME) 162, a Serving Gateway 164, and a Packet Data Network (PDN) Gateway 166. Although each of the above elements is depicted as part of the core network 107, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator.

[0171] 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 function 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 specific serving gateway during initial attach of the WTRUs 102a, 102b, and 102c, etc. 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.

[0172] 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 / 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, and managing and storing the context of the WTRUs 102a, 102b, and 102c.

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

[0174] 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, and may facilitate communications between the WTRUs 102a, 102b, and 102c and traditional terrestrial communications devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves 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 networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0175] 27D is a system diagram of an example RAN 105 and core network 109 that may implement the methods, systems, and devices for beam failure detection and recovery using multi-TRP and multi-panel transmission disclosed herein. The RAN 105 may employ NR radio technology and communicate with the WTRUs 102a and 102b over an air interface 117. The RAN 105 may also communicate with the core network 109. A Non-3GPP Interworking Function (N3IWF) 199 may employ non-3GPP radio technology and communicate with the WTRU 102c over an air interface 198. The N3IWF 199 may also communicate with the core network 109.

[0176] The RAN 105 may include gNode-Bs 180a and 180b. It will be understood 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 an integrated access and backhaul connection 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, the gNode-B 180a may use multiple antennas, for example, to transmit wireless signals to and receive wireless signals from the WTRU 102a. It should be understood that the RAN 105 may employ other types of base stations, such as eNode-Bs. It will also be understood that the RAN 105 may employ more than one type of base station. For example, a RAN may employ eNode-Bs and gNode-Bs.

[0177] 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 an 802.11 protocol.

[0178] 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, scheduling of users on the uplink or downlink, etc. As shown in FIG. 27D, the gNode-Bs 180a and 180b may communicate with each other, for example, over an Xn interface.

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

[0180] In the example of Figure 27D, the 5G core network 109 may include an Access and Mobility Management Function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPF) 176a and 176b, a User Data Management Function (UDM) 197, an Authentication Server Function (AUSF) 190, a Network Exposure Function (NEF) 196, a Policy Control Function (PCF) 184, a Non-3GPP Interworking Function (N3IWF) 199, and a User Data Repository (UDR) 178. While each of the above elements is depicted as part of the 5G core network 109, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator. It will be understood that the 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements. Although each network function is shown in Figure 27D as connecting directly to each other, it should be understood that they may communicate through a routing agent, such as a Diameter routing agent or message bus.

[0181] In the example of Figure 27D, connectivity between network functions is achieved through a set of interfaces or reference points. It will be appreciated that network functions may be modeled, described, or implemented as a set of services that are invoked or invoked by other network functions or services. Invocation of network function services may be achieved through direct connections between network functions, messaging exchanges on a message bus, or software function invocations.

[0182] The AMF 172 may be connected to the RAN 105 via an N2 interface and may function 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 delivering 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 shown in FIG. 27D.

[0183] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly, the SMF may be connected to the PCF 184 via an N7 interface and to the UPFs 176a and 176b via an N4 interface. The SMF 174 may function 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, managing and configuring rules for directing traffic in the UPFs 176a and 176b, and generating downlink data notifications to the AMF 172.

[0184] 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 type of network that exchanges packets of data. The UPF 176a and UPF 176b may receive rules for directing traffic from the SMF 174 via the N4 interface. The UPF 176a and UPF 176b may provide access to the packet data network by connecting to the packet data network using the N6 interface or by connecting to each other and to other UPFs using the N9 interface. In addition to providing access to the packet data network, the UPF 176 may be responsible for packet routing and forwarding, policy rule enforcement, quality of service management for user plane traffic, and buffering of downlink packets.

[0185] The AMF 172 may also be connected 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 an air interface technology that is not 3GPP specified. The AMF may interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0186] The PCF 184 may be connected to the SMF 174 via an N7 interface, to the AMF 172 via an N15 interface, and to the Application Function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not shown in FIG. 27D. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and the SMF 174 so that each control plane node can enforce these rules. The PCF 184 may send policies intended for the WTRUs 102a, 102b, and 102c to the AMF 172, which may then distribute 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.

[0187] The UDR 178 serves as a repository of authentication credentials and subscription information. The UDR may connect to a network function so that the network function can add to, read from, or modify data in the repository. For example, the UDR 178 may connect to the PCF 184 via an N36 interface. Similarly, the UDR 178 may connect to the NEF 196 via an N37 interface and to the UDM 197 via an N35 interface.

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

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

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

[0191] The application functions 188 may interact with network functions within the 5G core network 109. The interaction between the application functions 188 and the network functions may be 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 may be deployed by a company that has a business relationship with the mobile network operator.

[0192] Network slicing is a mechanism that may be used by mobile network operators to support one or more "virtual" core networks behind the operator's air interface. It involves "slicing" the core network into one or more virtual networks to support different service types operating across different RANs, or even a single RAN. Network slicing allows operators to create customized networks to provide optimized solutions for different market scenarios that demand diverse requirements in functionality, performance, and independence, for example.

[0193] 3GPP has designed the 5G core network to support network slicing. Network slicing is a good tool that network operators can use to support a diverse set of 5G use cases (e.g., large-scale IoT, critical communications, V2X, and enhanced mobile broadband), which are highly diverse and often demanding. Without the use of network slicing techniques, where each use case has its own unique set of performance, scalability, and availability requirements, the network architecture may not be flexible and scalable enough to efficiently support a wide range of use case needs. Furthermore, the introduction of new network services must be more efficient.

[0194] Referring again to FIG. 27D , in a network slicing scenario, the WTRU 102a, 102b, or 102c may connect to the AMF 172 via an N1 interface. The AMF may be logically part of one or more slices. The AMF may coordinate connectivity 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. If they are part of different slices, they may be isolated from each other in that they may utilize different computing resources, security credentials, etc.

[0195] The core network 109 may facilitate communications with other networks. For example, the core network 109 may include or 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 communicate with a short message service (SMS) service center that facilitates communications via 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 the server or application function 188. Additionally, 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.

[0196] It should be understood that while the core network entities described herein and illustrated in Figures 27A, 27C, 27D, or 27E are identified by names given to those entities in certain existing 3GPP specifications, in the future, those entities and functions may be identified by other names, and that certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Accordingly, it should be understood that the specific network entities and functions described and illustrated in Figures 27A, 27B, 27C, 27D, or 27E are provided by way of example only, and that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or defined in the future.

[0197] 27E illustrates an example of a communication system 111 in which systems, methods, and apparatuses implementing beam failure detection and recovery using multi-TRP and multi-panel transmission described herein may be used. The communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, and F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein may apply to any number of WTRUs, base stations gNBs, V2X networks, or other network elements. One, some, or all of WTRUs A, B, C, D, E, and F may be outside the range of access network coverage 131. Among WTRUs A, B, and C in a V2X group, WTRU A is the group leader, and WTRUs B and C are group members.

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

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

[0200] 27F is a block diagram of an example apparatus or device WTRU 102 that may be configured for wireless communication and operation in accordance with systems, methods, and apparatuses implementing beam failure detection and recovery with multi-TRP and multi-panel transmission, described herein, such as the WTRU 102 (e.g., UE) of FIG. 27A, 27B, 27C, 27D, or 27E, or of FIGs. 1-20. As shown in FIG. 27F, 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 / indicators 128, non-removable memory 130, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It should be understood that the WTRU 102 may comprise any subcombination of the above-described elements. Also, the base stations 114a and 114b, or nodes which may refer to the base stations 114a and 114b, such as, but not limited to, a base transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home Node-B, an evolved home Node-B (eNode-B), 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 some or all of the elements depicted in FIG. 27F and may be example implementations for carrying out the disclosed systems and methods for beam failure detection and recovery using multi-TRP and multi-panel transmissions described herein.

[0201] The processor 118 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, 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. While FIG. 27F depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0202] The transmit / receive element 122 of the UE may be configured to transmit or receive signals to or from a base station (e.g., base station 114a in FIG. 27A) over the air interface 115 / 116 / 117 or to another UE over 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 light signals. It will be understood that the transmit / receive element 122 may be configured to transmit or receive any combination of wireless or wired signals.

[0203] 27F depicts the transmit / receive element 122 as a single element, 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) to transmit and receive wireless signals over the air interface 115 / 116 / 117.

[0204] 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 mentioned 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.

[0205] The processor 118 of the WTRU 102 may be coupled to and receive user input data from a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a Liquid Crystal Display (LCD) display device or an Organic Light-Emitting Diode (OLED) display device). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, or the display / touchpad / indicator 128. Additionally, 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, etc. The processor 118 may access information and store data in memory that is not physically located on the WTRU 102, such as a server hosted on a cloud or edge computing platform, or in a home computer (not shown). The processor 118, in some examples described herein, may be configured to control a lighting pattern, image, or color on a display or indicator 128 depending on whether the setup of the beam fault detection and recovery using multi-TRP and multi-panel transmission was successful or failed, or to indicate the status of the beam fault detection and recovery using multi-TRP and multi-panel transmission and associated components.The control of lighting patterns, images, or colors on the display or indicator 128 may reflect the status of any of the method flows or components of each figure (e.g., FIGS. 1-25, etc.) shown or discussed herein. Messages and procedures for beam failure detection and recovery using multi-TRP and multi-panel transmission are disclosed herein. The messages and procedures may be extended to provide an interface / API for a user via an input source (e.g., speaker / microphone 124, keypad 126, or display / touchpad / indicator 128) to request resources and, among other things, to request, configure, or query beam failure detection and recovery using multi-TRP and multi-panel transmission related information that may be displayed on the display 128.

[0206] The processor 118 may obtain power from the power source 134 and may be configured to distribute or control power to other components within the WTRU 102. The power source 134 may be any suitable device that provides power to the WTRU 102. For example, the power source 134 may include one or more dry cells, solar cells, fuel cells, etc.

[0207] The processor 118 may also be coupled to a 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 instead 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 may determine its location based on the timing of signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by any suitable location method.

[0208] The processor 118 may further 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 an accelerometer, a biometric (e.g., fingerprint) sensor, an e-compass, a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port or other interconnection interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a Frequency Modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, etc.

[0209] The WTRU 102 may be included in other apparatus or devices, such as a sensor, a consumer electronics product, a wearable device such as a smart watch or smart clothing, a medical or e-health device, a robot, industrial equipment, a drone, or a vehicle such as a car, truck, train, or airplane. The WTRU 102 may connect to other components, modules, or systems of such an apparatus or device via one or more interconnection interfaces, such as an interconnection interface that may comprise one of the peripherals 138.

[0210] FIG. 27G is a block diagram of an exemplary computing system 90 that may be embodied in one or more devices of the communications networks shown in FIGS. 27A, 27C, 27D, and 27E, such as certain nodes or functional entities within the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, other networks 112, or network services 113, and beam failure detection and recovery using multi-TRP and multi-panel transmission, such as the systems and methods shown in FIGS. 1 through 20 and described or claimed herein. The computing system 90 may include a computer or server and may be primarily controlled by computer-readable instructions, which may be in the form of software (wherever or however such software is stored or accessed). Such computer-readable instructions may be executed within a processor 91 to operate the computing system 90. The 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, etc. The processor 91 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the computing system 90 to operate within a communications network. The coprocessor 81 is an optional processor distinct from the main processor 91 and may perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 may receive, generate, and process data, e.g., RRC IEs, related to the methods and apparatus described herein for beam failure detection and recovery using multi-TRP and multi-panel transmission.

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

[0212] Memories coupled to the system bus 80 include random access memory (RAM) 82 and read-only memory (ROM) 93. Such memories include circuits that enable information to be stored and read. ROM 93 generally contains stored data that cannot be easily modified. Data stored in RAM 82 may be read or changed by the processor 91 or other hardware devices. Access to RAM 82 or ROM 93 may be controlled by a memory controller 92. The memory controller 92 may provide an address translation function that converts virtual addresses to physical addresses when instructions are executed. The memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in the first mode may only access memory mapped by its own process virtual address space and cannot access memory in the virtual address space of another process unless memory sharing between processes is configured.

[0213] Additionally, computing system 90 may include a peripheral controller 83 responsible for communicating instructions from processor 91 to peripheral devices such as printer 94 , keyboard 84 , mouse 95 and disk drive 85 .

[0214] The display 86, controlled by the display controller 96, is used to display 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 with a CRT-based video display, an LCD-based flat-panel display, a gas plasma-based flat-panel display, or a touch panel. The display controller 96 contains the electronic components necessary to generate the video signal that is sent to the display 86.

[0215] Additionally, computing system 90 may include communications circuitry, such as, for example, a wireless or wired network adapter 97, that may be used to connect computing system 90 to external communications networks or devices, such as RAN 103 / 104 / 105 of Figure 27A, 27B, 27C, 27D, or 27E, core networks 106 / 107 / 109, PSTN 108, the Internet 110, WTRU 102, or other networks 112, to enable computing system 90 to communicate with other nodes or functional entities in those networks. Communications circuitry may be used alone or in combination with processor 91 to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.

[0216] It should be understood that any or all of the devices, systems, methods, and processes described herein may be embodied 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 may be implemented in the form of such computer-executable instructions and executed by the processor of a device or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile media, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storage of information, although 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, magnetic cassettes, magnetic tape, magnetic disk storage devices or other magnetic storage devices, or any other tangible or physical medium that may be used to store the desired information and that may be accessed by a computing system.

[0217] In describing the preferred method, system, or apparatus of the disclosed subject matter of beam fault detection and recovery using multi-TRP and multi-panel transmission, as shown in the figures, specific terminology is used for the sake of clarity, however, it is understood that the claimed subject matter is not intended to be limited to such selected specific terminology, and that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose.

[0218] The various techniques described herein may be implemented in conjunction with hardware, firmware, software, or combinations thereof, where appropriate. Such hardware, firmware, and software may reside in apparatus located at various nodes of a communications network. The apparatuses may operate alone or in conjunction with each other to perform the methods described herein. As used herein, the terms "apparatus," "network apparatus," "node," "device," "network node," etc. may be used interchangeably. Additionally, the word "or" is used throughout this specification inclusively unless otherwise specified. As referred to herein, "best"

[0219] This specification uses examples to disclose the invention, including the best mode, and to enable any person skilled in the art to practice the invention, including making and using any device or system and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples (e.g., omitting steps, combining steps, or adding steps between each exemplary method disclosed herein) that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal words of the claims, or if they include equivalent structural elements with insignificant differences from the literal words of the claims.

[0220] JPEG0007745536000073.jpg159170

[0221] JPEG0007745536000074.jpg80170

[0222] The methods, systems, and devices described herein may, among other things, provide means for configuring (detecting) a first set of reference signals (RSs) and a second set of RSs for beam failure detection (BFD), configuring (detecting) a third set of RSs and a fourth set of RSs for new beam identification, and implementing BFD based on the radio link quality of the first set of RSs or the radio link quality of the second set of RSs when a bandwidth part (BWP) is active. The methods, systems, and devices described herein may, among other things, provide means for receiving a first RS of the first set of RSs from a first TRP and a second RS of the second set of RSs from a second TRP. The radio link quality of the first set of RSs or the radio link quality of the second set of RSs may be based on reference signal received power (RSRP) or reference signal received quality (RSRQ). The radio link quality of the first set of RSs may be from the first TRP, and the radio link quality of the second set of RSs is from the second TRP. The methods, systems, and devices described herein may, among other things, provide means for receiving radio link qualities of one or more RSs in a first set of RSs and, based on the radio link qualities of a first threshold number of one or more RSs in the first set falling below a radio link quality threshold, providing an indication to another layer of the radio link qualities of at least the RSs in the first set of RSs. The indication may be provided by a physical layer. The methods, systems, and devices described herein may, among other things, provide means for receiving radio link qualities of one or more RSs in the first set of RSs and, based on the radio link qualities of a second threshold number of one or more RSs in the second set falling below a radio link quality threshold, providing an indication to another layer of the radio link qualities of at least the RSs in the second set of RSs. The methods, systems, and devices described herein may, among other things, provide means for receiving a third RS in a third set of RSs from a first TRP and a fourth RS in a fourth set of RSs from a second TRP.The methods, systems, and devices described herein may, among other things, provide means for receiving radio link qualities for a third set of RSs from a first TRP and for receiving radio link qualities for a fourth set of RSs from a second TRP. The methods, systems, and devices described herein may, among other things, provide means for performing new beam identification based on the radio link qualities for the third set of RSs or the radio link qualities for the fourth set of RSs reaching one or more thresholds upon request (e.g., in response to a request). The methods, systems, and devices described herein may, among other things, provide means for the MAC layer to request the PHY layer to perform new beam identification for the first link corresponding to the third set of RSs of the PHY based on an indication of beam failure for the first link (e.g., NBI based on the third set). The beam failure recovery request may be received through a physical random access channel, a physical uplink control channel, or a physical uplink shared channel. If the higher layer determines beam failure based on an indication associated with the first set, the higher layer may request new beam identification based on the third set. Similarly, the second set may be associated with the fourth set. All combinations (including omissions or additions of steps) in this and the following paragraphs of the specification are contemplated in a manner consistent with the rest of the detailed description.

[0223] The methods, systems, and devices described herein may, among other things, provide means for measuring the radio link quality of one or more RSs in a third set of RSs from a first TRP. The methods, systems, and devices described herein may, among other things, provide means for measuring the radio link quality of a fourth set of RSs from a second TRP. The methods, systems, and devices described herein may, among other things, provide means for performing new beam identification based on the radio link quality of the third set of RSs and the radio link quality of the fourth set of RSs, where the radio link quality (e.g., the third or fourth set) may be based on the RSRP. The methods, systems, and devices described herein may, among other things, provide means for evaluating the measured radio link quality of one or more RSs in the first set of RSs, determining whether the measured radio link quality of one or more RSs in the first set of RSs 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 set of RSs may be from a first TRP. The second set of RSs may be from a second TRP. The radio link quality of the first set of RSs or the radio link quality of the second set of RSs may be based on a virtual block error rate. All combinations (including omissions or additions of steps) in this and the above specification paragraphs are contemplated in a manner consistent with other parts of the detailed description.

Claims

1. 1. A user terminal comprising a processor, The processor: receiving a beam failure detection (BFD) configuration, the BFD configuration indicating a first set of reference signals (RSs) associated with a first transmission reception point (TRP) and a second set of RSs associated with a second TRP, where 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 the first set of RSs associated with the first TRP is below a threshold associated with BFD; determining whether a measurement associated with a second set of RSs associated with the second TRP is below the threshold associated with BFD; performing BFD of the first TRP based on the measurements associated with the first set of RSs being below the threshold associated with BFD, and performing BFD of the second TRP based on the measurements associated with the second set of RSs being below the threshold associated with BFD; receiving a beam failure recovery (BFR) configuration, the BFR configuration including one or more physical random access channel (PRACH) resources, the one or more PRACH resources being associated with a third TRP; and receiving one or more recovery search space identifications, the one or more recovery search space identifications configured according to a control resource set (CORESET); a user terminal configured to:

2. The user terminal of claim 1 , wherein the processor is configured to measure a radio link quality of one or more RSs of the first set of RSs or the second set of RSs.

3. The user terminal of claim 1 , wherein the first cell and the second cell are the same.

4. The user terminal of claim 1 , wherein the first cell is different from the second cell.

5. 2. The user terminal of claim 1, wherein the processor is configured to initiate one or more contention-free random access (CFRA) transmissions based on a BFD detected in the first TRP or the second TRP.

6. A method executed by a user terminal, comprising: receiving a beam failure detection (BFD) configuration, the BFD configuration indicating a first set of reference signals (RSs) associated with a first transmission reception point (TRP) and a second set of RSs associated with a second TRP, where 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 the first set of RSs associated with the first TRP is below a threshold associated with BFD; determining whether a measurement associated with a second set of RSs associated with the second TRP is below the threshold associated with BFD; performing BFD of the first TRP based on the measurements associated with the first set of RSs being below the threshold associated with BFD, and performing BFD of the second TRP based on the measurements associated with the second set of RSs being below the threshold associated with BFD; receiving a beam failure recovery (BFR) configuration, the BFR configuration including one or more physical random access channel (PRACH) resources, the one or more PRACH resources being associated with a third TRP; and receiving one or more recovery search space identifications, the one or more recovery search space identifications configured according to a control resource set (CORESET); A method comprising:

7. The method of claim 6 , further comprising measuring radio link quality of one or more RSs of the first set of RSs or the second set of RSs.

8. The method of claim 6 , wherein the first cell and the second cell are the same.

9. The method of claim 6 , wherein the first cell is different from the second cell.

10. 10. A computer readable storage medium having stored thereon a computer program, the computer program being loadable into a data processing unit and adapted to cause the data processing unit to perform the method steps of any one of claims 6 to 9 when executed by the data processing unit.

Images