# US 2019/0320446 A1 · Scheduling request indication

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

- Number: US 2019/0320446 A1
- Document ID: US20190320446A1
- Status: Published application
- Kind: A1
- Application number: 16/476,235
- Filed: 2017-01-05
- Published: 2019-10-17
- Earliest claimed: 2017-01-05
- Assignees: Motorola Mobility LLC
- Applicants: Motorola Mobility LLC
- Inventors: Hongchao Li; Xiaodong Yu; Haipeng Lei
- Web page: https://patentgrep.com/patent/US20190320446A1

## CPC

- H04W 72/543: based on requested quality, e.g. QoS
- 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
- H04W 72/52: based on load
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Apparatuses, methods, and systems are disclosed for scheduling request indication. One apparatus (200) includes a transmitter (210) that transmits (602) a scheduling request in response to data arriving at a buffer. The scheduling request includes an indication of a traffic type, a requested number of scheduling transmissions, an expected number of transmissions, an expected scheduling interval, a latency requirement, or some combination thereof. The apparatus (200) also includes a receiver (212) that receives (604) an uplink grant in response to transmitting the scheduling request. The transmitter (210) transmits (606) the data in response to receiving the up-link grant.

## Claims

### Claim 1

An apparatus comprising:
a transmitter that transmits a scheduling request in response to data arriving at a buffer, wherein the scheduling request comprises an indication of a traffic type, a requested number of scheduling transmissions, an expected number of transmissions, an expected scheduling interval, a latency requirement, or some combination thereof; and
a receiver that receives an uplink grant in response to transmitting the scheduling request, wherein the transmitter transmits the data in response to receiving the uplink grant.

### Claim 2

(canceled)

### Claim 3

(canceled)

### Claim 4

(canceled)

### Claim 5

(canceled)

### Claim 6

(canceled)

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the transmitter transmits the scheduling request in an uplink control channel.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the transmitter transmits the scheduling request in a physical resource region outside of a control channel.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the transmitter transmits the scheduling request in a spreading sequence space.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the transmitter transmits the data in a grant-free transmission.

### Claim 11

A method comprising:
transmitting a scheduling request in response to data arriving at a buffer, wherein the scheduling request comprises an indication of a traffic type, a requested number of scheduling transmissions, an expected number of transmissions, an expected scheduling interval, a latency requirement, or some combination thereof;
receiving an uplink grant in response to transmitting the scheduling request; and
transmitting the data in response to receiving the uplink grant.

### Claim 12 (depends on 11)

The method of claim 11, wherein the indication indicates a single-shot schedule request with the size of the data below a predetermined threshold.

### Claim 13 (depends on 11)

The method of claim 11, wherein the indication indicates a multiple-shot schedule request with the size of the data below a predetermined threshold.

### Claim 14 (depends on 11)

The method of claim 11, wherein the indication indicates a periodic transmission schedule request with a predetermined periodicity.

### Claim 15 (depends on 11)

The method of claim 11, wherein the indication comprises two bits that indicate four different states.

### Claim 16 (depends on 11)

The method of claim 11, wherein the indication comprises one bit that indicates a buffer status report will not be sent.

### Claim 17

(canceled)

### Claim 18

(canceled)

### Claim 19

(canceled)

### Claim 20

(canceled)

### Claim 21

An apparatus comprising:
a receiver that receives a scheduling request, wherein the scheduling request comprises an indication of a traffic type, a requested number of scheduling transmissions, an expected number of transmissions, an expected scheduling interval, a latency requirement, or some combination thereof; and
a transmitter that transmits an uplink grant in response to receiving the scheduling request, wherein the receiver receives data in response to transmitting the uplink grant.

### Claim 22

(canceled)

### Claim 23

(canceled)

### Claim 24

(canceled)

### Claim 25

(canceled)

### Claim 26

(canceled)

### Claim 27 (depends on 21)

The apparatus of claim 21, wherein the receiver receives the scheduling request in an uplink control channel.

### Claim 28 (depends on 21)

The apparatus of claim 21, wherein the receiver receives the scheduling request in a physical resource region outside of a control channel.

### Claim 29 (depends on 21)

The apparatus of claim 21, wherein the receiver receives the scheduling request in a spreading sequence space.

### Claim 30 (depends on 21)

The apparatus of claim 21, wherein the receiver receives data in a grant-free transmission.

### Claim 31

A method comprising:
receiving a scheduling request, wherein the scheduling request comprises an indication of a traffic type, a requested number of scheduling transmissions, an expected number of transmissions, an expected scheduling interval, a latency requirement, or some combination thereof;
transmitting an uplink grant in response to receiving the scheduling request; and
receiving data in response to transmitting the uplink grant.

### Claim 32 (depends on 31)

The method of claim 31, wherein the indication indicates a single-shot schedule request with the size of data below a predetermined threshold.

### Claim 33 (depends on 31)

The method of claim 31, wherein the indication indicates a multiple-shot schedule request with the size of data below a predetermined threshold.

### Claim 34 (depends on 31)

The method of claim 31, wherein the indication indicates a periodic transmission schedule request with a predetermined periodicity.

### Claim 35 (depends on 31)

The method of claim 31, wherein the indication comprises two bits that indicate four different states.

### Claim 36 (depends on 31)

The method of claim 31, wherein the indication comprises one bit that indicates a buffer status report will not be sent.

### Claim 37

(canceled)

### Claim 38

(canceled)

### Claim 39

(canceled)

### Claim 40

(canceled)
