# US 11,910,433 B2 · Physical uplink shared channel (PUSCH) transmission scheduling for new radio (NR)

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

- Number: US 11,910,433 B2
- Document ID: US11910433B2
- Status: Granted
- Kind: B2
- Application number: 17/175,420
- Filed: 2021-02-12
- Published: 2021-06-17
- Granted: 2024-02-20
- Earliest claimed: 2020-02-13
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Yingyang Li; Yongjun Kwak
- Web page: https://patentgrep.com/patent/US11910433B2

## CPC

- H04L 5/0083: {symbol-by-symbol}
- H04W 74/002: {Transmission of channel access control information}
- H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH}
- H04L 27/0006: {Assessment of spectral gaps suitable for allocating digitally modulated signals, e.g. for carrier allocation in cognitive radio (for spectrum sharing between different networks H04W16/14)}
- H04L 27/2607: {Cyclic extensions}
- H04W 72/1268: of uplink data flows
- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04W 74/0808: using carrier sensing, e.g. carrier sense multiple access [CSMA]
- H04W 74/0816: with collision avoidance
- H04L 5/0062: {Avoidance of ingress interference, e.g. ham radio channels}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure is related to listen-before-talk (LBT) operations for multiple consecutive physical uplink shared channel (PUSCH) transmissions scheduled by a single downlink control information (DCI) or multiple DCIs. In a fifth generation (5G)/new radio (NR) system operating in an unlicensed spectrum, when multiple physical uplink shared channel (PUSCH) transmissions are scheduled (e.g., by one or more DCIs), and if LBT operation has failed before the start of a first PUSCH transmission of the multiple PUSCH transmissions, an LBT type and cyclic prefix (CP) extension for a subsequent PUSCH transmission of the multiple PUSCH transmissions is determined. In some examples, the multiple PUSCH transmissions are consecutive PUSCH transmission. Other embodiments may be described and/or claimed.

## Claims

### Claim 1

An apparatus of a user equipment (UE) comprising:
memory circuitry to store configuration information that is to schedule multiple consecutive physical uplink shared channel (PUSCH) transmissions based on multiple uplink (UL) grants, wherein the multiple consecutive PUSCH transmissions include a first PUSCH transmission and a second PUSCH transmission scheduled subsequent to the first PUSCH transmission and with a same channel access priority class (CAPC) or a lower CAPC as the first PUSCH transmission; and
processor circuitry coupled with the memory circuitry, wherein the processor circuitry is to:
perform a CAT-4 listen-before-talk (LBT) operation before a start of the first PUSCH transmission;
determine the LBT operation is not successful;
continue the CAT-4 LBT subsequent to failure of the CAT-4 LBT failing before the first PUSCH transmission; and
in response to determining the LBT operation is not successful, skip transmission of the PUSCH transmission.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the configuration information is included in a received downlink control information (DCI) format 1_1 message.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the processor circuitry is to perform a second LBT operation before a start of a second PUSCH transmission from the multiple scheduled PUSCH transmissions.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the LBT operation is a CAT-4 LBT operation, and wherein the processing circuitry is to continue the LBT operation until a start of a subsequent PUSCH transmission from the multiple scheduled PUSCH transmissions.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the LBT operation is a CAT-4 LBT operation, the PUSCH transmission is a first PUSCH transmission, the multiple consecutive PUSCHs are scheduled by multiple UL grants, a second PUSCH transmission subsequent to the first PUSCH transmission is scheduled with a higher CAPC than the first PUSCH transmission, and wherein the processing circuitry is further to restart the CAT-4 LBT with the higher CAPC for the second PUSCH transmission.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the LBT operation is a CAT-4 LBT operation, and wherein the processor circuitry is further to generate a new counter for the CAT-4 LBT operation based on a CAPC of one or more of the multiple scheduled PUSCH transmissions or a number of idle clear channel assessment (CCA) slots.

### Claim 7

One or more non-transitory computer-readable media (NTCRM) comprising instructions, wherein execution of the instructions by one or more processors is to cause a user equipment (UE) to:
receive configuration information that is to schedule multiple consecutive physical uplink shared channel (PUSCH) transmissions, wherein the multiple consecutive PUSCHs are scheduled by multiple UL grants, and the multiple consecutive PUSCHs include a first PUSCH transmission and a second PUSCH transmission scheduled subsequent to the first PUSCH transmission and with a same channel access priority class (CAPC) or a lower CAPC as the first PUSCH transmission;
perform a CAT-4 listen-before-talk (LBT) operation before a start of the first PUSCH transmission;
determine the LBT operation is not successful;
continue the CAT-4 LBT subsequent to failure of the CAT-4 LBT failing before the first PUSCH transmission; and
in response to determining the LBT operation is not successful, skip transmission of the PUSCH transmission.

### Claim 8 (depends on 7)

The one or more NTCRM of claim 7, wherein the configuration information is included in a received downlink control information (DCI) format 1_1 message.

### Claim 9 (depends on 7)

The one or more NTCRM of claim 7, wherein execution of the instructions is to cause the UE to perform a second LBT operation before a start of a second PUSCH transmission from the multiple scheduled PUSH transmissions.

### Claim 10 (depends on 7)

The one or more NTCRM of claim 7, wherein the LBT operation is a CAT-4 LBT operation, and wherein execution of the instructions is to cause the UE to continue the LBT operation until a start of a subsequent PUSCH transmission from the multiple scheduled PUSCH transmissions.

### Claim 11 (depends on 7)

The one or more NTCRM of claim 7, wherein the LBT operation is a CAT-4 LBT operation, the PUSCH transmission is a first PUSCH transmission, the multiple consecutive PUSCHs are scheduled by multiple UL grants, a second PUSCH transmission subsequent to the first PUSCH transmission is scheduled with a higher CAPC than the first PUSCH transmission, and wherein execution of the instructions is to cause the UE to restart the CAT-4 LBT with the higher CAPC for the second PUSCH transmission.

### Claim 12 (depends on 7)

The one or more NTCRM of claim 7, wherein the LBT operation is a CAT-4 LBT operation, and wherein execution of the instructions is to cause the UE to generate a new counter for the CAT-4 LBT operation based on a CAPC of one or more of the multiple scheduled PUSCH transmissions or a number of idle clear channel assessment (CCA) slots.

### Claim 13

One or more non-transitory computer-readable media (NTCRM) comprising instructions, wherein execution of the instructions by one or more processors is to cause a user equipment (UE) to:
receive configuration information that is to schedule multiple consecutive physical uplink shared channel (PUSCH) transmissions;
perform a listen-before-talk (LBT) operation before a start of a PUSCH transmission from the multiple scheduled PUSCH transmissions in the configuration information;
determine the LBT operation is not successful; and
in response to determining the LBT operation is not successful, skip transmission of the PUSCH transmission and apply a cyclic prefix (CP) extension associated with the PUSCH transmission to a subsequent PUSCH transmission from the multiple scheduled PUSCH transmissions.

### Claim 14 (depends on 13)

The one or more NTCRM of claim 13, wherein the configuration information is received from downlink control information (DCI) or an uplink (UL) grant.

### Claim 15 (depends on 13)

The one or more NTCRM of claim 13, wherein the CP extension is 25 μs.

### Claim 16 (depends on 13)

The one or more NTCRM of claim 13, wherein the CP extension is 0 μs.

### Claim 17 (depends on 13)

The one or more NTCRM of claim 13, wherein the CP extension is based on a length of a start symbol of the subsequent PUSCH transmission.

### Claim 18 (depends on 13)

The one or more NTCRM of claim 13, wherein the CP extension is based on a length of one or more symbols prior to a start symbol of the subsequent PUSCH transmission.