# US 2020/0404640 A1 · System and method for transmitting beam failure recovery request

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0404640 A1
- Document ID: US20200404640A1
- Status: Published application
- Kind: A1
- Application number: 17/004,920
- Filed: 2020-08-27
- Published: 2020-12-24
- Earliest claimed: 2017-06-14
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Muhammad Nazmul ISLAM; Sundar SUBRAMANIAN; Juergen CEZANNE; Junyi LI
- Web page: https://patentgrep.com/patent/US20200404640A1

## CPC

- H04W 72/046: {the resource being in the space domain, e.g. beams}
- H04B 7/06964: {Re-selection of one or more beams after beam failure}
- H04L 1/00: Arrangements for detecting or preventing errors in the information received {(correcting synchronisation H04L7/00)}
- H04L 5/0048: {Allocation of pilot signals, i.e. of signals known to the receiver (allocation of control signalling H04L5/0053; use of control signalling H04L5/0091)}
- H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals}
- H04L 5/1469: {using time-sharing}
- H04W 16/28: using beam steering
- H04W 74/0833: Random access procedures, e.g. with 4-step access
- H04W 74/004: {in the uplink, i.e. towards network}
- H04W 74/0838: using contention-free random access [CFRA]
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04B: TRANSMISSION
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A user equipment (UE) can transmit a beam failure recovery request using contention-based physical random access channel (PRACH) resources to supplement and/or replace non-contention-based resources for transmitting the beam failure recovery request. The UE can reduce beam recovery latency by informing its intention for beam failure recovery by transmitting a beam failure recovery request during the random access channel (RACH) procedure. The base station may dedicate a set of RACH resources that can be used for both transmitting regular contention-based RACH messages and beam failure recovery request.

## Claims

### Claim 1

A method of wireless communications at a user equipment (UE), comprising:
determining a beam failure of a current beam with a scheduling entity;
transmitting a random access channel (RACH) preamble in response to the determination of the beam failure;
receiving a RACH response from the scheduling entity; and
transmitting a radio resource control (RRC) connection request to the scheduling entity, wherein the RRC connection request indicates that the RACH preamble comprises a beam failure recovery request.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
detecting a set of beams from the scheduling entity;
selecting a beam from the set of beams to replace the current beam to recover from the beam failure;
determining at least one of a RACH resource or a waveform corresponding to the selected beam; and
transmitting the RACH preamble utilizing the at least one of the RACH resource or the waveform.

### Claim 3 (depends on 1)

The method of claim 1, wherein the RACH response queries the UE whether a RACH procedure is being performed to transmit the beam failure recovery request.

### Claim 4 (depends on 3)

The method of claim 3, wherein only if the RACH response queries the UE whether the RACH procedure is performed to transmit the beam failure recovery request, the RRC connection request indicates that the RACH procedure is performed to transmit the beam failure recovery request.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
receiving, from the scheduling entity, a beam refinement reference signal (BRRS) or a channel state information reference signal (CSI-RS); and
selecting a refined beam based on the BRRS or the CSI-RS.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving allocation information of contention-based RACH resources through at least one of a master information block (MIB), a system information block (SIB), a master system information block (MSIB), a remaining minimum system information (RMSI), an other SIB (OSIB), or radio resource control (RRC) signaling.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving allocation information of contention-based RACH resources through a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH), wherein at least a portion of the contention-based RACH resources is allocated to transmission of the beam failure recovery request.

### Claim 8

A method of beam failure recovery operable at a scheduling entity, comprising:
receiving a random access channel (RACH) preamble in a RACH procedure from a user equipment (UE);
transmitting a RACH response to the UE; and
receiving a radio resource control (RRC) connection request from the UE, wherein the RRC connection request indicates that the RACH preamble comprises a beam failure recovery request.

### Claim 9 (depends on 8)

The method of claim 8, wherein the RACH response queries the UE whether the RACH procedure is performed to transmit the beam failure recovery request.

### Claim 10 (depends on 9)

The method of claim 9, wherein only if the RACH response queries the UE whether the RACH procedure is performed to transmit the beam failure recovery request, the RRC connection request indicates that the RACH procedure is performed to transmit the beam failure recovery request.

### Claim 11 (depends on 8)

The method of claim 8, further comprising:
receiving, from the UE, a request to transmit a beam refinement reference signal (BRRS) or a channel state information reference signal (CSI-RS).

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
transmitting the BRRS or the CSI-RS in each of a plurality of refined beams.

### Claim 13 (depends on 8)

The method of claim 8, further comprising:
transmitting allocation information of contention-based RACH resources through at least one of a master information block (MIB), a system information block (SIB), a master system information block (MSIB), a remaining minimum system information block (RMSI), an other SIB (OSIB), or radio resource control (RRC) signaling.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
transmitting allocation information of contention-based RACH resources through a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH), wherein at least a portion of the contention-based RACH resources is allocated to transmission of the beam failure recovery request.

### Claim 15 (depends on 8)

The method of claim 8, further comprising:
transmitting an RRC connection setup message to the UE, the RRC connection setup message comprising allocation information of beam refinement resources.

### Claim 16

A method of beam failure recovery operable at a scheduling entity, comprising:
assigning a random access channel (RACH) resource to a plurality of scheduled entities including a user equipment (UE) for conveying a beam failure recovery request (BFRR); and
receiving, from the UE, the BFRR in a RACH procedure utilizing the assigned RACH resource;
receiving, in the RACH procedure, a cell radio network temporary identity (C-RNTI) from the UE; and
confirming the C-RNTI received from the UE corresponds to a C-RNTI stored in the scheduling entity.

### Claim 17 (depends on 16)

The method of claim 16, further comprising:
transmitting allocation information of the RACH resource to the plurality of scheduled entities utilizing at least one of:
a primary synchronization signal (PSS);
a secondary synchronization signal (SSS);
a physical broadcast channel (PBCH);
a remaining minimum system information (RMSI);
an other system information (OSI);
a physical downlink control channel (PDCCH);
a radio resource control (RRC) message; or
a handover message.

### Claim 18 (depends on 16)

The method of claim 16, further comprising:
forgoing, in the RACH procedure, transmitting a temporary C-RNTI to the UE.

### Claim 19 (depends on 16)

The method of claim 16, wherein the RACH resource comprises at least one of:
a RACH preamble; or
a time-frequency resource.

### Claim 20 (depends on 16)

The method of claim 16, wherein the RACH procedure is a contention-based random access procedure.

### Claim 21

A method of beam failure recovery operable at a user equipment (UE), comprising:
receiving, from a scheduling entity, an assignment of a random access channel (RACH) resource that is assigned to a plurality of scheduled entities including the UE for conveying a beam failure recovery request (BFRR); and
transmitting, to the scheduling entity, the BFRR in a RACH procedure utilizing the assigned RACH resource;
transmitting, in the RACH procedure, a cell radio network temporary identity (C-RNTI) to the scheduling entity; and
completing a beam failure recovery with the scheduling entity upon confirmation by the scheduling entity that the transmitted C-RNTI corresponds to a C-RNTI stored in the scheduling entity.

### Claim 22 (depends on 21)

The method of claim 21, further comprising:
receiving allocation information of the RACH resource from the scheduling entity utilizing at least one of:
a primary synchronization signal (PSS);
a secondary synchronization signal (SSS);
a physical broadcast channel (PBCH);
a remaining minimum system information (RMSI);
an other system information (OSI);
a physical downlink control channel (PDCCH);
a radio resource control (RRC) message; or
a handover message.

### Claim 23 (depends on 21)

The method of claim 21, further comprising:
forgoing, in the RACH procedure, receiving a temporary C-RNTI from the scheduling entity.

### Claim 24 (depends on 21)

The method of claim 21, wherein the RACH resource comprises at least one of:
a RACH preamble; or
a time-frequency resource.

### Claim 25 (depends on 21)

The method of claim 21, wherein the RACH procedure is a contention-based random access procedure.
