# US 2021/0282050 A1 · Efficient buffer management in multi-hops data forwarding

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

- Number: US 2021/0282050 A1
- Document ID: US20210282050A1
- Status: Published application
- Kind: A1
- Application number: 17/253,173
- Filed: 2019-06-20
- Published: 2021-09-09
- Earliest claimed: 2018-06-20
- Assignees: CONVlDA WIRELESS, LLC
- Applicants: CONVlDA WIRELESS, LLC
- Inventors: Pascal M. ADJAKPLE; Stephen E. TERRY; Guodong ZHANG; Joseph M. MURRAY; Qing LI; Mohamed AWADiN; Yifan LI; Allan Y. TSAI; Lakshmi R. IYER
- Web page: https://patentgrep.com/patent/US20210282050A1

## CPC

- H04L 1/0002: {by adapting the transmission rate}
- H04W 28/0273: {adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP] (wireless network protocols or protocol adaptations to wireless operation, e.g. wireless application protocol H04W80/00)}
- H04L 1/0015: {characterised by the adaptation strategy}
- H04L 1/0025: {Transmission of mode-switching indication}
- H04L 1/0027: {Scheduling of signalling, e.g. occurrence thereof}
- H04L 1/1841: {Resequencing}
- H04L 1/1874: {Buffer management}
- H04L 1/1896: {ARQ related signaling}
- H04W 28/0289: {Congestion control (load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling 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 88/14: Backbone network devices
- H04L 1/1685: {the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal}
- H04L 2001/0097: {Relays}
- H04W 88/04: adapted for relaying to or from another terminal or user
- Y02D 30/50: in wire-line communication networks, e.g. low power modes or reduced link rate
- 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)
- 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

Current approaches to radio link control (RLC) data forwarding with no end-to-end RLC entities between a given UE and IAB donor node lack proper buffer management. In various examples, the premature deletion of transmitted PDCP PDUs is avoided. Various embodiments also address buffer size control, for example end-to-end flow control, hot-by-hop flow control, explicit and implicit flow control options are described. Content of flow control messages, transmitter actions at the reception of flow control, and triggers for flow controls are also described herein.

## Claims

### Claim at position 1

-26. (canceled)

### Claim 27

An apparatus comprising a processor and a memory, the apparatus connected to a network, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to:
receive a flow control notification message from an intermediary node, the intermediary node connected between the apparatus and a receiver node in the network, such that data sent from the apparatus to the receiver node travels through the intermediary node; and
based on the flow control notification message; send a flow control message to the transmitter node,
wherein the flow control message includes an indication for the transmitter node to stop transmitting data, start transmitting data, increase its data transmission rate, decrease its data transmission rate, and/or transmit data at a new rate.

### Claim 28 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive the flow control notification message in response to an available capacity in the buffer of the intermediary node or receiver node being above a threshold.

### Claim 29 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive the flow control notification message in response to an amount of data in a buffer of the intermediary node or receiver node being above an upper edge threshold.

### Claim 30 (depends on 27)

The apparatus of claim 27, wherein the flow control notification message indicates an available capacity in a buffer of the intermediary node or receiver node, an amount of data in the buffer of the intermediary node or receiver node, an indication that the amount of data in the buffer of the intermediary node or receiver node is below a lower edge threshold, an indication that the amount of data in the buffer of the intermediary node or receiver node is above an upper edge threshold, an identity of a bearer, and identity of a quality of service flow, an identity of the intermediary node for which flow control should be applied, an identity of a route for which flow control should be applied, or an indication of a packet missing from the intermediary node or receiver node.

### Claim 31 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive the flow control notification message periodically.

### Claim 32 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive the flow control notification message in response to an available capacity in a buffer of the intermediary node or receiver node being below a threshold.

### Claim 33 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive the flow control notification message in response to an amount of data in a buffer of the intermediary node or receiver node being below a lower edge threshold.

### Claim 34 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive the flow control notification message in response to a change of route or a selection of new route between the intermediary node and the receiver node.

### Claim 35 (depends on 27)

The apparatus of claim 27, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, further cause the apparatus to:
receive a packet data convergence protocol (PDCP) protocol data unit (PDU) from an intermediary node, the PDCP PDU sent from an Integrated Access and Backhaul (IAB) node;
based on a trigger or a status request, generate a PDCP status report; and
send the PDCP status report to the Integrated Access and Backhaul (IAB) node,
wherein the PDCP status report indicates an acknowledgement of the PDCP PDU received by the apparatus.

### Claim 36 (depends on 2)

In a multi-hop Integrated Access and Backhaul (IAB) network that comprises a packet data convergence protocol (PDCP) transmitter, a PDCP receiver, and an intermediary node connected between the PDCP transmitter and PDCP receiver, a method comprising:
receiving, by the PDCP receiver, a PDCP protocol data unit (PDU) from the intermediary node, the PDCP PDU sent from the PDCP transmitter;
generating, by the PDCP receiver, a PDCP status report; and
sending, by the PDCP receiver, the PDCP status report to the PDCP transmitter, the PDCP status report indicating an acknowledgement of the PDCP PDU received by the PDCP receiver. (previous claim 2)

### Claim 37 (depends on 36)

The method of claim 36, the method comprising:
receiving, by the PDCP transmitter, the PDCP status report, wherein the acknowledgement indicates that a specific PDCP PDU was received by the PDCP receiver; and
in response to receiving the PDCP status report, deleting the PDCP PDU from a buffer of the PDCP transmitter.

### Claim 38 (depends on 36)

The method of claim 36, the method further comprising:
receiving, by the PDCP transmitter, the PDCP status report, wherein the acknowledgement indicates that a specific PDCP PDU was not received by the PDCP receiver; and
in response to receiving the PDCP status report, retransmitting the specific PDCP PDU regardless of whether the specific PDCP status report was already received by the intermediary node.

### Claim 39 (depends on 38)

The method of claim 38, wherein retransmitting the specific PDCP PDU is based on an indication in a radio resource control (RRC) message or the PDCP status report.

### Claim 40 (depends on 36)

The method of claim 36, the method further comprising:
receiving, by the PDCP receiver, a request from the PDCP transmitter to send the acknowledgement; and
generating the PDCP status report responsive to the request.

### Claim 41 (depends on 40)

The method of claim 40, wherein the request is indicated in a header of the PDCP PDU.

### Claim 42 (depends on 36)

The method of claim 36, the method further comprising:
generating the PDCP status report responsive to an internal event trigger without receiving a request from the PDCP transmitter.

### Claim 43 (depends on 36)

The method of claim 36, the method further comprising:
receiving, by the PDCP receiver, a handover or route update command; and
generating the PDCP status report responsive to the handover or route update command.

### Claim 44

A method performed by a PDCP transmitter, the method comprising:
sending a PDCP PDU to a first intermediary node, the PDCP PDU intended for a PDCP receiver;
saving the PDCP PDU in a buffer after the PDCP PDU is sent to the first intermediary node;
receiving an acknowledgement that indicates the PDCP PDU is received by the PDCP receiver; and
in response to the acknowledgement, deleting the PDCP PDU from the buffer.

### Claim 45 (depends on 44)

The method of claim 44, the method further comprising:
sending a second PDCP PDU to the first intermediary node, the PDCP PDU intended for the PDCP receiver;
receiving an intermediary acknowledgement that indicates that the second PDCP PDU is received by the first intermediary node;
receiving a negative acknowledgment that indicates that the second PDCP PDU has not been received by the PDCP receiver; and
retransmitting the second PDCP PDU, thereby sending the PDCP PDU irrespective of whether successful delivery has been confirmed by the intermediary node.

### Claim 46 (depends on 44)

The method of claim 44, the method further comprising:
receiving an indication that the PDCP PDU was received by the first intermediary node; and
maintaining the PDCP PDU in the buffer after receiving the indication that the PDCP PDU was received by the intermediary node.
