Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), Acknowledge Mode ("AM"), Backhaul ("BH"), Broadcast Multicast ("BM"), Buffer Occupancy ("BO"), Base Station ("BS"), Bandwidth Part ("BWP"), Component Carrier ("CC"), Coordinated Multipoint ("CoMP"), Control Plane ("CP"), CSI-RS Resource Indicator ("CRI"), Channel State Information ("CSI"), Channel Quality Indicator ("CQI"), Central Unit ("CU"), Codeword ("CW"), Downlink ("DL"), Demodulation Reference Signal ("DMRS"), Data Radio Bearer ("DRB"), Distributed Unit ("DU"), Enhanced Mobile Broadband ("eMBB"), Evolved Node B ("eNB"), Enhanced Subscriber Identification Module ("eSIM"), Enhanced ("E"), Frequency Division Duplex ("FDD"), Frequency Division Multiple Access ("FDMA"), Frequency Range ("FR"), Hybrid Automatic Repeat Request ("HARQ"), Integrated Access Backhaul ("IAB"), Identity or Identifier or Identification ("ID"), Interference Measurement ("IM"), International Mobile Subscriber Identity ("IMSI"), Internet-of-Things ("IoT"), Internet Protocol ("IP"), Joint Transmission ("JT"), Level <NUM> ("L1"), Logical Channel ("LCH"), Logical Channel Prioritization ("LCP"), Long Term Evolution ("LTE"), Multiple Input Multiple Output ("MIMO"), Mobile-Termination ("MT"), Machine Type Communication ("MTC"), Multi-User MIMO ("MU-MIMO"), Negative-Acknowledgment ("NACK") or ("NAK"), Next Generation ("NG"), Next Generation Node B ("gNB"), New Radio ("NR"), Non-Zero Power ("NZP"), Orthogonal Frequency Division Multiplexing ("OFDM"), Peak-to-Average Power Ratio ("PAPR"), Physical Broadcast Channel ("PBCH"), Physical Downlink Shared Channel ("PDSCH"), Policy Control Function ("PCF"), Packet Data Convergence Protocol ("PDCP"), Packet Data Network ("PDN"), Protocol Data Unit ("PDU"), Public Land Mobile Network ("PLMN"), Precoding Matrix Indicator ("PMI"), Packet Switched ("PS"), Quasi Co-Located ("QCL"), Quality of Service ("QoS"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Resource Element ("RE"), Rank Indicator ("RI"), Radio Link Failure ("RLF"), Radio Resource Control ("RRC"), Reference Signal ("RS"), Reference Signal Received Power ("RSRP"), Reference Signal Received Quality ("RSRQ"), Receive ("RX"), Secondary Cell ("SCell"), Service Data Unit ("SDU"), Subscriber Identity Module ("SIM"), Signal-to-Interference and Noise Ratio ("SINR"), Sequence Number ("SN"), Synchronization Signal ("SS"), SS/PBCH Block ("SSB"), Temporary Mobile Subscriber Identity ("TMSI"), Transmission Reception Point ("TRP"), Transmit ("TX"), User Entity/Equipment (Mobile Terminal) ("UE"), Universal Integrated Circuit Card ("UICC"), Uplink ("UL"), Unacknowledged Mode ("UM"), Universal Mobile Telecommunications System ("UMTS"), User Plane ("UP"), Universal Subscriber Identity Module ("USIM"), Universal Terrestrial Radio Access Network ("UTRAN"), Voice Over IP ("VoIP"), Visited Public Land Mobile Network ("VPLMN"), and Worldwide Interoperability for Microwave Access ("WiMAX"). As used herein, "HARQ-ACK" may represent collectively the Positive Acknowledge ("ACK") and the Negative Acknowledge ("NAK"). ACK means that a TB is correctly received while NAK means a TB is erroneously received.

In certain wireless communications networks, buffer status reports may be sent. In such networks, a device may not know when to send a buffer status report.

<NPL>, and presents an analysis of the congestion issue in multi-hop IAB network, and discusses two flow control schemes including end-to-end and hop-by-hop flow control.

Claim <NUM> defines a method and claim <NUM> defines an apparatus. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

Methods for triggering a buffer status report are disclosed. Apparatuses and systems also perform the functions of the apparatus. In one embodiment, the method includes determining to transmit a buffer status report corresponding to uplink data in response to a trigger condition. In certain embodiments, the method includes, in response to determining to transmit the buffer status report, transmitting the buffer status report to a parent integrated access backhaul device.

An apparatus for triggering a buffer status report, in one embodiment, includes a processor that determines to transmit a buffer status report corresponding to uplink data in response to a trigger condition. In various embodiments, the apparatus includes a transmitter that, in response to determining to transmit the buffer status report, transmits the buffer status report to a parent integrated access backhaul device.

<FIG> depicts an embodiment of a wireless communication system <NUM> for triggering a buffer status report. In one embodiment, the wireless communication system <NUM> includes remote units <NUM> and network units <NUM>. Even though a specific number of remote units <NUM> and network units <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM> and network units <NUM> may be included in the wireless communication system <NUM>.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), IoT devices, or the like. The remote units <NUM> may communicate directly with one or more of the network units <NUM> via UL communication signals.

In certain embodiments, a network unit <NUM> may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a RAN, a relay node, a device, a network device, an IAB node, a donor IAB node, or by any other terminology used in the art.

In one implementation, the wireless communication system <NUM> is compliant with the <NUM> or NG (Next Generation) of the 3GPP protocol, wherein the network unit <NUM> transmits using NG RAN technology. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols.

In various embodiments, a remote unit <NUM> may trigger a buffer status report. In various embodiments, the remote unit <NUM> may determine to transmit a buffer status report corresponding to uplink data in response to a trigger condition. In certain embodiments, the remote unit <NUM> may, in response to determining to transmit the buffer status report, transmit the buffer status report to a parent integrated access backhaul device. Accordingly, a remote unit <NUM> may be used for triggering a buffer status report.

In various embodiments, a network unit <NUM> may trigger a buffer status report. In various embodiments, the network unit <NUM> may determine to transmit a buffer status report corresponding to uplink data in response to a trigger condition. In certain embodiments, the network unit <NUM> may, in response to determining to transmit the buffer status report, transmit the buffer status report to a parent integrated access backhaul device. Accordingly, a network unit <NUM> may be used for triggering a buffer status report.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for triggering a buffer status report. The apparatus <NUM> includes one embodiment of the remote unit <NUM>. Furthermore, the remote unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. In some embodiments, the input device <NUM> and the display <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit <NUM> may not include any input device <NUM> and/or display <NUM>. In various embodiments, the remote unit <NUM> may include one or more of the processor <NUM>, the memory <NUM>, the transmitter <NUM>, and the receiver <NUM>, and may not include the input device <NUM> and/or the display <NUM>.

In certain embodiments, the processor <NUM> determine to transmit a buffer status report corresponding to uplink data in response to a trigger condition.

The transmitter <NUM> is used to provide UL communication signals to the network unit <NUM> and the receiver <NUM> is used to receive DL communication signals from the network unit <NUM>. In some embodiments, the transmitter <NUM> may, in response to determining to transmit a buffer status report, transmit the buffer status report to a parent integrated access backhaul device.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for triggering a buffer status report. The apparatus <NUM> includes one embodiment of the network unit <NUM>. Furthermore, the network unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> of the remote unit <NUM>, respectively.

In various embodiments, the processor <NUM> determines to transmit a buffer status report corresponding to uplink data in response to a trigger condition. In various embodiments, the transmitter <NUM>, in response to determining to transmit the buffer status report, transmits the buffer status report to a parent integrated access backhaul device.

Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the network unit <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>.

<FIG> is a schematic block diagram illustrating one embodiment of an integrated access backhaul ("IAB") system <NUM>. The IAB system <NUM> includes a first UE <NUM>, a second UE <NUM>, a first IAB node <NUM>, an IAB donor node <NUM>, a second IAB node <NUM>, a third IAB node <NUM>, and a fourth IAB node <NUM>. As illustrated, the first UE <NUM> is connected to the IAB donor node <NUM> via the first IAB node <NUM>. Moreover, the second UE <NUM> is connected to the IAB donor node <NUM> via the second IAB node <NUM>, the third IAB node <NUM>, and the fourth IAB node <NUM>. The IAB system <NUM>, as illustrated, may be used for multi-hop backhauling via multiple IAB nodes.

As may be appreciated, multi-hop backhauling systems may provide a larger range extension than single hop systems. This may especially be beneficial for frequencies above <NUM> due to a limited range of such frequencies. In some configurations, multi-hop backhauling enables backhauling around obstacles (e.g., buildings).

A maximum number of hops in a deployment may depend on many factors such as frequency, cell density, propagation environment, and traffic load. Thus, flexibility in hop count may be desirable. With an increased number of hops, scalability issues may arise, performance may be limited, and/or signaling load may increase signaling load to undesirable levels.

As may be appreciated, wireless backhaul links may be vulnerable to blockage (e.g., due to moving objects such as vehicles, due to seasonal changes (foliage), due to infrastructure changes (new buildings), and so forth). Such vulnerability may also apply to physically stationary IAB-nodes. In <FIG>, the first UE <NUM> may switch from communicating via the first IAB node <NUM> to communicating with the second IAB node <NUM> if a backhaul link is blocked by objects (e.g., moving objects). Moreover, traffic variations may create uneven load distribution on wireless backhaul links leading to local link congestion and/or node congestion.

In some embodiments, an IAB node may include MT and DU. The MT function may be a component of a mobile equipment, or, as used herein, MT may be a function residing on an IAB node that terminates radio interface layers of a backhaul Uu interface toward the IAB-donor or other IAB nodes.

In various embodiments, a gNB may include a gNB-CU and one or more gNB-DUs. Moreover, a gNB-CU and a gNB-DU may be connected via an F1 interface. A gNB-CU may be a gNB central unit that is a logical node hosting RRC, SDAP, and PDCP protocols of the gNB. Furthermore, a gNB-DU may be a gNB distributed unit that is a logical node hosting RLC, MAC, and PHY layers of the gNB. In some embodiments, one cell is supported by only one gNB-DU.

In <FIG> the IAB nodes may be in a standalone mode which includes one IAB-donor and multiple IAB-nodes. The IAB-donor node <NUM> may be treated as a single logical node that includes a set of functions such as gNB-DU, gNB-CU-CP, gNB-CU-UP and potentially other functions. In certain embodiments, the IAB-donor node <NUM> may be split according to its functions which can all be either collocated or non-collocated as allowed by 3GPP NG-RAN architecture.

In some embodiments, an IAB node may multiplex UE DRBs to BH RLC-channels. Various options may be considered for bearer mapping in an IAB node as illustrated in <FIG> and <FIG>.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> using one-to-one mapping. The system <NUM> includes a first UE <NUM> (e.g., UE1), a second UE <NUM> (e.g., UE2), a third UE <NUM> (e.g., UE3), a first IAB node <NUM>, a second IAB node <NUM>, and a donor IAB node <NUM>. In this one-to-one mapping between UE DRBs and BH RLC-channels, each DRB from the UEs is mapped to a separate RLC channel. For example, DRB1 (e.g., VoIP) corresponding to the first UE <NUM> may be mapped to RLC-CH1 (e.g., RLC-Channel <NUM> = UE1 DRB1), DRB2 (e.g., streaming) corresponding to the first UE <NUM> may be mapped to RLC-CH2 (e.g., RLC-Channel <NUM> = UE1 DRB2), DRB1 (e.g., VoIP) corresponding to the second UE <NUM> may be mapped to RLC-CH3 (e.g., RLC-Channel <NUM> = UE2 DRB1), DRB2 (e.g., web browsing) corresponding to the second UE <NUM> may be mapped to RLC-CH4 (e.g., RLC-Channel <NUM> = UE2 DRB2), DRB1 (e.g., VoIP) corresponding to the third UE <NUM> may be mapped to RLC-CH5 (e.g., RLC-Channel <NUM> = UE3 DRB1), DRB2 (e.g., web browsing) corresponding to the third UE <NUM> may be mapped to RLC-CH6 (e.g., RLC-Channel <NUM> = UE3 DRB2), and DRB3 (e.g., streaming) corresponding to the third UE <NUM> may be mapped to RLC-CH7 (e.g., RLC-Channel <NUM> = UE3 DRB3).

In this embodiment, each UE DRB is mapped onto a separate BH RLC-channel. Furthermore, each BH RLC-channel is mapped onto a separate BH RLC-channel on a next hop (e.g., from the second IAB node <NUM> to the donor IAB node <NUM>). Accordingly, the number of established BH RLC-channels is equal to the number of established UE DRBs.

In some embodiments, a BH RLC channel may be mapped onto BH LCH. The mapping association can include: one BH RLC-channel mapped onto one BH LCH; or multiple BH RLC-channels mapped onto one BH LCH.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> using many-to-one mapping. The system <NUM> includes a first UE <NUM> (e.g., UE1), a second UE <NUM> (e.g., UE2), a third UE <NUM> (e.g., UE3), a first IAB node <NUM>, a second IAB node <NUM>, and a donor IAB node <NUM>. In this many-to-one mapping between UE DRBs and BH RLC-channels, many DRB from the UEs are mapped to one RLC channel. For example, DRB1 (e.g., VoIP) corresponding to the first UE <NUM>, DRB1 (e.g., VoIP) corresponding to the second UE <NUM>, and DRB1 (e.g., VoIP) corresponding to the third UE <NUM> may all be mapped to RLC-CH1 (e.g., RLC-Channel <NUM> = UE1 DRB1 + UE2 DRB1 + UE3 DRB1), DRB2 (e.g., streaming) corresponding to the first UE <NUM> and DRB3 (e.g., streaming) corresponding to the third UE <NUM> may both be mapped to RLC-CH2 (e.g., RLC-Channel <NUM> = UE1 DRB2 + UE3 DRB3), and DRB2 (e.g., web browsing) corresponding to the second UE <NUM> and DRB2 (e.g., web browsing) corresponding to the third UE <NUM> may both be mapped to RLC-CH3 (e.g., RLC-Channel <NUM> = UE2 DRB2 + UE3 DRB2).

Thus, for the many-to-one mapping, several UE DRBs are multiplexed onto a single BH RLC-channel based on specific parameters such as a bearer QoS profile. Other information such as hop-count may also be configured. In some embodiments, the IAB node may multiplex UE DRBs into a single BH RLC-channel even if they belong to different UEs. Furthermore, a packet from one BH RLC-channel may be mapped onto a different BH RLC-Channel on the next hop.

Because a BH RLC-channel multiplexes data from and/or to multiple bearers, and possibly even different UEs, each data block transmitted in a BH RLC-channel may contain an identifier of the UE, DRB, and/or IAB node it is associated with.

Furthermore, in some embodiments, BH RLC channels may be mapped onto a BH LCH in a MAC layer. There may be several mapping options for this. In one embodiment, a one-to-one mapping is established between BH RLC channels and BH LCHs. In another embodiment, several BH RLC channels may be mapped to one LCH.

In some configurations, such as in a <NUM> system, one DRB may be one-to-one mapped onto RLC which is also one-to-one mapped onto LCH. Moreover, RRC may configure LCG that may include several LCHs. A BSR may be reported based on a LCG.

In various embodiments, UL BSR may be used to provide support for QoS-aware packet scheduling. In some embodiments, an UL BSR may refer to data that is buffered for a group of LCGs in a UE. In certain embodiments, UL BSRs may be transmitted using MAC signaling.

In some embodiments, a BSR may be triggered based on the following conditions: a MAC entity has new UL data available for a logical channel which belongs to a LCG; and either: the new UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG; or none of the logical channels which belong to an LCG contains any available UL data, in which case the BSR is referred to as "Regular BSR. " In certain embodiments, UL resources may be allocated and a number of padding bits may be equal to or larger than the size of the Buffer Status Report MAC CE plus its subheader, in which case the BSR is referred to as "Padding BSR. " In various embodiments, retxBSR-Timer expires, and at least one of the logical channels which belong to an LCG contains UL data, in which case the BSR is referred to as "Regular BSR. " In one embodiment, periodicBSR-Timer expires, in which case the BSR is referred to as "Periodic BSR.

Various communications may be used to describe triggers that may be used in an IAB system. In a first communication, a donor IAB (e.g., CU portion) may configure an IAB node2. In one embodiment, a parameter "X" may be configured for the IAB node2.

In a second communication, the IAB node2 (e.g., DU portion) may receive UL data from a child IAB node and/or access UEs.

In some embodiments, the IAB node2 (e.g., MT portion) may determine whether a trigger condition is met. If a trigger condition is met, a buffer status (e.g., BSR) may be triggered to report the buffer status to a parent IAB node.

In certain embodiments, an IAB may transmit a periodic BSR only in response to certain conditions (e.g., trigger conditions) occurring in addition to a timer expiring. As may be appreciated, the timer expiring may also be considered a trigger condition.

In one embodiment, a trigger condition may include that a content of a BO is different from content of a previously indicated BO. In such an embodiment, the trigger condition may occur in addition to the timer expiring. As used herein, BO may be defined as a percentage of a buffer. Furthermore, the percentage of the buffer may be quantified to different levels. For example, index0 may be associated with a range of <NUM>% to <NUM>%, index1 may be associated with a range of <NUM>%-<NUM>%, and so forth. In some embodiments, a trigger condition may include that a content of a BO is different from content of a previous BO by a predetermined percentage (e.g., <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, and so forth) and/or by a predetermined range (e.g., between <NUM>% and <NUM>% different, between <NUM>% and <NUM>% different, and so forth). In such embodiments, an index associated with a range or percentage may be used to indicate the predetermined percentage or the predetermined range. In some embodiments, BO may be associated with one or more LCGs. For example, BO may be associated with all LCGs. In various embodiments, an IAB node may know that a BO is the same as a previously indicated BO if a periodic BSR is not received by the IAB node (e.g., within a predetermined time period).

In another embodiment, a trigger condition may include that a BO is above a predetermined threshold. In such an embodiment, the trigger condition may occur in addition to the timer expiring. The predetermined threshold may be configured by RRC signaling. In such embodiments, BO may be associated with one or more LCGs. For example, BO may be associated with all LCGs. In some embodiments, an IAB node may know that a BO is below the predetermined threshold if a periodic BSR is not received by the IAB node (e.g., within a predetermined time period).

In some embodiments, a BSR is triggered if certain trigger conditions occur even if the timer does not expire. In one embodiment, a trigger condition may include new UL data being available for a UE bearer that belongs to a LCG. In such an embodiment, the new UL data may belong to a UE bearer having a higher priority than the priority of any UE bearer containing available UL data that belongs to any LCG. In the present invention, a trigger condition includes new UL data being available for a UE bearer that belongs to a LCG. In the present invention, none of the UE bearers that belong to a LCG may contain any available UL data. In the present invention, a trigger condition includes new UL data being available for x (e.g., a configured number) UE bearers that belong to a LCG and the UL data is received before a second timer expires. In the present invention, the new UL data belongs to x UE bearers with higher priority than the priority of any UE bearers containing available UL data that belong to any LCG. The second timer may be started at a time at which a BSR is reported. The second timer may be configured by RRC signaling. When the second timer expires and BSR is not triggered, the count for x is set <NUM>. As may be appreciated, x is a number that may be configured by RRC. For example, x may be <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and so forth. In the present invention, a trigger condition includes new UL data being available for y UE bearers that belong to a LCG before a third timer expires. In such embodiments, none of the UE bearers that belong to a LCG may contain any available UL data. The third timer may be started at a time at which a BSR is reported. The third timer may be configured by RRC signaling. When the third timer expires and BSR is not triggered, the count for y is set <NUM>. As may be appreciated, y is a number that may be configured by RRC. For example, y may be <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and so forth. While some of the trigger conditions are described in relation to a UE bearer, similar triggers may be used that use a RLC channel or LCH in place of the UE bearer. In certain embodiments, a trigger condition may include a BO being above a predetermined threshold. In such embodiments, the BSR may be per LCG or for all LCGs.

In a third communication, a parent IAB node (e.g., IAB node3) may allocate UL resources to the IAB node2 (e.g., MT) for UL data transmission. The size of allocated UL resources may be based on a reported buffer status.

In a fourth communication, the IAB node <NUM> (e.g., MT) may schedule the resources for the UL data pending in the buffer and may transmit the UL data.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for triggering a buffer status report. In some embodiments, the method <NUM> is performed by an apparatus, such as the remote unit <NUM> or the network unit <NUM> (e.g., IAB node). In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include determining <NUM> to transmit a buffer status report corresponding to uplink data in response to a trigger condition. In certain embodiments, the method <NUM> includes, in response to determining to transmit the buffer status report, transmitting <NUM> the buffer status report to a parent integrated access backhaul device.

In various embodiments, the method <NUM> comprises receiving the uplink data at a remote unit or an integrated access backhaul device. In some embodiments, transmitting the buffer status report comprises transmitting the buffer status report in response to multiple remote unit bearers being multiplexed into one logical channel. In certain embodiments, the trigger condition comprises a timer corresponding to the buffer status report expiring and a first content of a current buffer occupancy differing from a second content of a previous buffer occupancy.

In one embodiment, the trigger condition comprises the first content being different from the second content by a predetermined percentage range. In various embodiments, the predetermined percentage range is indicated by an index value corresponding to the predetermined percentage range. In some embodiments, the current buffer occupancy and the previous buffer occupancy are associated with at least one logical channel group.

In certain embodiments, the parent integrated access backhaul device determines that the first content and the second content are the same in response to not receiving the buffer status report. In one embodiment, the trigger condition comprises a timer corresponding to the buffer status report expiring and a buffer occupancy exceeding a predetermined threshold. In various embodiments, the predetermined threshold is configured by radio resource control signaling.

In some embodiments, the buffer occupancy is associated with at least one logical channel group. In certain embodiments, the parent integrated access backhaul device determines that the buffer occupancy is less than the predetermined threshold in response to not receiving the buffer status report. In one embodiment, the trigger condition comprises determining that new uplink data is available for a bearer that belongs to a logical channel group, and the bearer has a priority higher than other bearers having available uplink data that belong to any logical channel group.

In various embodiments, the trigger condition comprises determining that new uplink data is available for a bearer that belongs to a logical channel group, and other bearers that belong to any logical channel group do not have available uplink data. In some embodiments, the trigger condition comprises determining that new uplink data is available for a predetermined number of bearers that belong to a logical channel group prior to expiration of a timer, and the predetermined number of bearers has a priority higher than other bearers having available uplink data that belong to any logical channel group. In certain embodiments, the timer is started in response to transmitting a prior buffer status report.

In one embodiment, the timer is configured by radio resource control signaling. In the present invention, method <NUM> comprises, in response to the expiration of the timer and the trigger condition not occurring, setting the predetermined number of bearers equal to zero. In the present invention, the predetermined number of bearers is configured by radio resource control signaling.

In the present invention, the trigger condition comprises determining that new uplink data is available for a predetermined number of bearers that belong to a logical channel group prior to expiration of a timer, other bearers that belong to any logical channel group do not have available uplink data. In one embodiment, the timer is started in response to transmitting a prior buffer status report. In various embodiments, the timer is configured by radio resource control signaling.

In the present invention, the method <NUM> comprises, in response to the expiration of the timer and the trigger condition not occurring, setting the predetermined number of bearers equal to zero. In the present invention, the predetermined number of bearers is configured by radio resource control signaling. In one embodiment, the trigger condition comprises a buffer occupancy exceeding a predetermined threshold. In various embodiments, the buffer occupancy is for one logical channel group. In some embodiments, the buffer occupancy is for all logical channel groups.

In one embodiment, a method comprises: determining to transmit a buffer status report corresponding to uplink data in response to a trigger condition; and in response to determining to transmit the buffer status report, transmitting the buffer status report to a parent integrated access backhaul device.

In various embodiments, the method comprises receiving the uplink data at a remote unit or an integrated access backhaul device.

In some embodiments, transmitting the buffer status report comprises transmitting the buffer status report in response to multiple remote unit bearers being multiplexed into one logical channel.

In certain embodiments, the trigger condition comprises a timer corresponding to the buffer status report expiring and a first content of a current buffer occupancy differing from a second content of a previous buffer occupancy.

In one embodiment, the trigger condition comprises the first content being different from the second content by a predetermined percentage range.

In various embodiments, the predetermined percentage range is indicated by an index value corresponding to the predetermined percentage range.

In some embodiments, the current buffer occupancy and the previous buffer occupancy are associated with at least one logical channel group.

In certain embodiments, the parent integrated access backhaul device determines that the first content and the second content are the same in response to not receiving the buffer status report.

In one embodiment, the trigger condition comprises a timer corresponding to the buffer status report expiring and a buffer occupancy exceeding a predetermined threshold.

In various embodiments, the predetermined threshold is configured by radio resource control signaling.

In some embodiments, the buffer occupancy is associated with at least one logical channel group.

In certain embodiments, the parent integrated access backhaul device determines that the buffer occupancy is less than the predetermined threshold in response to not receiving the buffer status report.

In one embodiment, the trigger condition comprises determining that new uplink data is available for a bearer that belongs to a logical channel group, and the bearer has a priority higher than other bearers having available uplink data that belong to any logical channel group.

In various embodiments, the trigger condition comprises determining that new uplink data is available for a bearer that belongs to a logical channel group, and other bearers that belong to any logical channel group do not have available uplink data.

In some embodiments, the trigger condition comprises determining that new uplink data is available for a predetermined number of bearers that belong to a logical channel group prior to expiration of a timer, and the predetermined number of bearers has a priority higher than other bearers having available uplink data that belong to any logical channel group.

In certain embodiments, the timer is started in response to transmitting a prior buffer status report.

In one embodiment, the timer is configured by radio resource control signaling.

In various embodiments, the method comprises, in response to the expiration of the timer and the trigger condition not occurring, setting the predetermined number of bearers equal to zero.

In some embodiments, the predetermined number of bearers is configured by radio resource control signaling.

In certain embodiments, the trigger condition comprises determining that new uplink data is available for a predetermined number of bearers that belong to a logical channel group prior to expiration of a timer, other bearers that belong to any logical channel group do not have available uplink data.

In one embodiment, the timer is started in response to transmitting a prior buffer status report.

In various embodiments, the timer is configured by radio resource control signaling.

In some embodiments, the method comprises, in response to the expiration of the timer and the trigger condition not occurring, setting the predetermined number of bearers equal to zero.

In certain embodiments, the predetermined number of bearers is configured by radio resource control signaling.

In one embodiment, the trigger condition comprises a buffer occupancy exceeding a predetermined threshold.

In various embodiments, the buffer occupancy is for one logical channel group.

In some embodiments, the buffer occupancy is for all logical channel groups.

In one embodiment, an apparatus comprises: a processor that determines to transmit a buffer status report corresponding to uplink data in response to a trigger condition; and a transmitter that, in response to determining to transmit the buffer status report, transmits the buffer status report to a parent integrated access backhaul device.

In various embodiments, the apparatus comprises a receiver that receives the uplink data at a remote unit or an integrated access backhaul device.

In some embodiments, the transmitter transmits the buffer status report by transmitting the buffer status report in response to multiple remote unit bearers being multiplexed into one logical channel.

In various embodiments, the processor, in response to the expiration of the timer and the trigger condition not occurring, sets the predetermined number of bearers equal to zero.

In some embodiments, the processor, in response to the expiration of the timer and the trigger condition not occurring, sets the predetermined number of bearers equal to zero.

Claim 1:
A method (<NUM>) comprising:
determining (<NUM>) to transmit a buffer status report corresponding to uplink data in response to a trigger condition, wherein the trigger condition comprises determining that new uplink data is available for a predetermined number of bearers that belong to a logical channel group prior to expiration of a timer, and the predetermined number of bearers has a priority higher than other bearers having available uplink data that belong to any logical channel group, and the predetermined number of bearers is configured by radio resource control signaling;
in response to the expiration of the timer and the trigger condition not occurring, setting the predetermined number of bearers equal to zero; and
in response (<NUM>) to determining to transmit the buffer status report, transmitting the buffer status report to a parent integrated access backhaul device.