WO2022155514A1

WO2022155514A1 - Enhanced detection and recovery for beam failure for multi-transmission points

Info

Publication number: WO2022155514A1
Application number: PCT/US2022/012592
Authority: WO
Inventors: Alexei Davydov; Bishwarup Mondal; Avik SENGUPTA
Original assignee: Intel Corporation
Priority date: 2021-01-15
Filing date: 2022-01-14
Publication date: 2022-07-21

Abstract

This disclosure describes systems, methods, and devices related to detecting beam failure communicating with multiple transmission reception points (TRPs). A device may identify first beam failure detection resources associated with a first beam used by the device to communicate with a first TRP and second beam failure detection resources associated with a second beam used by the device to communicate with a second TRP at a first time; determine, based on the first beam failure detection resources and the second beam failure detection resources, a beam failure of the first beam at the first time while the second beam is active at the first time; and send, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time.

Description

ENHANCED DETECTION AND RECOVERY FOR BEAM FAILURE FOR MULTI¬

TRANSMISSION POINTS

CROSS-REFERENCE TO RELATED PATENT APPLICATION(S)

This application claims the benefit of U.S. Provisional Application No. 63/138,230, filed January 15, 2021, the disclosure of which is incorporated by reference as set forth in foil.

TECHNICAL FIELD

This disclosure generally relates to systems and methods for wireless communications and, more particularly, to detecting and recovering from beam failure.

BACKGROUND

Wireless devices are becoming widely prevalent and are increasingly using wireless channels. The 3^rd Generation Partnership Program (3GPP) is developing one or more standards for wireless communications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example environment and beam recovery process with multiple transmission reception points (multi-TRPs) in which a user equipment device (UE) may communicate simultaneously with multiple TRPs, in accordance with one or more example embodiment s of the present disclosure.

FIG. 2 illustrates an example multi-TRP environment and beam recovery process in which one TRP may communicate with multiple antenna panels of the UE of FIG. 1, in accordance with one or more example embodiments of the present disclosure.

FIG. 3 illustrates example an example multi-TRP environment with small cross-beam interference, in accordance with one or more example embodiments of the present disclosure.

FIG. 4 illustrates example an example multi-TRP environment with large cross-beam interference, in accordance with one or more example embodiments of the present disclosure.

FIG. 5 illustrates a flow diagram of illustrative process for multi-TRP beam failure detection and recovery, in accordance with one or more example embodiments of the present disclosure.

FIG, 6 illustrates a network, in accordance with one or more example embodiments of the present disclosure. FIG. 7 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure.

FIG. 8 is a block diagram illustrating components, in accordance with one or more example embodiments of the present disclosure.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

For cellular telecommunications, the 3^rd Generation Partnership Program (3GPP) define communication techniques, including for beam failure detection and for the use of multiple transmission reception points (multi-TRPs). Multi-TRPs may refer to when a user equipment device (UE) is connected to multiple transmission reception points (e.g., antenna panels of devices at a network side) using different respective antenna beams (e.g., each beam having an antenna direction).

The 3GPP standards define techniques for devices to detect when a beam failure occurs. For example, a device’s physical layer (PHY) (e.g., of the communication stack) may detect when a signal using a particular beam is weak enough, and the device’s medium access control (MAC) layer of the communication stack may maintain a count of how many times the beam’s signal is weak enough during a time period. When the beam’s signal is weak enough for a certain number of times within the time period, such may indicate a beam failure, which may trigger a beam recovery process also defined by the 3GPP standards.

For example, multiple non-collocated TRPs (e.g., separate devices at the network side) may be in communication with a same UE, each TRP using a different beam with the UE. Any of the beams from the TRPs may be active or may fail at the same time, so one beam from one TRP to the UE may fail while another beam from the other TRP to the UE may remain active. Current techniques allow for beam failure recovery (BFR) only when both TRPs connected to the UE (e.g., both of the TRP beams) fail.

Therefore, enhanced beam failure detection and recovery may be beneficial for multi-

TRPs. In one or more embodiments, to enable TRP-specific beam failure detection resources (BFD), the multiple sets of BFD resources for the multi-TRPs may be identified (e.g., using a failureDetectionResources parameter). failureDetecRonResources is not configured, a current default cell-specific BFD may be implemented. The maximum number of BFD- reference signals (RS) per bandwidth part (BWP) may be increased. In this manner, instead of current techniques using one BFD set for any number of TRPs, each TRP may have a BFD set (e.g., two BFDs associated with two TRPs) to allow for TRP-specific BFD resources.

In addition, in Rel-15 NR, control resource set (CORESET) is defined as a set of resource element groups (REGs) with one or more symbol duration. In one or more embodiments, a UE may be configured with CORESETs, and each CORESET may be associated with one or more TRPs, and multiple CORESETs may be associated with the same TRP. A CORESET may be configured with a CORESET-subset-index having a value k, where k=1,...,nTRP. The UE may determine the BFD RS set q0(k) to include a periodic channel state information CSI-RS resource configuration resource configuration indices with the same values as the RS indices in the RS sets indicated by a transmission configuration indicator TCI- state for each CORESET configured with a CORESET-subset-index having the value k, and when there are two RS indices in a TCI state, the set q0(k) may include RS indices configured with qc1-Type set to “typeD” for the corresponding TCI states. The UE may expect the set q0(k) to include up to two RS indices, and may expect a single port RS in the set q0(k). The PHY layer in the UE may address the radio link quality according to the set q0(k) of resource configurations against the threshold Qout,LR. In this manner, the UE may distinguish between BFD resources from different CORESETS.

In one or more embodiments, to enable TRP specific candidate beam failure recovery/replacement (CBD), two sets of CBD resources may be identified representing TRP- 1 and TRP-2 using the parameter candidaateBeamRSSCellList-r 16 as used for SCell (secondary cell) BFR. For example, current techniques may use one CBD set for any number of TRPs, each TRP may have a CBD set (e.g., two CBDs may be associated with two TRPs) to allow for TRP-specific CBD. CBD resources associated with a dedicated physical random access channel (PRACH) may be identified in a TRP-specific manner as well. A UE may be provided for each BWP of a serving cell, and may use a set q1(k) of periodic CSI-RS resource configuration indices and/or service set/ physical broadcast channel (SS/PBCH) block indices by candidateBeamR.SList, candidateBeamRSListExt, or candidaateBeamRSSCellLis for radio quality measurements on the BWP of the serving cell, k=1,...nTRP. The UE may expect a single-port or two-port (e.g., antenna ports) CSI-RS with a frequency density equal to one or three resource elements (REs) per resource block (RB) in the set ql(k).

In one or more embodiments, for the primary cell (PCell) or primary secondary cell (PSCell), upon request from higher layers in the communication stack, the UE may provide to its higher layers the periodic CSI-RS configuration indices and/or the SS/PBCH block indices from the set ql(k) and the corresponding L1-RSRP (layer 1 - reference signal received power) measurements that are larger than or equal to the Qin.LR threshold. For the secondary cell (SCell), upon request from higher layers, the UE may indicate to its higher layers whether there is at least one periodic CSI-RS configuration index and/or SS/PBCH block index from the set with corresponding LR-RSRP measurements larger than or equal to the Qin,LR threshold, and may provide the periodic CSI-RS configuration indices and/or the SS/PBCH block indices from theset and the corresponding L 1 -RSRP measurements that are larger than or equal to the Qin, ER threshold, if any. Each BFD RS set to q0(k) may be associated in a 1:1 manner with a candidate beam RS set ql(k), k=l,...,nTRP.

In one or more embodiments, instead of using one beam failure recovery request (BFRQ) for any number of TRPs, a UE may send a BFRQ for each TRP for which beam failure has been detected. In a given serving cell, if beam failure is observed in both TRP-1 and TRP- 2 BFD resources, the BFRQ procedure may follow the release- 15/16 (Rel- 15/16 standard) BFR procedure. When beam failure is observed on either TRP-1 or TRP-2 (e.g., one of the two TRPs, but not the other), the BFRQ may follow the Rel- 16 SCell BFR procedure including the following steps: (1) Transmitting a link recovery request (LRR, e.g., reused from SCell BFR) over a dedicated SR-like physical uplink control channel (PUCCH) resource (e.g., PUCCH- BFR). When a UE is able to identify an existing uplink grant for the TRP that has not failed, this step can be skipped. (2) MAC-CE reports details: when at least one new beam is identified for the failed TRP, the UE may report only the one new beam with a corresponding beam index, otherwise the UE may report no new beam identified and a failed TRP index.

In one or more embodiments, a PUCCH SR resource may be associated with each TRP, and may be implemented by configuring nTRP PUCCH resources, PUCCH-Resourceld(k), k=1,...,nTRP configured as part of a SchedulmgRequestResourceConfig associated with a MAC~CellGroupConfig BFR function. The PUCCH-Resourceld(k) may be associated in a 1 : 1 manner with BFD RS set q0(k), k=1,...,nTRP. The The PUCCH-Resourceld(k) may be associated in a 1 : 1 manner with BFD RS set q0(k) and a candidate beam RS set ql(k), k^:: =1... ,nTRP. For example:

SchedulingRequestResourceConfig ::= SEQUENCE { schedulingRequestResourceld SchedulingRequestResourceld, schedulingRequestID SchedulingRequestld, periodicity AndOffset CHOICE { sym2 NULL, sym6or7 NULL, sI1 NULL. — Recurs in every slot sI2 INTEGER (0..1), sl4 INTEGER (0..3), sI5 INTEGER (0..4), sI8 INTEGER (0..7), sI10 INTEGER (0..9), sI16 INTEGER (0..15), sI20 INTEGER (0. 19), sI40 INTEGER (0..39), sI80 INTEGER (0..79), sI160 INTEGER (0..159), sl320 INTEGER (0..319), sI640 INTEGER (0..639) } OPTIONAL, - Need M resource Pl JCCH-Resourceldl , PUCCH-Resourceld2,..., PUCCH-Resourceld-nTRP, OPTIONAL - Need M }

In one or more embodiments, a PUCCH-resource corresponding to PUCCH- Resourceld(k) may be associated with a spatial-relation-info. If beam failure is detected from BFD RS set q0(k), PUCCH-SR may be selected from PUCCH-Resourceld(j) where j#k. As an example, if beam failure is detected from BFD RS set q0(0), PUCCH-SR may be selected from PUCCH-Resourceld(l) and vice-versa. If beam failure is detected from BFD RS set q0(k), PUCCH-SR may be selected from PUCCH-Resourceld(j) where j#k. The PUCCH- Resourceld(j) may be selected such that L1-RSRP/L1-SINR measured from candidate beam RS set q l(j) is the maximum from all j-fk. If beam failure is detected from all BFD RS set q0(k), k=1,...,nTRP, in a PCell or a PSCell, UE proceeds with dedicated RACH provided by PRACH-ResourceDedicatedBFR which may be a configuration for a PRACH transmission.

In one or more embodiments, the enhancements herein may allow a UE to be aware that certain transmit beams are associated with the same panel/TRP and may not be suitable for multi-TRP operation. This can be achieved by grouping SSB indices into two mutually exclusive groups, which can be sufficient to also partition the associated quasi co-locationed (QCL-ed) CSI-RS resources. When groupBasedBeamReporting is enabled in a CSI- ReportConfig, the associated CSl-ResourceConfig may include two CSI-SSB-ResourceSets, each representing a TRP/panel. A CSI-SSB-ResourceSet representing TRP- 1 also may act as a resource for NZP-IM for the CSI-SSB-ResourceSet representing TRP-2. When groupBasedBeamReporting is enabled in a CSI-ReportConfig, the associated CSI- ResourceConfig may include two CSI-SSB-ResourceSets, each representing a TRP/panel.

In one or more embodiments, aUE may need to indicate which beams have good quality metrics. In some current techniques, the UE selects the best beams from one set of beams. However, when there are multiple sets of beams (e.g., for multi-TRPs), the UE may consider interference between the CSI of multiple sets of beams. If groupBasedBeamReporting is enabled, the UE may report CRI-1 and CRI-2 (e.g., CSI indicators) in a single reporting instance for both the cases of single Rx beam or two Rx beams. In both cases, it is possible that a high value of L1-RSRP is observed for both CRI-1 and CRI-2. However, significant crossbeam interference may be expected and may not be suitable for mTRP reception. Due to the lack of consideration of cross-beam interference, current groupBasedBeamReporting may not be sufficient for a 5^th Generation radio node (gNB) to make a determination of beam-pairs for mTRP scheduling.

In one or more embodiments, in a multi-TRP environment, a UE may need to consider both L1-RSRP and inter-beam interference for determining the simultaneous reception criteria and ranking the beam pairs for groupBasedBeamReporting. Enabling groipBasedBeamReporting implies an mTRP (multi-TRP) reception hypothesis -- in particular, this impacts the following UE behaviors: L1-RSRP reporting is based on reception from the selected best UE Rx panel (and not based on reception due to multiple panels), and reported Ll-SINR includes interference due to the other reported beam-pair. In this manner, the UE may include inter-beam interference (e.g., L1-SINR) in a report to a gNB. The Ll- SINR metric may distinguish from the measuring of interference of a single beam (e.g., allowing for a measurement of inter-beam interference).

In one or more embodiments, enabling groupBasedBeamReporting. or using some other indication, implies an mTRP (simultaneous) reception hypothesis (e.g., the UE may simultaneously receive from both TRPs of a multi-TRP environment). This means: a) Ll- RSRP reported is based on reception from the selected best UE Rx panel (and not based on reception due to multiple panels); and b) Ll-SINR reported includes interference due to the other reported beam-pair.

In one or more embodiments, disabling groupBasedBeamReporting or by some other indication implies an sTRP (simultaneous TRP) reception hypothesis (e.g., the same TRP uses both UE antenna panels) --- in particular, this impacts the following UE behaviors: reported Ll- RSRP may be based on reception from one or more Rx panels, and reported Ll-SINR includes interference due to other cells.

In one or more embodiments, disabling groupBasedBeamReporting implies an sTRP reception hypothesis. This means a) reported L1-RSRP may be based on reception from one or more Rx panels, and b) reported Ll-SINR includes interference due to other cells.

In one or more embodiments, the gNB response may follow SCell BFR (e.g., Rel-16). The BFRR process may use MAC-CE of a BFRQ, which may be a normal uplink grant to schedule a new transmission for the same hybrid automatic repeat request (HARQ) process identifier as a PUSCH that carries the MAC-CE. When a UE receives the uplink grant from the gNB, the BFR procedure may be considered complete.

The above descriptions are for purposes of illustration and are not meant to be limi ting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.

FIG . 1 illustrates an example environment 100 and beam recovery process with multiple transmission reception points (multi-TRPs) in which a user equipment device (UE) may communicate simultaneously with multiple TRPs, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG, 1, multiple TRPs (e.g., TRP 102 and TRP 104) may communicate with a UE device 106. In particular, the UE device 106 may have multiple beamforming pairs with the TRPs: beam 108 with the TRP 102, and beam 110 w ith the TRP 104. However, any of the beams may fail at some point (e.g., may have a signal strength below a threshold or other CSI that does not satisfy signal quality criteria). As shown, beam 110 may fail while beam 108 is still actively used by the UE 106 and the TRP 102. When beam failure occurs, the UE may implement a process 150 to detect the beam failure and to recover the failed beam. In particular, the process 150 may include step 152 in which the UE 106 monitors the beams from the multi-TRPs using BFD resources specific to each beam. CORESETS may allow the UE 106 to distinguish between BFD resources of the different sets of beams. When a beam fails (e.g., the beam 110 as shown), the UE 106 may monitor the CBDs of the different beams of the multi-TRPs to determine which of the beams can be used for recovery (e.g., as opposed to using one BFD for both TRPs and one CBD for both TRPs). At step 154, the UE 106 may perform a BFRQ procedure to recover the failed beam. For example, the LIE 106 may send a link recovery request (e.g., using a resource, such as a PUCCH resource, of the active beam) to recover the failed beam. In this manner, the UE 106 may use the active beam 108 with the TRP 102 even though the beam 110 with the TRP 104 has failed because the UE 106 may distinguish between the beams to detect which beam has failed.

In one or more embodiments, the UE 106 may need to consider both an L1-RSRP-1 for the TRP 102 and an L1-RSPR-2 for the TRP 104, and inter-beam interference for determining a simultaneous reception criteria and ranking the beam pairs for groupBasedBeamReporting. Use of the groupBasedBeamReporting may imply the mRTRP reception hypothesis.

FIG. 2 illustrates an example multi-TRP environment 200 and beam recovery process in which one TRP may communicate with multiple antenna panels of the UE 106 of FIG. 1, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG. 2, the TRP 102 uses the beam 108 and a beam 202 with the UE 106, and the L1-RSRP measurement may be based on the sTRP hypothesis (e.g., in which is disabled). The UE 106 may use a process 250 to detect the beam failure and to recover the failed beam. In particular, the process 250 may include step 252 in which the UE 106 monitors the beams from the multi-TRPs using BFD resources specific to each beam. CORESETS may allow the UE 106 to distinguish between BFD resources of the different sets of beams. When a beam fails (e.g., the beam 202 as shown), the UE 106 may monitor the CBDs of the different beams of the multi-TRPs to determine which beams can be used for recovery/replacement (e.g., as opposed to using one BFD for both TRPs and one CBD for both TRPs). At step 254, the UE 106 may perform a BFRQ procedure to recover the failed beam. For example, the UE 106 may send a link recovery request (e.g., using a resource, such as a PUCCH resource, of the active beam) to recover the failed beam. In this manner, the UE 106 may use the active beam 108 with the TRP 102 even though the beam 202 with the TRP 102 has failed because the UE 106 may distinguish between the beams to detect which beam has failed.

FIG. 3 illustrates example an example multi-TRP environment 300 with small crossbeam interference, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG. 3, the multi -TRP environment 300 may include the TRP 102 and the UE 106 communicating using the beam 108, and the TRP 104 and the UE 106 communicating using the beam 110. In the multi-TRP environment 300, two spatial domain Rx filters may be used by the UE 106, and there may be small cross-beam Interference between the beam 108 and the beam 110. When groupBasedBeamReporting is enabled, the UE 106 may report CRJ- 1 and CRI-2 in a single reporting instance.

FIG. 4 illustrates example an example multi-TRP environment 400 with large crossbeam interference, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG. 4, the multi-TRP environment 400 may include the TRP 102 and the UE 106 communicating using beam 402, and the TRP 104 and the UE 106 communicating using the beam 402. In the multi-TRP environment 300, one spatial domain Rx filter may be used by the LIE 106, and there may be large cross-beam interference. When groupBasedBeamReporting is enabled, the UE 106 may report. CRI-1 and CRI-2 in a single reporting instance.

Referring to FIGs. 3-4, it is possible that a high value of L1-RSRP may be observed for both CRI-1 and CRI-2. However, more cross-beam interference may be expected in FIG. 4 than in FIG. 3 and may not be suitable for mTRP reception. When the cross-beam interference is not considered, groupBasedBeamReporting reporting may not be sufficient for a gNB (e.g., TRP 102 or TRP 104) to determine beam-pairs for mTRP scheduling.

In one or more embodiments, the UE 106 of FIG. 1 may include any suitable processor- driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, the UE 106 may include, a. personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook^TM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (loT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a. DVB device, a relatively small computing device, a non-desktop computer, a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a. digital video disc (DVD) player, a. high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.

As used herein, the term “Internet of Things (loT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An loT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An loT device can have a particular set of attributes (e.g., a device state or status, such as whether the loT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a lightemitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, loT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the loT network. loT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the loT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).

Any of the UE 106 and the TRPs 102 and 104 of FIG. 1 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the UE 106 and the TRPs 102 and 104. Some non-limiting examples of suitable communications antennas include 3GPP antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the UE 106 and the TRPs 102 and 104.

It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

FIG. 5 illustrates a flow diagram of illustrative process 500 for multi-TRP beam failure detection and recovery, in accordance with one or more example embodiments of the present disclosure.

At block 502, a UE device (e.g., the UE 106 of FIG. 1, the UE 602 of FIG. 6) may identify first BFD resources for a first beam (e.g., the beam 108 of FIG. 1) used by the UE device to communicate with a first TRP (e.g., the TRP 102 of FIG. 1). The UE device may be a multi-TRP device, meaning that the UE device may communicate with multiple TRPs simultaneously. The UE device may use distinct BFD resources indexed for each set of beams used by a respective TRP, allowing the UE device to distinguish between BFD resources used by one TRP versus BFD resources used by another TRP. CORESET indices for the respective TRPs may be used to evaluate CSI for the respective beams, allowing the UE to determine the radio link quality for each beam set (e.g., BFD).

At block 504, the UE device may identify second BFD resources for a second beam (e.g., the beam 110 of FIG. 1) used by the UE device to communicate with a second TRP (e.g., the TRP 104 of FIG. 1). The UE device may distinguish between the BFD resources of the different beams by using different CORESET indices as explained above.

At block 506, the UE device may determine a first radio link quality for the first beam based on the first BFD resources. At block 508, the UE device may determine a second radio link quality for the second beam based on the second BFD resources. A CORESET is configured with a CORESET -subset-index taking value k, k:::l,...,nTRP. The UE determines the BFD RS set q0(k) to include periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by TCI- State for the each such CORESET configured with CORESET-subset-index taking value k and if there are two RS indexes in a TCI state, the set q0(k) includes RS indexes configured with qcl-Type set to 'typeD' for the corresponding TCI states. The UE expects the set q0(k) to include up to two RS indexes. The UE may expect a single port RS in the set q0(k).

At block 510, the UE device may detect a failure of the first beam based on the first radio link quality. At block 512, the UE device may determine that the second radio link quality is indicative of the second link remaining active (e.g., even when the first link has failed). The physical layer in the UE may assess the radio link quality according to the set q0(k) of resource configurations compared against the threshold Qout,LR. In order to enable TRP-specific CBD, we can consider identification of two sets of CBD resources representing TRP-1 and TRP-2 (candidateBeamRSSCellList-rl6) as used for SCell BFR. CBD resources associated with dedicated PRACH can be also identified in a TRP specific manner. A UE can be provided, for each BWP of a serving cell, a set ql(k) of periodic CSI-RS resource configuration indexes and/or SS/PBCH block indexes by candidateBeamRSList or candidateBeamRSList. Ext or candidateBeamRSSCellList for radio link quality measurements on the BWP of the serving cell, k=l,...,nTRP. The UE may expect a single-port or two-port CSI-RS with frequency density equal to one or three REs per RB in the set q1(k). For the PCell or the PSCell, upon request from higher layers, the UE provides to higher layers the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set ql(k) and the corresponding L1-RSRP measurements that are larger than or equal to the Qin, LR threshold. For the SCell, upon request from higher layers, the UE indicates to higher layers whether there is at least one periodic CSI- RS configuration index and/or SS/PBCH block index from the set with corresponding Ll- RSRP measurements that are larger than or equal to the Qin,LR. threshold, and provides the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set and the corresponding L1-RSRP measurements that are larger than or equal to the Qin,LR threshold, if any. Each BFD RS set q0(k) may be associated in a 1 : 1 manner with candidate beam RS set ql(k), k=1,...,nTRP.

At block 514, the UE device may generate and send a. radio link recovery request for the first beam while the second beam is active, and at block 516 may send a report indicating whether a new beam has been identified for the failed beam. When beam failure is observed on either TRP-1 or TRP-2 (e.g., one of the two TRPs, but not the other), the BFRQ may follow the Rel-16 SCell BFR procedure including the following steps: (1) Transmitting a link recoveryrequest (LRR, e.g., reused from SCell BFR) over a dedicated SR-like physical uplink control channel (PUCCH) resource (e.g., PUCCH-BFR). When a UE is able to identify an existing uplink grant for the TRP that has not failed, this step can be skipped. (2) MAC-CE reports details: when at least one new beam is identified for the failed TRP, the UE may report only the one new beam with a corresponding beam index, otherwise the UE may report no new beam identified and a failed TRP index.

The examples herein are not meant to be limiting.

FIG. 6 illustrates a network 600 in accordance with various embodiments. The network 600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection. The UE 602 may be communicatively coupled with the RAN 604 by a Uu interface. The UE 602 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, lo'T device, etc.

In some embodiments, the network 600 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 602 may additionally communicate with an AP 606 via an over-the-air connection. The AP 606 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 604. The connection between the UE 602 and the AP 606 may be consistent with any IEEE 802.1 1 protocol, wherein the AP 606 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 602, RAN 604, and AP 606 may utilize cellular-WLAN aggregation (for example, LWA/WIP). Cellular-WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WL AN resources.

The RAN 604 may include one or more access nodes, for example, AN 608. AN 608 may terminate air-interface protocols for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 608 may enable data/voice connectivity between CN 620 and the UE 602. In some embodiments, the AN 608 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In embodiments in which the RAN 604 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 604 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 602 with an air interface for network access. The UE 602 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 604. For example, the UE 602 and RAN 604 may use carrier aggregation to allow the UE 602 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/ second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 604 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 602 or AN 608 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that, provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/ software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/ WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. In some embodiments, the RAN 604 may be an LTE RAN 610 with eNBs, for example, eNB 612. The LTE RAN 610 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/d election at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 604 may be an NG-RAN 614 with gNBs, for example, gNB 616, or ng-eNB s, for example, ng-eNB 618. The gNB 616 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 616 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 618 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 616 and the ng-eNB 618 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, w'hich carries traffic data between the nodes of the NG-RAN 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN614 and an AMF 644 (e.g., N2 interface).

The NG-RAN 614 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 602 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 604 is communicatively coupled to CN 620 that includes network elements to provide various functions to support data and telecommunications services to customers/ subscribers (for example, users of UE 602). The components of the CN 620 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 620 onto physical compute/ storage resources in servers, switches, etc. A logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.

In some embodiments, the CN 620 may be an LTE CN 622, which may also be referred to as an EPC. The LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 622 may be briefly introduced as follows.

The MME 624 may implement mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation/ deactivation, handovers, gateway selection, authentication, etc.

The SGW 626 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 622, The SGW 626 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 628 may track a location of the UE 602 and perform security functions and access control. In addition, the SGSN 628 may perform mter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 624; MME selection for handovers; etc. The S3 reference point between the MME 624 and the SGSN 628 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.

The HSS 630 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 620. The PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application/content server 638. The PGW 632 may route data packets between the LTE CN 622 and the data network 636. The PGW 632 may be coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 632 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 632 and the data network 6 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 632 may be coupled with a PCRF 634 via a Gx reference point.

The PCRF 634 is the policy and charging control element of the LTE CN 622. The PCRF 634 may be communicatively coupled to the app/content server 638 to determine appropriate QoS and charging parameters for service flows. The PCRF 632 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 620 may be a 5GC 640. The 5GC 640 may include an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 640 may be briefly introduced as follows.

The AUSF 642 may store data for authentication of UE 602 and handle authentication- related functionality. The AUSF 642 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 640 over reference points as shown, the AUSF 642 may exhibit an Nausf service-based interface.

The AMF 644 may allow other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602, The AMF 644 may be responsible for registration management (for example, for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646, and act as a transparent proxy for routing SM messages. AMF 644 may also provide transport for SMS messages between UE 602 and an SMSF. AMF 644 may interact, with the AUSF 642 and the UE 602 to perform various security anchor and context management functions. Furthermore, AMF 644 may be a, termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 604 and the AMF 644; and the AMF 644 may be a termination poin t of NAS (N1) signaling, and perform N AS ciphering and integrity protection. AMF 644 may also support NAS signaling with the UE 602 over an N3 IWF interface.

The SMF 646 may be responsible for SM (for example, session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 to route traffic to proper destination, termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawfi.il intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 644 over N2 to AN 608; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 602 and the data network 636.

The UPF 648 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 636, and a branching point to support multi-homed PDU session. The UPF 648 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow' mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 648 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 650 may select a set of network slice instances serving the UE 602. The NSSF 650 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 650 may also determine the AMF set to be used to serve the UE 602, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 654. The selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 with which the UE 602 is registered by interacting with the NSSF 650, which may lead to a change of AMF. The NSSF 650 may interact with the AMF 644 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 650 may exhibit an Nnssf service-based interface.

The NEF 652 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 660), edge computing or fog computing systems, etc. In such embodiments, the NEF 652 may authenticate, authorize, or throttle the AFs. NEF 652 may also translate information exchanged with the AF 660 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 652 may exhibit an Nnef service-based interface.

The NRF 654 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 654 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 654 may exhibit the Nnrf service-based interface.

The PCF 656 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658. In addition to communicating with functions over reference points as shown, the PCF 656 exhibit an Npcf service-based interface.

The UDM 658 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644. The UDM 658 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652. The Nudr sendee-based interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 658 may exhibit the Nudtn service-based interface.

The AF 660 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 640 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to data network 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660. In this way, the AF 660 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 660 is considered to be a trusted entity, the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may exhibit an Naf service-based interface.

The data network 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 638.

FIG. 7 schematically illustrates a wireless network 700 in accordance with various embodiments. The wireless network 700 may include a UE 702 in wireless communication with an AN 704. The UE 702 and AN 704 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 702 may be communicatively coupled with the AN 704 via connection 706. The connection 706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an L.TE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 702 may include a host platform 708 coupled with a modem platform 710. The host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710. The application processing circuitry 712 may run various applications for the UE 702 that source/ sink application data. The application processing circuitry 712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706. The layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/ decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/ detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF' front end (RFFE) 724, which may include or connect to one or more antenna panels 726. Briefly, the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 724 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 718, receive circuitry 720, RF circuitry 722, RFFE 724, and antenna panels 726 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714. In some embodiments, the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 726. A UE transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726. In some embodiments, the transmit components of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 726.

Similar to the UE 702, the AN 704 may include a host platform 728 coupled with a modem platform 730. The host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730. The modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746. The components of the AN 704 may be simiiar to and substantially interchangeable with like-named components of the UE 702. In addition to performing data transmission/reception as described above, the components of the AN 708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

FIG. 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory/ storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.

The processors 810 may include, for example, a processor 812 and a processor 814. The processors 810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/ storage devices 820 may include main memory, disk storage, or any suitable combination thereof The memory/storage devices 820 may include, but are not limited to, any type of volatile, non-volatile, or semi- volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808. For example, the communication resources 830 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory/storage devices 820, or any suitable combination thereof. Furthermore, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.

As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art.. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.1 1 standards.

Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an onboard device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wared or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multistandard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.

Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subjectmatter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.

The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Example 1 may be an apparatus of a user equipment device (UE) for detecting beam failure communicating with multiple transmission reception points (TRPs), the apparatus comprising processing circuitry coupled to storage, the processing circuitry configured to: identify first beam failure detection resources associated with a first, beam used by the UE to communicate with a first TRP at a first time; identify second beam failure detection resources associated with a second beam used by the UE to communicate with a second TRP at the first time; determine, based on the first beam failure detection resources, a first radio link quality for the first beam; determine, based on the second beam failure detection resources, a second radio link quality for the second beam, detect, based on a comparison of the first radio link quality to a threshold quality, a beam failure of the first beam at the first time; detect, based on a comparison of the second radio link quality to the threshold quality, that the second beam is active at the first time; and generate, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time.

Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the first TRP is associated with a first radio node B, and wherein the second TRP is associated with a second radio node B.

Example 3 may include the apparatus of example 1 or 2 and/or some other example herein, wherein the processing circuitry is further configured to: identify a first control resource set (CORESET) index associated with the first TRP, wherein to identify the first beam failure detection resources is based on the first CORESET index; and identify a second CORESET index associated with the second TRP, wherein to identify the second beam failure detection resources is based on the second CORESET index. Example 4 may include the apparatus of example 1 or 2 and/or some other example herein, wherein the processing circuitry is further configured to: identify first candidate beam detection (CBD) resources associated with the first TRP; identify second CBD resources associated with the second TRP; and detect a replacement beam at the first time based on the first CBD resources and the second CBD resources.

Example 5 may include the apparatus of example 1 and/or some other example herein, wherein the link recovery request is sent to the second TRP over a physical uplink control channel resource dedicated to a beam failure recovery process.

Example 6 may include the apparatus of example 5 and/or some other example herein, wherein the physical uplink control channel resource is a first physical uplink control channel resource dedicated to the second TRP, and wherein a second physical uplink control channel resource is dedicated to the first TRP for a second beam failure recovery process associated with the second beam.

Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to: generate an indication of the beam failure of the first beam to transmit to the second TRP.

Example 8 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to: generate an indication of a third beam to replace the first beam to transmit to the second TRP.

Example 9 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to: identify an uplink grant received from the second TRP in response to the link recovery request.

Example 10 may include a computer-readable storage medium comprising instructions to cause processing circuitry of a user equipment device (UE), upon execution of the instructions by the processing circuitry, to: identify first beam failure detection resources associated with a first beam used by the UE to communicate with a first transmission reception point (TRP) at a first time; identify second beam failure detection resources associated with a second beam used by the UE to communicate with a second TRP at the first time; determine, based on the first beam failure detection resources, a first radio link quality for the first beam; determine, based on the second beam failure detection resources, a second radio link quality for the second beam; detect, based on a comparison of the first radio link quality to a threshold quality, a beam failure of the first beam at the first time; detect, based on a comparison of the second radio link quality to the threshold quality, that the second beam is active at the first time; and generate, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time.

Example 11 may include the computer-readable medium of example 10 and/or some other example herein, wherein the first. TRP is associated with a first radio node B, and wherein the second TRP is associated with a second radio node B.

Example 12 may include the computer-readable medium of example 11 or claim 10 and/or some other example herein, wherein execution of the instructions further causes the processing circuitry to: identify a first control resource set (CORESET) index associated with the first TRP, wherein identifying the first beam failure detection resources is based on the first CORESET index; and identify a second CORESET index associated with the second TRP, wherein identifying the second beam failure detection resources is based on the second CORESET index.

Example 13 may include the computer-readable medium of example 10 and/or some other example herein, wherein execution of the instructions further causes the processing circuitry to: identify first candidate beam detection (CBD) resources associated with the first TRP; identify second CBD resources associated with the second TRP, and detect a new beam for replacement at the first time based on the first CBD resources and the second CBD resources.

Example 14 may include the computer-readable medium of example 10 and/or some other example herein, wherein the link recovery request is sent to the second TRP over a physical uplink control channel resource dedicated to a beam failure recovery process.

Example 15 may include the computer-readable medium of example 14 and/or some other example herein, wherein the physical uplink control channel resource is a first physical uplink control channel resource dedicated to the second TRP, and wherein a second physical uplink control channel resource is dedicated to the first TRP for a second beam failure recovery process associated with the second beam.

Example 16 may include the computer-readable medium of example 10 and/or some other example herein, wherein execution of the instructions further causes the processing circuitry to: generate an indication of the beam failure of the first beam to transmit to the second TRP.

Example 17 may include the computer-readable medium of example 10 and/or some other example herein, wherein execution of the instructions further causes the processing circuitry to: generate an indication of a third beam to replace the first beam to send to the second TRP. Example 18 may include the computer-readable medium of example 10 and/or some other example herein, wherein execution of the instructions further causes the processing circuitry to: identify an uplink grant received from the second TRP in response to the link recovery request.

Example 19 may include a system for detecting beam failure communicating with multiple transmission reception points (TRPs), the system comprising processing circuitry of a user equipment device (UE) coupled to memory of the UE, the processing circuitry configured to: identify first beam failure detection resources associated with a first beam used by the UE to communicate with a first transmission reception point (TRP) at a first time; identify second beam failure detection resources associated with a second beam used by the UE to communicate with a second TRP at the first time; determine, based on the first beam failure detection resources, a first radio link quality for the first beam; determine, based on the second beam failure detection resources, a second radio link quality for the second beam; detect, based on a comparison of the first radio link quality to a threshold quality, a beam failure of the first beam at the first time; detect, based on a comparison of the second radio link quality to the threshold quality, that the second beam is active at the first time; and generate, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time.

Example 20 may include the system of example 19 and/or some other example herein, wherein the processing circuitry is further configured to: identify a first control resource set (CORESET) index associated with the first TRP, wherein to identify the first beam failure detection resources is based on the first CORESET index; and identify a second CORESET index associated with the second TRP, wherein to identify the second beam failure detection resources is based on the second CORESET index.

Example 21 may include the system of example 19 and/or some other example herein, wherein the processing circuitry is further configured to: identify first candidate beam detection (CBD) resources associated with the first TRP; identify second CBD resources associated with the second TRP; and detect a new beam for replacement at the first time based on the first CBD resources and the second CBD resources.

Example 22 may include the system of any of examples 19-21 and/or some other example herein, wherein the link recovery request is sent to the second TRP over a physical uplink control channel resource dedicated to a beam failure recovery process.

Example 23 may include the system of example 22 and/or some other example herein, wherein the physical uplink control channel resource is a first physical uplink control channel resource dedicated to the second TRP, and wherein a second physical uplink control channel resource is dedicated to the first TRP for a second beam failure recovery process associated with the second beam.

Example 24 may include the system of example 19 and/or some other example herein, wherein the processing circuitry is further configured to: generate an indication of the beam failure of the first beam to transmit to the second TRP.

Example 25 may include the system of example 19 and/or some other example herein, wherein the processing circuitry is further configured to: generate an indication of a third beam to replace the first beam to send to the second TRP.

Example 26 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.

Example 27 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1 -25, or any other method or process described herein.

Example 28 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.

Example 29 may include a method, technique, or process as described in or related to any of examples 1-25, or portions or parts thereof

Example 30 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that., when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.

Example 31 may include a signal as described in or related to any of examples 1-25, or portions or parts thereof.

Example 32 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.

Example 33 may include a signal encoded with data as described in or related to any of examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure. Example 34 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-25, or portions or parts thereof’ or otherwise described in the present disclosure.

Example 35 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.

Example 36 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.

Example 37 may include a signal in a wireless network as shown and described herein.

Example 38 may include a method of communicating in a wireless network as shown and described herein.

Example 39 may include a system for providing wireless communication as shown and described herein.

Example 40 may include a device for providing wireless communication as shown and described herein.

Certain aspects of the disclosure are described above with reference to block and flowdiagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.

These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instractions may also be stored in a computer-readable storage media or memory that, may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.

Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardw^?are-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way- required for one or more implementations or that one or more implementations necessarily include logic for deciding, wdth or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of; or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data, information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a. single-core processor, a dual-core processor, a. triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component, interfaces, network interface cards, and/or the like. The term “user equipment” or “LIE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/ systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide sendees, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a. data element that contains content.

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl 6.0.0 (2019-06) and/or any other 3GPP standard. For the purposes of the present document, the following abbreviations (shown in Table 1) may apply to the examples and embodiments discussed herein.

Table 1: Abbreviations

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment device (UE) for detecting beam failure communicating with multiple transmission reception points (TRPs), the apparatus comprising processing circuitry coupled to storage, the processing circuitry configured to: identify first beam failure detection resources associated with a first beam used by the LIE to communicate with a first TRP at a first time; identify second beam failure detection resources associated with a second beam used by the UE to communicate with a second TRP at the first time; determine, based on the first beam failure detection resources, a first radio link quality for the first beam; determine, based on the second beam failure detection resources, a second radio link quality for the second beam; detect, based on a comparison of the first radio link quality to a threshold quality, a beam failure of the first beam at the first time, detect, based on a comparison of the second radio link quality to the threshold quality, that the second beam is active at the first time; and generate, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time,

2. The apparatus of claim 1, wherein the first TRP is associated with a first radio node B, and wherein the second TRP is associated with a second radio node B.

3. The apparatus of any of claims 1 or 2, wherein the processing circuitry is further configured to: identify a first control resource set (CORESET) index associated with the first TRP, wherein to identify the first beam failure detection resources is based on the first CORESET index; and identify a second CORESET index associated with the second TRP, wherein to identify the second beam failure detection resources is based on the second CORESET index.

4. The apparatus of any of claims 1 or 2, wherein the processing circuitry is further configured to: identify first candidate beam detection (CBD) resources associated with the first TRP; identify second CBD resources associated with the second TRP; and detect a replacement beam at the first time based on the first CBD resources and the second CBD resources.

5. The apparatus of claim I, wherein the link recovery' request is sent to the second

TRP over a physical uplink control channel resource dedicated to a beam failure recovery process.

6. The apparatus of claim 5, wherein the physical uplink control channel resource is a first physical uplink control channel resource dedicated to the second TRP, and wherein a second physical uplink control channel resource is dedicated to the first TRP for a second beam failure recovery process associated with the second beam.

7. The apparatus of claim 1 , wherein the processing circuitry is further configured to: generate an indication of the beam failure of the first beam to transmit to the second

TRP.

8. The apparatus of claim 1, wherein the processing circuitry is further configured to: generate an indication of a third beam to replace the first beam to transmit to the second TRP.

9. The apparatus of claim 1, wherein the processing circuitry is further configured to: identify an uplink grant received from the second TRP in response to the link recovery request.

10. A computer-readable storage medium comprising instructions to cause processing circuitry of a user equipment device (UE), upon execution of the instructions by the processing circuitry, to: identify first beam failure detection resources associated with a first beam used by the UE to communicate with a first transmission reception point (TRP) at a first time, identify second beam failure detection resources associated with a second beam used by the UE to communicate with a second TRP at the first time; determine, based on the first beam failure detection resources, a first radio link quality for the first beam; determine, based on the second beam failure detection resources, a second radio link quality for the second beam; detect, based on a comparison of the first radio link quality to a threshold quality, a beam failure of the first beam at the first time; detect, based on a comparison of the second radio link quality to the threshold quality, that the second beam is active at the first time; and generate, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time.

11 . The computer-readable medium of claim 10, wherein the first TRP is associated with a first radio node B, and wherein the second TRP is associated with a second radio node B.

12. The computer-readable medium of claim 10 or claim 11, wherein execution of the instructions further causes the processing circuitry to: identify a first control resource set (CORESET) index associated with the first TRP, wherein identifying the first beam failure detection resources is based on the first CORESET index; and identify a second CORESET index associated with the second TRP, wherein identifying the second beam failure detection resources is based on the second CORESET index.

13. The computer-readable medium of claim 10, wherein execution of the instructions further causes the processing circuitry to: identify first candidate beam detection (CBD) resources associated with the first TRP, identify second CBD resources associated with the second TRP; and detect a new beam for replacement at the first time based on the first CBD resources and the second CBD resources.

14. The computer-readable medium of claim 10, wherein the link recovery request is sent to the second TRP over a physical uplink control channel resource dedicated to a beam failure recovery process.

15. The computer-readable medium of claim 14, wherein the physical uplink control channel resource is a first physical uplink control channel resource dedicated to the second TRP, and wherein a second physical uplink control channel resource is dedicated to the first TRP for a second beam failure recovery process associated with the second beam.

16. The computer-readable medium of claim 10, wherein execution of the instructions further causes the processing circuitry to: generate an indication of the beam failure of the first beam to transmit to the second TRP.

17. The computer-readable medium of claim 10, wherein execution of the instructions further causes the processing circuitry to: generate an indication of a third beam to replace the first beam to send to the second TRP.

18. The computer-readable medium of claim 10, wherein execution of the instructions further causes the processing circuitry to: identify an uplink grant received from the second TRP in response to the link recovery request.

19. A system for detecting beam failure communicating with multiple transmission reception points (TRPs), the system comprising processing circuitry of a user equipment device (UE) coupled to memory of the UE, the processing circuitry configured to: identify first beam failure detection resources associated with a first beam used by the UE to communicate with a first transmission reception point (TRP) at a first time; identify second beam failure detection resources associated with a second beam used by the UE to communicate with a second TRP at the first time; determine, based on the first beam failure detection resources, a first radio link quality for the first beam; determine, based on the second beam failure detection resources, a second radio link quality for the second beam; detect, based on a comparison of the first radio link quality to a threshold quality, a beam failure of the first beam at the first time, detect, based on a comparison of the second radio link quality to the threshold quality, that the second beam is active at the first time; and generate, at a second time, a link recovery request for the first beam based on the beam failure, wherein the second beam is active at the second time.

20. The system of claim 19, wherein the processing circuitry is further configured to: identify a first control resource set (CORESEI') index associated with the first TRP, wherein to identify the first beam failure detection resources is based on the first CORESET index; and identify a second CORESET index associated with the second TRP, wherein to identify the second beam failure detection resources is based on the second CORESET index.

21. The system of claim 19, wherein the processing circuitry is further configured to: identify first candidate beam detection (CBD) resources associated with the first

TRP; identify second CBD resources associated with the second TRP; and detect a new beam for replacement at the first time based on the first CBD resources and the second CBD resources.

22. The system of any of claims 19-21, wherein the link recovery request is sent to the second TRP over a physical uplink control channel resource dedicated to a beam failure recovery process,

23. The system of claim 22, wherein the physical uplink control channel resource is a first physical uplink control channel resource dedicated to the second TRP, and wherein a second physical uplink control channel resource is dedicated to the first TRP for a second beam failure recovery process associated with the second beam,

24. The system of claim 19, wherein the processing circuitry is further configured to: generate an indication of the beam failure of the first beam to transmit to the second

TRP.

25. The system of claim 19, wherein the processing circuitry is further configured to: generate an indication of a third beam to replace the first beam to send to the second

TRP.