Method and apparatus for integrated multi-hop access and return systems

ES3083397T8Undetermined Publication Date: 2026-11-11ASUSTEK COMPUTER INC (100 00)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
ES2019178719T
Authority / Receiving Office
ES · ES
Patent Type
Applications
Current Assignee / Owner
Priority Date
2018-06-29
Filing Date
2019-06-06
Publication Date
2026-11-11
Estimated Expiration
2039-06-06

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in reducing uplink delay in multi-hop integrated access and backhaul (IAB) wireless communication systems, particularly in 5G NR networks, which impact the efficiency of Voice over IP and multimedia services.

Method used

The implementation of a method and apparatus that optimize uplink (UL) delay by utilizing beamforming techniques, multi-hop forwarding architectures, and adaptive resource partitioning in IAB systems, including the use of relay nodes and integrated access and backhaul links to enhance communication efficiency.

Benefits of technology

This approach reduces uplink delay, improving the performance of Voice over IP and multimedia services in 5G NR networks by enhancing signal-to-noise ratio and minimizing interference, thereby increasing overall system efficiency.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

A method and device are described. For example, a first node can trigger a scheduling request (SR) based on an expected transmission from a second node, which is a child node of the first (2405). The first node can determine a first SR configuration from several SR configurations assigned to the first node (2410).
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for integrated multi-hop access and return systems FIELD The present description relates generally to wireless communication networks and, more particularly, to a method and apparatus for reducing uplink (UL) delay in multi-hop integrated access and backhaul (IAB) wireless communication systems. In particular, the present invention relates to a method according to the precharacterizing portion of independent claim 1 and a corresponding communication device. US documents 2017 / 310433 A1 and US documents 2017 / 331577 A1, respectively, describe said method and the corresponding communication device. WO2017 / 131389A1 describes a general architectural description of relay nodes and resource partitioning. BACKGROUND With the rapidly increasing demand for large-scale data communication to and from mobile devices, traditional mobile voice networks are evolving into networks that communicate using Internet Protocol (IP) data packets. This IP data packet communication can provide mobile device users with Voice over IP, multimedia, multicast, and on-demand communication services. An example of a network structure is the new 5G radio (New Radio, NR). The 5G NR system can provide high data throughput to implement the aforementioned Voice over IP and multimedia services. The 3GPP standards organization is analyzing a new radio technology for the next generation (e.g., 5G). Consequently, changes to the current 3GPP standard are currently being introduced and are considered to be evolving and finalizing the 3GPP standard. SUMMARY According to the present description, the invention is defined by the appended claims. A method and apparatus are provided as set forth in the independent claims. The dependent claims define preferred embodiments thereof. BRIEF DESCRIPTION OF THE DRAWINGS FIG.1 shows a diagram of a wireless communication system. FIG. 2 is a block diagram of a transmitter system (also known as an access network) and a receiver system (also known as user equipment or UE). FIG.3 is a functional block diagram of a communication system. FIG.4 is a functional block diagram of the program code in FIG.3. FIG. 5 illustrates an example of a network with Integrated Access and Backhaul (IAB) links. FIG.6A illustrates an example of an independent mode network architecture. Figure 6B illustrates an example of a network architecture associated with standalone mode operation. Figure 6C illustrates an example of a network architecture where a network UE can operate in non-standalone mode with the Evolved Packet Core (EPC) and / or a network IAB node can operate in standalone mode with the Next Generation Core (NGC). Figure 6D illustrates an example of a network architecture where a network UE can operate in non-standalone mode with EPC and / or a network IAB node can operate in non-standalone mode with EPC. FIG.7A illustrates a first IAB architecture of a network that provides multi-hop forwarding. FIG.7B illustrates a second IAB architecture of a network that provides multi-hop forwarding. FIG.8 illustrates an example of an IAB system. FIG.9 illustrates an example of a scenario associated with an IAB system. FIG.10 illustrates an example of a scenario associated with an IAB system. FIG.11 illustrates an example of a scenario associated with an IAB system. FIG.12 illustrates an example of a scenario associated with an IAB system. FIG.13 illustrates an example of a scenario associated with an IAB system. FIG.14 illustrates an example of a scenario associated with an IAB system. FIG.15 illustrates an example of a scenario associated with an IAB system. FIG.16 illustrates an example of a scenario associated with an IAB system. FIG.17 illustrates an example of a scenario associated with an IAB system. FIG.18 is a flowchart. FIG.19 is a flowchart. FIG.20 is a flowchart. FIG.21 is a flowchart. FIG.22 is a flowchart. FIG.23 is a flowchart. FIG.24 is a flowchart. FIG.25 is a flowchart. DETAILED DESCRIPTION The exemplary wireless communication systems and devices described below employ a wireless communication system that supports a broadcast service. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), 3GPP Long Term Evolution (LTE) wireless access, 3GPP LTE-A or LTE-Advanced, 3GPP2 Ultra Fast Mobile Broadband (UMB), WiMAX, 3GPP New Radio (NR), or other modulation techniques. In particular, the examples of wireless communication system devices described below can be designed to support one or more standards, such as the standard offered by a consortium called the "3rd Generation Partnership Project," referred to in this invention as 3GPP, which includes: 3GPP TR 38.913 V14.1.0, Study on Scenarios and Requirements for Next Generation Access Technologies; 3GPP TS 38.321 V15.2.0, Medium Access Control (MAC) protocol specification; RP172290, Study on Integrated Access and Backhaul for NR; and 3GPP TR 38.874 V0.3.2, Study on Integrated Access and Backhaul. Figure 1 presents a multi-access wireless communication system according to one or more embodiments of the description. An Access Network (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional one including 112 and 114. In FIG.1, only two antennas are shown for each antenna group, however, more or fewer antennas can be used for each antenna group. Access Terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from access terminal 116 via reverse link 118. AT 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In a frequency-division duplexing (FDD) system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, the forward link 120 may use a different frequency than the one used by the reverse link 118. Each group of antennas and / or the area where they are designed to communicate is often called an access network sector. In implementation, each group of antennas can be designed to communicate with access terminals in one sector of the areas covered by the access network. In communication via direct links 120 and 126, the transmission antennas of access network 100 can use beamforming to improve the signal-to-noise ratio of the direct links for the different access terminals 116 and 122. Furthermore, an access network that uses beamforming to transmit to access terminals randomly scattered throughout its coverage typically causes less interference to access terminals in neighboring cells than an access network that transmits through a single antenna to all its access terminals. An access network (AN) can be a fixed station or base station used to communicate with terminals, and may also be called an access point, Node B, base station, enhanced base station, eNodeB, gNB, node, access node, IAB node, or by other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, a terminal, or by other terminology. FIG.2 presents an embodiment of a transmitter system 210 (also known as an access network) and a receiver system 250 (also known as an access terminal (AT) or user equipment (UE)) in a multiple-input and multiple-output (MIMO) system 200. In the transmitter system 210, traffic data corresponding to several data streams can be supplied from a data source 212 to a transmit data processor (TX) 214. In one embodiment, each data stream is transmitted through a respective transmit antenna. The TX 214 data processor formats, encodes, and interleaves the traffic data for each data stream according to a particular encoding scheme selected for that data stream to provide encoded data. The encoded data for each data stream can be multiplexed with pilot data using OFDM techniques. The pilot data typically consists of a known data pattern that is processed in a known way and can be used in the receiving system to estimate the channel response. The pilot data and the corresponding multiplexed encoded data for each data stream can then be modulated (i.e., symbol-mapped) according to a particular modulation scheme (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-ary Phase Shift Keying (M-PSK), or M-ary Quadrature Amplitude Modulation (M-QAM)) selected for that data stream in order to provide modulation symbols.The data rate, encoding and / or modulation for each data stream can be determined by instructions executed by the processor 230. The modulation symbols for all data streams are then provided to a TX MIMO 220 processor, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO 220 processor then provides NT modulation symbol streams to NT transmitters (TMTR) 222a to 222t. In certain embodiments, the TX MIMO 220 processor can apply beamforming weights to the data stream symbols and to the antenna from which the symbol is transmitted. Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. The modulated NT signals from transmitters 222a to 222t can then be transmitted from the NT antennas 224a to 224t, respectively. In receiver system 250, the transmitted modulated signals are received by the NR antennas 252a to 252r, and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a to 254r. Each receiver 254 can condition (e.g., filter, amplify, and convert to a lower frequency) a respective received signal, digitize the conditioned signal to provide samples, and further process the samples to provide a corresponding "received" symbol stream. An RX 260 data processor then receives and processes the received NR symbol streams from NR receivers 254 using a specific receiver processing technique to provide NT "detected" symbol streams. The RX 260 data processor can then demodulate, deintercalate, and decode each detected symbol stream to recover traffic data for the data stream. The processing by the RX 260 data processor can be complementary to that performed by the TX MIMO processor 220 and the TX 214 data processor in the transmitter system 210. A 270 processor can periodically determine which pre-encoding matrix to use (discussed later). The 270 processor formulates a backlink message comprising an array index part and a range value part. The return link message may contain various types of information regarding the communication link and / or the received data stream. The return link message may then be processed by a data processor TX 238, which may also receive traffic data for a series of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a to 254r, and transmitted back to the transmitter system 210. In the transmitter system 210, the modulated signals from the receiver system 250 are received by the antennas 224, conditioned by the receivers 222, demodulated by a demodulator 240, and processed by an RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 can then determine which pre-coding matrix to use to determine the beamforming weights and can then process the extracted message. Figure 3 presents an alternative simplified functional block diagram of a communication device according to an embodiment of the subject matter described. As shown in Figure 3, the communication device 300 in a wireless communication system can be used to implement UEs (or ATs) 116 and 122 in Figure 1 or the base station (or AN) 100 in Figure 1, and the wireless communication system is preferably the LTE system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in memory 310 through the CPU 308, thereby controlling an operation of the communication device 300.The communication device 300 can receive signals entered by a user through the input device 302, such as a keyboard or numeric keypad, and can output images and sounds through the output device 304, such as a monitor or speakers. The transceiver 314 is used to receive and transmit wireless signals, supplying received signals to the control circuit 306, and wirelessly transmitting signals generated by the control circuit 306. The communication device 300 in a wireless communication system can also be used to perform the AN 100 described in FIG. 1. Figure 4 is a simplified block diagram of the 312 program code shown in Figure 3, according to one embodiment of the subject matter described. In this embodiment, the 312 program code includes a 400 application layer, a 3402 layer portion, and a 2404 layer portion, and is coupled to a 1406 layer portion. The 3402 layer portion can typically perform radio resource control. The 2404 layer portion can typically perform link control. The 1406 layer portion can typically perform physical connections. A Scheduling Request (SR) can be used to request one or more Uplink Shared Channel (UL-SCH) resources for a new transmission. A MAC entity can be configured with zero SR configurations. Alternatively and / or additionally, the MAC entity can be configured with one or more SR configurations.An SR configuration (of one or more SR configurations) may comprise a set of Physical Uplink Control Channel (PUCCH) resources for an SR through one or more Bandwidth Parts (BWP) and / or one or more cells. In some examples, an SR configuration may correspond to one or more logical channels. A logical channel (of one or more logical channels) may be mapped to zero SR configurations and / or one or more SR configurations (for example, the logical channel and / or one or more SR configurations may be configured via Radio Resource Control (RRC)). An SR configuration of a logical channel associated with the activation of a Buffer Status Report (BSR) may be considered as a corresponding SR configuration for the BSR. In some examples, if an SR associated with an SR configuration is triggered and / or there are no other SRs corresponding to the SR configuration that are pending, the MAC entity may set the SR_COUNTER variable of the SR configuration to 0. Alternatively and / or additionally, when an SR is triggered, the SR may be considered pending until the SR is canceled. Alternatively and / or additionally, one or more pending SRs that are triggered before a Protocol Data Unit (PDU) MAC assembly may be canceled and / or one or more sr-ProhibitTimer parameters associated with one or more pending SRs may be stopped when a MAC PDU is transmitted. The MAC PDU may comprise a BSR MAC Control Element (MAC Control Element, MAC CE) and / or may comprise a buffer state associated with (and / or until) a most recent event (e.g., a last event) that triggered a BSR before the MAC PDU assembly.One or more pending SRs can be cancelled when one or more uplink (UL) leases can host pending data (and / or all pending data) available for transmission. In an example where one or more SRs are pending, the MAC entity can perform one or more operations for one SR of the one or more SRs (and / or for each SR of the one or more SRs). For example, if a first condition is met, a Random Access (RA) procedure can be initiated on a Special Cell (SpCell), and / or the SR can be canceled. The first condition can be met if the MAC entity does not have a valid PUCCH resource for the SR. Alternatively and / or additionally, if the first condition is not met, if a second condition is met, and / or if a third condition is met, an SR_COUNTER parameter can be incremented by 1, a physical layer can be instructed to point to the SR on a valid PUCCH resource for SRs, and / or an sr-ProhibitTimer parameter can be initiated.The second condition can be met if the MAC entity has an SR transmission occasion in the valid SR PUCCH resource, if an sr-ProhibitTimer parameter is not running during the SR transmission occasion, if the PUCCH resource for the SR transmission occasion does not overlap with a metering gap, and / or if the PUCCH resource for the SR transmission occasion does not overlap with a UL-SCH resource. Alternatively and / or additionally, the third condition can be met if the SR_COUNTER parameter is smaller than an sr-TransMax parameter.Alternatively and / or additionally, if the first condition is not met, if the second condition is met, and / or if the third condition is not met, an RRC may be notified to release PUCCH for one or more service cells, the RRC may be notified to release one or more Sounding Reference Signals (SRS) for the one or more service cells, one or more configured downlink assignments and / or one or more uplink leases may be deleted, an RA procedure may be initiated on the SpCell, and / or one or more SRs may be canceled. In some examples, the UE implementation may be associated with selecting a (valid) PUCCH resource for the SR to signal the SR when the MAC entity has more than one overlapping valid PUCCH resource for an SR transmission occasion. A buffer status reporting procedure can be used to provide a service gNB (for example, gNodeB) with information associated with the UL data volume in the MAC entity. In some examples, a logical channel can be assigned to a Logical Channel Group (LCG). The maximum number of LCGs can be 8 (and / or a different number). The MAC entity can determine the amount of UL data available for a logical channel based on a data volume calculation procedure. A regular BSR (e.g., a BSR) can be triggered if the MAC entity has new UL data available for a logical channel belonging to an LCG. Alternatively and / or additionally, the regular BSR can be triggered if the new UL data belongs to a logical channel with a higher priority than a logical channel containing available UL data belonging to an LCG, and / or if the logical channels belonging to an LCG do not contain available UL data. Alternatively and / or additionally, the regular BSR can be triggered if a retxBSR-Timer expires and / or one or more logical channels belonging to an LCG contain UL data. In some examples, for the regular BSR, if the regular BSR is activated for a logical channel for which a `logicalChannelSR-DelayTimerApplied` parameter is configured by the upper layers, a `logicalChannelSR-DelayTimer` may be started and / or restarted. Alternatively and / or additionally, for the regular BSR, if the regular BSR is not activated for a logical channel for which the `logicalChannelSR-DelayTimerApplied` parameter is configured by the upper layers, the `logicalChannelSR-DelayTimer` may be stopped if it is already running. Alternatively and / or additionally, a padding BSR (e.g., a BSR) may be activated if UL resources are allocated and / or the number of padding bits is greater than or equal to the size of a MAC CE BSR (with a subheader). Alternatively and / or additionally, a periodic BSR (e.g., a BSR) can be activated if a periodic BSR timer expires. In some examples, for the regular BSR and / or the periodic BSR, if more than one LCG has data available for transmission when a MAC PDU comprising the regular BSR and / or the periodic BSR is to be built, a long BSR may be reported for the more than one LCG that has data available for transmission. Alternatively and / or additionally, for the regular BSR and / or the periodic BSR, if only one LCG has data available for transmission when the MAC PDU comprising the regular BSR and / or the periodic BSR is to be built, a short BSR may be reported. In some examples, a BSR (for example, a regular BSR) may be activated based on the expiration of a retxBSR-Timer parameter. The MAC entity may consider a logical channel associated with the BSR activation to be a higher-priority logical channel that has data available for transmission when the BSR is activated. In some examples, if a buffer status reporting procedure determines that one or more BSRs are activated and / or not canceled, and / or if one or more UL-SCH resources are available for a new transmission, a multiplexing and assembly procedure may be instructed to generate one or more MAC CE BSRs, a periodic BSR timer parameter may be started and / or reset unless one or more (and / or all) BSRs are long or short truncated BSRs, and / or the retxBSR timer may be started and / or reset.Alternatively and / or additionally, if a buffer status reporting procedure determines that one or more BSRs are activated and / or not canceled, if a regular BSR is activated and / or a LogicalChannelSR-DelayTimer parameter is not running, if the MAC entity is configured with one or more UL leases configured and / or the regular BSR is not activated (and / or was not activated) for a logical channel for which logical channel SR masking (e.g., a LogicalChannelSRMask parameter) is configured by higher layers and / or if one or more UL-SCH resources available for a new transmission do not comply with the Logical Channel Prioritization (LCP) mapping restrictions configured for one or more logical channels associated with the activation of one or more BSRs, an SR may be activated. In some examples, a MAC PDU associated with multiple events that trigger a BSR may comprise a single MAC CE BSR. Alternatively and / or additionally, a regular BSR and / or a periodic BSR may take precedence over a padding BSR. Alternatively and / or additionally, a MAC entity may reset the retxBSR timer in response to receiving a grant for transmitting new data on a UL-SCH. Alternatively and / or additionally, one or more triggered BSRs may be canceled when one or more UL grants can accommodate pending data (and / or all pending data) available for transmission and / or when one or more UL grants are insufficient to accommodate a MAC CE BSR with a subheader. In some examples, one or more BSRs (and / or all BSRs) triggered before a MAC PDU assembly may be canceled when a MAC PDU comprising a MAC CE BSR is transmitted. In some examples, Integrated Access and Backhaul (IAB) can facilitate the deployment of a (dense) New Radio (NR) cell network with its own backhaul in an integrated manner by relying on many control channels and / or procedures and / or data channels and / or procedures defined to provide access to the UE. Figure 5 illustrates an example 500 of a network with IAB links. The relay nodes (e.g., Relay Transmission / Reception Points, rTRPs) can multiplex the access and / or return links in time, frequency, and / or space (e.g., beam-based operation). Link operation can be associated with similar and / or different frequencies (e.g., links can be associated with in-band and / or out-of-band relays). In-band operation can be associated with close inter-operation with access links operating at a similar frequency. In some examples, Mobile Termination (MT), gNB Distributed Unit (gNB-DU), gNB Central Unit (gNB-CU), User Plane Function (UPF), Access and Mobility Management Function (AMF), and / or Session Management Function (SMF) may be used in IAB functions and / or included in IAB architectures. Alternatively and / or additionally, one or more interfaces, such as the NR Uu interface (associated with E-UTRA and / or UMTS Terrestrial Radio Access, UTRA), the F1 interface, the NG interface, the X2 interface, and / or the N4 interface, may be used in IAB functions and / or included in IAB architectures. Alternatively and / or additionally, one or more functionalities such as multi-hop forwarding may be used in IAB functions and / or may be included in IAB architectures.The MT function can be a component of a mobile device. The MT function can be associated with IAB node termination radio interface layers of a return network interface to an IAB donor and / or other IAB nodes. Figure 6A illustrates an example of a 600 architecture for a standalone network. For example, the network might comprise an IAB 606 donor and / or a plurality of IAB 608 nodes. The IAB donor might be associated with a single logical node comprising one or more functions, such as gNB-DU, gNB-CU Control Plane (gNB-CU-CP), gNB-CU User Plane (gNB-CU-UP), and / or one or more other functions. In some examples, the IAB 606 donor might be partitioned according to one or more functions. The one or more functions might be colocated and / or non-platted (depending on the 3GPP Nextgen-RAN architecture). In some examples, the IAB nodes of the plurality of IAB nodes 608 can connect to the donor IAB 606 through one or more wireless backlinks of a plurality of wireless backlinks 602.Alternatively and / or additionally, a first IAB node of the plurality of IAB nodes 608 may connect to a second IAB node of the plurality of IAB nodes 608 through one or more wireless backlinks of the plurality of wireless backlinks 602. Alternatively and / or additionally, a UE may connect to an IAB node of the plurality of IAB nodes 608 through a wireless access link of a plurality of wireless access links 604. Figure 6B illustrates an example of a 620 network architecture associated with standalone operation. In some examples, a UE 622 in the network can operate in standalone mode with a Next Generation Core (NGC). Alternatively and / or additionally, an IAB 624 node in the network can operate in standalone mode with an NGC. The UE 622 can connect to the IAB 624 node. Alternatively and / or additionally, a UE can choose an operating mode (e.g., non-standalone mode) different from the operating mode of an IAB node connected to the UE. Figure 6C illustrates an example of a 640 network architecture where a UE 642 in the network can operate in non-standalone mode with Evolved Packet Core (EPC) and / or an IAB node 644 in the network can operate in standalone mode with NGC. The UE 642 can be connected to the IAB node 644. Alternatively and / or additionally, the UE can be connected to an eNB 646 that is different from the IAB node 644. Figure 6D illustrates an example of a 660 network architecture, where a UE 662 in the network can operate in non-independent mode with EPC and / or an IAB 664 node in the network can operate in non-independent mode with EPC. The UE 662 can be connected to the IAB 664 node. Alternatively and / or additionally, the UE can be connected to an eNB 666 that is different from the IAB 664 node. Figure 7A illustrates a first IAB 700 architecture of a network providing multi-hop forwarding. The first IAB 700 architecture can use a split architecture of a Central Unit (CU) and / or a Distributed Unit (DU). The first IAB 700 architecture can be associated with the return of an F1 User Plane (F1-U) using an adaptation layer. Alternatively and / or additionally, the first IAB 700 architecture can be associated with the General Packet Radio Service Tunneling Protocol (GTP) and / or a GTP User Plane (GTP-U) with an adaptation layer. Alternatively and / or additionally, the first IAB 700 architecture can be associated with hop-by-hop forwarding through intermediate nodes using an adaptation layer for operation with NGC.Alternatively and / or additionally, the first IAB 700 architecture may be associated with Packet Data Network (PDN) connection layer routing for operation with EPC. In some examples, the first IAB 700 architecture may be associated with a two-hop chain of IAB nodes, comprising a first IAB 702 node and / or a second IAB 704 node, and / or an IAB 706 donor node. The first IAB 702 node, the second IAB 704 node, and / or one or more UEs may be connected (in standalone mode) to an NGC 708. The first IAB 702 node may contain a first DU and / or a first MT. The second IAB 704 node may contain a second DU and / or a second MT. The first IAB 702 node may connect to an upstream IAB node (e.g., the second IAB 704 node) using the first MT. Alternatively and / or additionally, the second IAB 704 node may connect to the IAB 706 donor node via the second MT. Alternatively and / or additionally, the first IAB 702 node can connect and / or establish one or more first Radio Link Control (RLC) channels to one or more UE and / or one or more downstream IAB nodes via the first DU.Alternatively and / or additionally, the second IAB node 704 can connect and / or establish one or more second RLC channels to one or more UEs and / or one or more downstream IAB nodes (e.g., the first IAB node 702) via the second DU. In some examples, the first RLC channel(s) and / or the second RLC channel(s) may be associated with a modified RLC (e.g., represented as RLC* in Fig. 7A). In some examples, donor IAB 706 maintains a third DU to support one or more UEs and / or one or more MTs (e.g., the second MT) from one or more downstream IAB nodes (e.g., the second IAB node 704). Donor IAB 706 may maintain a CU to support DUs (e.g., the first DU and / or the second DU) from IAB nodes and / or the third DU of donor IAB 706. The first DU of the first IAB node 702 and / or the second DU of the second IAB node 704 may connect to the CU of donor IAB 706 using a modified F1-U 712 (e.g., represented as F1-U* and / or F1* in Fig. 7A) and / or using a modified second F1-U 714 (e.g., represented as F1-U* and / or F1* in Fig. 7A). The modified F1-U 712 and / or the second modified F1-U 714 can be configured according to the F1-U 710 (e.g., the F1-U interface). The modified F1-U 712 and / or the second modified F1-U 714 runs over one or more RLC channels in a wireless backhaul network between a MT of a service IAB node (for example, the second MT of the second IAB node 704) and the third DU of the donor IAB 706. The modified F1-U 712 and / or the second modified F1-U 714 may comprise an adaptation layer comprising routing information associated with hop-to-hop forwarding. The adaptation layer of the modified F1-U 712 and / or the second modified F1-U 714 can replace the IP functionality of the F1-U 710. The modified F1-U 712 and / or the second modified F1-U 714 can carry a GTP-U header for end-to-end association between the CU and one or more DUs (e.g., the first DU, the second DU, the third DU, etc.). Alternatively and / or additionally, the modified F1-U 712 can be further modified to configure the second modified F1-U 714 by including the GTP-U header in the adaptation layer. For non-standalone operation with EPC, a MT (e.g., the first MT and / or the second MT) can connect to a network using E-UTRAN New Radio - Dual Connectivity (EN-DC). The MT can maintain a PDN connection with the EPC. Figure 7B illustrates a second IAB 720 architecture of a network providing multi-hop forwarding. This second IAB 720 architecture can use a CU and / or DU split architecture. It can be associated with return traffic from an F1-U interface at an access node using the GTP-U interface, User Datagram Protocol (UDP), and / or Internet Protocol (IP). Alternatively, and / or additionally, this second IAB 720 architecture can be associated with hop-by-hop forwarding through intermediate nodes using an adaptation layer. In some examples, the second IAB 720 architecture may be associated with a two-hop chain of IAB nodes, comprising a first IAB 722 node and / or a second IAB 724 node, and / or an IAB 726 donor node. The first IAB 722 node, the second IAB 724 node, and / or one or more UEs may be connected (in standalone mode) to an NGC 728. The first IAB 722 node may contain a first DU and / or a first MT. The second IAB 724 node may have a second DU and / or a second MT. The first IAB 722 node may connect to an upstream IAB node (e.g., the second IAB 724 node) using the first MT. Alternatively and / or additionally, the second IAB 724 node may connect to the IAB 726 donor node via the second MT. Alternatively and / or additionally, the first IAB node 722 can connect and / or establish one or more first RLC channels to one or more UE and / or one or more downstream IAB nodes via the first DU.Alternatively and / or additionally, the second IAB node 724 can connect and / or establish one or more second RLC channels to one or more UE and / or one or more downstream IAB nodes (e.g., the first IAB node 722) via the second DU. In some examples, the donor IAB 726 maintains a third DU to support one or more UEs and / or one or more MTs (e.g., the second MT) from one or more downstream IAB nodes (e.g., the second IAB 724 node). The donor IAB 726 may maintain a CU to support DUs (e.g., the first and / or second DUs) from IAB nodes and / or the donor IAB 726's third DU. The first DU of the first IAB 722 node and / or the second DU of the second IAB 724 node may connect to the donor IAB 726's CU using a modified F1-U 732 (e.g., represented as F1-U* and / or F1* in Fig. 7B). The modified F1-U 732 may be configured according to the F1-U 730 (e.g., the F1-U interface). In some examples, the first MT of the first IAB 722 node can establish a PDU session with a first UPF residing on the donor IAB 726. The PDU session can carry the modified F1-U 732 for the first DU (placed). For example, the PDU session can provide a point-to-point link between the first DU and the CU. Alternatively and / or additionally, the second MT of the second IAB 724 node can establish a PDU session with a second UPF residing on the donor IAB 726. The PDU session can carry the modified F1-U 732 for the second DU (placed). For example, the PDU session can provide a point-to-point link between the second DU and the CU. For non-standalone operation with EPC, a MT (e.g., the first MT and / or the second MT) can be connected via dual connectivity to a network using EN-DC. The MT can maintain a PDN connection with an L-GW residing at the donor IAB 726. In some examples, an IAB node may correspond to a RAN node. The IAB node may support wireless access to one or more UEs. Alternatively and / or additionally, the IAB node may wirelessly return access traffic (associated with wireless access to one or more UEs). In some examples, the IAB node may correspond to an rTRP. In some examples, an IAB donor may provide an interface associated with a UE to a core network. The IAB donor may provide wireless backhaul functionality to one or more IAB nodes. In some examples, the IAB donor may correspond to an anchor node. In some examples, a parent node of a first IAB node may be connected to the first IAB node. For example, the first IAB node may have a direct link to the parent node. In some examples, an address from the first IAB node to the parent node is associated with an uplink address. For example, the first IAB node may be served by the parent node. Alternatively and / or additionally, the first IAB node may be scheduled by the parent node. In some examples, the parent node may correspond to an IAB node (different from the first IAB node and / or different from the child node). Alternatively and / or additionally, the parent node may correspond to an IAB donor. In some examples, a child node of the first IAB node may be connected to the first IAB node. For example, the first IAB node may have a direct link to the child node. In some examples, an address from the first IAB node to the child node is associated with a downlink address. For example, the first IAB node may serve the child node. Alternatively and / or additionally, the first IAB node may schedule the child node. In some examples, the child node may correspond to a UE. Alternatively and / or additionally, the child node may correspond to an IAB node (different from the first IAB node). In some examples, the first IAB node (and / or other IAB nodes) may comprise a Network (NW) part and / or an MT part. The NW part may have one or more functionalities associated with a network and / or a gNB-DU. The MT part may have one or more functionalities associated with a UE (e.g., a mobile phone and / or a different type of UE). In some examples, the first IAB node can perform network operations using the NW portion to interact with the child node. For example, these network operations may be associated with and / or similar to the operations performed by a network. In some examples, the first IAB node can perform UE operations using the MT part to interact with the parent node. For example, the UE operations may be associated with and / or similar to the operations performed by a UE. In some examples, the first IAB node can perform network operations and / or UE operations concurrently (e.g., simultaneously). Alternatively and / or additionally, the first IAB node may perform network operations and / or UE operations separately (for example, network operations and / or UE operations may be performed in a time-splitting manner). In some examples, the first IAB node may acquire UL resources (from the parent node of the first IAB node) by transmitting a signal to the parent node of the first IAB node. In some examples, the signal may correspond to a SR. The SR may be transmitted (to the parent node) through a PUCCH. The PUCCH may correspond to a UL channel between the first IAB node and the parent node. Alternatively and / or additionally, the signal may correspond to an RA preamble. The RA preamble may be transmitted through a Physical Random Access Channel (PRACH). The PRACH may correspond to a UL channel between the first IAB node and the parent node. In response to receiving the signaling, the parent node can grant a UL lease to the first IAB node (for example, based on a determination that the first IAB node transmitted the signaling). The first IAB node can then transmit the UL data over a Physical Uplink Shared Channel (PUSCH) based on the UL lease. In some instances, the UL lease might correspond to Downlink Control Information (DCI) received over a Physical Downlink Control Channel (PDCCH). The PUSCH might correspond to a UL channel between the first IAB node and the parent node. The PDCCH might correspond to a DL channel between the first IAB node and the parent node. In some examples, a first UE can connect (e.g., connect directly) to the first IAB node. The first IAB node may correspond to a first access node of the first UE. A link between the first UE and the first IAB node may correspond to an access link. Alternatively and / or additionally, there may be one or more intermediate IAB nodes between (a connection from) the first IAB node and an IAB donor. Alternatively and / or additionally, the first IAB node (e.g., the first access node) may correspond to an intermediate node (between the first UE and the IAB donor). A link between the first IAB node and a second IAB node may correspond to a return link. Alternatively and / or additionally, a link between the first IAB node and the IAB donor may correspond to a return link.The first IAB node can be associated with one or more child nodes (for example, the first IAB node can be connected to one or more child nodes, such as one or more UEs and / or one or more IAB nodes). Alternatively and / or additionally, the first IAB node can be associated with one or more parent nodes (for example, the first IAB node can be connected to one or more parent nodes, such as one or more IAB donors and / or one or more IAB nodes). In some examples, an IAB system can be associated with multi-hop functionality. Figure 8 illustrates an example of an IAB 800 system. The IAB 800 system may comprise a first UE 812 (UE 1), a second UE 814 (UE 2), a third UE 802 (UE 3), and / or a fourth UE 816 (UE 4). The IAB 800 system may comprise a first IAB 806 node (Node 1), a second IAB 808 node (Node 2), and / or a third IAB 804 node (Node 3). The IAB 800 system may comprise a first IAB 810 donor. The first UE 812 can be (directly) connected to the first IAB 806 node (via an access link). The first IAB 806 node can be an access node of the first UE 812. The second IAB 808 node can be between (a connection from) the first IAB 806 node and the first IAB 810 donor. The second IAB 808 node can be an intermediate node between the first IAB 806 node and the first IAB 810 donor (for example, the first IAB 806 node can be connected to the second IAB 808 node via a return link and / or the second IAB 808 node can be connected to the first IAB 810 donor via a return link). The second UE 814 can be (directly) connected to the second IAB 808 node (via an access link). The second IAB 808 node can correspond to an access node of the second UE 814. The second IAB 808 node can be (directly) connected to the first IAB 810 donor (via a return link). The third UE 802 node may be (directly) connected to the third IAB 802 node (via an access link). The third IAB 802 node may correspond to an access node of the third UE 802 node. The second IAB 808 node may be between (a connection from) the third IAB 802 node and the first IAB 810 donor node. The second IAB 808 node may correspond to an intermediate node between the third IAB 802 node and the first IAB 810 donor node (for example, the third IAB 802 node may be connected to the second IAB 808 node via a return link and / or the second IAB 808 node may be connected to the first IAB 810 donor node via a return link). The fourth UE 816 can be (directly) connected to the first donor IAB 810. In some examples, the first UE 812 may be associated with a first hop count associated with the return. For example, the first hop count may correspond to a first IAB node number between the first UE 812 and the first IAB 812 donor (e.g., the first hop count may be 2 based on the first IAB 806 node and / or the second IAB 808 node between the first UE 812 and the first IAB 812 donor). Alternatively and / or additionally, the third UE 802 may be associated with the first hop count (e.g., based on the third IAB 802 node and / or the second IAB 808 node between the third UE 802 and the first IAB 812 donor). The first hop count (e.g., 2) may be associated with a multi-hop return. For example, a number of hops may correspond to a number of IAB (intermediate) nodes between a UE and an IAB donor. In some examples, the first UE 812 may be connected to the first IAB 806 node via a first access link. Alternatively and / or additionally, the first IAB 806 node may be connected to the second IAB 808 node via a first return link. Alternatively and / or additionally, the second IAB 808 node may be connected to the first IAB 810 donor via a second return link. In some examples, the first return link and / or the first access link may (partially and / or completely) overlap in frequency and / or the first return link may be in-band with respect to the first access link. In some examples, the in-band return network may be associated with (and / or may cause) half-duplexing and / or interference restrictions.Alternatively and / or additionally, when performing in-band return operations, the first IAB 806 node may not transmit and / or receive data on the first access link and the first return link simultaneously. Alternatively and / or additionally, the first return link and / or the first access link may not overlap in frequency and / or the first return link may be out of band with respect to the first access link. In some examples, the first IAB 806 node and / or the second IAB 808 node can retransmit and / or forward the first data received from the first UE 812 to the first IAB 810 donor. For example, the first IAB 806 node can receive the first data from the first UE 812 via the first access link. This first data can then be retransmitted and / or forwarded by the first IAB 806 node to the second IAB 808 node via the first return link. In some examples, the first data can be retransmitted and / or forwarded by the first IAB 806 node to the second IAB 808 node by adding and / or combining data from other IAB nodes with the first data into a first combined set of data (e.g., a transport block and / or a MAC PDU) (using one or more multiplexing techniques) and / or transmitting the first combined set of data to the second IAB 808 node.Alternatively and / or additionally, the first data may be retransmitted and / or forwarded by the second IAB node 808 to the first IAB donor 810 via the second return link. In some examples, the first data may be retransmitted and / or forwarded by the second IAB node 808 to the first IAB donor 810 by adding and / or combining data from other IAB nodes with the first data into a second combined data set and / or transmitting the second combined data set to the first IAB donor 810. In some examples, the first data may correspond to UL data (with respect to the first UE 812). Alternatively and / or additionally, the first IAB 806 node and / or the second IAB 808 node may retransmit and / or forward the second data received from the first IAB 810 donor to the first UE 812. For example, the second IAB 808 node may receive the second data from the first IAB 810 donor. The second data may then be retransmitted and / or forwarded by the second IAB 808 node to the first IAB 806 node. In some examples, the second data may be retransmitted and / or forwarded by the second IAB 808 node to the first IAB 806 node by adding and / or combining data from other IAB nodes with the second data into a third combined data set and / or transmitting the third combined data set to the first IAB 806 node. Alternatively and / or additionally, the second data may be retransmitted and / or forwarded by the first IAB node 806 to the first UE 812. In some examples, the second data may correspond to DL data (with respect to the first UE 812). In some examples, an IAB node (e.g., the first IAB node 806) may be physically fixed to a location. Alternatively, the IAB node may be mobile (e.g., the IAB node may be placed on a bus, a train, and / or a different moving object). In some examples, a relay in an IAB system may be an L2 relay or an L3 relay. Alternatively and / or additionally, the coordination of resources among the IAB nodes of the IAB system may be distributed or centralized. UL data can arrive in a UE buffer. In some instances, a BSR can be activated by the UE (for example, in response to UL data arriving in the UE buffer). Alternatively and / or additionally, a SR can be activated. The SR can be activated in response to a lack of available UL resources for transmitting UL data and / or the BSR. The UE can transmit the SR (for example, via PUCCH) to an access node. The SR can be transmitted to the access node to acquire one or more UL resources (for example, one or more transmission resources) (if PUCCH resources for the SR are configured for the UE). In response to receiving the SR, the access node (and / or a portion of the access node's NW) can perform one or more network operations. For example, the access node can transmit and / or provide a UL lease to the UE. The UE can transmit UL data to the access node according to the UL lease. In an example where the access node is an IAB node and / or not an IAB donor, the access node can forward and / or retransmit the UL data to a parent node associated with it (for example, the access node can be connected to the parent node via a return link). For example, the parent node can be an IAB donor and / or an IAB node. The access node can process the UL data (for example, the access node can perform data processing on the UL data using one or more protocol stacks associated with it). Alternatively and / or additionally, the access node (and / or a MT portion of the access node) can perform one or more UE operations. For example, the access node can activate a second BSR and / or the access node can activate a second SR.The access node can transmit the second SR to the parent node to acquire one or more second UL resources (if PUCCH resources for the second SR are configured for the access node). Figure 9 illustrates an example of a 900 scenario associated with an IAB system. In this example, a UE 902 might be connected to an access node (via an access link). The UE 902 might perform one or more first 910 operations. These first 910 operations might be associated with UL data arriving in a UE 902 buffer, the UE 902 activating a BSR, and / or the UE 902 activating an SR 912. For example, the UE 902 might transmit the SR 912 to the access node. A first 904 part of the access node might receive the SR 912. The first 904 part of the access node might correspond to a NW part of the access node. The first 904 part of the access node might be associated with performing one or more network operations. The first part 904 of the access node can transmit a UL 914 lease to UE 902 (in response to receiving SR 912). UE 902 can then transmit UL 916 data to the access node based on the UL 914 lease.The access node can receive data from UL 916 from UE 902. In some examples, the access node may forward and / or retransmit UL 916 data to a parent node associated with the access node (for example, the access node may be connected to the parent node via a return link). The access node may process the UL data (for example, the access node may perform 918 data processing on the UL data using one or more protocol stacks associated with the access node). Alternatively and / or additionally, the access node may perform one or more secondary 920 operations. For example, one or more secondary 920 operations may be performed by a secondary 906 part of the access node. For example, the secondary 906 part of the access node may correspond to an MT part of the access node. Alternatively and / or additionally, the secondary 906 part of the access node may correspond to the performance of one or more UE operations.In some examples, one or more second operations (920) may be associated with UL data arriving at a second buffer of the access node, the second part (906) of the access node activating a second BSR, and / or the second part (906) of the access node activating a second SR (922). The access node (and / or the second part (906) of the access node may transmit the second SR (922) to the parent node. Alternatively and / or additionally, the second SR (922) may be received by a third part (908) of the parent node, associated with performing one or more network operations. For example, the third part (908) of the parent node may transmit a second UL (924) lease to the access node (for example, the second UL (924) lease may be received by the second part (906) of the access node). Alternatively and / or additionally, the access node (and / or the second part 906 of the access node) may transmit second UL 926 data to the parent node according to the second UL 924 grant. In some examples, the second UL 926 data stream may include the UL 916 data stream. Alternatively and / or additionally, the transmission of the second UL 926 data stream to the parent node may be associated with the completion of the UL 916 data stream that is forwarded to the parent node associated with the access node. In some examples, the forwarding and / or retransmission of the UL 916 data stream through IAB nodes via return links may be repeated until the UL 916 data stream is received by an IAB donor node. For example, for each instance where UL 916 data is forwarded by an IAB node to a different IAB node, one or more steps are performed (for example, the one or more steps may correspond to one or more SR transmissions, UL grant receptions, UL 916 data transmissions, data processing, BSR activation, SR activation, etc.).Performing each stage of the one or more steps introduces a delay (e.g., a UL delay) corresponding to the transmission of UL 916 data from the UE to the donor IAB. Alternatively and / or additionally, an increase in the number of hops (associated with a number of IAB nodes forwarding and / or retransmitting the initial UL 916 data via return links) causes an increase in the end-to-end delay (e.g., end-to-end UL delay) of the transmission of UL 916 data from the UE to the donor IAB. A first delay, the end-to-end delay associated with the transmission of UL 916 data from the UE to the donor IAB, is associated with the time between the access node's reception of the UL 916 data from UE 902 and the transmission of the second UL 926 data (which includes the UL 916 data) to the parent node. For example, during the time between the reception of the UL 916 data and the reception of the second UL 924 grant, the 918 data processing can be performed on the UL 916 data, the second BSR can be activated, the second SR 922 can be activated, and / or the second SR 922 can be transmitted to the parent node. To reduce delay, for example, the initial end-to-end delay between the UE and the donor IAB, the SR can be activated by an IAB node earlier. The IAB node could activate the SR when it knows that data will be forwarded (or retransmitted) to its parent node. The IAB node can activate the SR before receiving data from its child node. The IAB node can activate the SR when no data is available for transmission originating from the IAB node. The IAB node can activate the SR when the BSR is not activated. For example, the IAB node could activate the SR when it receives the SR from its child node. Alternatively, or additionally, the IAB node could activate the SR when it receives a random access preamble from its child node. Alternatively, or additionally, the IAB node could activate the SR when it assigns the UL grant to a child node. The UL grant can be for a new transmission. The UL concession may be for a retransmission. In some examples, the second SR 922 may be activated (earlier) before the access node (and / or the first part 904 of the access node) receives the UL 916 data. The second SR 922 may be activated when the UL 916 data is not available to the access node and / or the first part 904 of the access node. Alternatively and / or additionally, the second SR 922 may be activated before the UL 914 lease is transmitted to UE 902. Alternatively and / or additionally, the second SR 922 may be activated before the second BSR (and / or a different BSR) is activated. Alternatively and / or additionally, the second SR 922 may be activated regardless of whether the second BSR (and / or a different BSR) is activated. Alternatively and / or additionally, the second SR 922 can be activated in response to the receipt of SR 912 from UE 902 (and / or from a child node other than the access node).Alternatively and / or additionally, the second SR 922 may be activated in response to the receipt of an RA preamble from UE 902 (and / or from a child node other than the access node). Alternatively and / or additionally, the second SR 922 may be activated in response to the allocation (and / or provisioning) of the UL 914 lease to UE 902 (and / or to a child node other than the access node). For example, the UL 914 lease may be associated with a new transmission (e.g., a new transmission of the UL 916 data). Alternatively and / or additionally, the UL 914 lease may be associated with a retransmission (e.g., a retransmission of the UL 916 data). Alternatively and / or additionally, the second SR 922 may be activated in response to the activation of the second BSR (and / or a different BSR). For example, the second BSR (and / or a different BSR) may be activated when UL 916 data is unavailable to the access node and / or the first part 904 of the access node. Alternatively and / or additionally, the second BSR (and / or a different BSR) may be activated before the transmission of the UL 914 lease to UE 902. Alternatively and / or additionally, the second BSR (and / or a different BSR) may be activated in response to the reception of SR 912 from UE 902 (and / or from a different child node of the access node). Alternatively and / or additionally, the second BSR (and / or a different BSR) can be activated in response to receiving an RA preamble from UE 902 (and / or from a child node other than the access node). Figure 10 illustrates an example of scenario 1000 associated with the IAB system. In response to receiving SR 912 from UE 902 (and / or a different child node of the access node), the access node (e.g., the first part 904 of the access node) may activate the second SR 922. For example, the access node (e.g., the first part 904 of the access node) may activate the second SR 922 after receiving SR 912. For example, one or more SR 1014 retransmission operations may be performed in response to receiving SR 912 from UE 902 (and / or a different child node of the access node). One or more SR 1014 retransmission operations may involve activating the second SR 922. Alternatively and / or additionally, the second SR 922 may be transmitted to the parent node (e.g., the third part 908 of the parent node).The second UL 924 grant can be received from the parent node (e.g., the parent node's third part 908) while data processing 918 is in progress. Alternatively and / or additionally, the second UL 924 grant can be received from the parent node (and / or the parent node's third part 908) before data processing 918 is in progress. Alternatively and / or additionally, the second UL 924 grant can be received from the parent node (e.g., the parent node's third part 908) after data processing 918 is in progress. Alternatively and / or additionally, the second UL 926 data (which may include UL 916 data) can be transmitted to the parent node (e.g., the parent node's third part 908) according to the second UL 924 grant. By retransmitting and / or forwarding the UL 916 data according to scenario 1000 (instead of scenario 900), the first delay (associated with the time between the access node's reception of the UL 916 data from UE 902 and the transmission of the second UL 926 data (comprising the UL 916 data) to the parent node) can be reduced by 1030 times. For example, the second UL 924 lease can be received and / or acquired more quickly in scenario 1000 compared to scenario 900. Alternatively and / or additionally, the parent node, the IAB donor, and / or one or more intermediate IAB nodes can receive an SR more quickly and / or become aware that the UL 916 data is being sent to the IAB donor.For example, each instance of an IAB node from the parent node and / or one or more intermediate nodes receives an SR; one or more SR retransmission operations can be performed, and / or an SR can be transmitted by the IAB node to a parent node instance of the IAB node. Therefore, the end-to-end delay (associated with the transmission of UL 916 data to the donor IAB) can be reduced. In some systems (e.g., NR systems), there may be a single SR configuration configured for a UE. Alternatively, there may be multiple SR configurations configured for the UE. In some examples, the first SR configuration among the multiple SR configurations may be associated with a first service type (e.g., one or more Enhanced Mobile Broadband (eMBB), Massive Machine Type Communications (mMTC), Ultra-Reliable and Low Latency Communications (URLC), etc.). In some examples, the first SR configuration may correspond to one or more first logical channels among a plurality of logical channels. Alternatively and / or additionally, a second SR configuration among the multiple SR configurations may be associated with a second service type (e.g., one or more eMBB, mMTC, URLLC, etc.).In some examples, the second SR configuration may correspond to one or more second logical channels out of the plurality of logical channels. The one or more second logical channels may be different from the one or more first logical channels associated with the first SR configuration. A logical channel (from a plurality of logical channels) can be mapped to an SR configuration. For example, a first logical channel can be mapped to the first SR configuration (i.e., one or more first logical channels can comprise the first logical channel). A second logical channel can be mapped to the second SR configuration (i.e., one or more second logical channels can comprise the second logical channel). A third logical channel can be mapped to a third SR configuration. A fourth logical channel may not be assigned to an SR configuration. The first / second / third / fourth logical channels and / or the first / second / third / fourth SR configurations can be configured by RRC. A first SR associated with the first service type can be received by a network (e.g., an IAB node, a base station, etc.) from the UE. In response to a determination that the first SR is associated with the first service type, one or more first UL resources can be allocated to the UE according to one or more first service requirements associated with the first service type. Alternatively and / or additionally, a second SR associated with the second service type can be received by the network from the UE. In response to a determination that the second SR is associated with the second service type, one or more second UL resources can be allocated to the UE according to one or more second service requirements associated with the second service type. In some examples, an IAB node can be configured with multiple SR configurations. For example, the IAB node can use multiple SR configurations to activate an SR. Alternatively and / or additionally, the IAB node can use multiple SR configurations to transmit an SR. Alternatively and / or additionally, multiple SR configurations can be used by an MT portion of the IAB node. In some examples, a BSR can be activated by one logical channel from a plurality of logical channels. Alternatively and / or additionally, an SR can be activated based on the BSR and / or the logical channel. For example, an SR configuration can be associated with a logical channel. In one example, a first BSR can be activated by the first logical channel associated with the first SR configuration. The first SR associated with the first SR configuration can be activated based on the first logical channel (and / or based on the first logical channel that is associated with the first SR configuration). Alternatively and / or additionally, a BSR cannot be activated before an SR is activated. For example, the SR may not be activated based on an activated BSR and / or a logical channel that activated a BSR. Consequently, the SR configuration of an activated SR may not be determined by a BSR and / or a logical channel that activated a BSR. In one example, an IAB node may receive a first SR from a child node (for example, a UE and / or a different IAB node). The SR configuration of a second SR (associated with the first SR) may not be determined by a BSR and / or a logical channel that activated a BSR. In a first embodiment, one or more second SR configurations of one or more second SRs can be determined by an IAB node based on one or more first SR configurations of one or more first SRs received from a child node. For example, there can be a mapping (e.g., an implicit mapping) from the child node's first SR configurations to the IAB node's second SR configurations. In some instances, the mapping can be fixed (e.g., the mapping can be based on an SR configuration index). Alternatively and / or additionally, the mapping can be based on one or more predefined rules.In some examples, the mapping can establish a one-to-one correspondence (e.g., a single SR configuration to a single SR configuration), a many-to-one correspondence (e.g., multiple SR configurations to a single SR configuration), a one-to-many correspondence (e.g., a single SR configuration to multiple SR configurations), and / or a many-to-many correspondence (e.g., multiple SR configurations to multiple SR configurations). In response to receiving the first one or more SRs from the child node, the first one or more SR configurations can be determined from the first one or more SRs. Alternatively and / or additionally, in response to receiving the first one or more SRs from the child node, the second one or more SR configurations can be determined to activate and / or generate the second one or more SRs.For example, a first SR configuration of one or more first SR configurations can be mapped to a second SR configuration of one or more second SR configurations based on the SR configuration index. For example, the first SR configuration of one or more first SR configurations can be mapped to the second SR configuration of one or more second SR configurations based on a first index of the first SR configuration and / or a second index of the second SR configuration (for example, the SR configuration index can comprise the first index and / or the second index, and / or the first index and / or the second index can be determined based on the SR configuration index). For example, the first index of the first SR configuration can match and / or correspond to the second index of the second SR configuration.Alternatively and / or additionally, each SR configuration of the first one or more SR configurations can be mapped to an SR configuration of the second one or more SR configurations according to the SR configuration index. Figure 11 illustrates an example of scenario 1100 associated with an IAB system operating according to the first embodiment. For example, one or more first SRs associated with one or more first SR configurations can be activated by a first child node 1102 (e.g., a UE "UE 1"). Alternatively and / or additionally, one or more second SRs associated with one or more second SR configurations can be activated by a second child node 1120 (e.g., a UE "UE 2"). In some examples, the one or more first SR configurations may comprise a first SR configuration 1108 (SR No. 1 in Figure 11) and / or a second SR configuration 1110 (SR No. 2 in Figure 11). Alternatively and / or additionally, one or more second SR configurations may comprise the first SR 1108' configuration (SR No. 1' in FIG.11) and / or the second SR 1110' configuration (SR No. 2' in FIG.11). In some examples, the first SR 1108 configuration of the first child node 1102 and / or the first SR 1108' configuration of the second child node 1120 can be mapped to a third SR 1112 configuration (SR No. 3 in FIG. 11) of an IAB node 1104 (Node 1). For example, a first SR associated with the first SR 1108 configuration can be transmitted by the first child node 1102 to the IAB node 1104. The first SR 1108 configuration associated with the first SR can be mapped to the third SR 1112 configuration according to a first SR configuration index of the IAB node 1104. Alternatively and / or additionally, a second SR, associated with the first SR, can be activated by the IAB node 1104. The second SR can be associated with the third SR 1112 configuration. Alternatively and / or additionally, a third SR associated with the first SR 1108' configuration can be transmitted by the second child node 1120 to the IAB node 1104. The first SR 1108' configuration associated with the third SR can be mapped to the third SR 1112 configuration according to the first SR configuration index of the IAB node 1104. Alternatively and / or additionally, a fourth SR, associated with the third SR, can be activated by the IAB node 1104. The fourth SR can be associated with the third SR 1112 configuration. Alternatively and / or additionally, the second SR 1110 configuration of the first child node 1102 and / or the second SR 1110' configuration of the second child node 1120 can be mapped to a fourth SR 1114 configuration (SR No. 4 in Fig. 11) of node IAB 1104. For example, a fifth SR associated with the second SR 1110 configuration can be transmitted by the first child node 1102 to node IAB 1104. The second SR 1110 configuration associated with the fifth SR can be mapped to the fourth SR 1114 configuration according to the first SR configuration index of node IAB 1104. Alternatively and / or additionally, a sixth SR, associated with the fifth SR, can be activated by node IAB 1104. The sixth SR can be associated with the fourth SR 1114 configuration. Alternatively and / or additionally, a seventh SR associated with the second SR 1110' configuration can be transmitted by the second child node 1120 to the IAB node 1104. The second SR 1110' configuration associated with the seventh SR can be mapped to the fourth SR 1114 configuration according to the first SR configuration index of the IAB node 1104. Alternatively and / or additionally, an eighth SR, associated with the seventh SR, can be activated by the IAB node 1104. The eighth SR can be associated with the fourth SR 1114 configuration. Alternatively and / or additionally, the third SR 1112 configuration of the first IAB node 1104 can be mapped to a fifth SR 1116 configuration (SR No. 5 in FIG. 11) of a parent node 1106 (Node 2) according to a second SR configuration index of the parent node 1106. Alternatively and / or additionally, the fourth SR 1114 configuration of the first IAB node 1104 can be mapped to a sixth SR 1118 configuration (SR No. 6 in FIG. 11) of the parent node 1106 according to the second SR configuration index of the parent node 1106. In some examples, a second number of SR configurations from a first plurality of SR configurations associated with the first child node 1102 can be configured so that each SR configuration from the first plurality of SR configurations can be mapped to an SR configuration from a second plurality of SR configurations of the IAB node 1104. Alternatively and / or additionally, a second number of SR configurations from a second plurality of SR configurations associated with the first IAB node 1104 can be configured so that each SR configuration from the second plurality of SR configurations can be mapped to an SR configuration from a third plurality of SR configurations of the parent node 1106.Alternatively and / or additionally, the second number of SR configurations and / or the second plurality of SR configurations can be configured such that each SR configuration of the first plurality of SR configurations can be mapped to an SR configuration of the second plurality of SR configurations of IAB node 1104. In a second embodiment, one or more SR configurations of one or more SRs can be determined by an IAB node according to a configuration (e.g., an explicit configuration). For example, one or more second SR configurations of one or more second SRs can be determined by an IAB node according to the configuration and / or according to one or more first SR configurations of one or more first SRs received from one or more child nodes. For example, the configuration can be a mapping table that can be used to map the one or more first SR configurations to the one or more second SR configurations.In some examples, the configuration may be generated by an IAB donor associated with the IAB node. Alternatively and / or additionally, the IAB donor may provide the configuration to the IAB node (and / or the IAB donor may transmit the configuration to the IAB node). Alternatively and / or additionally, the configuration may be generated by a parent node (for example, a second IAB node) associated with the IAB node. Alternatively and / or additionally, the parent node may provide the configuration to the IAB node (and / or the parent node may transmit the configuration to the IAB node). In some examples, the mapping table can establish a one-to-one correspondence (e.g., a single SR configuration to a single SR configuration), a many-to-one correspondence (e.g., multiple SR configurations to a single SR configuration), a one-to-many correspondence (e.g., a single SR configuration to multiple SR configurations), and / or a many-to-many correspondence (e.g., multiple SR configurations to multiple SR configurations). In response to receiving the first one or more SRs from the child node, the first one or more SR configurations can be determined from the first one or more SRs. Alternatively and / or additionally, in response to receiving the first one or more SRs from one or more child nodes, the second one or more SR configurations can be determined to activate and / or generate the second one or more SRs.For example, a first SR configuration of one or more first SR configurations can be mapped to a second SR configuration of one or more second SR configurations according to the configuration (and / or mapping table). Alternatively and / or additionally, the configuration may comprise a plurality of mapping tables associated with a plurality of child nodes. For example, a first mapping table within the plurality of mapping tables may correspond to a first child node within the plurality of child nodes. Alternatively and / or additionally, a second mapping table within the plurality of mapping tables may correspond to a second child node within the plurality of child nodes. For example, in response to receiving a third SR from the first child node, a third SR configuration of the third SR and / or the first child node may be mapped to a fourth SR configuration according to the first mapping table. Alternatively and / or additionally, in response to receiving a fifth SR from the second child node, a fifth SR configuration of the fifth SR and / or the second child node may be mapped to a sixth SR configuration based on the second mapping table.Alternatively and / or additionally, the configuration may comprise a (single) mapping table that can be applied to the SR configurations of the child nodes associated with the IAB node. Figure 12 illustrates an example of scenario 1200 associated with an IAB system operating according to the second embodiment. For example, one or more first SRs associated with one or more first SR configurations can be activated by a first child node 1202 (e.g., a UE "UE 1"). Alternatively and / or additionally, one or more second SRs associated with one or more second SR configurations can be activated by a second child node 1220 (e.g., a UE "UE 2"). In some examples, the one or more first SR configurations may comprise a first SR configuration 1208 (SR No. 1 in Figure 12) and / or a second SR configuration 1210 (SR No. 2 in Figure 12). Alternatively and / or additionally, one or more second SR configurations may comprise the first SR configuration 1208' (SR No. 1' in FIG. 12) and / or the second SR configuration 1210' (SR No. 2' in FIG. 12). For simplicity, the SR configuration notations in Fig.Figure 11 is numbered 1 through 6, while the SR configuration annotations in Figure 12 are numbered 1 through 7. As a result, some of the SR annotations in Figure 12 are similar to some of the SR annotations in Figure 11. However, a subject matter expert should understand that the numbering (e.g., SR No. 1 or SR No. 2) is only to distinguish different SR configurations of a single UE (i.e., it is the index of the SR configuration within the single UE). In other words, an SR configuration in Figure 11 is not directly equivalent to an SR configuration with the same notation in Figure 12. In some examples, the first SR 1208 configuration of the first child node 1202 can be mapped to a third SR 1212 configuration (SR No. 3 in Fig. 12) of an IAB node 1204 (Node 1). For example, a first SR associated with the first SR 1208 configuration can be transmitted by the first child node 1202 to the IAB node 1204. The first SR 1208 configuration associated with the first SR can be mapped to the third SR 1212 configuration according to a configuration of the IAB node 1204. For example, the configuration can be provided to the IAB node 1204 by a parent node 1206 (Node 2). Alternatively and / or additionally, the configuration may be provided to IAB node 1204 by an IAB donor associated with IAB node 1204. In some examples, the configuration may comprise a (single) mapping table. For example, the first SR 1208 configuration associated with the first SR may be mapped to the third SR 1212 configuration according to the mapping table.Alternatively and / or additionally, the configuration may comprise a plurality of mapping tables associated with a plurality of child nodes. A first mapping table 1228 of the plurality of mapping tables may be associated with the first child node 1202. For example, the first SR configuration 1208 associated with the first SR may be mapped to the third SR configuration 1212 according to the first mapping table 1228. Alternatively and / or additionally, a second SR, associated with the first SR, may be activated by the IAB node 1204. The second SR may be associated with the third SR configuration 1212. In some examples, the second SR 1210 configuration of the first child node 1202 can be mapped to a fourth SR 1214 configuration (SR No. 4 in FIG. 12) of the IAB node 1204. For example, a third SR associated with the second SR 1210 configuration can be transmitted by the first child node 1202 to the IAB node 1204. The second SR 1210 configuration associated with the third SR can be mapped to the fourth SR 1214 configuration according to the configuration of the IAB node 1204. For example, the second SR 1210 configuration associated with the third SR can be mapped to the fourth SR 1214 configuration according to the mapping table. Alternatively and / or additionally, the second SR 1210 configuration associated with the third SR can be mapped to the fourth SR 1214 configuration according to the first mapping table 1228. Alternatively and / or additionally, a fourth SR, associated with the third SR, can be activated by the IAB node 1204.The fourth SR may be associated with the fourth SR 1214 configuration. In some examples, the first SR 1208' configuration of the second child node 1220 can be mapped to the third SR 1212 configuration and / or the fourth SR 1214 configuration of the IAB node 1204. For example, a fifth SR associated with the first SR 1208' configuration can be transmitted by the second child node 1220 to the IAB node 1204. The first SR 1208' configuration associated with the fifth SR can be mapped to the third SR 1212 configuration and / or the fourth SR 1214 configuration, depending on the configuration of the IAB node 1204. For example, the first SR 1208' configuration associated with the fifth SR can be mapped to the third SR 1212 configuration, according to the mapping table. Alternatively and / or additionally, a second mapping table 1232 from the plurality of mapping tables may be associated with the second child node 1220.Alternatively and / or additionally, the first SR 1208 configuration associated with the fifth SR can be mapped to the fourth SR 1214 configuration according to the second mapping table 1232. Alternatively and / or additionally, a sixth SR, associated with the fifth SR, can be activated by the IAB node 1204. The sixth SR can be associated with the fourth SR 1214 configuration. In some examples, the second SR 1210' configuration of the second child node 1220 can be mapped to a fifth SR 1226 configuration (SR No. 5 in FIG. 12) of IAB node 1204 and / or to the fourth SR 1214 configuration of IAB node 1204. For example, a seventh SR associated with the second SR 1210' configuration can be transmitted by the second child node 1220 to IAB node 1204. The second SR 1210' configuration associated with the seventh SR can be mapped to the fifth SR 1226 configuration and / or to the fourth SR 1214 configuration, depending on the configuration of IAB node 1204. For example, the second SR 1210' configuration associated with the seventh SR can be mapped to the fourth SR 1214 configuration, according to the mapping table. Alternatively and / or additionally, the second SR 1210' configuration associated with the seventh SR can be mapped to the fifth SR 1226 configuration according to the second mapping table 1232 associated with the second child node 1220.Alternatively and / or additionally, an eighth SR, associated with the seventh SR, can be activated by the IAB node 1204. The eighth SR can be associated with the fifth SR configuration 1226. Alternatively and / or additionally, the third SR 1212 configuration of the first IAB node 1204 can be mapped to a sixth SR 1216 configuration (SR No. 6 in FIG. 12) of the parent node 1206 according to a second configuration of the parent node 1206. For example, the second configuration can be provided to the parent node 1206 by a second parent node of the parent node 1206. Alternatively and / or additionally, the second configuration can be provided to the parent node 1206 by the donor IAB. In some examples, the third SR 1212 configuration of the first IAB node 1204 can be mapped to the sixth SR 1216 configuration of the parent node 1206 according to a third mapping table 1230 of the second configuration. For example, the second configuration can (simply) comprise the third mapping table 1230 which can be applied to SR configurations of child nodes (comprising the IAB node 1204) associated with the parent node 1206.Alternatively and / or additionally, the second configuration may comprise a second plurality of mapping tables. The third mapping table 1230 of the second plurality of mapping tables may be associated with node IAB 1204. Alternatively and / or additionally, the fourth SR 1214 configuration of the first IAB node 1204 can be mapped to the sixth SR 1216 configuration of the parent node 1206 according to the third mapping table 1230. Alternatively and / or additionally, the fifth SR 1226 configuration of the first IAB node 1204 can be mapped to a seventh SR 1218 configuration (SR No. 7 in FIG. 12) of the parent node 1206 according to the third mapping table 1230. In a third embodiment, a specific SR configuration can be used to activate and / or generate one or more SRs. The specific SR configuration can be a defined SR configuration. In some examples, the specific SR configuration can be used to activate and / or generate an SR if the SR is not activated according to a BSR (activated). Alternatively and / or additionally, the specific SR configuration can be used to activate and / or generate the SR if the SR is not activated according to data from (and / or to) an available logical channel for transmission. Alternatively and / or additionally, the specific SR configuration can be used to activate and / or generate the SR if the SR is activated according to the reception of a different SR. In one example, a first SR can be received by an IAB node (for example, the first SR can be received from a child node of the IAB node). A second SR can be triggered and / or generated (by the IAB node) in response to receiving the first SR. The second SR can be triggered and / or generated according to the specific SR configuration. For example, the second SR can be associated with a specific SR configuration (for example, the SR configuration of the second SR can correspond to the specific SR configuration).In some examples, the second SR may be triggered and / or generated based on the IAB node's specific SR configuration (and / or the IAB node's specific SR configuration may be triggered) in response to receiving the first SR, regardless of the first SR's SR configuration (for example, the first SR's SR configuration may match the child node's specific SR configuration and / or the first SR's SR configuration may differ from the child node's specific SR configuration). Alternatively and / or additionally, the IAB node may be an access node of a UE. The access node may receive the first SR from the UE.The second SR can be activated and / or generated according to the IAB node's specific SR configuration (and / or the IAB node's specific SR configuration can be activated) in response to receiving the first SR, regardless of the first SR's SR configuration (e.g., the first SR's SR configuration may correspond to the child node's specific SR configuration and / or the first SR's SR configuration may be different from the child node's specific SR configuration). In some examples, the IAB node-specific SR configuration (and / or the second SR) may be associated with one or more logical channels of the IAB node. Alternatively and / or additionally, the IAB node-specific SR configuration (and / or the second SR) may not be associated with one or more logical channels of the IAB node. In some examples, the IAB node-specific SR configuration and / or the second SR may be canceled in response to the IAB node transmitting the second SR to a parent node of the IAB node. Alternatively and / or additionally, the second SR and / or the IAB node-specific SR configuration can indicate a request for one or more transmission resources for a future transmission. For example, the second SR and / or the IAB node-specific SR configuration can be used to indicate to the IAB node's parent node that one or more transmission resources are being requested for a future transmission. For example, the one or more transmission resources might correspond to one or more resources for transmitting data to the parent node. The future transmission might correspond to a data transmission (to the parent node) of data that is not available to the IAB node (for example, the IAB node has not yet received data (e.g., UL data) from a child node). The second SR and / or the IAB node-specific SR configuration can be a (special) signal.In some examples, the IAB node-specific SR configuration may be associated with an IAB node SR configuration (e.g., a plurality of IAB node SR configurations may comprise the specific SR configuration). Alternatively and / or additionally, the IAB node-specific SR configuration may not be associated with an IAB node SR configuration (e.g., the plurality of IAB node SR configurations may not comprise the specific SR configuration). Alternatively and / or additionally, the second SR and / or the IAB node-specific SR configuration may be transmitted (to the parent node) on an uplink control channel (e.g., PUCCH). Alternatively and / or additionally, the second SR and / or the IAB node-specific SR configuration may not be transmitted (to the parent node) on an uplink control channel.Alternatively and / or additionally, the second SR and / or the IAB node-specific SR configuration may apply a counter (e.g., SR_COUNTER and / or a different counter) and / or a timer (e.g., SR ban timer and / or a different timer). Alternatively and / or additionally, the second SR and / or the IAB node-specific SR configuration may not apply a counter and / or a timer. In some examples, each of the first, second, and third realizations can be implemented independently and / or separately. Alternatively and / or additionally, a combination of one or more of the first, second, and / or third realizations can be implemented. In some examples, a first BSR can be received by an IAB node from a child node of the IAB node (for example, the child node can be a second IAB node associated with the IAB node and / or the child node can be a UE served by the IAB node). The IAB node can trigger and / or generate a second BSR in response to receiving the first BSR. The first BSR can be indicative of an approximate buffer state (for example, one or more buffer states of one or more logical channel groups) associated with the child node. In response to the activation of the second BSR (and / or when the second BSR is activated), the IAB node may activate a SR. For example, the SR may be associated with a request for one or more UL resources from a parent node of the IAB node (e.g., the SR may be activated to request one or more UL resources from the parent node). In some examples, the SR may be activated and / or generated based on a lack of UL-SCH resource availability for a new transmission (e.g., no UL-SCH resources are available for the new transmission). Alternatively and / or additionally, the SR may be activated and / or generated in response to the identification of an uplink grant (e.g., a configured uplink grant) and / or the activation of the second BSR (e.g., a regular BSR) for a logical channel for which a logicalChannelSR-Mask parameter is set to false.Alternatively and / or additionally, the SR may be activated and / or generated in response to one or more UL-SCH resources being available and / or one or more UL-SCH resources not meeting one or more LCP mapping constraints configured for a logical channel that triggered the second BSR. Alternatively and / or additionally, an SR configuration associated with the logical channel that triggered the second BSR may be associated with the SR (for example, the SR may have the SR configuration). In some examples, the first BSR may indicate one or more logical channel groups (associated with the child node), one or more priorities associated with the one or more logical channel groups, and / or one or more buffer states associated with the one or more logical channel groups. Each logical channel group within the one or more logical channel groups may be associated with and / or comprise one or more logical channels with one or more priorities. It may be difficult for the IAB node to determine which logical channel of the child node triggered the first BSR. Alternatively and / or additionally, the one or more logical channels associated with the child node may be mapped to one or more second logical channels associated with the IAB node. It may be difficult for the IAB node to determine which one or more logical channels of the IAB node will receive data before the UL data is received from the child node. In a fourth embodiment, an SR configuration for an SR activated according to a BSR can be determined based on a different SR received from a child node. For example, an IAB node can receive a first BSR from a child node of the IAB node (for example, the child node can be a second IAB node associated with the IAB node and / or the child node can be a UE served by the IAT node). The IAB node can activate and / or generate a second BSR in response to receiving the first BSR. The first BSR can be indicative of an approximate buffer state (for example, one or more buffer states of one or more logical channel groups) associated with the child node. In response to the activation of the second BSR (and / or when the second BSR is activated), the IAB node may activate a first SR and / or a first SR configuration associated with the first SR. In some examples, before receiving the first BSR from the child node, the IAB node may receive a second SR associated with a second SR configuration from the child node. For example, the second SR and / or the second SR configuration may indicate a request for the IAB node to allocate a UL grant to the child node for the transmission of the first BSR to the IAB node. The first SR and / or the first SR configuration may be activated and / or generated based on the second SR and / or the second SR configuration.For example, according to the first embodiment presented herein, a mapping (e.g., an implicit mapping) can be used to activate and / or determine the first SR and / or the first SR configuration based on the second SR and / or the second SR configuration (e.g., the second SR and / or the second SR configuration can be mapped to the first SR and / or the first SR configuration based on an SR configuration index). Alternatively and / or additionally, according to the second embodiment presented herein, a mapping table and / or a configuration (e.g., an explicit configuration) can be used to activate and / or determine the first SR and / or the first SR configuration based on the second SR and / or the second SR configuration (e.g., the second SR and / or the second SR configuration can be mapped to the first SR and / or the first SR configuration based on the mapping table that can be received from a parent node of the IAB node and / or from an IAB donor associated with the IAB node). In some examples, the IAB node may not receive an SR from the child node before receiving the first BSR from the child node (and / or the IAB node may not identify an SR received from the child node before receiving the first BSR from the child node). In a fifth embodiment, the first SR and / or the first SR configuration can be determined and / or activated based on the first BSR (received from the child node of the IAB node). In some examples, the first BSR may indicate one or more logical channel groups (associated with the child node), one or more priorities associated with the one or more logical channel groups, and / or one or more buffer states associated with the one or more logical channel groups. Each logical channel group within the one or more logical channel groups may be associated with and / or may comprise one or more logical channels with one or more priorities. In some examples, a first logical channel with a higher priority among the logical channels within the one or more logical channel groups may be identified.It can be determined (and / or assumed) that the first logical channel activated the first BSR (on the child node) based on a determination that the first logical channel has the highest priority among the logical channels of one or more logical channel groups. In one example, one or more logical channel groups may comprise a first logical channel group and / or a second logical channel group. The first logical channel group may comprise logical channel A and / or logical channel B. The second logical channel group may comprise logical channel C and / or logical channel D. In response to a determination that logical channel A has a higher priority (compared to logical channel B, logical channel C, and / or logical channel D), the IAB node may determine and / or assume that the first BSR is triggered by logical channel A (even if the first BSR is triggered by a different logical channel, such as logical channel B). In response to the determination (and / or assumption) that the first logical channel activated the first BSR and / or in response to the determination that the first logical channel has the highest priority among the logical channels of one or more logical channel groups, the IAB node can map the first logical channel to a second logical channel of the IAB node. The first SR and / or the first SR configuration can be determined, generated, and / or activated based on the second logical channel. Alternatively and / or additionally, a second SR and / or a second SR configuration associated with the first logical channel can be identified. The first SR and / or the first SR configuration can be activated and / or generated based on the second SR and / or the second SR configuration.For example, according to the first embodiment presented herein, a mapping (e.g., an implicit mapping) can be used to activate and / or determine the first SR and / or the first SR configuration based on the second SR and / or the second SR configuration (e.g., the second SR and / or the second SR configuration can be mapped to the first SR and / or the first SR configuration based on an SR configuration index). Alternatively and / or additionally, according to the second embodiment presented herein, a mapping table and / or a configuration (e.g., an explicit configuration) can be used to activate and / or determine the first SR and / or the first SR configuration based on the second SR and / or the second SR configuration (e.g., the second SR and / or the second SR configuration can be mapped to the first SR and / or the first SR configuration based on the mapping table that can be received from a parent node of the IAB node and / or from an IAB donor associated with the IAB node). In a sixth embodiment, the first SR and / or the first SR configuration may be determined and / or activated based on a specific SR configuration (e.g., the first SR may be associated with the specific SR configuration and / or the first SR configuration of the first SR may correspond to the specific SR configuration) (in response to a determination that the first SR and / or the first SR configuration is activated based on the second BSR activated by the IAB node). The specific SR configuration may be a defined SR configuration. In some examples, the specific SR configuration (and / or the second SR) may be associated with one or more logical channels of the IAB node. Alternatively and / or additionally, the specific SR configuration (and / or the second SR) may not be associated with one or more logical channels of the IAB node. In some examples, each of the fourth, fifth, and sixth realizations can be implemented independently and / or separately. Alternatively and / or additionally, a combination of one or more of the fourth, fifth, and / or sixth realizations can be implemented. In some examples, a pending SR that is triggered by an IAB node before the IAB node receives UL data from a child node can be canceled (for example, with respect to Fig. 10, the second SR 922 triggered before the access node receives UL data 916 can be canceled). For example, one or more pending SRs can be canceled based on a first condition and / or a second condition. For example, under the first condition, one or more pending SRs can be canceled if they are triggered before a MAC PDU assembly, if (and / or when) the MAC PDU is transmitted, and / or if a MAC PDU (associated with the MAC PDU assembly) comprises a MAC CE BSR that includes a buffer state associated with (and / or up to) a more recent event (for example, a last event) that triggered a BSR before the MAC PDU assembly.Alternatively and / or additionally, under the second condition, one or more pending SRs may be canceled if (and / or when) one or more UL grants can host pending data (and / or all pending data) available for transmission. In some examples, an SR may be canceled under the first condition and / or the second condition if the SR is triggered by a received BSR and / or an activated BSR (triggered by the received BSR and / or a received SR). For example, one or more pending SRs may be triggered by a received BSR and / or an activated BSR (triggered by the received BSR and / or a received SR). Alternatively and / or additionally, an SR cannot be canceled under the first and / or second conditions if the SR is triggered by a second SR received from a child node. Alternatively and / or additionally, an SR can be canceled under the first and / or second conditions if the SR is triggered by a second SR received from a child node. Alternatively and / or additionally, an SR cannot be canceled under the first and / or second conditions if the SR is not triggered by a received BSR and / or a triggered BSR (triggered by a received BSR and / or a received SR). Alternatively and / or additionally, an SR can be canceled under the first and / or second conditions if the SR is not triggered by a received BSR and / or a triggered BSR (triggered by a received BSR and / or a received SR). In some examples, an SR ban timer can be used in one or more IAB systems. For example, the SR ban timer can be used to limit the SR transmission frequency due to a (short) SR periodicity (e.g., 1 millisecond). In some examples, when an SR ban timer associated with an SR configuration is running, a UE (and / or an IAB node) may not transmit an SR using that SR configuration. Alternatively and / or additionally, when an SR ban timer associated with an IAB node is running, an SR may be triggered based on one or more events other than the activation of a BSR (by the IAB node) and / or different from data available for transmission. For example, an SR may be triggered by the IAB node upon receiving a second SR from a child node of the IAB node (e.g., the SR may be triggered while the SR ban timer is running).In some examples, the SR ban timer may run for a ban time interval (e.g., 4 milliseconds). Alternatively and / or additionally, the SR ban timer may be independent of (and / or not rely on) whether UL data retransmission from the child node is required. In some examples, the IAB node can determine whether UL data retransmission from the child node is required by receiving and / or decoding data transmitted by the child node. For example, upon receiving data transmitted by the child node, the IAB node may determine that UL data retransmission from the child node is not required. Alternatively, and / or additionally, upon not receiving data from the child node, the IAB node may determine that UL data retransmission from the child node is required. The transmission of UL data could be considered an indication of whether or not UL data retransmission is required. In some examples, an IAB node may receive a first SR from a child node (e.g., a UE and / or a different IAB node). For example, a second SR may be triggered by the IAB node based on the first SR (e.g., as illustrated in Fig. 10) and / or in response to receiving the first SR. Alternatively and / or additionally, the IAB node may receive an RA preamble from the child node. For example, the second SR may be triggered by the IAB node based on the RA preamble and / or in response to receiving the RA preamble. Alternatively and / or additionally, the second SR may be triggered in response to the assignment of a UL grant to the child node (e.g., the UL grant may be associated with the first SR and / or the RA preamble).The second SR can be transmitted to a parent node of the corresponding IAB node in response to a request for one or more UL resources for the transmission of UL data associated with the child node and / or associated with the first SR received from the child node (for example, the UL data may not be available and / or may not be received by the IAB node when the second SR is transmitted to the parent node). The parent node can transmit a UL grant to the IAB node according to the second SR. The IAB node may receive the UL grant before successfully receiving the UL data from the child node. Alternatively and / or additionally, the IAB node may receive the UL grant before the UL data processing is completed by the IAB node. In some examples, the IAB node may transmit second UL data that is available for transmission according to the UL grant (to the parent node).For example, the second UL data may be different from, and / or may not include, the UL data. Alternatively and / or additionally, the second UL data may be associated with a second child node, different from the child node (for example, the second UL data may be received from the second child node). Alternatively and / or additionally, the IAB node may transmit filler data to the parent node according to the UL grant. Alternatively and / or additionally, the IAB node may not transmit data to the parent node according to the UL grant (for example, the UL grant may be waived if the data for transmission to the parent node is unavailable). Alternatively and / or additionally, the second SR may be canceled. Alternatively and / or additionally, a third SR may be activated in response to the receipt of the UL data from the child node and / or in response to the completion of processing (for example, data processing) of the UL data.Therefore, the first delay (e.g., described with respect to Fig.9 and / or Fig.10) may not be reduced. Figure 13 illustrates an example of scenario 1300 associated with an IAB system. In scenario 1300, a UE 1302 can be connected to an access node (via an access link). The UE 1302 can perform one or more first 1310 operations. These first 1310 operations can be associated with UL data arriving in a UE 1302 buffer, the UE 1302 activating a BSR, and / or the UE 1302 activating an SR 1312. For example, the UE 1302 can transmit SR 1312 to the access node. Alternatively, a first 1304 part of the access node can receive SR 1312. For example, the first 1304 part of the access node can correspond to a NW part of the access node. Alternatively and / or additionally, the first part 1304 of the access node may be associated with performing one or more network operations. In some examples, in response to receiving SR 1312 from UE 1302, the access node (and / or the first part 1304 of the access node) may activate a second SR 1316. For example, one or more SR 1336 retransmission operations may be performed in response to receiving SR 1312 from UE 1302. The one or more SR 1336 retransmission operations may include activating the second SR 1316. Alternatively and / or additionally, the second SR 1316 may be transmitted by the access node (and / or by a second part 1306 of the access node) to a parent node of the access node (and / or to a third part 1308 of the parent node). Alternatively and / or additionally, the first part 1304 of the access node may transmit a UL 1314 lease to UE 1302 (in response to receiving SR 1312). Alternatively and / or additionally, UE 1302 may transmit UL 1320 data to the access node according to the UL 1314 lease.For example, the access node can receive data from UL 1320 from UE 1302. In some examples, a second UL 1324 lease may be received by the access node from the parent node. This second UL 1324 lease may be received by the access node before receiving the UL 1320 data and / or completing the UL 1322 data processing of the UL 1320 data. In some examples, the access node may transmit second UL 1328 data to the parent node according to the UL lease. The second UL 1328 data may be different from the UL 1320 data and / or may not include the UL 1320 data. For example, the second UL 1328 data may be associated with a second child node, different from the UE (e.g., the second UL 1328 data may be received from the second child node). Alternatively and / or additionally, the second UL data may include padding data.Alternatively and / or additionally, the second SR 1316 can be cancelled (for example, the second SR 1316 can be cancelled in response to the transmission of the second UL 1328 data to the parent node). Alternatively and / or additionally, a third SR 1330 may be activated in response to the receipt of UL 1320 data from the child node and / or in response to the completion of data processing 1322 of the UL 1320 data. For example, one or more second operations 1326 may be performed by the access node in response to the receipt of UL 1320 data from the child node and / or in response to the completion of data processing 1322 of the UL 1320 data. In some examples, the one or more second operations 1326 may be associated with UL data arriving in a buffer of the access node, the access node activating a second BSR, and / or the access node activating the third SR 1330. The third SR 1330 may be transmitted to the parent node (and / or to the third party 1308 of the access node). Alternatively and / or additionally, the parent node may transmit a third UL 1332 grant to the access node according to the third SR 1330.Alternatively and / or additionally, the access node may transmit third UL 1334 data, comprising the UL 1320 data, to the parent node according to the third grant of UL 1332. In some examples, the UL 1320 data may be received by the access node after the access node receives the second grant of UL 1324 and / or after the processing of UL 1322 data is completed because the UL 1320 data is unsuccessfully transmitted to the access node and / or retransmitted to the access node (using one or more data retransmission techniques, such as Hybrid Automatic Repeat Request (HARQ)). In a seventh embodiment, a pending SR that is an early-activated SR is not canceled when (and / or responding to) the BSR comprises a buffer state up to (and / or indicative of) a more recent event (e.g., a last event) that activated a BSR before a MAC PDU assembly. Alternatively and / or additionally, the pending SR that is an early-activated SR may not be canceled when a second BSR is transmitted (and / or responding to). An early-activated SR may correspond to an SR that is activated, according to an SR received from a child node, before an IAB node receives UL data from the child node. Alternatively and / or additionally, an early-activated SR may correspond to an SR that is activated according to a received BSR and / or an activated BSR, before the IAB node receives UL data from the child node.Alternatively and / or additionally, an early-activated SR may correspond to an SR that is activated based on an SR received from the child node, before the IAB node transmits a UL grant to the child node. Alternatively and / or additionally, an early-activated SR may correspond to an SR that is activated based on a received BSR and / or an activated BSR, before the IAB node transmits the UL grant to the child node. For example, an early-activated SR may be activated for the (subsequent) transmission of UL data associated with the child node to a parent node of the IAB node. Alternatively and / or additionally, a pending SR that is an early activated SR is not canceled when (and / or in response to) one or more UL grants (received from the parent node) may host pending data (and / or all pending data) available for transmission (from the IAB node to the parent node). Alternatively and / or additionally, the pending SR may not be canceled and / or may remain pending when (and / or in response to) it performs the transmission of UL data to the parent node, and / or the data does not include the UL data associated with the child node. Alternatively and / or additionally, the pending SR may not be canceled and / or may remain pending when (and / or in response to) the transmission of the UL data associated with the child node to the parent node is not performed and / or completed. In some examples, the pending SR may not be canceled and / or remain pending if a MAC PDU (associated with the MAC PDU assembly) includes a BSR MAC CE.Alternatively and / or additionally, the pending SR cannot be canceled and / or remains pending if the MAC PDU does not include a MAC CE BSR. For example, the pending SR cannot be canceled if the SR is used to request one or more transmission resources for transmitting the child node's UL data (which is not yet available for transmission) to the parent node, if the child node's UL data is not transmitted to the parent node, and / or if a BSR indicating a child node buffer state is not transmitted to the parent node. In some examples, while the SR is pending, the IAB node may acquire UL resources (e.g., broadcast resources). Alternatively and / or additionally, the SR may not be canceled when (and / or in response to) a MAC PDU is assembled and / or the MAC PDU does not contain the child node's UL data (and / or the MAC PDU does not contain a BSR that reflects the child node's buffer state). In some examples, a second BSR transmitted by the IAB node to the parent node may be indicative of the child node's buffer state (e.g., the buffer state can be determined based on the BSR received from the child node). For example, the second BSR may be indicative of a quantity of data (associated with UL data that the IAB node has not yet received from the child node and / or has not yet processed) indicated by the BSR received from the child node. In some examples, UL data may be available to the IAB node (for example, UL data may be received by the IAB node from the child node and / or the UL data may be processed by the IAB node using data processing). In some examples, the SR (for example, the pre-activated SR) may be canceled when (and / or in response to) UL data (associated with the child node) is transmitted to the parent node by the IAB node. Alternatively and / or additionally, the SR may be canceled when (and / or in response to) the IAB node transmits data (for example, a MAC PDU) to the parent node, and / or the data comprises UL data associated with the child node (and / or comprises a BSR indicative of the child node's buffer state). In some examples, the SR may be canceled if the data (and / or the MAC PDU) transmitted to the parent node comprises a MAC CE.Alternatively and / or additionally, the SR may be canceled if the data (and / or the MAC PDU) transmitted to the parent node does not include a MAC CE. Alternatively and / or additionally, the SR may be canceled in response to the receipt of a first indication from the child node (for example, the first indication may be that retransmission of the UL data to the IAB node is not required). Alternatively and / or additionally, the SR may not be canceled in response to the receipt of a second indication from the child node (for example, the second indication may be that retransmission of the UL data to the IAB node is required). In some examples, the first and / or second indication may include the transmission of UL data. Figure 14 illustrates an example of a 1400 scenario associated with an IAB system operating according to the seventh embodiment. In some examples, a UE 1402 can connect to an access node 1404 (via an access link). UE 1402 can perform one or more first operations 1410. The first operation 1410 can be associated with UL data arriving in a buffer of UE 1402. UE 1402 activates a BSR and / or UE 1402 activates SR 1412. For example, UE 1402 can transmit SR 1412 to access node 1404. Alternatively and / or additionally, access node 1404 can receive SR 1412. In 1414, a second SR can be activated in response to receiving SR 1412 from UE 1402. In some examples, a "1st SR" SR 1416, associated with the second SR and / or an SR configuration associated with the second SR, can be transmitted to a parent node 1408 of access node 1404 (for example, SR 1416). "1st SR" may include the second SR). Alternatively and / or additionally, access node 1404 may transmit a first UL grant to UE 1402. In some instances, a first 1418 transmission of the UL data may be unsuccessful (and / or may fail). For example, the UL data may not be received by access node 1404 in response to the first 1418 transmission. Alternatively and / or additionally, access node 1404 may receive a second UL grant from parent node 1408. For example, the second UL grant may be transmitted to access node 1404 according to SR 1416 "1st SR". In some instances, the second UL data 1422 may be transmitted to parent node 1408 according to the second UL grant. The second UL data 1422 may not include the UL data associated with UE 1402.Alternatively and / or additionally, in 1420, the second SR may not be cancelled (e.g., the second SR may not be cancelled according to the second UL data 1422 that does not comprise the UL data associated with UE 1402). In some examples, an SR 1428 "2nd SR", associated with the second SR and / or the SR configuration associated with the second SR, may be transmitted to the parent node 1408. Alternatively and / or additionally, a second 1424 transmission of the UL data and / or a third 1430 transmission of the UL data may be unsuccessful (and / or may fail). For example, the UL data may not be received by the access node 1404 in response to the second 1424 transmission and / or the third 1430 transmission. Alternatively and / or additionally, the access node 1404 may receive a third UL grant from the parent node 1408. For example, the third UL grant may be transmitted to the access node 1404 according to SR 1428 "2nd SR". In some examples, third-party data from UL 1434 may be transmitted to the parent node 1408 according to the third-party UL grant. Third-party data from UL 1434 may not include UL data associated with UE 1402.Alternatively and / or additionally, in 1426, the second SR may not be cancelled (e.g., the second SR may not be cancelled according to third-party UL data 1434 that does not comprise the UL data associated with UE 1402). In some examples, a third SR (SR 1438), associated with the second SR and / or the SR configuration associated with the second SR, may be transmitted to the parent node 1408. Alternatively and / or additionally, a fourth transmission of the UL data (1436) may be successful. For example, the UL data may be received by the access node 1404 in response to the fourth transmission (1436). Alternatively and / or additionally, the access node 1404 may receive a fourth UL grant from the parent node 1408. For example, the fourth UL grant may be transmitted to the access node 1404 according to the third SR (SR 1438). In some examples, the fourth UL data (1440) may be transmitted to the parent node 1408 according to the fourth UL grant. The fourth data of UL 1440 may comprise the UL data associated with UE 1402.Alternatively and / or additionally, in 1432, the second SR may be cancelled (for example, the second SR may be cancelled according to the fourth data of UL 1440 comprising the UL data associated with UE 1402). In an eighth embodiment, a pre-activated SR can be activated in one or more cases based on one or more indications received from a child node. For example, an IAB node can activate the SR in response to receiving a second SR from the child node. The SR can be activated before the IAB node receives UL data from the child node. Alternatively and / or additionally, the IAB node can activate the SR based on a received BSR and / or an activated BSR, before the IAB node receives UL data from the child node. In some examples, the SR may be canceled in response to the IAB node transmitting the SR to a parent node of the IAB node. Alternatively and / or additionally, the SR may not be canceled in response to the IAB node transmitting the SR to the parent node. Alternatively and / or additionally, the SR may be canceled in response to the IAB node transmitting UL data (e.g., a MAC PDU) to the parent node, and / or the data comprises UL data (from the child node) (and / or the data comprises a BSR indicative of a buffer state of the child node). Alternatively and / or additionally, the SR may be canceled in response to a MAC PDU being assembled, where the MAC PDU comprises UL data from the child node (and / or the MAC PDU comprises a BSR that reflects the buffer state of the child node). Alternatively and / or additionally, the SR may be cancelled according to one or more SR cancellation conditions (such as the first condition and / or the second condition set forth herein). In some examples, a second BSR transmitted by the IAB node to the parent node can be indicative of the child node's buffer state (for example, the buffer state can be determined based on the BSR received from the child node). For instance, the second BSR might indicate a quantity of data (associated with UL data that the IAB node has not yet received from the child node and / or has not yet processed) as indicated by the BSR received from the child node. In some examples, the IAB node may receive an initial indication from the child node. In some examples, the initial indication may be that retransmission of the UL data to the IAB node is not required. Alternatively and / or additionally, the initial indication may be that retransmission of the UL data to the IAB node is required. In some examples, the initial indication may correspond to a transmission of UL data. For example, the initial indication may include the UL data. In some examples, in response to receiving the initial indication and / or determining (based on the initial indication) that retransmission of the UL data to the IAB node is required, the IAB node may activate (for example, reactivate) the SR.Alternatively and / or additionally, in response to receiving the first indication and / or determining (based on the first indication) that retransmission of the UL data to the IAB node is not required, the IAB node may not activate the SR. Alternatively and / or additionally, the IAB node may activate (e.g., reactivate) the SR at a time when it expects to receive the first indication (and / or in response to a determination that the first indication is not received at that time). Alternatively and / or additionally, the SR may be activated (e.g., reactivated) in response to (and / or when) a PDCCH, indicating a UL lease for retransmission, is transmitted to the child node. Alternatively and / or additionally, the SR can be activated (e.g., reactivated) during a period of time between the receipt of the first indication from the child node and / or the transmission of the PDCCH, indicative of the UL grant for retransmission, to the child node.Alternatively and / or additionally, the SR can be activated (e.g., reactivated) during a period of time between the time the first indication is expected to be received and the transmission of the PDCCH, indicative of the UL grant for retransmission, to the child node. Alternatively and / or additionally, a second SR can be activated based on a BSR. For example, the BSR can be activated in response to UL data being successfully received from the child node. Alternatively and / or additionally, the second SR can be activated in response to the activation of the BSR. It can be seen that, by activating the SR according to the eighth realization, the number of times the IAB node transmits the SR can be reduced and / or it can result in less data transmission from the IAB node to the parent node. Figure 15 illustrates an example of scenario 1500 associated with an IAB system operating according to the eighth realization. In some examples, a UE 1502 can connect to an access node 1504 (via an access link). UE 1502 can perform one or more first operations 1510. The first operation 1510 can be associated with UL data arriving in a buffer of UE 1502, UE 1502 activating a BSR, and / or UE 1502 activating an SR 1512. For example, UE 1502 can transmit SR 1512 to access node 1504. Alternatively and / or additionally, access node 1504 can receive SR 1512. In 1514, a second SR (for example, SR1) can be activated in response to receiving SR 1512 from UE 1502. In some examples, an SR 1516 "1st SR", associated with the second SR, and / or an SR configuration associated with the second SR, can be transmitted to a parent node 1508 of access node 1504 (for example, SR 1516 "1st SR" may include the second SR).Alternatively and / or additionally, at 1520, the second SR can be cancelled in response to the transmission of SR 1516 "1st SR" to parent node 1508 (and / or the second SR can be cancelled when SR 1516 "1st SR" is transmitted to parent node 1508). Alternatively and / or additionally, access node 1504 may transmit a first UL lease to UE 1502. In some instances, a first 1518 transmission of the UL data may be unsuccessful (and / or fail). For example, the UL data may not be received by access node 1504 in response to the first 1518 transmission. Alternatively and / or additionally, at 1526, an SR2 (for example, an SR) associated with the second SR and / or SR configuration may be activated. In some instances, the SR2 may be activated at 1526 in response to the first unsuccessful 1518 transmission. Alternatively and / or additionally, SR2 can be activated at 1526 in response to receiving a first indication from UE 1502 via the first transmission 1518 and / or determine (based on the first indication) that retransmission of UL data from UE 1502 to access node 1504 is required. Alternatively and / or additionally, access node 1504 may receive a second UL grant from parent node 1508. For example, the second UL grant may be transmitted to access node 1504 according to SR 1516 "1st SR". In some examples, the second UL data 1522 may be transmitted to parent node 1508 according to the second UL grant. The second UL data 1522 may not include the UL data associated with UE 1502. Alternatively and / or additionally, a second transmission of the UL data 1524 may be unsuccessful (and / or may fail). For example, UL data may not be received by access node 1504 in response to the second transmission 1524. Alternatively and / or additionally, at 1532, an SR3 (e.g., an SR) associated with the second SR and / or SR configuration may be activated. In some examples, the SR3 may be activated at 1532 in response to the unsuccessful second transmission 1524.Alternatively and / or additionally, SR3 may be activated at 1532 in response to the receipt of a second indication from UE 1502 via the second transmission 1524 and / or determine (based on the second indication) that retransmission of UL data from UE 1502 to access node 1504 is required. Alternatively and / or additionally, access node 1504 may transmit an SR 1528 "2nd SR" associated with the second SR and / or SR configuration to parent node 1508. Alternatively and / or additionally, at 1538, SR2 and / or SR3 may be canceled in response to the transmission of SR 1528 "2nd SR" to parent node 1508 (and / or SR2 and / or SR3 may be canceled when SR 1528 "2nd SR" is transmitted to parent node 1508). Alternatively and / or additionally, a third 1530 transmission of the UL data may be unsuccessful (and / or may fail). For example, access node 1504 may not receive the UL data in response to the third 1530 transmission. Alternatively and / or additionally, at 1542, an SR4 (e.g., an SR) associated with the second SR and / or the SR configuration may be activated. In some examples, the SR4 may be activated at 1542 in response to the unsuccessful third 1530 transmission. Alternatively and / or additionally, the SR4 may be activated at 1542 in response to the receipt of a third indication from UE 1502 via the third 1530 transmission and / or the determination (based on the third indication) that retransmission of the UL data from UE 1502 to access node 1504 is required. Alternatively and / or additionally, access node 1504 may receive a third UL grant from parent node 1508. For example, the third UL grant may be transmitted to access node 1504 according to SR 1528 "2nd SR". In some examples, the third UL data from 1534 may be transmitted to parent node 1508 according to the third UL grant. Third-party UL data 1534 may not include UL data associated with UE 1502. Alternatively and / or additionally, access node 1504 may transmit an SR 1540 "3rd SR" associated with the second SR and / or SR configuration to parent node 1508. Alternatively and / or additionally, at 1544, SR4 may be canceled in response to the transmission of SR 1540 "3rd SR" to parent node 1508 (and / or SR4 may be canceled when SR 1540 "3rd SR" is transmitted to parent node 1508). Alternatively and / or additionally, a fourth 1536 transmission of the UL data may be successful. For example, the UL data may be received by access node 1504 in response to the fourth 1536 transmission. In some examples, one or more second 1546 operations may be performed by access node 1504 in response to the fourth 1536 transmission. Alternatively and / or additionally, one or more second 1546 operations may be performed by access node 1504 in response to receiving a fourth indication from UE 1502 via the fourth 1536 transmission and / or determining (based on the fourth indication) that retransmission of the UL data from UE 1502 to access node 1504 is not required. For example, one or more second operations 1504 may be associated with UL data arriving at a buffer on access node 1504, access node 1504 activating a BSR, and / or access node 1504 activating an SR5 (e.g., an SR) associated with the second SR and / or the SR configuration. Alternatively and / or additionally, access node 1504 may receive a fourth UL grant from parent node 1508. For example, the fourth UL grant may be broadcast to access node 1504 according to SR 1540 "3rd SR". In some examples, the fourth UL data 1550 may be broadcast to parent node 1508 according to the fourth UL grant. The fourth data of UL 1550 may comprise the UL data associated with UE 1502. Alternatively and / or additionally, in 1548, SR5 may be cancelled (for example, the second SR and / or SR5 may be cancelled according to the transmission of the fourth data of UL 1550 comprising the UL data associated with UE 1502). Figure 16 illustrates an example of scenario 1600 associated with the IAB system operating according to the eighth realization. In some examples, access node 1504 may receive SR 1512 from UE 1502. The second SR may not be canceled in response to the transmission of SR 1516 "1st SR" to parent node 1508. Alternatively and / or additionally, in scenario 1626, the second SR (e.g., SR1) and / or SR2 may be canceled in response to the transmission of the second UL data 1522, which does not comprise the UL data associated with UE 1502, to parent node 1508 (and / or the second SR (e.g., SR1) and / or SR2 may be canceled when the second UL data 1522 is transmitted to parent node 1508).Alternatively and / or additionally, in 1632, SR3 and / or SR4 may be canceled in response to the transmission of the third UL data 1534, which does not comprise the UL data associated with UE 1502, to the parent node 1508 (and / or SR3 and / or SR4 may be canceled when the third UL data 1534 is transmitted to the parent node 1508). Alternatively and / or additionally, in 1646, SR5 may be canceled (for example, the second SR and / or SR5 may be canceled based on the fourth UL data 1550, which comprises the UL data associated with UE 1502). In some examples, SR5 (and / or the second SR) may be canceled based on one or more SR cancellation conditions (such as the first and / or second condition set forth herein). In a ninth embodiment, an SR prohibition timer, associated with an SR that is an early-activated SR, can be stopped based on one or more indications received from a child node. For example, an IAB node can activate the SR in response to receiving a second SR from the child node. The SR can be activated before the IAB node receives UL data from the child node. Alternatively and / or additionally, the IAB node can activate the SR based on a received BSR and / or an activated BSR, before the IAB node receives UL data from the child node. In some examples, the IAB node may initiate the SR ban timer (if the SR ban timer associated with the SR is configured) in response to the IAB node transmitting the SR to a parent node of the IAB node. Alternatively and / or additionally, the IAB node may receive an initial indication from the child node. In some examples, the initial indication may be that retransmission of the UL data to the IAB node is not required. Alternatively and / or additionally, the initial indication may be that retransmission of the UL data to the IAB node is required. In some examples, the initial indication may correspond to a UL data transmission. For example, the initial indication may include the UL data. In some examples, in response to receiving the first indication and / or determining (based on the first indication) that retransmission of UL data to the IAB node is required, the IAB node may stop the SR ban timer (if the SR ban timer is running). For example, the IAB node may stop the SR ban timer to acquire one or more UL resources sooner than if the IAB node did not stop the SR ban timer. Alternatively and / or additionally, in response to receiving the first indication and / or determining (based on the first indication) that retransmission of UL data to the IAB node is not required, the IAB node may not stop the SR ban timer (if the SR ban timer is running).For example, by not stopping the SR ban timer, the number of times the IAB node transmits the SR may be reduced and / or may result in less data transmission from the IAB node to the parent node. Alternatively and / or additionally, the IAB node may stop the SR ban timer at the time the first indication is expected to be received (and / or in response to a determination that the first indication is not received at that time). Alternatively and / or additionally, the SR ban timer may be stopped in response to (and / or when) a PDCCH, indicating a UL retransmission grant, is transmitted to the child node. Alternatively and / or additionally, the SR ban timer may be stopped for a period of time between the receipt of the first indication from the child node and / or the transmission of the PDCCH, indicating the UL retransmission grant, to the child node.Alternatively and / or additionally, the prohibition timer and SR can be stopped for a period of time between the time the first indication is expected to be received and the transmission of the PDCCH, indicative of the UL grant for retransmission, to the child node. Alternatively and / or additionally, the SR may be canceled in response to the IAB node transmitting UL data (e.g., a MAC PDU) to the parent node and / or the data comprises UL data (from the child node) (and / or the data comprises a BSR indicative of the child node's buffer state). Alternatively and / or additionally, the SR may be canceled in response to an assembled MAC PDU, where the MAC PDU comprises the child node's UL data (and / or the MAC PDU comprises a BSR reflecting the child node's buffer state). Alternatively and / or additionally, the SR may be canceled based on one or more SR cancellation conditions (such as the first and / or second conditions presented herein). Alternatively and / or additionally, in response to the receipt of the first indication and / or the determination (according to the first indication) that retransmission of the UL data to the IAB node is required, the IAB node cannot cancel the SR.Alternatively and / or additionally, in response to the receipt of the first indication and / or the determination (according to the first indication) that retransmission of the UL data to the IAB node is not required, the IAB node may cancel the SR. In some examples, a BSR transmitted by the IAB node to the parent node can be indicative of the child node's buffer state (for example, the buffer state can be determined based on a second BSR received from the child node). For instance, the BSR might indicate a quantity of data (associated with UL data that the IAB node has not yet received from the child node and / or has not yet processed) as indicated by the second BSR received from the child node. Figure 17 illustrates an example of scenario 1700 associated with the IAB system operating according to the ninth embodiment. In some examples, access node 1504 may receive SR 1512 from UE 1502. In some examples, at 1514, the second SR (e.g., SR1) may be activated in response to the reception of SR 1512 from UE 1502. In some examples, at 1720, an SR ban timer associated with the second SR may be initiated in response to the transmission of SR 1516 "1st SR" to the parent node 1508. Alternatively and / or additionally, at 1726, the SR ban timer may be stopped (if the SR ban timer is running) in response to the first unsuccessful transmission of UL data at 1518.Alternatively and / or additionally, the SR ban timer can be stopped at 1726 (if the SR ban timer is running) in response to receiving the first indication from UE 1502 via the first transmission 1518 and / or determine (based on the first indication) that retransmission of UL data from UE 1502 to access node 1504 is required. Alternatively and / or additionally, at 1732, the SR ban timer may be stopped (if the SR ban timer is running) in response to the second unsuccessful UL data transmission at 1524. Alternatively and / or additionally, the SR ban timer may be stopped at 1732 (if the SR ban timer is running) in response to receiving the second indication from UE 1502 via the second UL data transmission at 1524 and / or determining (based on the second indication) that retransmission of the UL data from UE 1502 to access node 1504 is required. In some examples, at 1738, the SR ban timer may start in response to the transmission of SR 1528 "2nd SR" to parent node 1508. Alternatively and / or additionally, at 1742, the SR ban timer may stop (if the SR ban timer is running) in response to the third transmission 1530 of the UL data, which is unsuccessful. Alternatively and / or additionally, the SR ban timer may stop at 1742 (if the SR ban timer is running) in response to the reception of the third indication from UE 1502 via the third transmission 1530 and / or determining (based on the third indication) that retransmission of the UL data from UE 1502 to access node 1504 is required. In some examples, at 1744, the SR ban timer may be initiated in response to the transmission of SR 1540 "3rd SR" to parent node 1508. Alternatively and / or additionally, at 1746 the second SR (e.g., SR1) may be canceled in response to the successful fourth transmission of UL data at 1536. Alternatively and / or additionally, the second SR may be canceled at 1746 in response to the reception of the fourth indication from UE 1502 via the fourth transmission at 1536 and / or determining (based on the fourth indication) that retransmission of UL data from UE 1502 to access node 1504 is not required. In some examples, each of the first, second, third, fourth, fifth, sixth, seventh, eighth, and ninth realizations can be implemented independently and / or separately. Alternatively and / or additionally, a combination of one or more of the first, second, third, fourth, fifth, sixth, seventh, eighth, and / or ninth realizations can be implemented. Figure 18 is a flowchart 1800 according to an exemplary embodiment, from the perspective of a first node. In step 1805, a first signal may be received from a second node to request one or more first transmission resources (for example, the first signal may be a request for one or more first transmission resources). In step 1810, in response to the receipt of the first signal, a second signal may be triggered to request one or more second transmission resources (for example, the second signal may be a second request for one or more second transmission resources). Figure 19 is a flow diagram 1900 according to an exemplary embodiment, from the perspective of a first node. In step 1905, a third signal to allocate one or more third transmission resources can be transmitted to a second node. In step 1910, a second signal can be activated to request one or more second transmission resources according to the third signal. In the context of one or more of the embodiments illustrated in FIG.18 and / or the embodiment illustrated in FIG.19 and analyzed above, the first node can transmit the second signaling to a third node after (and / or in response to) activating the second signaling. In the context of the embodiment illustrated in FIG. 19 and analyzed above, the first node can transmit the third signal in response to receiving a first signal to request one or more first transmission resources. Alternatively and / or additionally, the first node can activate the second signal in response to the transmission of the third signal to the second node. Figure 20 is a flowchart 2000 according to an exemplary embodiment, from the perspective of a first node. At stage 2005, a fourth signal can be received to configure a plurality of SR configurations. At stage 2010, an SR can be activated when data for transmission is not available at the first node (e.g., the SR can be activated when no data is available at the first node). At stage 2015, the first node can determine, according to a rule, to use a first SR configuration for the SR, where the plurality of SR configurations comprises the first SR configuration. In the context of the embodiment illustrated in FIG. 20 and analyzed above, the fourth signaling may comprise an RRC message. Alternatively and / or additionally, the first node may activate the SR in response to receiving a fifth signaling from a second node to request one or more transmission resources. Alternatively and / or additionally, the fifth signaling may comprise a second SR associated with the second node. Alternatively and / or additionally, the second SR may be associated with a second SR configuration set for the second node. Alternatively and / or additionally, the rule may be associated with a mapping (e.g., an implicit mapping). Alternatively and / or additionally, the first node may map the second SR configuration to the first SR configuration based on a first index of the first SR configuration and / or a second index of the second SR configuration. Alternatively and / or additionally, the rule may be associated with a mapping (for example, an explicit mapping). Alternatively and / or additionally, the first node may map the second SR configuration to the first SR configuration according to a mapping table configured for the first node. Alternatively and / or additionally, the mapping table may map the second SR configuration (associated with the second node) to the first SR configuration (associated with the first node). Alternatively and / or additionally, the rule may be associated with a defined SR configuration, from among the plurality of SR configurations, for the SR (for example, the first SR configuration may correspond to the SR configuration defined based on the rule). The defined SR configuration may be predefined. Alternatively and / or additionally, the defined SR configuration may be configurable (and / or changeable). In some examples, the mapping (e.g., implicit and / or explicit mapping) can establish a one-to-one correspondence (e.g., a single SR configuration to a single SR configuration). Alternatively and / or additionally, the mapping can correspond to many-to-one (e.g., a plurality of SR configurations to a single SR configuration). Alternatively and / or additionally, the mapping can correspond to one-to-many (e.g., a single SR configuration to a plurality of SR configurations). Alternatively and / or additionally, the mapping can correspond to many-to-many (e.g., a plurality of SR configurations to a plurality of SR configurations). In the context of one or more of the embodiments illustrated in FIG. 18, the embodiment illustrated in FIG. 19, and / or the embodiment illustrated in FIG. 20 and discussed above, the third signaling element may be Downlink Control Information (DCI) transmitted through a PDCCH. Alternatively and / or additionally, the DCI may include an uplink lease. Alternatively and / or additionally, the uplink lease may be associated with a new transmission. Figure 21 is a flowchart 2100 according to an exemplary embodiment, from the perspective of a first node. In step 2105, a first SR can be activated to transmit to a third node. In step 2110, the UL data can be transmitted to the third node after activating the first SR, where the UL data may comprise a BSR MAC CE comprising a buffer state associated with an event. The event may be associated with a BSR that is triggered at the first node (for example, the event may be a more recent event associated with the triggered BSR). In step 2115, the first SR may not be canceled. The first SR may not be canceled based on the UL data and / or the transmission of UL data to the third node. In the context of the embodiment illustrated in FIG. 21 and discussed above, the first node may cancel the first SR if the UL data includes second UL data received from a second node. Alternatively and / or additionally, the first node may cancel the first SR if the UL data includes a second BSR indicative of a second buffer state at the second node. Alternatively and / or additionally, the first node may cancel the first SR in response to a determination that data retransmission from the second node to the first node is not required. Alternatively and / or additionally, the first node may activate a second SR to be transmitted to the third node before transmitting the UL data to the third node. Alternatively and / or additionally, the first node may cancel the second SR upon (and / or in response to) the transmission of the UL data to the third node. Alternatively and / or additionally, the first SR may be a pre-activated SR that is not activated by a BSR. Alternatively and / or additionally, the second SR may be activated in response to the activation of a BSR. Alternatively and / or additionally, the UL data may not include the second UL data (and / or the third UL data) associated with the second node. Alternatively and / or additionally, the UL data may not include a BSR indicative of a buffer state for the second node. Figure 22 is a flowchart 2200 according to an exemplary embodiment, from the perspective of a first node. In step 2205, a first signal may be received from a second node requesting one or more first transmission resources (for example, the first signal may be a request for one or more first transmission resources). In step 2210, the first node may determine whether data retransmission from the second node to the first node is required. In step 2215, a second signal may be activated (and / or reactivated) based on a determination that data retransmission is required. In the context of the embodiment illustrated in FIG. 22 and analyzed above, the first node can activate the second signal to request one or more second transmission resources in response to receiving the first signal (for example, the second signal can be a request for one or more second transmission resources). Alternatively and / or additionally, the first node can transmit the second signal to a third node after activating the second signal. Alternatively and / or additionally, the first node can cancel the second signal upon and / or in response to the transmission of the second signal to the third node. Alternatively and / or additionally, the first node may transmit UL data to the third node after triggering the second signaling. Alternatively and / or additionally, the first node may cancel the second signaling if the UL data comprises a MAC CE BSR that includes a buffer state associated with an event (e.g., a more recent event) that triggered a BSR on the first node. Alternatively and / or additionally, the determination that data retransmission is required can be based on a second UL data transmission from the second node. Alternatively and / or additionally, the second signaling may not be activated (and / or may not be reactivated) in response to a determination that data retransmission is not required. Figure 23 is a flowchart 2300 according to an exemplary embodiment, from the perspective of a first node. In step 2305, a first signal may be received from a second node to request one or more first transmission resources (for example, the first signal may be a request for one or more first transmission resources). In step 2310, a second signal may be activated to be transmitted to a third node to request one or more second transmission resources. In step 2315, a timer associated with the second signal may be initiated based on a transmission of the second signal (and / or the timer may be initiated in response to the transmission of the second signal). In step 2320, the first node may determine, while the timer is running, whether data retransmission from the second node to the first node is required.In step 2325, the timer can be stopped based on a determination that data retransmission from the second node to the first node is required. In the context of the embodiment illustrated in FIG. 23 and analyzed above, the first node can transmit UL data to the third node after activating the second signaling. Alternatively and / or additionally, the first node can cancel the second signaling based on the transmission of UL data if the UL data includes second UL data (received) from the second node. Alternatively and / or additionally, the first node can cancel the second signaling based on the transmission of UL data if the UL data includes a BSR indicating a buffer state of the second node. Alternatively and / or additionally, the first node may not cancel the second signaling based on the determination that data retransmission from the second node to the first node is required. Alternatively and / or additionally, the determination that data retransmission is required may be based on a third-party UL data transmission from the second node. Alternatively and / or additionally, the first node may cancel the second signaling based on a determination that data retransmission from the second node to the first node is not required. Alternatively and / or additionally, the first node can activate the second signaling in response to receiving the first signaling. Alternatively and / or additionally, the timer can be an SR prohibition timer. Alternatively and / or additionally, the SR prohibition timer can be used to prohibit the transmission of the second signal. In the context of one or more of the embodiments illustrated in FIG.22 and / or the embodiment illustrated in FIG.23, and analyzed above, the first node can transmit the second signaling to the third node after activating the second signaling and / or before canceling the second signaling. In the context of one or more of the embodiments illustrated in FIG. 18, the embodiment illustrated in FIG. 19, the embodiment illustrated in FIG. 20, the embodiment illustrated in FIG. 21, the embodiment illustrated in FIG. 22 and / or the embodiment illustrated in FIG. 23, and analyzed above, the first one or more transmission resources and / or the second one or more transmission resources may be associated with UL data transmission in a PUSCH. Alternatively and / or additionally, the first signaling may be an SR received via a PUCCH. Alternatively and / or additionally, the first signaling may be an RA preamble received via a PRACH. Alternatively and / or additionally, the first signaling may be a BSR received via a PUSCH. Alternatively and / or additionally, the first signaling may be a MAC CE received via a PUSCH. Alternatively and / or additionally, the first signaling may be an RRC message received via a PUSCH. Alternatively and / or additionally, the second signaling may be an RA preamble transmitted via a PRACH. Alternatively and / or additionally, the second signaling may be a BSR transmitted via a PUSCH. Alternatively and / or additionally, the second signaling may be a MAC CE transmitted via a PUSCH. Alternatively and / or additionally, the second signaling may be an RRC message transmitted via a PUSCH. Alternatively and / or additionally, the second signaling may be an SR transmitted via a PUCCH. Alternatively and / or additionally, the SR may be activated when the data associated with the first node and / or the data originating from the first node are not available for transmission. Alternatively and / or additionally, the SR may be activated when a BSR associated with the first node and / or originating from the first node is not activated (and / or when no BSR associated with the first node and / or originating from the first node is activated). Alternatively and / or additionally, the first SR may be activated when the data associated with the first node and / or the data originating from the first node are not available for transmission. Alternatively and / or additionally, the first SR may be activated when a BSR associated with the first node and / or originating from the first node is not activated (and / or when no BSR associated with the first node and / or originating from the first node is activated). Alternatively and / or additionally, the first node can be an IAB node. Alternatively and / or additionally, the first node can be a relay node. Alternatively and / or additionally, the first node can be a network node. Alternatively and / or additionally, the first node can be an access node. Alternatively and / or additionally, the second node can be a UE. Alternatively and / or additionally, the second node can be an IAB node. Alternatively and / or additionally, the second node can be a relay node. Alternatively and / or additionally, the second node can be a network node. Alternatively and / or additionally, the third node can be an IAB node. Alternatively and / or additionally, the third node can be a relay node. Alternatively and / or additionally, the third node can be a network node. Alternatively and / or additionally, the third node can be an IAB donor. Alternatively and / or additionally, the third node can be a parent node of the first node. Alternatively and / or additionally, the second node can be a child node of the first node. Alternatively and / or additionally, the first node can be an access node (and / or a parent node) of the second node. Figure 24 is a flowchart 2400 according to an exemplary embodiment, from the perspective of a first node. In step 2405, the first node can activate a SR based on an expected transmission from a second node. The second node can be a child node of the first node. In step 2410, the first node can determine a first SR configuration for the SR from a plurality of SR configurations configured for the first node. With reference again to Figures 3 and 4, in an exemplary embodiment of a first node, the device 300 includes a program code 312 stored in memory 310. The CPU 308 can execute the program code 312 (i) to activate an SR based on an expected transmission from a second node that is a child node of the first node, and (ii) to determine a first SR configuration for the SR from a plurality of SR configurations configured for the first node.Furthermore, CPU 308 can execute program code 312 to perform some and / or all of the actions and steps described above and / or others described herein. In the context of the embodiment illustrated in FIG. 24 and discussed above, the SR can be activated when data for transmission is not available at the first node (and / or when no data is available for transmission at the first node). Alternatively and / or additionally, the SR can be activated in response to the reception of a second SR from the second node (and / or the SR can be activated based on the reception of the second SR from the second node). Alternatively and / or additionally, the second SR may be associated with a second SR configuration configured for the second node. Alternatively and / or additionally, the first node determines the first SR configuration based on the second SR configuration. Alternatively and / or additionally, the determination may be associated with a mapping (e.g., an implicit mapping). The first SR configuration may be determined by mapping the second SR configuration to the first SR configuration according to a first index of the first SR configuration and / or a second index of the second SR configuration. Alternatively and / or additionally, the determination may be associated with a mapping (e.g., an explicit mapping). The first SR configuration may be determined by mapping the second SR configuration to the first SR configuration according to a mapping table configured for the first node. Alternatively and / or additionally, the mapping table maps one or more first SR configurations of the second node to one or more second SR configurations of the first node. Alternatively and / or additionally, the determination may be associated with the use of a defined SR configuration, from the plurality of SR configurations, for the SR. Figure 25 is a flowchart 2500 according to an exemplary embodiment, from the perspective of a first node. In step 2505, the first node can activate a SR based on an expected transmission of the first data from a second node. In step 2510, the SR can be transmitted to a third node. In step 2515, in response to the transmission of the SR to the third node, the first node can start a timer associated with the SR. In step 2520, in response to the determination that a retransmission of the first data to the first node is required, the timer can be stopped. With reference again to Figures 3 and 4, in an exemplary embodiment of a first node, the device 300 includes program code 312 stored in memory 310. The CPU 308 can execute program code 312 (i) to activate a SR based on an expected transmission of first data from a second node, (ii) to transmit the SR to a third node, (iii) to start a timer associated with the SR in response to the transmission of the SR to the third node, and (iv) to stop the timer in response to the determination that a retransmission of the first data to the first node is required. Furthermore, the CPU 308 can execute program code 312 to perform some and / or all of the actions and steps described above and / or others described herein. In the context of the embodiment illustrated in Figure 25 and discussed above, the timer can be an SR prohibition timer.Alternatively and / or additionally, the second data may be transmitted to the third node after the SR is activated. Alternatively and / or additionally, the second data may be transmitted to the third node in response to the receipt of one or more transmission resources from the third node. Alternatively and / or additionally, the one or more transmission resources may be associated with the SR. Alternatively and / or additionally, the second data may not include the first data. Alternatively and / or additionally, the SR may be canceled in response to the transmission of the first data to the third node. Alternatively and / or additionally, the SR may be canceled in response to the transmission of a BSR to the third node, where the BSR is indicative of a buffer state of the second node. It can be seen that the application of one or more of the techniques presented in this document can result in one or more benefits that include, but are not limited to, a decrease in UL delay of a UE when the UE is connected to an IAB system that has multiple hops, and / or a decrease in UL delay of a UE when the UE is connected to an IAB system that has multiple hops, where UL transmission between nodes of the IAB system fails one or more times. A communication device (e.g., a UE, a base station, etc.) may be provided, wherein the communication device may comprise a control circuit, a processor installed in the control circuit, and / or memory installed in the control circuit and coupled to the processor. The processor may be configured to execute program code stored in memory to perform the steps of the procedure illustrated in FIG. 18, FIG. 19, FIG. 20, FIG. 21, FIG. 22, FIG. 23, FIG. 24, and / or FIG. 25. Furthermore, the processor may execute program code to carry out some and / or all of the actions and steps described above and / or others described herein. Several aspects of the description have been described above. It should be evident that the teachings of this invention can be realized in a wide variety of ways and that any specific structure, function, or both described herein are merely representative. Based on the teachings of this invention, a person skilled in the art should appreciate that one aspect described herein can be implemented independently of any other aspect and that two or more of these aspects can be combined in various ways. For example, an apparatus can be implemented or a procedure can be carried out using any number of the aspects set forth in this invention. Additionally, such an apparatus can be implemented or such a procedure can be carried out using another structure, function, or structure and function in addition to or another of one or more of the aspects set forth in this invention.As an example of some of the above concepts, in some aspects concurrent channels can be established based on pulse repetition frequencies. In some aspects, concurrent channels can be established based on pulse position or offsets. In some aspects, concurrent channels can be established based on time-jump sequences. In some aspects, concurrent channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time-jump sequences. Those knowledgeable in the field will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the preceding description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Experts will also appreciate that the various illustrative logic blocks, modules, processors, media, circuits, and algorithm stages described in relation to the aspects described in this invention can be implemented as electronic hardware (for example, a digital implementation, an analog implementation, or a combination of the two, which can be designed using source coding or some other technique), various forms of program code or design incorporating instructions (which may be referred to in this invention, for convenience, as "software" or "software module"), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and stages have been described above in general terms of their functionality.Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Experts may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as a departure from the scope of this description. Additionally, the various illustrative logic blocks, modules, and circuits described in relation to the aspects described in this invention may be implemented or realized by means of an integrated circuit (IC), an access terminal, or an access point. The IC may comprise a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described in this invention, and may execute code or instructions residing within the IC, outside the IC, or both.A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other such configuration. It is understood that any specific order or hierarchy of steps in any described process is an example of a sample strategy. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of this description. The attached procedure claims elements present in the various steps in a sample order and is not intended to be limited to the specific order or hierarchy presented. The steps of a procedure or algorithm described in relation to the aspects described in this invention can be performed directly in hardware, in a software module executed by a processor, or in a combination of both. A software module (for example, including executable instructions and related data) and other data can reside in a data memory such as RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium can be coupled to a machine such as a computer / processor (which may be referred to in this invention, for convenience, as a "processor") so that the processor can read information (for example, code) from it and write information to the storage medium.A sample storage medium may be part of the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in the user's computer. Alternatively, the processor and storage medium may reside as discrete components in the user's computer. Furthermore, in some respects, any suitable software product may comprise a computer-readable medium comprising codes related to one or more of the aspects of the description. In some respects, a software product may comprise packaging materials.

Claims

1. A procedure for a first node, comprising: activating (2405) a first scheduling request, hereinafter also referred to as SR, according to a first buffer state report, hereinafter also referred to as BSR, activated before the first node receives uplink data from the second node, wherein the second node is a child node of the first node, and wherein the first SR is activated to request one or more transmission resources for uplink transmission from the first node to a third node; and maintaining the first SR pending in response to the first node having an uplink grant that can accommodate all pending data available for transmission on the first node and / or a BSR comprising a more recent buffer state being transmitted, when uplink data is not yet available for transmission on the first node. 2.The method according to claim 1, wherein the uplink grant is for a transmission from the first node to a third node.

3. The method according to claim 1, wherein a configuration for the first SR is one of a plurality of SR configurations of the first node.

4. The method according to any of claims 1 to 3, further comprising: activating a second BSR in response to uplink data arriving at a buffer of the first node.

5. The method according to claim 4, further comprising: activating a second SR in response to the activation of the second BSR. 6.The method according to claim 4, further comprising: canceling the second BSR when one or more uplink leases can accommodate all pending data available for transmission and / or when one or more uplink leases are insufficient to accommodate a BSR Medium Access Control element with a subheader.

7. The method according to any of claims 5 to 6, further comprising: canceling the second SR when one or more UL leases can accommodate all pending data available for transmission.

8. The method according to claim 2, wherein the third node is a parent node of the first node. 9.A communication device, comprising: a processor (308); and a memory (310) comprising processor-executable instructions which, when executed by the processor (308), cause operations to be performed, the operations comprising the steps of the procedure according to any of the preceding claims.