BACKGROUND

Technical Field

[0001] The exemplary and non-limiting embodiments relate generally to wireless communication and, more particularly, to scheduling of communications.

Brief Description of Prior Developments

[0002] Integrated Access and Backhaul (IAB) is a study item for 3GPP Release 15 and is scheduled to be a work item for Release 16. Work currently underway in RAN2 and RAN 3 envisions support for a multi-hop self-backhaul network whereby 5G is used to transport packets between IAB nodes and a Donor such as with a fiber connection to the NGC or EPC for example.

[0003] The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:

3GPP 3rd Generation Partnership Project

4G Fourth Generation

5G Fifth Generation BSR Buffer Status Report

cu Central Unit

DeNB Donner eNB

DL Downlink

DU Distributed Unit

eNB (or eNodeB) evolved Node B (e.g., an LTE base station) gNB 5 ^th generation Node B

EPC Enhanced Packet Core

LAB Integrated Access and Backhaul

LTE Long Term Evolution

MT Mobile Terminal

NGC Next Generation Core

RRC Radio Resource Control

Rx Receive

sBH self back haul

Tx Transmit

UE User Equipment

UL Uplink SUMMARY

[0004] The following summary is merely intended to be exemplary. The summary is not intended to limit the scope of the claims.

[0005] In accordance with one aspect, an example method comprises receiving, at an integrated access and backhaul node, signals from at least one subtending integrated access and backhaul node and at least one User Equipment; determining at the integrated access and backhaul node, at least partially based upon the received signals, information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node, and a number of User Equipment on the at least one subtending integrated access and backhaul node; and transmitting the determined information from the integrated access and backhaul node to an upstream node .

[0006] In accordance with another aspect, an example apparatus is provided comprising an integrated access and backhaul node, where the integrated access and backhaul node comprises: means for receiving at the integrated access and backhaul node signals from at least one subtending integrated access and backhaul node and at least one User Equipment; means for determining at the integrated access and backhaul node, at least partially based upon the received signals, information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node; and a number of User Equipment on the at least one subtending integrated access and backhaul node; and means for transmitting the determined information from the integrated access and backhaul node to an upstream node.

[0007] In accordance with another aspect, an example embodiment is provide with a non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: determining at an integrated access and backhaul node, at least partially based upon the signals received at the integrated access and backhaul node from at least one subtending integrated access and backhaul node and at least one User Equipment, Information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node, and a number of User Equipment on the at least one subtending integrated access and backhaul node; and enabling transmitting of the determined information from the integrated access and backhaul node to an upstream node.

[0008] In accordance with another aspect, an example method comprises receiving information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions. [0009] In accordance with another aspect, an example embodiment is provided in an apparatus comprising means for receiving information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and/or a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and means for using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions.

[0010] In accordance with another aspect, an example embodiment is provided with a non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: enable receiving information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions . BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The foregoing aspects and other features are explained in the following description, taken in connection with the accompanying drawings, wherein:

[0012] Fig. 1 is a schematic diagram illustrating an example of various devices in a network;

[0013] Fig. 2 is a diagram illustrating some components of some of the devices shown in Fig. 1;

[0014] Fig. 3 is a diagram illustrating scheduling not using a Weighted Proportional Fair (wPF) scheduler;

[0015] Fig. 4 is a diagram illustrating scheduling using a Weighted Proportional Fair (wPF) scheduler;

[0016] Fig. 5 is a diagram illustrating an example method;

[0017] Fig. 6A-6D are diagrams illustrating handling of downlink packets; and

[0018] Fig. 7 is a diagram illustrating an example method.

DETAILED DESCRIPTION OF EMBODIMENTS

[0019] Referring to Fig. 1, a schematic diagram illustrating an example of various devices in a network 100 is shown. The network 100 in this example supports a multi-hop self-backhaul whereby 5G may used to transport packets between Integrated Access and Backhaul (IAB) nodes and a Donor, such as with a fiber connection to the Next Generation Core (NG-Core or NGC) or Evolved Packet Core (EPC) for example. In this example three (3) IAB nodes 12 are shown; IAB Node-1 14, IAB Node-2 16 and IAB Node-3 18. However, more or less nodes may be provided and their topology may vary. Fig. 1 also shows a Donor 20 and various User Equipments (UEs) 110. Each IAB node consists logically of at least a UE or Mobile Termination (MT) (IAB MT) that communicates with upstream nodes, and a RAN component, such as a gNB Distributed Unit (DU) for example (DU/gNB) , that communicates with downstream IAB nodes or subscriber UEs 110. In one type of example embodiment, the IAB Node UE and IAB Node MT may be used interchangeably. A UE contains a MT, and the MT part supports the access interface.

[0020 ] Turning to Fig. 2, this figure shows a block diagram of possible and non-limiting exemplary components for some of the devices shown in Fig. 1. In Fig. 2, the user equipment (UE) 110 is in wireless communication with the wireless network 100. The UE is a wireless, typically mobile, device that can access the wireless network. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver (Rx) 132 and a transmitter (Tx) 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with the apparatus 170 via a wireless link 111. 170 may be any one of the TAB donor 20 or the IAB nodes 12 for example. In this example the base station 170 has features or components of a gNB . A wireless attached IAB node, a Donor IAB node and a conventional gNB may be implemented on identical hardware or may include different hardware, but some of the core components such as processor { s ) , memory (ies), receiver (s) and transmitter (s } are present in each. Fig. 2 is merely intended to show a simplified version of some of the components of a IAB node, a Donor IAB node and a conventional gNB, but it is understood that there is a differentiation between a wireless IAB node and a Donor IAB node/gNB.

[0021] The gNB 170 is a base station (for example, for 5G/LTE} that provides access by wireless devices such as the UE 110 to the wireless network 100. The gNB 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F ( s) ) 161, and one or more transceivers 160 interconnected through one or more buses- 157. Each of the one or more transceivers 160 includes a receiver (Rx) 162 and a transmitter (Tx) 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the gNB 170 to perform one or more of the operations as described herein. The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 communicate using, for example, link 176. The link 176 may be wired or wireless or both and may implement, for example, an X2 or Xn interface .

[0022] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195, with the other elements of the gNB 170 being physically in a different location from the RRH, and the one or more buses 157 could be implemented in part as fiber optic cable to connect the other elements of the gNB 170 to the RRH 195.

[0023] It is noted that description herein indicates that "cells" perform functions, but it should be clear that the gNB that forms the cell will perform the functions. The cell makes up part of an gNB. That is, there can be multiple cells per gNB. For instance, there could be three cells for a single gNB carrier frequency and associated bandwidth, each cell covering one-third of a 360 degree area so that the single gNB' s coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and an gNB may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the gNB has a total of 6 cells. [ 0024 ] The wireless network 100 may include one or more network elements 190. For example, with a EPC the network elements 190 may include MME (Mobility Management Entity) and/or SGW (Serving Gateway) functionality. As another example, with a 5G core network (5GCN) the network elements may include Access and Mobility Function (AMF) , MME (Mobility Management Entity) and/or SGW (Serving Gateway) functionality. Connectivity with a further network may be provided, such as a telephone network and/or a data communications network (for example, the Internet) . The gNB/eNB 170 is coupled via a link 131 to the network element 190. The link 131 may be implemented as, for example, an SI or NG interface. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.

[ 0025] Those skilled in the art will appreciate that the various network elements shown in Fig. 2 may be implemented differently in future wireless networks, and are not limited to 4G, LTE or 5G wireless networks. For example, the terms NCE, MME, and SGW are terms generally used for the core elements in a LTE network. In contrast to LTE, future wireless networks may carry out network functions (NFs) by a plurality of cooperating devices. The different NFs, may include for example, Access and Mobility Function (AMF) , Session Management Function (SMF) , Policy Control Function (PCF) , Application Function (AF) , Authentication Server Function (AUSF) , User Plane Function (UPF) , and User Data Management (UDM) . These NFs may be a virtualized function instantiated on an appropriate platform, such as a cloud infrastructure. For example, certain protocols (such as non real-time protocols for example) may be performed by one or more centralized units (CUs) in a cloud infrastructure, while one or more distributed units (DUs) operate the remaining protocols (e.g. real-time protocols) of the 5G radio interface. In this way, the various NFs may be split between CUs and DUs. Together a CU, underlying DUs, and RRHs may be considered as forming a logical base station (which may be represented by gNB 170 in Fig. 2 for example) .

[0026] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects. [0027] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, eNB/gNB 170, and other functions as described herein.

[0028] In general, the various example embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions . [0029] A Central Unit (CU) is a logical node which may include the functions (i.e., gNB functions) such as Transfer of user data, Mobility control, Radio access network sharing, Positioning, Session Management etc., except those functions allocated exclusively to the DU. A CU may control the operation of DUs over a front-haul (Fl) interface. A central unit (CU) may also be known as BBU/REC/RCC/C-RAN/V-RA . A Distributed Unit (DU) is a logical node which may include a subset of the functions (i.e., gNB functions), depending on the functional split option. The operation of the DU may be controlled by the CU. A Distributed Unit (DU) may also be known with other names like RRH/RRU/RE/RU .

[0030] Referring back to Fig. 1, both the Donor 20 and each IAB node 12 may directly serve a subscriber UE 110. IAB Nodes 12 and subscriber UEs 110 may handover to different upstream IAB nodes 12 or to a different Donor 20 as radio conditions change. Additional UEs 110 may connect to any IAB node 12 or to the Donor 20 as subscribers or devices initiate transactions. In addition, new additional IAB nodes may be deployed and establish connectivity with an upstream IAB node or the Donor .

[0031] The Donor 20 comprises a scheduler 22 as shown in Fig. 3. In one type of example the scheduler 22 may simply see logical channels from three UEs, two of which are IAB-Node-UEs (IAB Node-1 and IAB Node-2) , and one of which is a subscriber UE to the Donor 20. If proportional fair scheduling is used to allocate resources amongst these three logical channel UEs (assuming equivalent radio conditions) , one third is provided to each as shown by 24, 26, 28 even though, unbeknownst to the Donor 20, the IAB Node-1 UE 110 has five subtending subscriber UEs 110i ₄ , 110ie and IAB Node 2 has two subtending subscriber UEs llOie- A number of "subtending" subscriber UEs generally means the aggregate number of downstream subscriber UEs from a particular IAB node or donor; attached via the various branches including through hops. For the example shown in Fig. 3, the IAB node-3 18 has four (4) subtending subscriber UEs llO s , the IAB node-2 16 has two (2) subtending subscriber UEs 110i _6f the IAB node-1 14 has five (5) subtending subscriber UEs 110i ₄ and l l O s , and the donor 20 has eight (8) subtending subscriber UEs l l Cko l l On , l l O e , 110i ₈ . Likewise, IAB Node-1 14, IAB Node-2 16, IAB Node-3 18 are subtending integrated access and backhaul nodes relative to the donor 20, and IAB Node-3 is a subtending integrated access and backhaul node relative to the IAB Node-1 14. Thus, "subtending" generally means connected, directly or indirectly in a "logical" fashion/scheme, in a line.

[ 0032 ] For the system shown in Fig. 3, the proportional fair scheduler 22 is merely configured to determine the number N of "proximate" connections 24, 26, 28 relative to the scheduler 22 and allocates resources from that scheduler 22 based upon that number. In the example shown, because there are three (3) proximal connections 24, 26, 28, the scheduler 22 divides the resources by

N=3; which equals 1/3 for each connection 24, 26, 28 in this example. Likewise, the downstream IAB nodes also then use the number N of their respective "proximate" downstream connections relative to their respective schedulers to allocate resources from their respective schedulers based upon their respective number (s) of "proximate" downstream connections . When applied at each hop H and UE connection in the IAB tree shown in Fig. 3, the resulting allocation of resources is indicated by the fractions shown including 1/24 to each of IIO _IB , 1/6 to each of IIO14, 1/6 to 110i ₆ , and 1/3 to IIO20- This limited proximal location connection proportional fair scheduling is clearly an undesirable outcome as the subscriber UE IIO20 directly connected to the Donor 20 gets eight times the resources compared to one of the UEs llOis connected to IAB-Node-3 18 (1/3 versus 1/24) . Please note that this merely illustrates the problem with use of limited proximal location connection proportional fair scheduling in a simplified scenario. It assumes all UEs have data pending to transmit or receive, and all UEs and IAB Nodes are in the same radio conditions.

[0033] Instead of using proportional fair scheduling (pFS), the schedule 22 is configured to use a Weighted Proportional Fair (wPF) scheduler or other similar such scheduler which is able to determine a more accurate number of UEs in a downstream direction from the scheduler including beyond one hop, such as actual numbers of UEs two or more hops downstream from the scheduler for example. So long as the scheduler is able to take into consideration a more accurate number of UEs downstream from the scheduler by a scheduling system different from the limited proximal number connection proportional fair scheduling as used in Fig. 3, a fairer resource allocation will be provided. A proportional fair scheduling which is not limited to only the number of proximal connections, which takes into consideration a number of subtending users (with data pending) , provides this fairer resource allocation. With Weighted Proportional Fair scheduling, for example, a weight factor may be applied to the user selection metric at each hop H. Under constant channel conditions, the fraction of time slots allocated to a link by Weighted Proportional Fair scheduling may be proportional to a weight factor. If the weight factor is set to a number of subtending users {with data pending) of an IAB Node, Weighted Proportional Fair scheduling may approximate a wireless Greedy Primal Dual (wGPD) algorithm scheduler in that the scheduler 22 may assign timeslots according to the number of UEs with data pending. Features as described herein allow for a signaling protocol for determining the weight factors according to the number of subtending users of an IAB node or Donor; which was previously inadequate for using wPF or similar scheduler in a 5G system with IAB.

[0034] Features as described herein enable scheduling techniques, such as wPF in a 5G IAB networks for example, by enhancing signaling between nodes in the IAB topology. The IAB Nodes 12 may receive Buffer Status Reports (BSRs) and/or Scheduling Requests (SR) from subscriber UEs 110 as usual. The BSRs indicate the amount of pending uplink data, if any. Internal to the IAB Node, radios may relay to the IAB Node MT the following: a. the number of directly connected subscriber UEs with data pending {as per BSR and/or SR) , and/or b. the number of directly connected UEs in RRC connected state; and c. the number of subscriber UEs with data pending on subtending IAB nodes, and/or d. the number UEs in RRC connected state on subtending IAB nodes

In one example embodiment "a" and "c" above, and "b" and "d" above may instead be sent by the radio of the UE to the IAB Node MT of the IAB node rather than the DU/gNB of the IAB node. The "UEs with data pending" in option "a" above may include UEs with only downlink link data pending. This latter case differs from current BSR reports which only address uplink data.

[0035] The IAB Node MT sends the information to the upstream node (IAB or Donor) indicating the total number of subtending UEs with pending uplink data and/or the total number of UEs in the RRC Connected state. This information may be conveyed in an enhanced BSR or SR, or in a header field of user plane packets. The scheduler in the receiving IAB node may weight scheduling priority for uplink and downlink transmissions using the received information. The steps noted above may be repeated asynchronously at each IAB node and the Donor.

[0036] The four steps for conveying UE information on the uplink as described above is further shown in Figs. 4 and 5. The Donor and each IAB Node Radio may act independently to schedule directly connected UEs and IAB Node MTs as BSRs are received. As illustrated by 1 in Fig. 4 and 50 in Fig. 5, the IAB nodes may receive Buffer Status Reports (BSRs) and/or Scheduling Requests (SR) from subscriber UEs. The BSRs indicate the amount of pending uplink data, if any. As illustrated by 2 in Fig. 4 and 52 in Fig. 5, internal to the IAB Node, radios may relay to the IAB Node MT information. The information may include the number of directly connected subscriber UEs with data pending (as per BSR and/or SR} , and/or the number of directly connected UEs in RRC connected state. The information may include the number of subscriber UEs with data pending on subtending IAB nodes, and/or the number UEs in RRC connected state on subtending IAB nodes. As illustrated by 3 in Fig. 4 and 54 in Fig. 5, the IAB Node MT may send the information 80 to the upstream node (IAB or Donor) indicating the total number of subtending UEs with pending uplink data and/or the total number of UEs in the RRC Connected state. This information may be conveyed in an enhanced BSR or SR, or in a header field of user plane packets. As illustrated by 4 in Fig. 4 and 56 in Fig. 5, the scheduler in the receiving IAB node and the Donor may then weight scheduling priority for uplink and downlink transmissions using the received information 80. For example, with the eight (8) UEs shown in Fig. 4, each UE 110 may be allocated 1/8 of the resources by the scheduler (s) . This is more equitable and fairer than the situation shown in Fig. 3 where some of the same UEs 110is would only have 1/24 of the resources allocated to them and one of the UEs IIO20 would have 1/3 of the resources allocated to it. In some alternate embodiments, the Weighted Proportional Fair scheduling may not be totally equal; such as resulting in the 1/8 resource allocation for eight (8) UEs noted above for example. Besides the total number of UEs downstream of the Donor 20 being used as a weight factor in the Weighted Proportional Fair scheduling, one or more other variable parameters may be taken into account in using the Weighted Proportional Fair scheduling such as the potential instantiations data rate (i.e. spectral efficiency which may derived from channel quality feedback) for a UE and the time-windowed average data rate the UE has experienced for example. Besides the total number of UEs downstream of the Donor 20 and perhaps other variable parameters, one or more fixed parameters may be taken into account in using the Weighted Proportional Fair scheduling such as QoS parameters like guaranteed throughput, allowable delay, jitter and the like. Thus, additional weighting may be applied to account for the relative QoS between UE bearers based on different traffic types (e.g. voice, data, mission critical data, industrial automation, etc.). Schedulers 22 may be provided at each IAB node as illustrated by Fig. 4. However, in an alternate example, not all IAB nodes need to have a scheduler or a scheduler which uses Weighted Proportional Fair scheduling. Steps 50-56 may be repeated asynchronously at each IAB node and the Donor. Features as described herein may also be used with a system using both the proportional fair scheduling and the Weighted Proportional Fair scheduling or other scheduling techniques; perhaps switching between or among them based upon different situations or parameters.

[ 0037 ] In addition to the method described above, downstream packets destined to different UEs may be aggregated in the Core Network or in an upstream node. Aggregation may occur in the Donor 20, at the IAB nodes 12 or in the User Plane Function (UPF) as is shown in Figs. 6A and 6B. Similar information to that described above identifying the number of UEs in an aggregated bearer may be conveyed on each downlink hop so the scheduler at each hop is explicitly aware of the number of UEs for which downlink data are pending.

[0038] As with the uplink, either signaling messages, such as GPRS tunneling protocol user plane (GTP-U) for example, or a field (a "UE count field") in a user plane packet header may be used to convey the information. The "UE count field" may be localized such that the "UE count" identifies only the number or UEs flows aggregated in a current Protocol Data Unit (PDU) . Alternatively, the UE field may represent a composite of many PDUs such that it represents a running average of the number of UEs scheduled. The "UE count field" may be UE specific such that the presence of individual UEs with an aggregated PDU may be uniquely identified. With a UE specific encoding, the scheduler may determine the UE count based on the PDUs queued for transmission residing in the IABs node buffer. With features as described herein, the scheduler is enabled to receive information that is required for the scheduler to achieve a level of fairness (in the sense of proportional fair) when allocating resources. Additional information may also affect scheduling, for example when in-band IAB is used, to split resources between IAB Node MT Tx/Rx (for backhaul) , and IAB Node Radio (DU/gNB) Tx/Rx.

[0039] Referring also to Fig. 7, a diagram is shown illustrating an example method of using the information sent by the IAB Node. As illustrated by block 70, an upstream node, such as the Donor 20 one of the IAB node 14 for example, may receive information 80 from a downstream integrated access and backhaul node 12. the information comprises at least one of a number of User Equipment directly connected with the downstream integrated access and backhaul node having data pending and a number of User Equipment directly connected with the downstream integrated access and backhaul node in radio resource control connected state; and at least one of a number of User Equipment with data pending on at least one subtending downstream integrated access and backhaul node and a number User Equipment in radio resource control connected state on at least one downstream subtending integrated access and backhaul node. As indicated by block 72, the upstream node may then use the received information by the upstream integrated access and backhaul node to weight scheduling priority for uplink and/or downlink transmissions.

[ 0040 ] Figs. 6A and 6B show the handling of downlink packets in some embodiments for downlink packet aggregation at Donor and IAB nodes and downlink packet aggregation UPF. In the absence of this, individual UE flows may be aggregated prior to transmission to a downstream node. Aggregation may occur at the User Plane Function (UPF) 58 in the core network in which case UE packets may be sent over a common Protocol Data Unit (PDU) session to a downstream Donor. Alternatively or in addition, aggregation may occur in the Donor and IAB nodes in which case the UEs may share one or more Logical Channels and/or Radio Bearers on the IAB hops. Referring particularly to Fig. 6A, the Donor 20 may receive individual UE flows as illustrated by 61. The UEs may be aggregated in a bearer as indicated by 62. The radio part may communicate the number of UEs to the UE part as indicated by 63. The scheduler is unaware of individual UEs as indicated by 64.

[0041] As illustrated by Figs. 6C and 6D, which may be used in addition to the method described above with Figs. 6A and 6B, or as an alternative to the method described above with Figs. 6A and 6B , the number of UEs that are aggregated may be signaled to the downstream node, either in a user plane packet header, or via signalling. Thus, Figs. 6C and 6D illustrated enhanced signaling to support IAB scheduling. At each hop, the scheduler may be made aware of the number of UEs for which downlink data are pending, and can provide the appropriate scheduler weight for sending downstream packets. As illustrated by Fig. 6C, the central unit (CU) may communicate the number of UEs to the Distributed Units (DUs) as shown by step 65. The radio part may communicate the number of UEs to the UE part as shown by step 66. The number of UEs may be sent in a signaling message or in a packet header as shown by step 67. The scheduler may be aware of individual UEs with data pending as shown by step 68. As illustrated by Fig. 6D, the number of UEs may be sent in signaling messages or in a packet header from the User Plane Function (UPF) and the Donor 20. Features as described herein may also be used with a system using more than one of the downlink handling schemes noted above; perhaps switching among the four shown in Figs. 6A-6D based upon different situations or parameters.

[0042] In one example embodiment, a method is provided comprising: receiving, at an integrated access and backhaul node, signals from at least one subtending integrated access and backhaul node and at least one User Equipment; determining at the integrated access and backhaul node, at least partially based upon the received signals, information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node ; and a number of User Equipment on at least one subtending integrated access and backhaul node; and transmitting the determined information from the integrated access and backhaul node to an upstream node .

[0043] The determining of the information may comprise a number of the User Equipment directly connected with the integrated access and backhaul node having data pending; and/or a number of the User Equipment with data pending on at least one subtending integrated access and backhaul node. The determining of the information may comprise a number of the User Equipment directly connected with the integrated access and backhaul node in radio resource control connected state; and/or a number of the User Equipment in radio resource control connected state on at least one subtending integrated access and backhaul node. The receiving may occur at a base station of the integrated access and backhaul node. The receiving may occur at a mobile terminal of the integrated access and backhaul node. The determining of the number of User Equipment directly connected with the integrated access and backhaul node may include the number of User Equipment having only downlink link data pending. The determining of the number of User Equipment directly connected with the integrated access and backhaul node may include the number of User Equipment having only uplink link data pending. The receiving of the signals may comprise receiving a buffer status report and/or a scheduling request. The transmitting of the determined information may comprise transmitting an enhanced buffer status report and/or a modified scheduling request. The transmitting of the determined information may comprise transmitting the information in a header field of a user plane packet. The method may further comprise the upstream node using the determined information to weight scheduling priority for uplink and/or downlink transmissions. The method may further comprise receiving downlink packets by the integrated access and backhaul node from the upstream node, where the downlink packets are aggregated. The method may further comprise receiving a- signal by the integrated access and backhaul node from the upstream node in a user plane packet header or via user plane signaling regarding the aggregated downlink packets.

[0044] An example embodiment may be provided in an apparatus comprising an integrated access and backhaul node, where the integrated access and backhaul node comprises: means for receiving at the integrated access and backhaul node signals from at least one subtending integrated access and backhaul node and at least one User Equipment; means for determining at the integrated access and backhaul node, at least partially based upon the received signals, information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node; and a number of User Equipment on the at least one subtending integrated access and backhaul node; and means for transmitting the determined information from the integrated access and backhaul node to an upstream node. [0045] The means for determining the information may be configured to determine: a number of the User Equipment directly connected with the integrated access and backhaul node having data pending; and/or a number of the User Equipment with data pending on at least one subtending integrated access and backhaul node. The means for determining the information may be configured to determine: a number of the User Equipment directly connected with the integrated access and backhaul node in radio resource control connected state; and/or a number of the User Equipment in radio resource control connected state on at least one subtending integrated access and backhaul node. The means for receiving may comprise a base station of the integrated access and backhaul node. The means for receiving may comprise a mobile terminal of the integrated access and backhaul node. The means for determining the number of User Equipment directly connected with the integrated access and backhaul node may be configured to determine the number of User Equipment having only downlink link data pending. The means for determining of the number of User Equipment directly connected with the integrated access and backhaul node may be configured to determine the number of User Equipment having only uplink link data pending. The means for receiving the signals may comprise means for receiving a buffer status report and/or a scheduling request. The means for transmitting the determined information may comprise means for transmitting an enhanced buffer status report and/or a modified scheduling request. The means for transmitting the determined information may comprise means for transmitting the information in a header field of a user plane packet. The apparatus may further comprise means for receiving downlink packets by the integrated access and backhaul node from the upstream node, where the downlink packets are aggregated. The apparatus may further comprise means for receiving a signal by the integrated access and backhaul node from the upstream node in a user plane packet header or via user plane signaling regarding the aggregated downlink packets.

[ 0046 ] An example embodiment may be provided with a non- transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: determining at an integrated access and backhaul node, at least partially based upon the signals received at the integrated access and backhaul node from at least one subtending integrated access and backhaul node and at least one User Equipment, information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node, and a number of User Equipment on the at least one subtending integrated access and backhaul node; and enabling transmitting of the determined information from the integrated access and backhaul node to an upstream node.

[ 0047 ] The determining of the information may comprise a number of the User Equipment directly connected with the integrated access and backhaul node having data pending; and/or a number of the User Equipment with data pending on at least one subtending integrated access and backhaul node. The determining of the information may comprise a number of the User Equipment directly connected with the integrated access and backhaul node in radio resource control connected state; and/or a number of the User Equipment in radio resource control connected state on at least one subtending integrated access and backhaul node. The receiving may occur at a base station of the integrated access and backhaul node. The receiving may occur at a mobile terminal of the integrated access and backhaul node. The determining of the number of User Equipment directly connected with the integrated access and backhaul node may include the number of User Equipment having only downlink link data pending. The determining of the number of User Equipment directly connected with the integrated access and backhaul node may include the number of User Equipment having only uplink link data pending. The receiving of the signals may comprise receiving a buffer status report and/or a scheduling request. The transmitting of the determined information may comprise transmitting an enhanced buffer status report and/or a modified scheduling request. The transmitting of the determined information may comprise transmitting the information in a header field of a user plane packet. The operations may further comprise receiving a signal by the integrated access and backhaul node from the upstream node in a user plane packet header or via user plane signaling regarding the aggregated downlink packets.

[ 0048 ] An example method may be provided comprising receiving information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions .

[0049] The using of the received information by the integrated access and backhaul node or donor to weight the scheduling priority may comprise a scheduler using a weighted proportional fair scheduling to determine the scheduling priority. The information comprises: a number of the User Equipment directly connected with the integrated access and backhaul node having data pending; and/or a number of the User Equipment with data pending on the at least one subtending integrated access and backhaul node. The information may comprise: a number of the User Equipment directly connected with the integrated access and backhaul node in radio resource control connected state; and/or a number of the User Equipment in radio resource control connected state on the at least one subtending integrated access and backhaul node. The information may comprise an enhanced buffer status report and/or a modified scheduling request. The method may further comprise transmitting downlink transmissions to the downlink integrated access and backhaul node based upon the weighted scheduling priority. The method may further comprise transmitting downlink transmissions to at least one other downlink integrated access and backhaul node and/or at least one user equipment based upon the weighted scheduling priority. The method may further comprise transmitting scheduling information to at least one other downlink integrated access and backhaul node via a user plane packet header or via user plane signaling regarding aggregated downlink packets transmitted to the at least one other downlink integrated access and backhaul node.

[0050] An example embodiment may be provided in an apparatus comprising means for receiving information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and/or a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and means for using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions.

[0051] The means for using the received information by the integrated access and backhaul node or donor to weight the scheduling priority may comprise a scheduler configured to use a weighted proportional fair scheduling to determine the scheduling priority. the information comprises: a number of the User Equipment directly connected with the integrated access and backhaul node or donor having data pending; and/or a number of the User Equipment with data pending on the at least one subtending downstream integrated access and backhaul node. The information may comprise: a number of the User Equipment directly connected with the integrated access and backhaul node in radio resource control connected state; and/or a number of the User Equipment in radio resource control connected state on the at least one subtending downstream integrated access and backhaul node. The information may comprise an enhanced buffer status report and/or a modified scheduling request. The apparatus may further comprise means for transmitting downlink transmissions to the downlink integrated access and backhaul node based upon the weighted scheduling priority. The apparatus may. further comprise means for transmitting downlink transmissions to at least one other downlink integrated access and backhaul node and/or at least one user equipment based upon the weighted scheduling priority. The apparatus may further comprise means for transmitting scheduling information to at least one other downlink integrated access and backhaul node via a user plane packet header or via user plane signaling regarding aggregated downlink packets transmitted to the at least one other downlink integrated access and backhaul node.

[0052] An example embodiment may be provide with a non- transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising enable receiving information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions. [0053] The using of the received information by the integrated access and backhaul node or donor to weight the scheduling priority may comprise a scheduler using a weighted proportional fair scheduling to determine the scheduling priority. The information comprises a number of the User Equipment directly connected with the integrated access and backhaul node having data pending; and/or a number of the User Equipment with data pending on the at least one subtending integrated access and backhaul node. The information may comprise a number of the User Equipment directly connected with the integrated access and backhaul node in radio resource control connected state; and/or a number of the User Equipment in radio resource control connected state on the at least one subtending integrated access and backhaul node. The information may comprise an enhanced buffer status report and/or a modified scheduling request. The operations may further comprise transmitting downlink transmissions to the downlink integrated access and backhaul node based upon the weighted scheduling priority. The operations may further comprise transmitting downlink transmissions to at least one other downlink integrated access and backhaul node and/or at least one user equipment based upon the weighted scheduling priority. The operations may further comprise transmitting scheduling information to at least one other downlink integrated access and backhaul node via a user plane packet header or via user plane signaling regarding aggregated downlink packets transmitted to the at least one other downlink integrated access and backhaul node.

[0054] In accordance with one example embodiment, an apparatus may be provided comprising at least one processor; and at least one non-transitory memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: receive, at an integrated access and backhaul node, signals from at least one of another integrated access and backhaul node and at least one User Equipment; determine at the integrated access and backhaul node, based upon the received signals, information comprising at least one of: a number of User Equipment directly connected with the integrated access and backhaul node ; and a number of User Equipment on at least one subtending integrated access and backhaul node; and transmit the determined information from the integrated access and backhaul node to an upstream node.

[0055] In accordance with one example embodiment, an apparatus may be provided comprising at least one processor; and at least one non-transitory memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: receive information by an integrated access and backhaul node or donor from a downstream integrated access and backhaul node, where the information comprises at least one of: a number of User Equipment directly connected with the downstream integrated access and backhaul node or donor; and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and use the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions. [0056] In accordance with one example embodiment, an example method may be provided comprising: receiving information by an integrated access and backhaul node or donor, where the information comprises at least one of: a number of User Equipment directly connected with the integrated access and backhaul node or donor, and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions.

[0057] In accordance with one example embodiment, an apparatus may be provided comprising: means for receiving information by an integrated access and backhaul node or donor, where the information comprises at least one of: a number of User Equipment directly connected with the integrated access and backhaul node or donor, and/or a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and means for using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions.

[0058] In accordance with one example embodiment, an apparatus may be provided comprising a non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: enable receiving information by an integrated access and backhaul node or donor, where the information comprises at least one of: a number of User Equipment directly connected with the integrated access and backhaul node or donor, and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and using the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions .

[0059] In accordance with one example embodiment, an apparatus may be provided comprising at least one processor; and at least one non-transitory memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: enable receiving information by an integrated access and backhaul node or donor, where the information comprises at least one of: a number of User Equipment directly connected with the integrated access and backhaul node or donor, and a number of User Equipment on at least one subtending downstream integrated access and backhaul node; and use the received information by the integrated access and backhaul node or donor to weight scheduling priority for uplink and/or downlink transmissions.

[0060] Any combination of one or more computer readable medium(s) may be utilized as the memory. The computer readable medium may be a computer readable signal medium or a non-transitory computer readable storage medium. A non-transitory computer readable storage medium does not include propagating signals and may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0061] It should be understood that the foregoing description is only illustrative. Various alternatives and modifications can be devised by those skilled in the art. For example, features recited in the various dependent claims could be combined with each other in any suitable combination (s ) . In addition, features from different embodiments described above could be selectively combined into a new embodiment. Accordingly, the description is intended to embrace all such alternatives, modifications and variances which fall within the scope of the appended claims.