IP Library Granted Patent US 12,250,586
Granted Patent B2
US 12,250,586 · App. 17/421,350 · Granted Mar 11, 2025

Apparatus and method for communication with buffer status report

Inventors: Lianhai Wu (Beijing, CN); Joachim Loehr (Wiesbaden, DE); Prateek Basu Mallick (Dreieich, DE); Haiming Wang (Beijing, CN); Jing Han (Beijing, CN)
Assignee: Lenovo (Beijing) Limited
H04W28/0278H04W40/22H04W72/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,250,586
App. No.
17/421,350
Granted
Mar 11, 2025
Kind
B2
Abstract

Method and apparatus for communication in an Integrated Access and Backhaul (IAB) system with buffer status report (BSR) are disclosed. The apparatus include a receiver that receives a BSR indicating that data is expected to be received; a processor that calculates a first type of buffer size based on the received BSR indicating that data is expected to be received and/or a second type of buffer size based on data presently stored in a buffer; and a transmitter that transmits a buffer status comprising the first type of buffer size and/or the second type of buffer size.

Claims (59)

1. A parent integrated access and backhaul (IAB) node, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the parent IAB node to:

receive a buffer status report directly from a plurality of child IAB nodes, wherein the buffer status report indicates data that the plurality of child IAB nodes expect to receive from other nodes;

calculate a first type of buffer size based on the received buffer status report indicating that data is expected to be received; and

transmit a buffer status comprising the first type of buffer size, wherein the buffer status to be reported is allocated with an early buffer status report logical channel identifier that is different from logical channel identifiers of a short buffer status report, a long buffer status report, or a truncated buffer status report.

2. The parent IAB node of claim 1 , wherein the at least one processor is configured to cause the parent IAB node to receive a plurality of buffer status reports from a plurality of remote devices.

3. The parent IAB node of claim 2 , wherein the first type of buffer size comprises a total early buffer size indicating an amount of data that is expected to be received from the plurality of remote devices until a media access control protocol data unit assembly is received.

4. The parent IAB node of claim 2 , wherein:

the received buffer status report comprises a first received buffer status report from a first remote device and a second received buffer status report from a second remote device;

the first received buffer status report comprises a plurality of instances of buffer size with a priority; and

the second received buffer status report comprises a plurality of instances of buffer size with the same priority; and the buffer size value with the same priority from the first received buffer status report and the second received buffer status report are accumulated to form a buffer size of the priority.

5. The parent IAB node of claim 1 , wherein:

the received buffer status report comprises a plurality of logical channel groups for receiving data and a buffer size for each logical channel group of the plurality of logical channel groups;

the first type of buffer size comprises an early buffer size indicating an amount of data that is expected to be received in the plurality of logical channel groups; and

the buffer status to be reported is a combined buffer status, and further comprises:

a first buffer status comprising information of the first type of buffer size; and

a second buffer status comprising a second type of buffer size, wherein the second type of buffer size comprises a short buffer status report format, a long buffer status report format, or a long truncated buffer status report format.

6. The parent IAB node of claim 5 , wherein:

the second buffer status comprises the second type of buffer size which comprises the short buffer status report format; and

the combined buffer status to be reported comprises the second buffer status and the first buffer status added to the end of the second buffer status.

7. The parent IAB node of claim 5 , wherein:

the second buffer status comprises the second type of buffer size comprising the long buffer status report format or the long truncated buffer status report format; and

the combined buffer status to be reported comprises the second buffer status and the first buffer status added to the end of the long buffer status report format or the long truncated buffer status report format.

8. The parent IAB node of claim 1 , wherein:

the at least one processor is configured to cause the parent IAB node to receive a plurality of the buffer status reports from a single remote device; and

the first type of buffer size is calculated based on a last received buffer status report.

9. The parent IAB node of claim 1 , wherein:

the received buffer status report comprises a plurality of logical channel groups for receiving data and a buffer size for each logical channel of the plurality of logical channel groups; and

the first type of buffer size is organized according to priority information, wherein information of the logical channel groups is the priority information.

10. The parent IAB node of claim 9 , wherein information of a buffer size with a higher priority from the first type of buffer size and the second type of buffer size is included in the buffer status report when available uplink resources for transmitting the buffer status are limited.

11. The parent IAB node of claim 1 , wherein:

the received buffer status report comprises a first received buffer status report from a first remote device and a second received buffer status report from a second remote device;

the buffer size comprises a priority corresponding to the first type of buffer size;

the buffer size has a same priority corresponding to the second type of buffer size; and

the buffer size values with the same priority as the first type of buffer size and second type of buffer size are accumulated to form a buffer size of the priority.

12. The parent IAB node of claim 1 , wherein the first type of buffer size is included in the buffer status report with higher priority as compared to the second type of buffer size when available uplink resources for transmitting the buffer status are limited.

13. The parent IAB node of claim 1 , wherein the second type of buffer size is included in the buffer status report with higher priority as compared to the first type of buffer size when available uplink resources for transmitting the buffer status are limited.

14. The parent IAB node of claim 1 , wherein:

the received buffer status report comprises a plurality of logical channel groups for receiving data and a buffer size for each logical channel of the plurality of logical channel groups; and

the first type of buffer size comprises an early buffer size indicating an amount of data that is expected to be received in the plurality of logical channel groups.

15. The parent IAB node of claim 1 , wherein:

the received buffer status report comprises a plurality of logical channel groups for receiving data and a buffer size for each logical channel of the plurality of logical channel groups; and

the first type of buffer size is organized according to priority information, wherein information of logical channel groups is used to identify priority information.

16. The parent IAB node of claim 1 , wherein the buffer status to be reported further comprises information indicating a logical channel group for transmitting data.

17. A child integrated access and backhaul (IAB) node, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the child IAB node to:

receive a plurality of buffer status reports directly from a plurality of user equipments (UEs);

transmit a buffer status indicating that data is expected to be received from the plurality of UEs, wherein the buffer status to be reported is allocated with an early buffer status report logical channel identifier that is different from logical channel identifiers of a short buffer status report, a long buffer status report, or a truncated buffer status report; and

upon determination that there is no uplink resource available, transmit a scheduling request.

18. A method performed by a parent integrated access and backhaul (IAB) node, the method comprising:

receiving a buffer status report directly from a plurality of child IAB nodes, wherein the buffer status report indicates data that the plurality of child IAB nodes expect to receive from other nodes;

calculating a first type of buffer size based on the received buffer status report indicating that data is expected to be received; and

transmitting a buffer status comprising the first type of buffer size, wherein the buffer status to be reported is allocated with an early buffer status report logical channel identifier that is different from logical channel identifiers of a short buffer status report, a long buffer status report, or a truncated buffer status report.

19. A method performed by a child integrated access and backhaul (IAB) node, the method comprising:

receiving a plurality of buffer status reports directly from a plurality of user equipments (UEs);

transmitting a buffer status indicating that data is expected to be received from the plurality of UEs, wherein the buffer status to be reported is allocated with an early buffer status report logical channel identifier that is different from logical channel identifiers of a short buffer status report, a long buffer status report, or a truncated buffer status report; and

upon determination that there is no uplink resource available, transmitting a scheduling request.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 29, 2025
From: LENOVO (BEIJING) LIMITED
To: EDGEWOOD IP, LLC
Reel/Frame 073328/0682 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CORRECT DOCKET NUMBER IS SEC920180071-US-PCT PREVIOUSLY RECORDED ON REEL 69141 FRAME 242. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF ASSIGNORS INTEREST. Recorded Nov 7, 2024
From: WU, LIANHAI; LOEHR, JOACHIM; BASU MALLICK, PRATEEK; WANG, HAIMING; HAN, JING
To: LENOVO (BEIJING) LIMITED
Reel/Frame 069321/0760 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 5, 2024
From: WU, LIANHAI; LOEHR, JOACHIM; BASU MALLICK, PRATEEK; WANG, HAIMING; HAN, JING
To: LENOVO (BEIJING) LIMITED
Reel/Frame 069141/0242 →
Continuity (1)
Related Publication 20210400526A1 · Dec 23, 2021
References Cited (20)
US 6035335A · Franke et al. · 2000 [cited by applicant]
US 11350305B2 · Kim · 2022 [cited by examiner]
US 11496923B2 · Zhu · 2022 [cited by examiner]
US 20100070814A1 · Damnjanovic · 2010 [cited by examiner]
US 20100322144A1 · Lee et al. · 2010 [cited by applicant]
US 20110269393A1 · Oestergaard et al. · 2011 [cited by applicant]
US 20170273072A1 · Wittberg et al. · 2017 [cited by applicant]
US 20180234359A1 · Hosseini · 2018 [cited by examiner]
US 20180270698A1 · Babaei · 2018 [cited by examiner]
US 20200077295A1 · Shi · 2020 [cited by examiner]
US 20200344640A1 · Wu · 2020 [cited by examiner]
US 20210321426A1 · Lee · 2021 [cited by examiner]
US 20210345163A1 · Narasimha · 2021 [cited by examiner]
US 20210400526A1 · Wu · 2021 [cited by examiner]
CN 108289331A · 2018 [cited by applicant]
WO 2011123549A1 · 2011 [cited by applicant]
WO 2014162003A1 · 2014 [cited by applicant]
Internation Searching Authority, “Written Opinion of the International Searching Authority,” PCT/CN2019/071608, Sep. 23, 2019, pp. 1-3. [cited by applicant]
LG Electronics Inc., Scheduling enhancement in IAB, 3GPP TSG-RAN WG2 Meeting #103, R2-1812638, Aug. 20-24, 2018, pp. 1-2, Gothenburg, Sweden. [cited by applicant]
Intel Corporation, Uplink Latency in IAB networks, 3GPP TSG RAN WG2 Meeting #104, R2-1817700, Nov. 12-16, 2018, pp. 1-4, Spokane, USA. [cited by applicant]