IP Library Granted Patent US 12,284,652
Granted Patent B2
US 12,284,652 · App. 17/628,127 · Granted Apr 22, 2025

Method and apparatus for scheduling request and buffer status report transmissions

Inventors: Lianhai Wu (Beijing, CN); Haiming Wang (Beijing, CN); Jing Han (Beijing, CN); Zhi Yan (Beijing, CN); Jie Shi (Beijing, CN); Jie Hu (Beijing, CN)
Assignee: Lenovo (Beijing) Limited
H04W72/21H04W72/542H04W72/569
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,284,652
App. No.
17/628,127
Granted
Apr 22, 2025
Kind
B2
Abstract

The present disclosure relates to methods and apparatuses. According to some embodiments of the disclosure, a method includes: receiving a first buffer status report at a communication device; and triggering a pre-emptive buffer status report based on the first buffer status report if a trigger condition is met.

Claims (48)

1. A method at a communication device, the method comprising:

receiving a first buffer status report (BSR);

triggering a preemptive buffer status report (Pre-BSR) based on the first BSR in response to a trigger condition being met;

determining that no uplink resource is available for transmitting the pre-BSR; and

based on the determining, triggering a preemptive scheduling request (Pre-SR) in response to there being no uplink resource available for transmitting the Pre-BSR.

2. The method of claim 1 , wherein the Pre-BSR includes a buffer status of the first BSR and one or more buffer statuses of one or more second BSRs pending at the communication device.

3. The method of claim 1 , wherein:

triggering the Pre-BSR comprises triggering the Pre-BSR if a priority level of a logical channel (LCH) associated with the first BSR is higher than a priority threshold.

4. The method of claim 1 , wherein:

triggering the Pre-BSR comprises triggering the Pre-BSR if a latency value of a logical channel (LCH) associated with the first BSR is lower than a latency threshold.

5. The method of claim 1 , further comprising:

starting a timer in response to triggering the Pre-BSR.

6. The method of claim 5 , further comprising:

prohibiting another Pre-BSR until the timer expires.

7. The method of claim 5 , further comprising:

if the timer is running, if a priority of a logical channel (LCH) included in a received third BSR is higher than the highest priority among priorities of LCHs included in the first BSR, triggering another Pre-BSR.

8. The method of claim 5 , further comprising:

if the timer is running, if a latency value of a logical channel (LCH) included in a received third BSR is lower than the lowest latency value among latency values of LCHs included in the first BSR, triggering another Pre-BSR.

9. The method of claim 1 , further comprising:

transmitting the Pre-BSR; and

starting a retransmission timer in response to transmission of the Pre-BSR.

10. The method of claim 9 , further comprising:

retransmitting the Pre-BSR in response to an expiry of the retransmission timer if uplink data is expected to be received at the communication device.

11. The method of claim 1 , further comprising:

maintaining the triggered Pre-SR if uplink resource large enough to accommodate all pending data for transmission at the communication device but not enough to accommodate the Pre-BSR is granted.

12. The method of claim 11 , wherein the uplink resource is not large enough to accommodate the buffer statuses up to the last event that triggered a Pre-BSR.

13. The method of claim 1 , further comprising:

cancelling the triggered Pre-SR if uplink resource large enough to accommodate the Pre-BSR is granted.

14. The method of claim 13 , wherein the uplink resource is large enough to accommodate the buffer statuses up to the last event that triggered a Pre-BSR.

15. The method of claim 1 , wherein the Pre-SR is associated:

with an egress logical channel (LCH) corresponding to an ingress LCH having the highest priority among at least one ingress LCH associated with the first BSR;

with an egress LCH corresponding to an ingress LCH having the highest priority among at least one ingress LCH associated with the first BSR and one or more other BSRs received at the communication device;

with an egress LCH corresponding to an ingress LCH associated with a scheduling request (SR) received at the communication device;

with an egress LCH having the highest priority among at least one egress LCH, and wherein the at least one egress LCH is associated with at least one logical channel group (LCG) indicated in the Pre-BSR;

or some combination thereof.

16. The method of claim 1 , further comprising:

if the Pre-SR is to be transmitted at a transmission occasion the same as that for a first SR pending at the communication device, transmitting the first SR at the transmission occasion.

17. The method of claim 1 , further comprising:

if the Pre-SR is to be transmitted at a transmission occasion the same as that for a first SR pending at the communication device, transmitting one of the Pre-SR and the first SR which is associated with a logical channel (LCH) having the highest priority among the LCHs associated with the Pre-SR and the first SR;

if the Pre-SR is to be transmitted at a transmission occasion the same as that for a physical uplink shared channel (PUSCH) without an uplink shared channel (UL-SCH), transmitting the PUSCH at the transmission occasion;

or a combination thereof.

18. A communication device, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the communication device to:

receive a first buffer status report (BSR); and

trigger a preemptive buffer status report (Pre-BSR) based on the first BSR in response to a trigger condition being met;

determine that no uplink resource is available for transmitting the pre-BSR; and

based on the determining, trigger a preemptive scheduling request (Pre-SR) in response to there being no uplink resource available for transmitting the Pre-BSR.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 29, 2025
From: LENOVO (BEIJING) LIMITED
To: EDGEWOOD IP, LLC
Reel/Frame 073328/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2022
From: WU, LIANHAI; WANG, HAIMING; HAN, JING; YAN, ZHI; SHI, JIE; HU, JIE
To: LENOVO (BEIJING) LIMITED
Reel/Frame 058683/0660 →
Continuity (1)
Related Publication 20220256576A1 · Aug 11, 2022
References Cited (15)
US 20170353819A1 · Yin · 2017 [cited by examiner]
US 20190334663A1 · Dev · 2019 [cited by examiner]
US 20200037200A1 · Cho · 2020 [cited by examiner]
CN 106455089A · 2017 [cited by applicant]
CN 106658743A · 2017 [cited by applicant]
WO 2015041408A1 · 2015 [cited by applicant]
WO 2018228549A1 · 2018 [cited by applicant]
R2-1905829, “Triggering condition of Pre-BSR”, 3GPP TSG-RAN WG2 Meeting #106 (May 13-17, 2019). (Year: 2019). [cited by examiner]
R2-1905829 (Year: 2019). [cited by examiner]
LG Electronics, Enhancement for low latency uplink scheduling, 3GPP TSG-RAN WG2 #105, R2-1902167, Feb. 25-Mar. 1, 2019, pp. 1-4, Athens, Greece. [cited by applicant]
3GPP, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15), 3GPP TS 38.321 V15.0.0, (Dec. 2017), pp. 1-55. [cited by applicant]
Lenovo, Motorola Mobility, UL scheduling latency in IAB system, 3GPP TSG-RAN WG2 Meeting #106, R2-1906915, May 13-May 17, 2019, pp. 1-3, Reno, USA. [cited by applicant]
International Searching Authority, “Written Opinion of the International Searching Authority,” PCT/CN2019/096878, Apr. 10, 2020, pp. 1-3. [cited by applicant]
ZTE Corporation, Sanechips, Discussions on low latency scheduling in IAB, 3GPP TSG RAN WG2 Meeting #106, R2-1906571, May 13-17, 2019, pp. 1-4, Reno, NV, USA. [cited by applicant]
Vivo, Triggering conditions of Pre-BSR, 3GPP TSG RAN WG2 Meeting #106, R2-1905829, May 13-17, 2019, pp. 1-3, Reno, USA. [cited by applicant]