# US 12,120,730 B2 · Scheduling requests, status reports, and logical channel prioritization

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

- Number: US 12,120,730 B2
- Document ID: US12120730B2
- Status: Granted
- Kind: B2
- Application number: 17/555,933
- Filed: 2021-12-20
- Published: 2022-11-17
- Granted: 2024-10-15
- Earliest claimed: 2017-06-15
- Assignees: InterDigital Patent Holdings, Inc.
- Applicants: InterDigital Patent Holdings, Inc.
- Inventors: Guodong Zhang; Yifan Li; Pascal M. Adjakple; Stephen E. Terry; Joseph M. Murray
- Web page: https://patentgrep.com/patent/US12120730B2

## CPC

- H04W 72/569: {of the traffic information}
- H04B 7/0617: {for beam forming}
- H04L 1/1812: Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 28/0278: {using buffer status reports (dynamic wireless traffic scheduling definition H04W72/12)}
- H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network
- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04L 47/21: using leaky-bucket
- H04L 47/39: {Credit based}
- H04W 74/0833: Random access procedures, e.g. with 4-step access
- 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

Features, methods, and functions for beam failure recovery and scheduling requests are provided, including methods for triggering, canceling, and transmitting beam recovery requests. The scheduling request may be designed to accommodate new criteria for transmission on a grant-free uplink shared channel (UL-SCH) and for putting the schedule request on hold.

## Claims

### Claim 1

An apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a communications network via its communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to:
delay, based on an upcoming uplink grant, a random access channel procedure for a tracked duration, wherein the upcoming uplink grant is available for buffer status reporting (BSR).

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the random access channel procedure is associated with a physical random access channel (PRACH).

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the instructions further cause the apparatus to: determine, based on logical channel restrictions of the upcoming uplink grant, whether to delay the random access channel procedure.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the instructions further cause the apparatus to:
determine BSR is transmitted using the upcoming uplink grant; and
cancel tracking of the tracked duration.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the instructions further cause the apparatus to perform, subsequent to the delay, a random access procedure when:
there is no uplink grant, within the allowed latency, available to transmit the BSR.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the instructions further cause the apparatus to perform, subsequent to the delay, a random access procedure when:
a buffer status report (BSR) is triggered and not cancelled,
there is no scheduling request (SR) resource, and
there is no uplink grant, within the allowed latency, available to transmit the BSR.

### Claim 7

An apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a communications network via its communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to:
determine that a Buffer Status Report (BSR) has been triggered;
determine there is an upcoming uplink grant associated with the apparatus, wherein the upcoming uplink grant has a time duration;
determine that a transmission of the BSR cannot be sent during the time duration associated with the upcoming uplink grant; and
based on the determination that the BSR transmission cannot be sent during the time duration, then trigger a scheduling request (SR).

### Claim 8 (depends on 7)

The apparatus of claim 7, the instructions further cause the apparatus to:
determine there is no physical uplink control channel (PUCCH) resource available for transmission of the triggered SR; and
based on no PUCCH resource being available for transmission of the triggered SR, initiate a random access channel (RACH) procedure.

### Claim 9 (depends on 7)

The apparatus of claim 7, the instructions further cause the apparatus to when multiple SRs are pending and a first SR is indicated as successful, determine that remaining SRs of the multiple SRs are cancelled.

### Claim 10 (depends on 7)

The apparatus of claim 7, the instructions further cause the apparatus to:
determine that a Beam Recovery Request (BRR) has been triggered at the same time as the SR:
suspend the pending SR based on the determination that the BRR has been triggered at the same time as the SR;
transmit the BRR over a physical uplink control channel (PUCCH) resource;
receive a valid BRR command; and
resume the pending SR based on reception of the valid BRR command.

### Claim 11

A method comprising:
determining that a Buffer Status Report (BSR) has been triggered;
determining there is an upcoming uplink grant associated with the apparatus, wherein the upcoming uplink grant has a time duration;
determining that a transmission of the BSR cannot be sent during the time duration associated with the upcoming uplink grant; and
based on the determination that the BSR transmission cannot be sent during the time duration, then trigger a scheduling request (SR).

### Claim 12 (depends on 11)

The method of claim 11, the method comprising:
determining there is no physical uplink control channel (PUCCH) resource available for transmission of the triggered SR; and
based on no PUCCH resource being available for transmission of the triggered SR, initiating a random access channel (RACH) procedure.

### Claim 13 (depends on 11)

The method of claim 11, the method comprising:
determine that a Beam Recovery Request (BRR) has been triggered at the same time as the SR;
suspend the pending SR based on the determination that the BRR has been triggered at the same time as the SR;
transmit the BRR over a physical uplink control channel (PUCCH) resource;
receive a valid BRR command; and
resume the pending SR based on reception of the valid BRR command.

### Claim 14 (depends on 11)

The method of claim 11, the method comprising:
determine that a Beam Recovery Request (BRR) has been triggered at the same time as the SR; and
transmit the BRR and the SR over a single PUCCH resource.

### Claim 15 (depends on 11)

The method of claim 11, wherein the PUCCH resource is shared for transmission of the SR and the BRR.

### Claim 16 (depends on 11)

The method of claim 11, wherein the PUCCH resource is shared for transmission of the SR and the BRR, wherein the PUCCH resource carries an indication, indicating if the content is the SR, the BRR, or a combination of the SR and the BRR.

### Claim 17 (depends on 11)

The method of claim 11, the method comprising:
determine that an SR failure has occurred;
determine the impacted PUCCH resources, based on the determination that the SR failure has occurred;
release the impacted PUCCH resources; and
notify a second apparatus, based on the determination that the SR failure has occurred.

### Claim 18 (depends on 17)

The method of claim 17, wherein the SR failure is determined per SR configuration, per serving cell, per bandwidth part (BWP) or wherein the notification includes an SR configuration index.

### Claim 19 (depends on 11)

The method of claim 11, the method comprising when multiple SRs are pending, determine which pending SR to prioritize based on one or more of the following: the SR configuration with the most transmission opportunities, the SR configuration that corresponds to the highest priority logical channel, the SR configuration using a long PUCCH format, or the SR configuration using a short PUCCH format.
