# US 2020/0288344 A1 · Resource request method and device, method and device for processing resource request

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

- Number: US 2020/0288344 A1
- Document ID: US20200288344A1
- Status: Published application
- Kind: A1
- Application number: 16/764,645
- Filed: 2018-11-06
- Published: 2020-09-10
- Earliest claimed: 2017-11-16
- Assignees: Zte Corporation
- Applicants: Zte Corporation
- Inventors: Boyuan ZHANG; Lin CHEN; Ying HUANG; Mengzhen WANG
- Web page: https://patentgrep.com/patent/US20200288344A1

## CPC

- H04W 24/10: Scheduling measurement reports {; Arrangements for measurement reports}
- H04L 5/00: Arrangements affording multiple use of the transmission path
- H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W 28/0278: {using buffer status reports (dynamic wireless traffic scheduling definition H04W72/12)}
- H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)}
- H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network
- H04W 76/11: Allocation or use of connection identifiers
- H04W 4/06: Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W 4/44: for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
- H04W 4/46: for vehicle-to-vehicle communication [V2V]
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 92/18: between terminal devices
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Provided are a resource requesting method and device, and a resource request processing method and device. The method includes: acquiring, by a terminal, a buffer size corresponding to an same frequency point or anchor frequency point in a logical channel group; reporting, by the terminal, an Sidelink BSR to a base station, where the Sidelink BSR includes at least one of: a destination index corresponding to the same frequency point or anchor frequency point; a logical channel group identifier or a logical channel identifier; or a buffer size.

## Claims

### Claim 1

A resource requesting method, comprising:
acquiring, by a first communication mode, a buffer size corresponding to an same frequency point or anchor frequency point in a logical channel group;
reporting, by the first communication node, a Sidelink Buffer Status Report (BSR) to a second communication node, wherein the Sidelink BSR comprises at least one of:
a destination index corresponding to the same frequency point or anchor frequency point;
a logical channel group identifier or a logical channel identifier; or
the buffer size.

### Claim 2 (depends on 1)

The method of claim 1, wherein before the first communication node reporting the Sidelink BSR, the method further comprises:
receiving, by the first communication node, frequency point information configured or agreed in advance by the second communication node, wherein the frequency point information comprises at least one of:
Sidelink available frequency point information;
a number of frequency points supporting data distribution or data duplication;
a split ratio of each data split frequency point;
one or more split data sizes corresponding to the logical channel, wherein the split data size is a maximum data transmission amount of data of the logical channel split to a frequency point;
mapping information of an Sidelink logical channel and/or an Sidelink logical channel group and/or a destination identifier with one or more frequency points;
a frequency point priority; or
anchor frequency point information corresponding to the logical channel and/or the destination identifier.

### Claim 3 (depends on 2)

The method of claim 2, wherein before the first communication node reporting the Sidelink BSR to the second communication node, the method further comprises at least one of:
determining, by the first communication node, a number of frequency points to be used and/or a data transmission amount at each of the frequency points to be used according to at least one of: available frequency point information; the split data size; the split ratio; the number of frequency points supporting the data distribution or the data duplication; or the frequency point priority; or
determining, by the first communication node, at least one of the following information corresponding to a bearer of the data duplication: a number of frequency points to be used, a mapping relationship between a frequency point and a logical channel corresponding to the bearer.

### Claim 4 (depends on 2)

The method of claim 2, wherein before receiving the frequency point information configured or pre-configured by the second communication node, the method further comprises:
reporting, by the first communication node, at least one of following parameters corresponding to each destination identifier or logic channel to the second communication node:
a data rate;
a reliability level; or
ProSe Per-Packet Priority (PPPP) information.

### Claim 5

(canceled)

### Claim 6 (depends on 3)

The method of claim 3, wherein the first communication node determining the number of frequency points to be used and/or a data transmission amount on the each of the frequency points according to at least one of: available frequency point information; the split data size; the split ratio; the number of frequency points supporting the data distribution or the data duplication; or the frequency point priority comprises at least one of:
in a case where the buffer size of the logical channel is less than the split data size, selecting, by the first communication node, a first frequency point to transmit data;
in a case where the buffer size of the logical channel is greater than the split data size, using, by the first communication node, the first frequency point to transmit data of the split data size, selecting other frequency points from available frequency points to transmit data of remaining data size, wherein data amount transmitted at each frequency point in the other frequency points does not exceed the split data size; and
determining, by the first communication node, data amount transmitted at each frequency point according to the buffer size and the split ratio of the logical channel,
wherein the first communication node selecting the first frequency point and/or the other frequency points in a manner of:
selecting, by the first communication node, the frequency points used for data distribution in a high-to-low order according to priorities of the frequency points.

### Claim 7

(canceled)

### Claim 8 (depends on 1)

The method of claim 1, wherein before the first communication node reporting the Sidelink BSR to the second communication node, the method further comprises:
reporting, by the first communication node, only a destination identifier corresponding to the anchor frequency point in SidelinkUEInformation;
or, wherein before the first communication node reporting the Sidelink BSR to the second communication node, the method further comprises:
sending, by the first communication, at least one of the following information to the second communication node:
a destination identifier; available frequency point information corresponding to the logical channel group and/or the logical channel, wherein the available frequency point information comprises the anchor frequency point supporting the destination identifier, and/or optional frequency point information; or
the destination identifier; data split indication information corresponding to the logical channel group and/or the logical channel.

### Claim 9

(canceled)

### Claim 10 (depends on 1)

The method of claim 1, wherein in a case where the logical channel group comprises a plurality of logical channels, a sum of the buffer size of the corresponding same frequency point or anchor frequency point in the logical channels.

### Claim 11 (depends on 1)

The method of claim 1, wherein the first communication node reporting the Sidelink BSR to the second communication node comprises:
reporting, by the first communication node, the BSR according to the destination index corresponding to the anchor frequency point.

### Claim 12

A resource requesting method, comprising:
acquiring, by a first communication node, a buffer size corresponding to one or more frequency points in a logical channel, wherein the logical channel uses the one or more frequency points; and
reporting an Sidelink BSR according to a destination index corresponding to the one or more frequency points respectively, wherein the BSR comprises a buffer size of the frequency points used in the logical channel.

### Claim 13 (depends on 12)

The method of claim 12, wherein reporting the Sidelink BSR according to the destination index corresponding to the one or more frequency points respectively comprises:
in response to determining that the first communication node reports a v2x-Destination Info List corresponding to each frequency point in the SidelinkUEInformation, reporting a correspondence between a destination ID and each logical channel simultaneously,
wherein in a case where the destination ID has an anchor frequency point corresponding to different logical channels, the first communication node reporting the v2x-Destination Info List corresponding to each frequency point in the Sidelink UE information comprises:
reporting, by the first communication node, in the SidelinkUEInformation, only the destination ID in the v2x-Destination Info List corresponding to the anchor frequency point in each logical channel.

### Claim 14

(canceled)

### Claim 15

A resource request processing method, comprising:
receiving, by a second communication node, a Sidelink Buffer Status Report (BSR) reported by a first communication node, wherein the Sidelink BSR comprises at least one of: one or more logical channels in a logical channel group, a destination index corresponding to an same frequency point to be used or an anchor frequency point to be used; a logical channel group identifier or a logical channel identifier; or a buffer size of the same frequency point or anchor frequency point; and
allocating resources on a plurality of frequency points for the first communication node according to the Sidelink BSR.

### Claim 16 (depends on 15)

The method of claim 15, wherein before the second communication node receiving the Sidelink BSR reported by the first communication node, frequency point information configured or agreed in advance by the second communication node for the first communication node comprises at least one of:
Sidelink available frequency point information;
a number of frequency points supporting data distribution or data duplication;
a split ratio of each data split frequency point;
one or more split data sizes corresponding to the logical channel, wherein the split data size is a maximum data transmission amount of data of the logical channel split to a frequency point;
mapping information of an Sidelink logical channel and/or an Sidelink logical channel group and/or a destination identifier with one or more frequency points;
a frequency point priority; or
information corresponding to the anchor frequency point of the logical channel and/or the destination identifier,
wherein before the second communication node configuring or agreeing in advance to the frequency point information for the first communication node, receiving, by the second communication node, at least one of following parameters corresponding to each Vehicle-to-Everything (V2X) destination identifier or logical channel reported by the first communication node:
a data rate;
a reliability level; or
ProSe Per-Packet Priority (PPPP) information.

### Claim 17

(canceled)

### Claim 18 (depends on 15)

The method of claim 15, wherein before the second communication node receiving the Sidelink BSR reported by the first communication node, the second communication node receives at least one of the following information sent by the first communication node:
a destination identifier; available frequency point information corresponding to the logical channel group and/or the logical channel, wherein the available frequency point information comprises the anchor frequency point supporting the destination identifier, and/or optional frequency point information; or
the destination identifier; data split indication information corresponding to the logical channel group and/or the logical channel,
wherein before the second communication node receiving the Sidelink BSR reported by the first communication node, the method further comprises:
receiving SidelinkUEInformation of the first communication node, wherein the SidelinkUEInformation comprises only the destination identifier corresponding to the anchor frequency point, wherein destination identifier information is used for identifying the destination identifier,
wherein allocating resources on the frequency points for the first communication node according to the Sidelink BSR comprises:
receiving, by the second communication node, a BSR reported by the first communication node according to the destination index corresponding to the anchor frequency point;
executing, by the second communication node, at least one of: acquiring the destination identifier according to the destination index in the BSR, and acquiring available frequency point information corresponding to the destination identifier; determining, by the second communication node, whether to use a frequency point in the available frequency point information according to the data split indication information; and
in a case of determining to use the frequency point in the available frequency point information, determining, by the second communication node, a frequency point of resources to be allocated, allocating the resources to the frequency point of the resources to be allocated.

### Claim at position 19

19-20. (canceled)

### Claim 21 (depends on 15)

The method of claim 15, wherein allocating resources on the frequency points for the first communication node according to the Sidelink BSR comprises:
receiving, by the second communication node, the BSR reported by the first communication node according to a plurality of destination indexes corresponding to the frequency points; and
allocating, by the second communication node, the resources on the frequency points.

### Claim 22 (depends on 1)

A resource requesting device, comprising:
a processor; and
a memory for storing instructions executable by the processor,
wherein when executing the instructions, the processor is configured to implement the resource requesting method of claim 1.

### Claim 23 (depends on 12)

A resource requesting device, comprising:
a processor; and
a memory for storing instructions executable by the processor,
wherein when executing the instructions, the processor is configured to implement the resource requesting method of claim 12.

### Claim 24 (depends on 15)

A resource request processing device, comprising:
a processor; and
a memory for storing instructions executable by the processor,
wherein when executing the instructions, the processor is configured to implement the resource request processing method of claim 15.

### Claim 25 (depends on 1)

A nonvolatile computer readable storage medium, comprising stored programs which, when executed, execute the resource requesting method of claim 1.

### Claim 26

(canceled)

### Claim 27 (depends on 12)

A nonvolatile computer readable storage medium, comprising stored programs which, when executed, execute the resource requesting method of claim 12.

### Claim 28 (depends on 15)

A nonvolatile computer readable storage medium, comprising stored programs which, when executed, execute the resource request processing method of claim 15.
