Enhancements for periodic resources in integrated access and backhaul networks

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a wireless node may receive an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. The wireless node may communicate a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application Ser. No. 63 / 083,511, filed Sep. 25, 2020, entitled “PERIODIC RESOURCE COORDINATION IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK,” and U.S. patent application Ser. No. 63 / 083,513, filed Sep. 25, 2020, entitled “DOWNLINKCONF1GURED GRANT IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK,” and U.S. patent application Ser. No. 63 / 083,513, filed Sep. 25, 2020, entitled “PRIORITY FLAG SIGNALING FOR PERIODIC The present invention claims priority to U.S. patent application No. 63 / 198,052, entitled “PRIORITY FLAG SIGNALING FOR PERIODIC RESOURCES” and U.S. non-provisional patent application No. 17 / 447,021, filed on September 7, 2021, entitled “ENHANCHEMENTS FOR PERIODIC RESOURCES IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK,” which are hereby expressly incorporated herein by reference.

[0003] public domain

[0004] Aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques and apparatus for providing enhancements for periodic resources in integrated access and backhaul networks. Background Art

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment (UE) to communicate at the city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink (DL), using CP-OFDM or SC-FDMA (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to LTE and NR technologies. Preferably, these improvements are applicable to other multiple access technologies and telecommunication standards that adopt these technologies.

[0007] For periodic or deterministic low-latency traffic, such as time-sensitive communication (TSC) traffic, a wireless node may be required to meet strict latency requirements when forwarding or relaying traffic between a parent node and a child node of the wireless node. The wireless node may be an integrated access and backhaul (IAB) node that includes a mobile terminal (MT) component and a distributed unit (DU) component. For periodic traffic, one approach to meeting strict latency requirements is to allocate periodic resources in advance, such as via downlink semi-persistent scheduling (SPS) or uplink configured grants, so that a dynamic downlink control information (DCI) grant is not required for each data transmission of the periodic traffic. For downlink SPS and some uplink configured grant types, the allocation includes radio resource control (RRC) configuration of basic parameters, such as the periodicity or number of hybrid automatic repeat request (HARQ) processes. The RRC configuration may be transmitted by a central unit (CU) of the integrated access and backhaul (IAB) donor. The allocation may include an activation DCI grant with detailed allocation information (e.g., time and frequency resource allocation, modulation and coding scheme (MCS) or antenna port, etc.). The activation DCI grant may be transmitted by a scheduling node. The scheduling node may be a node that is scheduling communications, such as the CU of the IAB node, or another IAB node (e.g., a parent node).

[0008] In some cases, a DU component of a parent node of a wireless node (e.g., a scheduling node that is scheduling communications for the wireless node) may allocate periodic resources for TSC traffic to an MT component of the wireless node via activating a DCI grant. The DU component of the wireless node may allocate corresponding periodic resources to an MT component of a child node of the wireless node via activating a DCI grant. However, because the periodic resources associated with the MT component of the wireless node may be determined or allocated by the parent node of the wireless node, and the periodic resources associated with the DU component of the wireless node may be determined or allocated by the DU component of the wireless node, it may be difficult to ensure that the periodic resources associated with the MT component and the periodic resources associated with the DU component are configured such that strict latency requirements associated with forwarding or relaying TSC traffic are met (e.g., because the DU component may configure the periodic resources associated with the DU component before the MT component receives an allocation of the periodic resources associated with the MT component).

[0009] Overview

[0010] Some aspects described herein relate to a wireless node for wireless communication. The wireless node may include at least one processor and at least one memory communicatively coupled to the at least one processor and storing processor-readable code. The processor-readable code, when executed by the at least one processor, may be configured to cause the wireless node to receive an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters or a priority flag for coordinating periodic resources, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. The processor-readable code, when executed by the at least one processor, may be configured to cause the wireless node to communicate a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

[0011] Some aspects described herein relate to a method of wireless communication performed by a wireless node. The method may include receiving an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. The method may include communicating a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a wireless node. The set of instructions, when executed by one or more processors of the wireless node, may cause the wireless node to receive an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. The set of instructions, when executed by the one or more processors of the wireless node, may cause the wireless node to communicate a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a first periodic resource associated with a wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. The apparatus may include means for communicating a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, or processing systems substantially as described with reference to and as illustrated in the accompanying drawings and description.

[0015] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described hereinafter. The concepts and specific examples disclosed can be readily used as a basis for modifying or designing other structures for implementing the same purposes as the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, as well as the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures is provided for illustration and description purposes and is not intended to define limitations on the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to understand in detail the features of the present disclosure set forth above, a more particular description of the content briefly summarized above may be obtained with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only some typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 is a diagram illustrating an example base station (BS) and user equipment (UE) in communication in a wireless network according to the present disclosure.

[0020] Figure 3 is a diagram illustrating an example of a radio access network according to the present disclosure.

[0021] Figure 4is a diagram illustrating an example of an integrated access and backhaul (IAB) network architecture according to the present disclosure.

[0022] Figure 5 is a diagram illustrating an example of resource types in an IAB network according to the present disclosure.

[0023] Figure 6 is a diagram illustrating an example of latency due to resources in an IAB network according to the present disclosure.

[0024] Figure 7 is a diagram illustrating an example of latency due to resources in an IAB network according to the present disclosure.

[0025] Figure 8 is a diagram illustrating an example of periodic resource communication according to the present disclosure.

[0026] Figure 9 is a diagram illustrating an example associated with periodic resource coordination in an IAB network according to the present disclosure.

[0027] Figure 10 is a diagram illustrating an example associated with downlink semi-persistent scheduling (SPS) periodic resource coordination and uplink configuration grant (CG) periodic resource coordination in an IAB network according to the present disclosure.

[0028] Figures 11 to 15 is a diagram illustrating an example associated with priority flag signaling for periodic resources according to the present disclosure.

[0029] Figures 16 to 18 is a flow diagram illustrating an example process, eg, performed by a wireless node, in accordance with the present disclosure.

[0030] Figure 19 is a flow diagram illustrating an example process, eg, performed by a control node, according to the present disclosure.

[0031] Figure 20 is a flow diagram illustrating an example process, eg, performed by a wireless node, in accordance with the present disclosure.

[0032] Figure 21 is a flow diagram illustrating an example process, eg, performed by a control node, according to the present disclosure.

[0033] Figure 22 is a flow diagram illustrating an example process, such as performed by a parent node, according to the present disclosure.

[0034] Figure 23 is a flow diagram illustrating an example process, eg, performed by a wireless node, in accordance with the present disclosure.

[0035] Figures 24 to 29is a block diagram of an example device for wireless communications according to the present disclosure.

[0036] Detailed description

[0037] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and is not to be construed as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and they will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently of any other aspect of the present disclosure or implemented in combination. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using a supplement to the various aspects of the disclosure set forth herein or other other structures, functionality, or structure and functionality. Any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

[0038] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0039] Various aspects generally relate to enhancements for periodic resources in an integrated access and backhaul (IAB) network. Some aspects more specifically relate to periodic resource coordination in an IAB network. Some aspects more specifically relate to coordinating periodic resources of a mobile terminal (MT) component associated with an IAB node and periodic resources of a distributed unit (DU) associated with the IAB node. In some aspects, the IAB node may identify (e.g., determine or receive an indication of) one or more parameters for coordinating periodic resources of the MT component associated with the IAB node and periodic resources of the DU associated with the IAB node. For example, the one or more parameters may indicate a time gap or a time gap range between the periodic resources of the MT component associated with the IAB node and the periodic resources of the DU associated with the IAB node.

[0040] In some aspects, the IAB node may receive an activation message for activating a first periodic resource associated with an MT component of the IAB node. In some aspects, the IAB node may determine whether a second periodic resource corresponding to the first periodic resource and associated with a DU of the IAB node satisfies the one or more parameters. For example, the IAB node may be a relay node that forwards periodic communications between a parent node of the IAB node and a child node of the IAB node. In some examples, the first periodic resource may be a downlink periodic resource for receiving downlink communications from the parent node. In such examples, the second periodic resource may be a corresponding downlink periodic resource that is used to forward downlink communications received from the parent node using the first periodic resource to the child node. In some other examples, the first periodic resource may be an uplink periodic resource for transmitting uplink communications to the parent node. In such examples, the second periodic resource may be a corresponding uplink periodic resource that is used to receive uplink communications from the child node to be forwarded to the parent node using the first periodic resource.

[0041] If the IAB node determines that the second periodic resource does not satisfy the one or more parameters, the IAB node may modify the resource allocation associated with the second periodic resource. In some aspects, the IAB node may transmit an activation message associated with the second periodic resource to a child node associated with the IAB node, the activation message indicating the modified resource allocation associated with the second periodic resource. The IAB node may use the first periodic resource and the second periodic resource to communicate periodic communications (downlink communications or uplink communications). For example, the IAB node may use the first periodic resource to communicate (e.g., transmit or receive) communications via the MT component. The IAB node may use the second periodic resource to communicate (e.g., transmit or receive) communications via the DU (e.g., the second periodic resource may be modified by the DU as described in more detail elsewhere herein).

[0042] In some other aspects, a central unit (CU) of an IAB donor may configure downlink configured grants in the IAB network. In some examples, the CU of the IAB donor determines resource locations for downlink periodic resources in the IAB network. In some examples, the CU of the IAB donor may determine full grant information for downlink periodic resources in the IAB network so that IAB nodes within the IAB network can communicate using the downlink periodic resources without an activation message. In some other examples, the CU of the IAB donor may determine partial grant information for downlink periodic resources in the IAB network, including resource locations for the downlink periodic resources. In some such examples, if the CU of the IAB donor determines partial grant information, the remaining grant information (e.g., information required for the IAB node to communicate using the downlink periodic resources not indicated in the partial grant information) may be indicated in the activation message.

[0043] In some examples, the CU of the IAB donor may determine the resource location of the downlink periodic resource based at least in part on traffic patterns within the IAB network, duplex communication mode capabilities of IAB nodes within the communication path, IAB resource type patterns of IAB nodes within the communication path, average link quality across the communication path, processing capabilities of IAB nodes within the communication path, or latency requirements of IAB nodes within the communication path. In some examples, the CU of the IAB node may configure the resource location of the downlink periodic resource via a periodicity and an offset value associated with the downlink periodic resource.

[0044] In some other aspects, a priority flag can be assigned to a resource to indicate that the resource is available to the IAB node, regardless of the resource type associated with the resource. For example, assigning a priority flag to a resource can cause the resource to be used by the IAB node even when the resource corresponds to a resource type of Not Available (NA). In some examples, the resource can correspond to a downlink semi-persistent scheduling (SPS) opportunity or an uplink configured grant, and the resource can correspond to an NA resource type. In other words, the priority flag assigned to the resource can override the resource type associated with the resource.

[0045] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to coordinate periodic resources between a DU of an IAB node and a MT component of the IAB node for periodic low-latency traffic. Thus, resource allocation of periodic resources associated with the DU of the IAB node can be based at least in part on resource allocation of periodic resources associated with the MT component of a wireless node. As a result, the IAB node can forward traffic to the next-hop wireless node at the earliest possible time, thereby reducing latency associated with forwarding traffic.

[0046] In some examples, the described techniques may be used to optimize the resource location for downlink periodic resources for periodic low-latency traffic across multiple hops in an IAB network. For example, the CU of an IAB donor may utilize information available to the CU regarding the entire IAB network to coordinate the resource location for downlink periodic resources across a communication path for periodic low-latency traffic. As a result, the CU of an IAB donor may reduce the latency associated with conveying periodic low-latency traffic across a communication path that includes multiple hops or multiple wireless nodes. In addition, the CU of an IAB donor may optimize the downlink periodic resource pattern across multiple hops to reduce resource conflicts between multiple wireless nodes included in the communication path.

[0047] In some examples, the described techniques can be used to reduce latency associated with communications in an IAB network. For example, downlink SPS opportunities or uplink configured grants corresponding to the resource may not be canceled, in part because dynamic grants may not be configured for the communication (which would increase latency), which can allow communications involving IAB nodes to occur with reduced latency.

[0048] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network may be a 5G (NR) network or an LTE network, etc., or may include elements thereof. The wireless network may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, B node, gNB, 5G B node (NB), access point, or transmit reception point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0049] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. A BS may support one or more (e.g., three) cells.

[0050] A wireless network may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, or relay BSs. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, femto BS, and relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts). Figure 1 In the example shown in FIG, BS 110a may be a macro BS for macrocell 102a, BS 110b may be a pico BS for picocell 102b, and BS 110c may be a femto BS for femtocell 102c. A network controller 130 may be coupled to the set of BSs 102a, 102b, 110a, and 110b and may provide coordination and control for these BSs. The network controller 130 may communicate with each BS via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0051] In some aspects, the cells may not be stationary, but rather the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may interconnect with each other or with one or more other BSs or network nodes (not shown) in the wireless network via various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0052] The wireless network may also include relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or UE) and send transmissions of the data to a downstream station (e.g., a UE or BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1In the example shown in , relay BS 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, relay base station, relay, or the like.

[0053] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network, and each UE may be stationary or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, or stations, among others. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless medium.

[0054] Some UEs may be considered machine type communication (MTC) devices, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags, which can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as a processor component or a memory component.

[0055] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies or frequency channels. Frequencies may also be referred to as carriers. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0056] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly with each other using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), mesh networks, or a combination thereof. In such examples, UEs 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by base station 110.

[0057] Devices in a wireless network can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, or channels based on frequency or wavelength. For example, devices in a wireless network can communicate using an operating band having a first frequency range (FR1) that can span from 410 MHz to 7.125 GHz. As another example, devices in a wireless network can communicate using an operating band having a second frequency range (FR2) that can span from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the “sub-6 GHz band.” Similarly, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often referred to as the “millimeter wave” band. Therefore, unless otherwise specified, it should be understood that the term “sub-6 GHz” can broadly refer to frequencies less than 6 GHz, frequencies within FR1, mid-band frequencies (e.g., greater than 7.125 GHz), or a combination thereof. Similarly, unless otherwise specified, it should be understood that the term "millimeter wave" can broadly refer to frequencies within the EHF band, frequencies within FR2, mid-band frequencies (e.g., less than 24.25 GHz), or a combination thereof. The frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0058] Figure 2 is a diagram illustrating an example base station in communication with a UE in a wireless network according to the present disclosure. The base station may correspond to Figure 1 Similarly, the UE may correspond to the base station 110. Figure 1 UE 120.

[0059] Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general, T ≥ 1 and R ≥ 1. At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and control information (e.g., CQI requests, grants, or upper layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals and synchronization signals. A transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, as applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each MOD 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each MOD 232 may further process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from MODs 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0060] At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 or other base stations and may provide received signals to R demodulators (DEMODs) 254a through 254r, respectively. Each DEMOD 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each DEMOD 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R DEMODs 254a through 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination of one or more controllers and one or more processors. The channel processor may determine one or more of a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, or a CQI parameter, etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0061] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0062] Antennas, such as antennas 234a to 234t or antennas 252a to 252r, may include or be included within one or more antenna panels, antenna groups, sets of antenna elements, or antenna arrays. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, or antenna array may include a coplanar set of antenna elements or a non-coplanar set of antenna elements. An antenna panel, antenna group, set of antenna elements, or antenna array may include antenna elements within a single housing or antenna elements within multiple housings. An antenna panel, antenna group, set of antenna elements, or antenna array may include antenna elements coupled to one or more transmit or receive components, such as Figure 2 One or more antenna elements of one or more components).

[0063] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, or CQI) from a controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by MODs 254a through 254r (e.g., for discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) or orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM), and transmitted to the base station 110. In some aspects, the modulator and demodulator of the UE 120 (e.g., MOD / DEMOD 254) may be included in a modem of the UE 120. In some aspects, the UE 120 comprises a transceiver. The transceiver may include any combination of antenna(s) 252, a modulator 254, a demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0064] At base station 110, uplink signals from UE 120 and other UEs may be received by antenna 234, processed by DEMOD 232, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include a communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include a scheduler 246 to schedule UE 120 for downlink and uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in a modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, a modulator 232, a demodulator 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0065] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or Figure 2 Any other components of may perform one or more techniques associated with enhancements for periodic resources in an IAB network, as described in more detail elsewhere herein. For example, Figure 2 The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component may perform or direct the operation of, for example, the following processes: Figure 16 The process of 1600 Figure 17 The process of 1700 Figure 18 The process of 1800 Figure 19 The process of 1900, Figure 20 The process of 2000, Figure 21 Process 2100, Figure 22 The process of 2200 Figure 23 2300, or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, translation, or interpretation) by one or more processors of base station 110 or UE 120, may cause the one or more processors, UE 120, or base station 110 to perform or direct, for example, Figure 16 The process of 1600 Figure 17 The process of 1700 Figure 18 The process of 1800 Figure 19 The process of 1900, Figure 20 The process of 2000, Figure 21 Process 2100, Figure 22 The process of 2200 Figure 23 In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, or interpreting instructions.

[0066] In some aspects, a wireless node includes means for receiving an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. In some aspects, the wireless node includes means for communicating a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource. Means for the wireless node to perform the operations described herein may include, for example, a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, a scheduler 246, an antenna 252, a demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, or a memory 282.

[0067] Figure 3 3 is a diagram illustrating an example of a radio access network 300 according to the present disclosure. Figure 3 As shown in FIG, a radio access network 305 (e.g., a 3G network, a 4G network, or an LTE network) may include multiple base stations 310 (e.g., access nodes (ANs)), each of which communicates with a core network via a wired backhaul link 315 (such as a fiber optic connection). The base stations 310 may communicate with UEs 320 via access links 325 (which may be wireless links). In some aspects, Figure 3 The base station 310 shown in FIG. Figure 1 In some aspects, Figure 3 The UE 320 shown in FIG. 3 may be Figure 1 UE 120 is shown in FIG.

[0068] The radio access network 330 may include a wireless backhaul network, which is sometimes referred to as an IAB network. In an IAB network, at least one base station is an anchor base station 335, which communicates with the core network via a wired backhaul link 340 (such as a fiber optic connection). The anchor base station 335 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 345 (sometimes referred to as relay base stations or IAB nodes (or IAB-nodes)). The non-anchor base station 345 may communicate directly or indirectly with the anchor base station 335 via one or more backhaul links 350 (e.g., via one or more non-anchor base stations 345) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 350 may be a wireless link. The anchor base station(s) 335 or the non-anchor base station(s) 345 may communicate with one or more UEs 355 via an access link 360 (which may be a wireless link for carrying access traffic). In some aspects, Figure 3 The anchor base station 335 or the non-anchor base station 345 shown in FIG. Figure 1 In some aspects, Figure 3 The UE 355 shown in FIG. 3 may be Figure 1 UE 120 is shown in FIG.

[0069] In some aspects, the radio access network 365 including the IAB network may utilize millimeter wave technology or directional communication (e.g., beamforming) for communication between base stations or UEs (e.g., between two base stations, between two UEs, or between a base station and a UE). For example, the wireless backhaul link 370 between base stations may use millimeter wave signals to carry information or may be directed to a target base station using beamforming. Similarly, the wireless access link 375 between a UE and a base station may use millimeter wave signals or may be directed to a target wireless node (e.g., a UE or a base station). In this way, inter-link interference may be reduced.

[0070] Figure 3 The configuration of the base station and UE is shown as an example, and other examples are contemplated. For example, Figure 3 The one or more base stations illustrated in the figure may be replaced by one or more UEs communicating via a UE-to-UE access network (e.g., a peer-to-peer network or a device-to-device network). In such examples, an "anchor node" may refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).

[0071] Figure 4 4 is a diagram illustrating an example of an IAB network architecture 400 according to the present disclosure. Figure 4As shown in FIG, the IAB network may include an IAB donor 405 (shown as IAB-donor) connected to the core network via a wired connection (shown as wired backhaul). For example, the Ng interface of the IAB donor 405 may terminate at the core network. Additionally or alternatively, the IAB donor 405 may be connected to one or more devices of the core network that provide a core access and mobility management function (AMF).

[0072] In some aspects, the IAB donor 405 may include a base station 110, such as an anchor base station, as described above in conjunction with Figure 3 As described. As shown in the figure, the IAB donor 405 may include a CU, which may perform access node controller (ANC) functions or AMF functions, etc. The CU may configure the DU of the IAB donor 405, or may configure one or more IAB nodes 410 connected to the core network via the IAB donor 405 (e.g., MTs or DUs of the IAB nodes 410). Thus, the CU of the IAB donor 405 may control or configure the entire IAB network connected to the core network via the IAB donor 405, such as by using a control message or a configuration message (e.g., a radio resource control (RRC) configuration message or an F1 application protocol (F1-AP) message).

[0073] like Figure 4 As further shown in FIG, the IAB network may include IAB donors 410 (shown as IAB-node 1, IAB-node 2, and IAB-node 3) connected to the core network via IAB donor 405. As shown, the IAB nodes 410 may include MT functionality (sometimes also referred to as UE functionality (UEF)) and may include DU functionality (sometimes also referred to as access node functionality (ANF)). The MT functionality of an IAB node 410 (e.g., a child node) may be controlled or scheduled by another IAB node 410 (e.g., the parent node of the child node) or by the IAB donor 405. The DU functionality of an IAB node 410 (e.g., a parent node) may control or schedule other IAB nodes 410 (e.g., the child node of the parent node) or UE 120. Therefore, the DU may be referred to as a scheduling node or scheduling component, and the MT may be referred to as a scheduled node, scheduled component, or MT component. In some aspects, the IAB donor 405 may include DU functionality but not MT functionality. That is, the IAB donor 405 may configure, control, or schedule communications of the IAB node 410 or the UE 120. The UE 120 may include only MT functionality and not DU functionality. That is, communications of the UE 120 may be controlled or scheduled by the IAB donor 405 or the IAB node 410 (e.g., the parent node of the UE 120).

[0074] When a first node controls or schedules communications for a second node (e.g., when the first node provides DU functionality for the MT functionality of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU functionality of the parent node may control or schedule communications for the child node of the parent node. The parent node may be the IAB donor 405 or the IAB node 410, and the child node may be the IAB node 410 or the UE 120. Communications of the MT functionality of the child node may be controlled or scheduled by the parent node of the child node.

[0075] like Figure 4 As further shown in FIG, the link between UE 120 (e.g., which has only MT functionality and not DU functionality) and IAB donor 405, or between UE 120 and IAB node 410, may be referred to as an access link 415. Access link 415 may be a wireless access link that provides UE 120 with radio access to the core network via IAB donor 405 and, optionally, one or more IAB nodes 410. Thus, Figure 4 The network illustrated in may be referred to as a multi-hop network or a wireless multi-hop network.

[0076] like Figure 4 As further shown in FIG, the link between an IAB donor 405 and an IAB node 410, or between two IAB nodes 410, may be referred to as a backhaul link 420. The backhaul link 420 may be a wireless backhaul link that provides radio access to the core network to the IAB node 410 via the IAB donor 405 and, optionally, via one or more other IAB nodes 410. In an IAB network, network resources (e.g., time resources, frequency resources, or spatial resources, etc.) used for wireless communications may be shared between the access link 415 and the backhaul link 420. In some aspects, the backhaul link 420 may be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, the secondary backhaul link may be used if the primary backhaul link fails, becomes congested, becomes overloaded, or the like. For example, if the primary backhaul link between IAB node 2 and IAB node 1 fails, the backup link 425 between IAB node 2 and IAB node 3 may be used for backhaul communications. As used herein, a “node” or “wireless node” may refer to an IAB donor 405 or an IAB node 410 .

[0077] In some aspects, the IAB node 410 may be able to communicate in a half-duplex communication mode or a full-duplex communication mode. In the half-duplex communication mode, the IAB node 410 may be able to transmit or receive at a time. That is, the IAB node 410 may not be able to transmit and receive simultaneously when operating in the half-duplex communication mode. In some aspects, the half-duplex communication mode may require time division multiplexing (TDM). If the half-duplex communication mode requires TDM, the IAB node 410 may use the MT function of the IAB node 410 to communicate (e.g., transmit or receive) or may use the DU function of the IAB node to communicate. That is, the IAB node 410 may not be able to use the MT function of the IAB node 410 and the DU function of the IAB node 410 to communicate simultaneously. In some aspects, the half-duplex communication mode may include space division multiplexing (SDM) or frequency division multiplexing (FDM) for transmitting or receiving. If the half-duplex communication mode includes SDM or FDM for transmission, the IAB node 410 may be able to simultaneously transmit using the MT function of the IAB node 410 and transmit using the DU function of the IAB node 410. If the half-duplex communication mode includes SDM or FDM for reception, the IAB node 410 may be able to simultaneously receive using the MT function of the IAB node 410 and receive transmissions using the DU function of the IAB node 410.

[0078] In full-duplex communication mode, the IAB node 410 may be able to transmit and receive simultaneously. For example, the MT function and the DU function of the IAB node 410 may be able to transmit and receive simultaneously. The MT function of the IAB node 410 may be able to transmit communications to the parent node while the DU function of the IAB node 410 is receiving communications from the child node. Similarly, when operating in full-duplex communication mode, the MT function of the IAB node 410 may be able to receive communications from the parent node while the DU function of the IAB node 410 is transmitting communications to the child node. As used herein, the "duplex communication capability" or "duplex communication mode" of the IAB node 410 may refer to the above-mentioned half-duplex communication mode or full-duplex communication mode.

[0079] The access link 415 may include one or more access radio link control (RLC) channels. The access RLC channels may carry packet data convergence protocol (PDCP) communications (e.g., RRC communications or data radio bearer communications, etc.) from the MT function of the UE 120 or the IAB node 410 to the DU function of the IAB donor 405 or the IAB node 410.

[0080] Backhaul link 420 may include one or more backhaul RLC channels. The backhaul RLC channel may carry backhaul adaptation protocol (BAP) communications (e.g., backhaul for access traffic) from the MT function of IAB node 410 to the DU function of IAB donor 405 or IAB node 410 (e.g., the corresponding backhaul RLC channel may be between hops along the route from access IAB node 410 and the DU function of IAB donor 405). Accordingly, a radio bearer (e.g., a data radio bearer) for access traffic of the MT function of UE 120 or IAB node 410 may be mapped to a backhaul RLC channel, which may be an existing backhaul RLC channel or a backhaul RLC channel established for a radio bearer. As a result, different mappings between radio bearers and backhaul RLC channels may be used. For example, a particular backhaul RLC channel may be mapped to a single radio bearer or to multiple radio bearers, such as two radio bearers or three radio bearers.

[0081] In some approaches, an RLC channel may be associated with a Quality of Service (QoS) flow. For example, one or more QoS parameters associated with the QoS flow (such as a priority level, a permitted packet delay budget (PDB), or a permitted packet error rate, etc.) may be used to manage or schedule the RLC channel. In some aspects, an RLC channel may be associated with a Time Sensitive Communication (TSC) QoS flow. A TSC traffic pattern may be associated with periodic and deterministic traffic. For example, a TSC traffic pattern may be defined by periodicity and burst arrival times (e.g., the arrival time of a data burst at a parent node for downlink communication or the arrival time of a data burst at a child node for uplink communication).

[0082] A TSC QoS flow may be associated with low latency traffic or delay sensitive traffic. For example, a TSC QoS flow may be associated with a delay critical guaranteed bit rate (GBR) type QoS flow. The PDB may define an upper limit on the amount of time a packet may be delayed. The PDB for a delay critical GBR type QoS flow may include a 5G access network (5G-AN) PDB and a core network (CN) PDB. The PDB for a delay critical GBR type QoS flow may use a dynamic value of the CN PDB in order to obtain a more accurate PDB value that may be used for the 5G-AN.

[0083] Figure 5is a diagram illustrating an example of resource types 500 in an IAB network according to the present disclosure. In an IAB network, time domain resources (sometimes referred to as time resources) can be configured as downlink-only, uplink-only, flexible, or unavailable (e.g., unusable). When a time resource is configured as downlink-only for a wireless node, the time resource may only be available for downlink communications by the wireless node and not for uplink communications by the wireless node.

[0084] Similarly, when a time resource is configured as uplink-only for a wireless node, the time resource may only be used for uplink communications by the wireless node and not for downlink communications by the wireless node. When a time resource is configured as flexible for a wireless node, the time resource may be used for both downlink and uplink communications by the wireless node. When a time resource is configured as unavailable for a wireless node, the time resource cannot be used for any communications by the wireless node.

[0085] Examples of downlink communications include synchronization signal blocks (SSBs), channel state information reference signals (CSI-RSs), physical downlink control channel (PDCCH) communications, or physical downlink shared channel (PDSCH) communications, etc. Examples of uplink communications include physical random access channel (PRACH) communications, physical uplink control channel (PUCCH) communications, physical uplink shared channel (PUSCH) communications, or sounding reference signals (SRSs), etc.

[0086] In an IAB network, time resources configured as downlink-only, uplink-only, or flexible can be further configured as hard resources or soft resources. When a time resource is configured as a hard resource for a wireless node, the time resource is always available for communications by that wireless node. For example, a downlink-only hard time resource is always available for downlink-only communications by the wireless node, an uplink-only hard time resource is always available for uplink-only communications by the wireless node, and a flexible hard time resource is always available for both uplink and downlink communications by the wireless node.

[0087] When a time resource is configured as a soft resource for a wireless node, the availability of the time resource is controlled by the parent node of the wireless node. For example, the parent node may indicate (e.g., explicitly or implicitly) whether the soft time resource is available for communication by the wireless node. Thus, the soft time resource may be in one of two states: an available state (e.g., when the soft time resource is available for scheduling or communication by the wireless node) and an unavailable state (e.g., when the soft time resource is unavailable for scheduling and unavailable for communication by the wireless node).

[0088] For example, when the parent node of a wireless node indicates that only downlink soft time resources are available, the downlink-only soft time resources can only be used for downlink communications of the wireless node. Similarly, when the parent node of a wireless node indicates that only uplink soft time resources are available, the uplink-only soft time resources can only be used for uplink communications of the wireless node. When the parent node of a wireless node indicates that flexible soft time resources are available, the flexible soft time resources can only be used for uplink and downlink communications of the wireless node.

[0089] As an example, time resource 505 can be configured as a hard resource for a child node, and the parent node of the child node can be configured as unavailable. In such an example, the parent node cannot use the time resource to communicate, but the child node can schedule communications in the time resource or use the time resource to communicate. This configuration can reduce interference between the parent node and the child node, or can reduce scheduling conflicts between the parent node and the child node, etc.

[0090] As another example, time resource 510 may be configured as unavailable for a child node and as a hard resource, a soft resource, or unavailable for a parent node (e.g., depending on network configuration, network conditions, or the configuration of the parent node's parent node, etc.). In such an example, the child node cannot schedule communications in the time resource and cannot use the time resource to communicate.

[0091] As another example, time resource 515 can be configured as a soft resource for a child node and can be configured as a hard resource, a soft resource, or unavailable for a parent node (e.g., depending on network configuration, network conditions, or the configuration of the parent node of the parent node, etc.). In such examples, a child node cannot use the time resource to schedule or communicate unless the child node (e.g., explicitly or implicitly) receives an indication (e.g., a release indication) from the parent node that the time resource is available for use by the child node (in other words, released). If the child node receives such an indication, the child node can schedule communications in the time resource or use the time resource to communicate.

[0092] Figure 6 6 is a diagram illustrating an example of latency due to resources in the IAB network 600 according to the present disclosure. Figure 7As shown, an IAB node can receive data in the downlink (e.g., from an IAB donor or parent node) and forward the data in the downlink (e.g., to a child node). An IAB node can receive data in the uplink (e.g., from a child node) and forward the data in the uplink (e.g., to an IAB donor or parent node). Depending on the DU resource type, the IAB node may experience latency in the downlink or uplink. The DU resource type can be an NA (Not Available) resource type, a soft resource type associated with an explicit indication or implicit determination, or a hard resource type.

[0093] For NA resource types, waiting time may result at the IAB node from the IAB node DU skipping the NA resources. For soft resource types associated with explicit indication, coordination waiting time may be incurred at the IAB node depending on the PDCCH resource allocation used for downlink control information (DCI). For soft resource types associated with implicit determination, waiting time may be incurred at the IAB node because the use of the resource is blocked by the parent node with allocation for the IAB node MT. For soft resource types associated with implicit determination, waiting time may be incurred at the IAB node because the IAB node DU cannot perform implicit determination (such as determination of PDCCH configuration or minimum scheduling gap). For example, the IAB node may not be able to perform implicit determination of overlapping soft resources within the PDCCH decoding time (for example, when the PDCCH opportunity overlaps with the soft resources). For hard resource types, waiting time may be incurred at the IAB node MT when the co-located IAB node DU uses hard resources.

[0094] Figure 7 7 is a diagram illustrating an example of latency due to resources in the IAB network 700 according to the present disclosure. Figure 7As shown, the parent node can transmit an activation DCI to the IAB node. The parent node can be the parent node of the IAB node. The activation DCI can configure an SPS opportunity for the parent node, wherein the DU resource type corresponding to the SPS opportunity can be a hard resource type. The IAB node can transmit an activation DCI to the child node. The child node can be the child node of the IAB node. However, since the DU resource type corresponding to the SPS opportunity is an NA resource type, the activation DCI transmitted by the IAB node may cause the IAB node to configure an SPS opportunity that has been canceled. As a result, the canceled SPS opportunity may not be used by the IAB node to transmit data to the child node. The IAB node can configure dynamic grants to transmit the data to the child node. However, compared to the situation where the IAB node can use the SPS opportunity to transmit data to the child node, using dynamic grants to transmit data can result in additional waiting time. In other words, if the SPS opportunity is not canceled, the IAB can transmit data to the child node with reduced waiting time because the IAB node will not have to configure dynamic grants.

[0095] like Figure 7 As further shown in , since the DU resource type corresponding to the SPS opportunity is the NA resource type, the SPS opportunity for the parent node may become cancelled. Due to the cancelled SPS opportunity for the parent node, the parent node may not be able to transmit data to the IAB node. The IAB node can transmit a negative acknowledgment (NACK) to the parent node, and the parent node can configure a dynamic grant to transmit data to the IAB node based at least in part on receiving the NACK. However, because the parent node cannot transmit the data to the IAB due to the cancelled SPS opportunity, the SPS opportunity for the IAB node may also be cancelled, even if the DU resource type corresponding to the SPS opportunity is a hard resource type. Due to the cancelled SPS opportunity for the IAB node, the IAB node may not be able to transmit data to the child node. The child node can transmit a NACK to the IAB node, and the IAB node can configure a dynamic grant to transmit data to the child node based at least in part on receiving the NACK. However, using dynamic grants to transmit data may result in additional waiting time compared to the situation where the IAB node can use the SPS opportunity to transmit data to the child node.

[0096] Figure 8800 is a diagram illustrating an example of periodic resource communication 800 according to the present disclosure. As shown, periodic resource communication 800 includes a parent node 805 (e.g., a DU of an IAB node), a child node 810 (e.g., an MT component or UE of an IAB node), and a control node 815 (e.g., a CU of an IAB donor). In some aspects, periodic resource communication 800 may include downlink SPS resources (e.g., for downlink communication from a parent node 805 or another wireless node to a child node 810) or uplink configured grant (CG) resources (e.g., for uplink communication from a child node 810 to a parent node 805 or to another wireless node). Therefore, as used herein, "periodic resources" may refer to downlink SPS resources or uplink CG resources.

[0097] like Figure 8 As shown, in a first operation 820, the control node 815 may transmit a periodic resource configuration to the parent node 805 and the child node 810. For example, the control node 815 may transmit configuration information identifying the periodic resource configuration (e.g., in an RRC message). In some aspects, the configuration information identifying the periodic resource configuration may indicate a periodicity associated with the periodic resource or hybrid automatic repeat request (HARQ) feedback information associated with the periodic resource (e.g., the number of HARQ processes), etc.

[0098] In a second operation 825, the parent node 805 may transmit an activation message associated with the periodic resource configuration. For example, the second operation 825 may include the parent node 805 transmitting a DCI activation grant that activates the periodic resource. In some aspects, the DCI activation grant may indicate a resource allocation associated with the periodic resource (e.g., in the time domain, frequency domain, spatial domain, or code domain), an MCS associated with the periodic resource, an antenna port associated with the periodic resource, or a redundancy version (RV) mode or configuration associated with the periodic resource, among other things. In some aspects, the DCI activation grant may indicate a resource or resource set that the child node 810 may use for transmission of uplink communications (e.g., when the periodic resource is an uplink CG periodic resource). In some aspects, the DCI activation grant may indicate a resource or resource set that the child node 810 may use for reception of downlink communications (e.g., when the periodic resource is a downlink SPS periodic resource).

[0099] In some aspects, the parent node 805 may use a configured scheduling radio network temporary identifier (CS-RNTI) to scramble the DCI activation grant. Figure 8 As shown, the first operation 820 and the second operation 825 may be performed by separate devices. For example, the control node 815 may perform the first operation 820 and the parent node 805 may perform the second operation 825.

[0100] In some aspects, the periodic resource configuration may be a downlink SPS configuration, which configures periodic downlink resources for the child node 810 to receive downlink communications. In some aspects, the periodic resource configuration may be an uplink CG configuration, which configures uplink periodic resources for the child node 810 to transmit uplink communications. In some aspects, the uplink CG configuration (e.g., without an accompanying DCI activation grant) may be configured using only an RRC configuration. For example, the periodic resource configuration for the uplink CG configuration transmitted by the control node 815 in the first operation 820 may indicate resource allocation associated with the uplink periodic resource (e.g., in the time domain, frequency domain, spatial domain, or code domain), an MCS associated with the uplink periodic resource, an antenna port associated with the periodic resource, or an RV pattern or configuration associated with the uplink periodic resource, etc. As a result, the child node 810 may be enabled to transmit uplink communications using periodic uplink resources without receiving a DCI activation grant associated with the periodic uplink resource. An uplink CG configuration that is fully configured by RRC configuration may be referred to herein as a Type 1 uplink CG. An uplink CG configuration that is partially configured by RRC configuration and activated by a DCI activation grant may be referred to herein as a Type 2 uplink CG.

[0101] In a third operation 830, the parent node 805 and the child node 810 may communicate using the periodic resource. For example, if the periodic resource is a downlink SPS periodic resource, the third operation 830 may include the parent node 805 transmitting downlink communications to the child node 810 using the downlink periodic resource. If the periodic resource is an uplink CG periodic resource, the third operation 830 may include the child node 810 transmitting uplink communications to the parent node 805 using the uplink CG periodic resource.

[0102] Configuring periodic resources in a manner similar to that described above can be beneficial for periodic or deterministic traffic. For example, the parent node 805 can allocate or activate periodic resources aligned with the periodic pattern of the traffic to reduce the signaling overhead associated with allocating resources for the traffic. In some aspects, such as in an IAB network, periodic or deterministic traffic can occur across multiple hops. For example, for downlink communication, periodic traffic can be transmitted from a first IAB node to a second IAB node (e.g., a child node of the first IAB node). The second IAB node can relay or forward the traffic to another wireless node (e.g., a child node of the second IAB node). Similarly, for uplink communication, periodic traffic can be transmitted from a wireless node (e.g., an MT component of a UE or IAB node) to a first IAB node (e.g., a parent node of a wireless node). The first IAB node can relay or forward the traffic to a second IAB node (e.g., a parent node of the first IAB node). A parent node or control node (eg, a CU of an IAB donor or a DU of an IAB node) may configure periodic resources for one or more other wireless nodes for communicating periodic or deterministic traffic over multiple hops.

[0103] For periodic or deterministic low-latency traffic (such as TSC traffic), a wireless node may be required to meet strict latency requirements when forwarding or relaying traffic between a parent node of the wireless node and a child node of the wireless node. For periodic traffic, one approach may be to allocate periodic resources in advance, such as via a downlink SPS or uplink CG, so that a dynamic downlink DCI grant may not be required for each data transmission of the periodic traffic. For downlink SPS and some uplink configured grant types, the allocation includes the RRC configuration of basic parameters (such as the periodicity and number of HARQ processes) by the IAB donor's CU and an activation DCI grant with detailed allocation information (e.g., time and frequency resource allocation, MCS, or antenna ports, etc.) by the scheduling node.

[0104] The wireless node may be an IAB node including an MT component and a DU component. In some cases, the DU component of the parent node (e.g., a scheduling node) of the wireless node may allocate periodic resources for TSC traffic to the MT component of the wireless node via activating a DCI grant. The DU component of the wireless node may allocate corresponding periodic resources to the MT component of the child node of the wireless node via activating a DCI grant. However, since the periodic resources associated with the MT component of the wireless node may be determined or allocated by the parent node of the wireless node, and the periodic resources associated with the DU of the wireless node may be determined or allocated by the DU of the wireless node, it may be difficult to ensure that the periodic resources associated with the MT component and the periodic resources associated with the DU are configured so as to meet the strict latency requirements associated with forwarding or relaying TSC traffic.

[0105] In some cases, low-latency traffic can be transmitted from the originating IAB node to the first IAB node, to the second IAB node, and to the destination node (such as a child node or UE), wherein the first IAB node and the second IAB node act as relay nodes that forward the low-latency traffic to the next hop in the communication path. However, as described above, for downlink SPS resources, the resource location of the downlink periodic resources can be determined and indicated by the parent node. For example, the resource location of the downlink periodic resources used by the first IAB node can be determined and indicated by the originating IAB node (e.g., in an activation message). Similarly, the resource location of the downlink periodic resources used by the second IAB node can be determined and indicated by the first IAB node (e.g., in an activation message).

[0106] However, an IAB node (e.g., an originating IAB node, a first IAB node, a second IAB node, or a destination node) in the communication path for low-latency traffic may not be aware of information associated with the entire IAB network, such as the traffic arrival pattern across multiple IAB nodes, the duplex communication capabilities (e.g., half-duplex or full-duplex) of each IAB node in the IAB network, or the average link quality of each IAB node in the IAB network. Consequently, the IAB nodes in the communication path may not be able to coordinate the resource locations of downlink periodic resources across multiple hops for low-latency traffic. As a result, the resource locations of the downlink periodic resources for periodic low-latency traffic across multiple hops may increase the latency associated with communicating the periodic low-latency traffic across multiple hops. Furthermore, since each IAB node in the communication path may not be aware of the resource locations of other IAB nodes in the communication path, conflicts may exist between the downlink periodic resources in the communication path.

[0107] Various aspects generally relate to periodic resource coordination in an IAB network. Some aspects more specifically relate to coordinating periodic resources of a mobile operator component associated with an IAB node and periodic resources of a user unit associated with the IAB node. In some aspects, the IAB node may identify (e.g., determine or receive an indication of) one or more parameters for coordinating periodic resources of the mobile operator component associated with the IAB node and periodic resources of the user unit associated with the IAB node. For example, the one or more parameters may indicate a time gap or a range of time gaps between the periodic resources of the mobile operator component associated with the IAB node and the periodic resources of the user unit associated with the IAB node.

[0108] In some aspects, the IAB node may receive an activation message for activating a first periodic resource associated with an MT component of the IAB node. In some aspects, the IAB node may determine whether a second periodic resource corresponding to the first periodic resource and associated with a DU of the IAB node satisfies the one or more parameters. For example, the IAB node may be a relay node that forwards periodic communications between a parent node of the IAB node and a child node of the IAB node. In some aspects, the first periodic resource may be a downlink periodic resource for receiving downlink communications from the parent node. The second periodic resource may be a corresponding downlink periodic resource used to forward downlink communications received from the parent node using the first periodic resource to the child node. In some aspects, the first periodic resource may be an uplink periodic resource for transmitting uplink communications to the parent node. The second periodic resource may be a corresponding uplink periodic resource used to receive uplink communications from the child node to be forwarded to the parent node using the first periodic resource.

[0109] If the IAB node determines that the second periodic resource does not satisfy the one or more parameters, the IAB node may modify the resource allocation associated with the second periodic resource. In some aspects, the IAB node may transmit an activation message associated with the second periodic resource to a child node associated with the IAB node, the activation message indicating the modified resource allocation associated with the second periodic resource. The IAB node may communicate periodic communications (downlink communications or uplink communications) using the first periodic resource and the second periodic resource.

[0110] Some other aspects generally relate to a CU of an IAB donor configuring downlink configured grants in an IAB network. In some aspects, the CU of the IAB donor determines a resource location for downlink periodic resources in the IAB network. In some aspects, the CU of the IAB donor may determine full grant information for downlink periodic resources in the IAB network so that IAB nodes within the IAB network can communicate using the downlink periodic resources without an activation message. In some examples, the CU of the IAB donor may determine partial grant information for downlink periodic resources in the IAB network, including the resource location of the downlink periodic resources. In some examples, if the CU of the IAB donor determines partial grant information, the remaining grant information (e.g., information required for the IAB node to communicate using the downlink periodic resources not indicated in the partial grant information) may be indicated in the activation message.

[0111] In some aspects, the CU of the IAB donor may determine the resource location of the downlink periodic resource based at least in part on traffic patterns within the IAB network, duplex communication mode capabilities of IAB nodes within the communication path, IAB resource type patterns of IAB nodes within the communication path, average link quality across the communication path, processing capabilities of IAB nodes within the communication path, or latency requirements of IAB nodes within the communication path. In some aspects, the CU of the IAB node may configure the resource location of the downlink periodic resource via a periodicity and an offset value associated with the downlink periodic resource.

[0112] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to coordinate periodic resources between a DU of an IAB node and a MT component of the IAB node for periodic low-latency traffic. Thus, resource allocation of periodic resources associated with the DU of the IAB node can be based at least in part on resource allocation of periodic resources associated with the MT component of a wireless node. As a result, the IAB node can forward traffic to the next-hop wireless node at the earliest possible time, thereby reducing latency associated with forwarding traffic.

[0113] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to optimize resource locations for downlink periodic resources for periodic low-latency traffic across multiple hops in an IAB network. For example, the CU of an IAB donor may utilize information available to the CU regarding the entire IAB network to coordinate resource locations for downlink periodic resources across communication paths for periodic low-latency traffic. As a result, the CU of the IAB donor may reduce the latency associated with conveying periodic low-latency traffic across a communication path that includes multiple hops or multiple wireless nodes. In addition, the CU of the IAB donor may optimize the downlink periodic resource pattern across multiple hops to reduce resource conflicts between multiple wireless nodes included in the communication path.

[0114] Figure 9 9 is a diagram illustrating an example associated with periodic resource coordination 900 in an IAB network according to the present disclosure. Figure 9 As shown, the wireless node 905 (e.g., an IAB node) can communicate with a parent node 910 (e.g., a parent node of the wireless node 905, or a DU of the IAB node) and a child node 915 (e.g., an MT component of the IAB node or a UE). The wireless node 905 can communicate with the parent node 910 in accordance with the above. Figure 4The IAB node 410 described includes MT components and DU in a similar manner. In some aspects, the wireless node 905 can communicate with the CU of the IAB donor ( Figure 9 ). In some aspects, the wireless node 905 may perform functions similar to a layer 2 relay node.

[0115] In a first operation 920, the wireless node 905 may receive an activation message for activating a first periodic resource associated with an MT component of the wireless node 905. The first operation 920 may include a parent node transmitting the activation message to the wireless node 905. In some aspects, the activation message may activate the first periodic resource configured at least in part by an RRC configuration. In some aspects, the wireless node 905 may receive the RRC configuration from a CU of an IAB donor. In some aspects, the wireless node 905 may receive the RRC configuration from the CU of the IAB donor and may receive the activation message from the parent node 910.

[0116] In some aspects, the activation message may be a DCI activation grant (e.g., similar to the one described above in conjunction with Figure 8 For example, the activation message may indicate a resource allocation associated with the first periodic resource (such as in the time domain, frequency domain, spatial domain, or code domain), an MCS associated with the first periodic resource, an antenna port associated with the first periodic resource, or an RV mode or configuration associated with the first periodic resource, etc.

[0117] In some aspects, the activation message may be associated with a scheduling gap that indicates an amount of time between the activation message and the first periodic resource. The amount of time between the activation message and the first periodic resource may be based at least in part on a processing capability or processing time associated with the wireless node 905 (e.g., a processing capability or processing time associated with the wireless node 905 modifying a periodic resource corresponding to the first periodic resource and associated with the DU, as described herein). In some aspects, the wireless node 905 may receive an indication of the scheduling gap associated with the activation message from the CU of the IAB donor, such as via an RRC message or an F1-AP message. In some aspects, the wireless node 905 may receive an indication of the scheduling gap associated with the activation message from the parent node 910, such as via a medium access control (MAC) control element (MAC-CE) message or a DCI message.

[0118] In some aspects, the first periodic resource associated with the MT component of the wireless node 905 may be a downlink SPS periodic resource to be used to receive downlink communications from the parent node 910. In some aspects, the first periodic resource associated with the MT component of the wireless node 905 may be an uplink CG periodic resource (e.g., a type 2 uplink CG) to be used to transmit uplink communications to the parent node 910. In some aspects, the first periodic resource may be associated with an RLC channel between the parent node 910 and the wireless node 905, the RLC channel being associated with low-latency traffic (e.g., TSC traffic).

[0119] In a second operation 925, the wireless node 905 may identify one or more parameters for coordinating periodic resources associated with the MT component of the wireless node 905 and periodic resources associated with the DU of the wireless node 905. In some aspects, the second operation 925 may be performed by the DU of the wireless node 905. The one or more parameters may include a time gap between the periodic resources associated with the MT component and the periodic resources associated with the DU. In some aspects, the one or more parameters may include a time gap range between the periodic resources associated with the MT component and the periodic resources associated with the DU.

[0120] In some aspects, the time gap or range of time gaps between the periodic resources associated with the MT component and the periodic resources associated with the DU can be based at least in part on the processing capabilities of the wireless node. For example, the amount of time indicated by the time gap can be based at least in part on the amount of time required for the wireless node 905 to process communications (e.g., communications received by the MT component of the wireless node 905).

[0121] In some aspects, the time slot range may span from a first time slot to a second time slot. The amount of time indicated by the first time slot may be based at least in part on the amount of time required for the wireless node 905 to process a communication for forwarding to the next hop (such as a child node 915). For example, the amount of time required for the wireless node 905 to process a communication for forwarding to the next hop may include the amount of time associated with decoding the communication, performing layer 2 processing of the communication, and re-encoding the communication. The amount of time indicated by the second time slot may be based at least in part on a PDB associated with traffic carried using the periodic resources of the wireless node 905. In some aspects, the PDB may be a PDB for a single hop (e.g., a PDB for communication between a parent node 910 and the wireless node 905, or a PDB for communication between a wireless node 905 and a child node 915). In some aspects, the PDB may be an end-to-end PDB (e.g., a PDB associated with a multi-hop communication from an originating device (such as a parent node 910) to a destination device (such as a child node 915).

[0122] In some aspects, the second operation 925 may include the CU of the IAB donor transmitting an indication of the one or more parameters, and the wireless node 905 receiving the indication of the one or more parameters. For example, the CU of the IAB donor may determine the one or more parameters. In some aspects, the CU of the IAB donor may transmit the indication of the one or more parameters via an RRC message, an F1-AP message, or the like. In some aspects, if the CU of the IAB donor determines the one or more parameters, the CU of the IAB donor may transmit the indication of the one or more parameters to the parent node 910. As a result, the parent node 910 may be enabled to determine a set of resources that the DU of the wireless node 905 may use for low-latency communication, as described herein. In some aspects, the parent node 910 may not use the set of resources to schedule the MT component of the wireless node 905 to avoid potential conflicts with communications of the DU. As a result, the scheduling decisions made by the parent node 910 for the MT component of the wireless node 905 may be improved.

[0123] In some aspects, the second operation 925 may include the parent node 910 transmitting an indication of the one or more parameters, and the wireless node 905 receiving the indication of the one or more parameters. For example, the parent node 910 may determine the one or more parameters. In some aspects, a DU of the parent node 910 may transmit the indication of the one or more parameters. In some aspects, the parent node 910 may transmit the indication of the one or more parameters via a DCI message, a MAC-CE message, or the like. In some aspects, the parent node 910 may indicate the one or more parameters in the activation message transmitted in the first operation 920.

[0124] In some aspects, where the CU or parent node 910 of the IAB donor determines the one or more parameters, the wireless node 905 may transmit an indication of information to be used to determine the one or more parameters to the CU or parent node 910 of the IAB donor. For example, the wireless node 905 may transmit an indication of the processing capability of the wireless node (e.g., PDSCH processing capability or PUSCH processing capability), a latency requirement associated with the wireless node (e.g., a latency requirement associated with the amount of time from receiving a communication to forwarding the communication by the wireless node 905), or a PDB of an RLC channel associated with periodic resources of the wireless node 905, etc. The CU or parent node 910 of the IAB donor may determine the one or more parameters based at least in part on the information indicated by the wireless node 905.

[0125] In some aspects, the second operation 925 may include the wireless node 905 determining the one or more parameters (e.g., without receiving an indication of the one or more parameters from another wireless communication device). For example, the wireless node 905 may autonomously determine the one or more parameters. In some aspects, the wireless node 905 may determine the one or more parameters based at least in part on a processing capability of the wireless node (e.g., a PDSCH processing capability or a PUSCH processing capability), a latency requirement associated with the wireless node, or a PDB of an RLC channel associated with a periodic resource of the wireless node 905, etc.

[0126] In some aspects, where the wireless node 905 determines the one or more parameters, the wireless node 905 may transmit, and the parent node 910 may receive, an indication of the one or more parameters. The wireless node 905 may transmit the indication of the one or more parameters via a MAC-CE message or an uplink control information (UCI) message, etc. The parent node 910 may use the one or more parameters to make improved scheduling decisions for the MT component of the wireless node 905, as described above.

[0127] In a third operation 930, the wireless node 905 may determine whether a second periodic resource corresponding to the first periodic resource and associated with a DU of the wireless node 905 satisfies the one or more parameters. In some aspects, the third operation 930 may be performed by the DU of the wireless node 905. For example, the DU of the wireless node 905 may identify the second periodic resource corresponding to the first periodic resource. For example, if the first periodic resource is a downlink SPS resource, the second periodic resource may be a downlink SPS resource used by the DU of the wireless node 905 to forward downlink communications received from the parent node 910 to the child node 915. If the first periodic resource is an uplink CG resource, the second periodic resource may be an uplink CG resource used by the DU of the wireless node 905 to forward uplink communications received from the child node 915 to the parent node 910.

[0128] The wireless node 905 may determine whether the second periodic resource satisfies the one or more parameters based at least in part on a resource allocation associated with the second periodic resource. For example, as described above, the one or more parameters may indicate a time gap or time gap range between the periodic resource associated with the MT component and the periodic resource associated with the DU. The wireless node 905 may determine whether the resource allocation associated with the second periodic resource satisfies the time gap or time gap range in the time domain.

[0129] For example, the one or more parameters may indicate an amount of time permitted between a periodic resource associated with the MT component and a periodic resource associated with the DU. If the second periodic resource is scheduled to occur in the time domain more than the amount of time permitted from the first periodic resource, the wireless node 905 may determine that the one or more parameters are not satisfied. Similarly, the one or more parameters may indicate a range of time permitted between the periodic resource associated with the MT component and the periodic resource associated with the DU (e.g., from a first amount of time to a second amount of time). If the second periodic resource is scheduled to occur in the time domain outside of a time range from the first periodic resource (e.g., not between the first amount of time and the second amount of time), the wireless node 905 may determine that the one or more parameters are not satisfied.

[0130] In a fourth operation 935, the wireless node 905 may modify a resource allocation of a second periodic resource associated with the DU of the wireless node 905 based at least in part on determining that the second periodic resource does not satisfy at least one of the one or more parameters. For example, the wireless node 905 may modify a time domain resource allocation of the second periodic resource such that the modified time domain resource allocation satisfies the one or more parameters. In some aspects, the wireless node 905 may modify the time domain resource allocation of the second periodic resource such that the modified time domain resource allocation begins at an amount of time from the first periodic resource indicated by the one or more parameters (e.g., before the first periodic resource for uplink CG resources or after the first periodic resource for downlink SPS resources). In some aspects, the wireless node 905 may modify the time domain resource allocation of the second periodic resource such that the modified time domain resource allocation occurs within a time range from the first periodic resource indicated by the one or more parameters.

[0131] In some aspects, the wireless node 905 may perform the fourth operation 935 during a scheduling gap associated with the activation message received from the parent node 910 during the first operation 920. For example, the wireless node may perform the fourth operation 935 during an amount of time between receiving the activation message and starting a time-domain resource allocation associated with the first periodic resource. In some aspects, if the wireless node 905 determines that the second periodic resource satisfies the one or more parameters, the wireless node 905 may not perform the fourth operation 935. For example, if the wireless node 905 determines that the second periodic resource satisfies the one or more parameters, the wireless node 905 may not modify the resource allocation of the second periodic resource.

[0132] In a fifth operation 940, the wireless node 905 may transmit and the child node 915 may receive an activation message indicating a modified resource allocation associated with the second periodic resource. The fifth operation 940 may be performed by the DU of the wireless node 905. The activation message may be a DCI activation grant (e.g., similar to the one described above in conjunction with Figure 8 For example, the activation message may indicate a modified resource allocation associated with the second periodic resource (such as in the time domain, frequency domain, spatial domain, or code domain), an MCS associated with the second periodic resource, an antenna port of the child node 915 associated with the second periodic resource, or an RV mode or configuration associated with the second periodic resource, etc.

[0133] In some aspects, if the wireless node 905 determines that the second periodic resource satisfies the one or more parameters, the wireless node 905 may not perform the fifth operation 940. For example, if the wireless node 905 determines that the second periodic resource satisfies the one or more parameters, the wireless node 905 may not transmit an activation message associated with the second periodic resource. For example, the wireless node 905 may have previously transmitted an activation message to activate the second periodic resource. Thus, the child node 915 may be enabled to utilize the second periodic resource based at least in part on the previously transmitted activation message.

[0134] In some aspects, if the wireless node 905 determines that the second periodic resource satisfies the one or more parameters, the activation message may indicate the original resource allocation associated with the second periodic resource (e.g., unmodified). For example, if the wireless node 905 determines that the second periodic resource satisfies the one or more parameters, the wireless node 905 may not perform the fourth operation 935, but the wireless node 905 may perform the fifth operation 940 by transmitting an activation message indicating the original resource allocation associated with the second periodic resource.

[0135] In a sixth operation 945, the parent node 910 and the wireless node 905 may communicate using first periodic resources associated with the MT component of the wireless node 905. In a seventh operation 950, the wireless node 905 and the child node 915 may communicate using second periodic resources associated with the DU of the wireless node 905.

[0136] For example, if the first periodic resource and the second periodic resource are downlink SPS resources, the sixth operation 945 may include the parent node 910 transmitting downlink communications using the first periodic resource and the wireless node 905 receiving downlink communications using the first periodic resource. The seventh operation 950 may include the wireless node 905 forwarding (e.g., transmitting) the downlink communications to the child node 915 using the second periodic resource.

[0137] If the first periodic resource and the second periodic resource are uplink CG resources, the seventh operation 950 may include the child node 915 transmitting the uplink communication using the second periodic resource, and the wireless node 905 receiving the uplink communication using the second periodic resource. The sixth operation 945 may include the wireless node 905 forwarding (e.g., transmitting) the uplink communication to the parent node 910 using the first periodic resource.

[0138] Figure 10 1 is a diagram illustrating an example associated with downlink SPS periodic resource coordination 1000 and uplink CG periodic resource coordination 1005 in an IAB network according to the present disclosure. Figure 10 As shown, the IAB node 1010 (e.g., wireless node 905) can communicate with a parent node 1015 (e.g., a parent node of the IAB node 1010, or a DU of the IAB node, or the parent node 910) and a child node 1020 (e.g., an MT component of the IAB node, a UE, or a child node 915). The IAB node 1010 can communicate with the parent node 1015 in accordance with the above description. Figure 4 The IAB node 410 described above includes MT components and DUs in a similar manner. In some aspects, the IAB node 1010 can be connected to the CU ( Figure 10 In some aspects, IAB node 1010 may perform functions similar to those of a layer 2 relay node.

[0139] As shown in the example associated with downlink SPS periodic resource coordination 1000, the IAB node 1010 may receive an activation message 1025 from the parent node 1015. The activation message 1025 may activate downlink SPS resources 1035 associated with the MT component of the IAB node 1010. For example, the activation message 1025 may indicate a resource allocation associated with the downlink SPS resources 1035.

[0140] As above combined Figure 9 As described, the IAB node 1010 may identify (e.g., determine or receive an indication of) one or more parameters for coordinating the periodic resources of the MT component associated with the IAB node 1010 and the periodic resources of the DU associated with the IAB node 1010. The one or more parameters for coordinating the periodic resources of the MT component associated with the IAB node 1010 and the periodic resources of the DU associated with the IAB node 1010 may be combined as described above. Figure 9 are identified as described.

[0141] The IAB node 1010 (e.g., the DU of the IAB node 1010) may identify the downlink SPS resource 1040 associated with the DU of the IAB node 1010 and corresponding to the downlink SPS resource 1035. For example, the IAB node 1010 may determine or identify the resource allocation associated with the downlink SPS resource 1040. Figure 9 As described, the IAB node 1010 may determine whether the time gap 1045 between the downlink SPS resource 1035 and the downlink SPS resource 1040 satisfies one or more parameters for coordinating periodic resources of the MT component associated with the IAB node 1010 and periodic resources of the DU associated with the IAB node 1010 .

[0142] If the IAB node 1010 determines that the time gap 1045 between the downlink SPS resource 1035 and the downlink SPS resource 1040 does not satisfy the one or more parameters, the IAB node 1010 may modify the resource allocation associated with the downlink SPS resource 1040. For example, the IAB node 1010 may modify the resource allocation associated with the downlink SPS resource 1040 so that the time gap 1045 satisfies the one or more parameters.

[0143] The IAB node 1010 may transmit an activation message 1030 to the child node 1020 for activating the downlink SPS resource 1040. If the IAB node 1010 has modified the resource allocation associated with the downlink SPS resource 1040, the activation message 1030 may indicate the modified resource allocation associated with the downlink SPS resource 1040.

[0144] As described above, the one or more parameters may be based at least in part on the processing capability of the IAB node 1010, the PDB of the RLC channel between the IAB node 1010 and the parent node 1015 or between the IAB node 1010 and the child node 1020, or the latency requirements of the IAB node 1010, etc. As a result, the time gap 1045 between the downlink SPS resources 1035 and the downlink SPS resources 1040 may be reduced by coordinating the downlink SPS resources 1035 and the downlink SPS resources 1040. Therefore, the IAB node 1010 may reduce the latency associated with forwarding downlink communications received from the parent node 1015 using the downlink SPS resources 1035 to the child node 1020 using the downlink SPS resources 1040.

[0145] As shown in the example associated with uplink CG periodic resource coordination 1005, the IAB node 1010 may receive an activation message 1050 from the parent node 1015. The activation message 1050 may activate uplink (UL) CG resources 1060 associated with the MT component of the IAB node 1010. For example, the activation message 1050 may indicate a resource allocation associated with the uplink CG resources 1060.

[0146] The IAB node 1010 (e.g., the DU of the IAB node 1010) may identify an uplink CG resource 1065 associated with the DU of the IAB node 1010 and corresponding to the uplink CG resource 1060. For example, the IAB node 1010 may determine or identify a resource allocation associated with the uplink CG resource 1065. Figure 9 As described, the IAB node 1010 can determine whether the time gap 1070 between the uplink CG resource 1060 and the uplink CG resource 1065 satisfies one or more parameters for coordinating the periodic resources of the MT component associated with the IAB node 1010 and the periodic resources of the DU associated with the IAB node 1010.

[0147] If the IAB node 1010 determines that the time gap 1070 between the uplink CG resource 1060 and the uplink CG resource 1065 does not satisfy the one or more parameters, the IAB node 1010 may modify the resource allocation associated with the uplink CG resource 1065. For example, the IAB node 1010 may modify the resource allocation associated with the uplink CG resource 1065 so that the time gap 1070 satisfies the one or more parameters.

[0148] The IAB node 1010 may transmit an activation message 1055 to the child node 1020 for activating the uplink CG resource 1065. If the IAB node 1010 has modified the resource allocation associated with the uplink CG resource 1065, the activation message 1055 may indicate the modified resource allocation associated with the uplink CG resource 1065.

[0149] As described above, the one or more parameters may be based at least in part on the processing capability of the IAB node 1010, the PDB of the RLC channel between the IAB node 1010 and the parent node 1015 or between the IAB node 1010 and the child node 1020, or the latency requirements of the IAB node 1010, etc. As a result, the time gap 1070 between the uplink CG resource 1060 and the uplink CG resource 1065 can be reduced by coordinating the uplink CG resource 1060 and the uplink CG resource 1065. Therefore, the IAB node 1010 can reduce the latency associated with using the uplink CG resource 1060 to forward uplink communications received from the child node 1020 using the uplink CG resource 1065 to the parent node 1015.

[0150] When the SPS opportunity corresponds to the NA resource type, the node (e.g., a parent node or an IAB node) may not be able to transmit data in the downlink during the SPS opportunity. The SPS opportunity can be a periodic SPS opportunity configured using the activation DCI. When the node cannot use the SPS opportunity that has been canceled due to the DU resource type corresponding to the SPS opportunity being the NA resource type, the node can configure dynamic grant to transmit the data in the downlink. However, the configuration of dynamic grant may result in additional latency, which may be problematic for periodic low latency data.

[0151] Various aspects generally relate to a priority flag that can be assigned to a resource to indicate that the resource is available to an IAB node, regardless of the resource type associated with the resource. More specifically, aspects relating to assigning a priority flag to a resource can enable the resource to be used by an IAB node even when the resource corresponds to an NA resource type. In some aspects, the resource can correspond to a downlink SPS opportunity or an uplink configured grant, and the resource can correspond to an NA resource type. The priority flag assigned to a resource can enable the resource to be used by an IAB node even when the resource corresponds to an NA resource type. In other words, the priority flag assigned to the resource can override the resource type associated with the resource.

[0152] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to reduce latency associated with communications in an IAB network. For example, downlink SPS opportunities or uplink configured grants corresponding to the resource may not be canceled, in part because dynamic grants may not be configured for the communication (which would increase latency), which can allow communications involving IAB nodes to occur with reduced latency.

[0153] Figure 11 1 is a diagram illustrating an example associated with priority flag signaling 1100 for periodic resources according to the present disclosure. Figure 11 As shown, priority flag signaling 1100 includes communication 120 between an IAB node (e.g., IAB node 345), a parent node or IAB donor (e.g., IAB donor 335), and a child node (e.g., a UE). In some aspects, the IAB node, the parent node or IAB donor, and the child node may be included in a wireless network, such as wireless network 100. The IAB node, the parent node or IAB donor, and the child node may communicate over a wireless side link.

[0154] In some aspects, an IAB node, a parent node or IAB donor, and a child node may be included in a multi-hop IAB network. Messages originating from an IAB donor may be delivered to the IAB node via a routing path from the IAB donor to the IAB node. The routing path may include one or more intermediate IAB nodes, which may include the parent node of the IAB node.

[0155] In a first operation 1102, an IAB node may receive a priority flag associated with a periodic resource set from a parent node or an IAB donor. In some aspects, the priority flag may be received from an IAB donor CU associated with the IAB donor. In some cases, the priority flag may be received from a parent node DU associated with the parent node of the IAB node. The priority flag may indicate that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set. The periodic resource set may be available to the MT or DU of the IAB node. The resource type associated with the individual resources may be a configured DU resource type.

[0156] In some aspects, the resource type associated with an individual resource included in a periodic resource set may be an NA resource type, a hard resource type, or a soft resource type. In some aspects, when the resource type associated with an individual resource included in the periodic resource set is an NA resource type, a priority flag may indicate that the individual resource associated with the NA resource type is to be overridden and made available to the IAB node. In other words, the IAB node may use the individual resource associated with the NA resource type when the periodic resource set including the individual resource is assigned a priority flag.

[0157] In previous solutions, the DU resource type of a resource defined which entity of the IAB node (e.g., the DU or the MT of the IAB node) had priority to use the resource. For resources with a DU type of "hard," the DU had a higher priority to use the resource than the MT. For resources with a DU type of "NA," the DU could not use the resource except for the cell-defined signal set. For resources with a DU type of "soft," priority was controlled by the parent node via explicit instructions or at least partially based on implicit determinations.

[0158] In some aspects, a resource type associated with a periodic resource allocated for an entity of an IAB node (e.g., a DU or MT of the IAB node) may be overridden when the periodic resource is indicated with a priority flag. The priority flag may be a high priority flag assigned to the periodic resource that may indicate that the resource type associated with the periodic resource is to be overridden and made available to the IAB node.

[0159] In some aspects, a priority flag may provide an IAB node (e.g., a DU or MT of the IAB node) with a priority for using periodic resources for periodic low-latency traffic, regardless of the configured DU resource type associated with the periodic resource. Periodic resources assigned with a priority flag may be associated with a downlink SPS or an uplink configured grant for periodic low-latency traffic. When a priority flag for a periodic resource is indicated, the priority flag may be applied to periodic resources that conflict with the configured DU resource type. The periodic resource location may be previously known to the parent node and the child node, which may enable the parent node and the child node to coordinate periodic resource usage based at least in part on the known conflicting locations.

[0160] In some cases, resource types associated with periodic resources may be overridden and made available to the IAB node based at least in part on a dynamic DCI grant. However, timely delivery of the dynamic DCI grant may involve using available PDCCH resources, which is not applicable when using a priority flag to prioritize the use of periodic resources by the IAB node.

[0161] In some aspects, the IAB node may receive the priority flag via an RRC message from an IAB donor CU associated with the IAB node. In some aspects, the IAB node may receive the priority flag via an F1-AP message from an IAB donor CU associated with the IAB node. In some aspects, the IAB node may receive the priority flag via a MAC-CE from a DU of a parent node. In some aspects, the IAB node may receive the priority flag via an activation downlink control message from a DU of the parent node.

[0162] In some aspects, the periodic resource set may include downlink resources allocated via a downlink SPS or uplink resources allocated via an uplink configured grant (Type 1 or Type 2). The downlink SPS and uplink configured grant may be used to allocate periodic resources for downlink or uplink data communications. The downlink SPS method may include an RRC configuration and a DCI activation grant. The RRC configuration may be used to convey parameters such as periodicity, the number of HARQ processes, etc. The DCI activation grant may be an allocation grant for allocating periodic resources for downlink transmission. When the DCI activation grant is used to allocate periodic resources, the dynamic grant for downlink transmission may not be used. The uplink configured grant (Type 1) method may include an RRC configuration. The uplink configured grant (Type 2) method may include an RRC configuration and a DCI activation grant.

[0163] In some aspects, priority rules can be defined to resolve resource conflicts between allocations. For example, in the downlink, a dynamic DCI grant may have a higher priority than an SPS associated with a decreased index, and an SPS associated with a decreased index may have a higher priority than an SPS associated with an increased index. In another example, in the uplink, priority levels can be used to indicate dynamic DCI grants and configured grants. A dynamic DCI grant associated with an increased priority may have a higher priority than an SPS associated with an increased priority, an SPS associated with an increased priority may have a higher priority than a dynamic DCI grant associated with a decreased priority, and a dynamic DCI grant associated with a decreased priority may have a higher priority than an SPS associated with a decreased priority. For the same priority level, an SPS associated with a decreased index may have a higher priority than an SPS associated with an increased index.

[0164] In a second operation 1104, the IAB node may perform communication with a child node (e.g., a child IAB node or a UE) of the IAB node or a parent node of the IAB node using the periodic resource set based at least in part on a priority flag associated with the periodic resource set. In some aspects, when the periodic resource set is assigned to a DU of the IAB node, the IAB node may perform communication with the child node of the IAB node. In some aspects, when the periodic resource set is assigned to a MT of the IAB node, the IAB node may perform communication with the parent node of the IAB node.

[0165] In some aspects, a periodic resource set may be allocated to a MT of an IAB node or a DU of an IAB node. When a periodic resource set is allocated to an MT of an IAB node, the MT of the IAB node may use the periodic resource set to communicate with the parent node of the IAB node. When a periodic resource set is allocated to a DU of an IAB node, the DU of the IAB node may use the periodic resource set to communicate with the child nodes of the IAB node.

[0166] In some aspects, the communication may be associated with periodic reduced latency traffic (or periodic low latency traffic). In other words, the periodic resource set associated with the priority flag may be for periodic reduced latency traffic, such as TSC traffic.

[0167] In some aspects, TSC traffic may follow a periodic or deterministic traffic pattern. TSC traffic may be enabled by assistance information that may be communicated by the Session Management Function (SMF) to the base station via the AMF during QoS flow establishment to achieve efficient scheduling of TSC traffic. Assistance information may include the flow direction (e.g., uplink or downlink), periodicity, or burst arrival time of the TSC traffic. TSC QoS flows may use a delay-critical GBR type.

[0168] In some aspects, a channel associated with an IAB node carrying a type of traffic may utilize a periodic resource set associated with a priority flag. For example, an RLC channel associated with an IAB node carrying periodic reduced latency traffic may utilize a periodic resource set associated with a priority flag. In some aspects, other channels associated with an IAB node carrying periodic reduced latency traffic (e.g., a PDCP channel or a MAC channel) may utilize a periodic resource set associated with a priority flag.

[0169] In a third operation 1106, the IAB node may transmit to the parent node information associated with a periodic resource set available to the IAB node regardless of resource type. For example, the information may describe a downlink SPS or uplink configured grant for the IAB node associated with the periodic resource set, where the downlink SPS or uplink configured grant may be associated with a priority flag. In some aspects, the IAB node may transmit the information to the parent node via a MAC-CE.

[0170] In a fourth operation 1108, the parent node may adjust resource allocation based at least in part on the information received from the IAB node. For example, the parent node may detect that resources overlap with a downlink SPS or uplink configured grant of the IAB node, where the downlink SPS or uplink configured grant may be associated with a priority flag. In such an example, the parent node may avoid scheduling the child node with the resources and may instead schedule another node to use the resources.

[0171] In some aspects, the parent node may receive information associated with a periodic resource set with a priority flag allocated to the IAB node from the IAB donor, and the parent node may adjust the resource allocation based at least in part on the information received from the IAB donor. For example, the parent node may receive the information via an F1-AP message or an RRC message from an IAB donor CU of the IAB donor.

[0172] Figure 12 1 is a diagram illustrating an example associated with priority flag signaling 1200 for periodic resources according to the present disclosure. Figure 12 As shown, priority flag signaling 1200 includes communications between a parent node or IAB donor (e.g., IAB donor 335), an IAB node (e.g., IAB node 345), and a child node (e.g., UE 120). In some aspects, the parent node or IAB donor, the IAB node, and the child node may be included in a wireless network, such as wireless network 100. The parent node or IAB donor, the IAB node, and the child node may communicate over a wireless side link.

[0173] In a first operation 1202, an IAB node may receive a priority flag associated with a periodic resource set from a parent node or an IAB donor. The priority flag may be associated with a periodic resource set for a DU of the IAB node. The priority flag may indicate that the periodic resource set is available to the DU of the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set.

[0174] In a second operation 1204, the IAB node may perform communication with a child node of the IAB node (e.g., a child IAB node or a UE) using the periodic resource set associated with the priority flag. In other words, when the periodic resource set is allocated to the DU of the IAB node, the IAB node may perform communication with the child node of the IAB node.

[0175] Figure 13 1 is a diagram illustrating an example associated with priority flag signaling 1300 for periodic resources according to the present disclosure. Figure 13As shown, example 1300 includes communications between an IAB donor (e.g., IAB donor 335), a parent node, and an IAB node (e.g., IAB node 345). In some aspects, the IAB donor, parent node, and IAB node may be included in a wireless network, such as wireless network 100. The IAB donor, parent node, and IAB node may communicate over a wireless side link.

[0176] In a first operation 1302, an IAB node may receive a priority flag associated with a periodic resource set from an IAB donor or parent node. The priority flag may be associated with a periodic resource set for a MT of the IAB node. The priority flag may indicate that the periodic resource set is available to the MT of the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set.

[0177] In a second operation 1304, the IAB node may perform communication with the parent node of the IAB node using the periodic resource set associated with the priority flag. In other words, when the periodic resource set is allocated to the MT of the IAB node, the IAB node may perform communication with the parent node of the IAB node.

[0178] Figure 14 1 is a diagram illustrating an example associated with priority flag signaling 1400 for periodic resources according to the present disclosure. Figure 14 As shown, the parent node may transmit an activation DCI to the IAB node. The parent node may be the parent node of the IAB node. The activation DCI may configure an SPS opportunity for the parent node. The SPS opportunity may be associated with a priority flag to override the DU resource type of the periodic resources associated with the SPS opportunity. In such an example, the DU resource type corresponding to the SPS opportunity may be a hard resource type. The IAB node may transmit an activation DCI to the child node. The child node may be the child node of the IAB node. The activation DCI transmitted by the IAB node may configure an SPS opportunity for the IAB node. The SPS opportunity may be associated with a priority flag to override the DU resource type of the periodic resources associated with the SPS opportunity. In such an example, the DU resource type corresponding to the SPS opportunity may be an NA resource type, but the periodic resources may be available to the IAB node based at least in part on the priority flag. In other words, the NA resource type associated with the periodic resources corresponding to the SPS opportunity may be overridden and the SPS opportunity may become available to the IAB node. The IAB node may use the SPS opportunity to transmit data to the child node, and the IAB node may not have to configure a dynamic grant to transmit the data, thereby reducing latency when communicating with the child node.

[0179] Figure 151 is a diagram illustrating an example associated with priority flag signaling 1500 for periodic resources according to the present disclosure. In some aspects, based at least in part on a priority flag associated with a resource, a parent node may receive information associated with a resource that is available to an IAB node regardless of the resource type associated with the resource. The resource may correspond to a downlink SPS or uplink configured grant. The parent node may determine, based at least in part on this information, an instance of an SPS allocation (e.g., a high priority DU SPS allocation) that overrides the corresponding NA resource. In such an example, the parent node may schedule overlapping resources (e.g., hard resources) of the parent node to another node because the overlapping resources cannot be used by the parent node to communicate with the IAB node. In other words, when a resource associated with a priority flag overlaps with a downlink SPS or uplink configured grant of an IAB node, the parent node may avoid scheduling the child node with the resource, and the parent node may instead schedule another node to use the resource.

[0180] Figure 16 is a flow diagram illustrating an example process 1600, performed, for example, by a wireless node, in accordance with the present disclosure. The example process 1600 is an example in which a wireless node (e.g., wireless node 905, IAB node 1010, or IAB node 410) performs operations associated with periodic resource coordination in an IAB network.

[0181] like Figure 16 As shown, in some aspects, process 1600 may include receiving an activation message for activating a first periodic resource associated with an MT component of a wireless node (block 1610). For example, a wireless node (such as by using Figure 24 The receiving component 2402 depicted in FIG. 24 may receive an activation message for activating a first periodic resource associated with an MT component of a wireless node, as described above.

[0182] like Figure 16 As further shown, in some aspects, process 1600 may include identifying one or more parameters for coordinating periodic resources associated with an MT component of a wireless node, including a first periodic resource, with periodic resources associated with a DU of the wireless node, including a second periodic resource (block 1620). For example, a wireless node (such as by using Figure 24 Depicted parameter identifying component 2410) can identify one or more parameters for coordinating periodic resources associated with an MT component of a wireless node, including first periodic resources, with periodic resources associated with a DU of the wireless node, including second periodic resources, as described above.

[0183] like Figure 16As further shown, in some aspects, process 1600 may include determining whether the second periodic resource satisfies the one or more parameters (block 1630). For example, the wireless node (such as by using Figure 24 The determining component 2412 depicted in can determine whether the second periodic resource satisfies the one or more parameters, as described above.

[0184] like Figure 16 As further shown, in some aspects, process 1600 may include modifying a resource allocation associated with the second periodic resource based at least in part on determining that the second periodic resource does not satisfy at least one of the one or more parameters (block 1640). For example, the wireless node (such as by using Figure 24 The resource allocation modifying component 2414 depicted in can modify the resource allocation associated with the second periodic resource based at least in part on determining that the second periodic resource does not satisfy at least one of the one or more parameters, as described above.

[0185] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0186] In a first additional aspect, process 1600 includes transmitting an activation message associated with the second periodic resource to the child node, the activation message indicating a modified resource allocation associated with the second periodic resource.

[0187] In a second additional aspect, alone or in combination with the first aspect,

[0188] The first periodic resource and the second periodic resource are both downlink SPS resources or both are uplink configured grant resources.

[0189] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the first periodic resources or the second periodic resources are associated with an RLC channel carrying low-latency traffic.

[0190] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, the one or more parameters include at least one of a time gap between the periodic resources associated with the MT component and the periodic resources associated with the DU, or a range of time gaps between the periodic resources associated with the MT component and the periodic resources associated with the DU.

[0191] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the time gap is based at least in part on a processing capability of the wireless node.

[0192] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, identifying one or more parameters for coordinating periodic resources of an MT component associated with a wireless node and periodic resources of a DU associated with the wireless node includes receiving an indication of the one or more parameters from a control node.

[0193] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, receiving an indication of the one or more parameters from the control node includes receiving an indication of the one or more parameters via an RRC message or an F1-AP message.

[0194] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the control node is a CU of an IAB donor.

[0195] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, identifying one or more parameters for coordinating periodic resources of an MT component associated with a wireless node and periodic resources of a DU associated with the wireless node includes receiving an indication of the one or more parameters from a parent node.

[0196] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, receiving an indication of the one or more parameters from the parent node comprises receiving an indication of the one or more parameters via a DCI message or a MAC-CE message.

[0197] In an eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, receiving an indication of the one or more parameters from the parent node comprises receiving an indication of the one or more parameters in an activation message.

[0198] In a twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, the parent node is a DU of an IAB node.

[0199] In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, identifying one or more parameters for coordinating periodic resources of an MT component associated with a wireless node and periodic resources of a DU associated with the wireless node includes determining the one or more parameters.

[0200] In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, process 1600 includes transmitting an indication of the one or more parameters to a parent node associated with the wireless node.

[0201] In a fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, transmitting an indication of the one or more parameters to a parent node associated with the wireless node includes transmitting the indication of the one or more parameters via a MAC-CE message or a UCI message.

[0202] In a sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, determining the one or more parameters includes determining the one or more parameters based at least in part on a processing capability of the wireless node, a waiting time requirement associated with the wireless node, or a PDB of an RLC channel associated with the first periodic resource or the second periodic resource.

[0203] In a seventeenth additional aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1600 includes transmitting an indication of information to be used to determine the one or more parameters to a control node or parent node.

[0204] In an eighteenth additional aspect, alone or in combination with one or more of the first to seventeenth aspects, the information to be used to determine the one or more parameters includes at least one of: a processing capability of the wireless node, a waiting time requirement associated with the wireless node, or a PDB of an RLC channel associated with the first periodic resource or the second periodic resource.

[0205] In a nineteenth additional aspect, alone or in combination with one or more of aspects one to eighteen, process 1600 includes receiving an indication of the one or more parameters from a control node or parent node, the one or more parameters being based at least in part on information to be used to determine the one or more parameters.

[0206] In a twentieth additional aspect, alone or in combination with one or more of the first to nineteenth aspects, receiving an activation message for activating a first periodic resource associated with an MT component of a wireless node includes identifying a second periodic resource corresponding to the first periodic resource.

[0207] In a twenty-first additional aspect, alone or in combination with one or more of the first to twentieth aspects, determining whether the second periodic resource satisfies the one or more parameters comprises determining whether a resource allocation associated with the second periodic resource satisfies the one or more parameters.

[0208] In a twenty-second additional aspect, alone or in combination with one or more of the first to twenty-first aspects, process 1600 includes receiving an indication of a scheduling gap indicating an amount of time between the activation message and the first periodic resource.

[0209] In a twenty-third additional aspect, alone or in combination with one or more of aspects one to twenty-second, determining whether the second periodic resource satisfies the one or more parameters comprises determining whether the second periodic resource satisfies the one or more parameters during a scheduling gap.

[0210] In an additional twenty-fourth aspect, alone or in combination with one or more of aspects one to twenty-third, receiving an indication of a scheduling gap indicating an amount of time between an activation message and a first periodic resource comprises receiving an indication of the scheduling gap from a control node via an RRC message or an F1-AP message.

[0211] In an additional aspect twenty-fifth, alone or in combination with one or more of aspects one to twenty-fourth, receiving an indication of a scheduling gap indicating an amount of time between an activation message and a first periodic resource includes receiving an indication of the scheduling gap from a parent node via a DCI message or a MAC-CE message.

[0212] In a twenty-sixth additional aspect, alone or in combination with one or more of the first to twenty-fifth aspects, process 1600 includes receiving, by the MT component, a first communication from a parent node using a first periodic resource, and transmitting, by the DU, a second communication associated with the first communication to a child node using a second periodic resource.

[0213] In a twenty-seventh additional aspect, alone or in combination with one or more of the first to twenty-sixth aspects, process 1600 includes receiving, by the DU, a first communication from the child node using a second periodic resource, and transmitting, by the MT component, a second communication associated with the first communication to the parent node using the first periodic resource.

[0214] although Figure 16 Example blocks of process 1600 are shown, but in some aspects, process 1600 may include Figure 16 16. In some embodiments, the process 1600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 1600 may be executed in parallel.

[0215] Figure 17 17 is a flow diagram illustrating an example process 1700, for example, performed by a wireless node, in accordance with the present disclosure. Example process 1700 is an example in which a wireless node (e.g., parent node 910, parent node 1015, a CU of IAB donor 405, or a DU of IAB node 410) performs operations associated with periodic resource coordination in an IAB network.

[0216] like Figure 17As shown, in some aspects, process 1700 may include determining one or more parameters for coordinating periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with the different wireless nodes (block 1710). For example, a wireless node (such as by using Figure 25 Depicted parameter determining component 2510) can determine one or more parameters for coordinating periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with the different wireless nodes, as described above.

[0217] like Figure 17 As further shown, in some aspects, process 1700 may include transmitting an indication of the one or more parameters to the different wireless node (block 1720). For example, a wireless node (such as by using Figure 25 The transmitting component 2506 depicted in can transmit an indication of the one or more parameters to the different wireless node, as described above.

[0218] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0219] In a first additional aspect, the wireless node is a CU of an IAB donor or a DU of an IAB node.

[0220] In a second additional aspect, alone or in combination with the first aspect, determining one or more parameters for coordinating periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with the different wireless nodes includes determining at least one of: a time gap between the periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with different wireless nodes, or a time gap range between the periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with different wireless nodes.

[0221] In a third additional aspect, alone or in combination with one or more of the first and second aspects, determining one or more parameters for coordinating periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with different wireless nodes includes determining the one or more parameters based at least in part on information including at least one of: processing capabilities of the different wireless nodes, waiting time requirements associated with the different wireless nodes, or PDBs of RLC channels associated with the periodic resources of MT components associated with different wireless nodes or the periodic resources of DUs associated with different wireless nodes.

[0222] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, process 1700 includes receiving from a different wireless node an indication of at least one of a processing capability of the different wireless node or a latency requirement associated with the different wireless node.

[0223] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, transmitting an indication of the one or more parameters includes transmitting the indication of the one or more parameters via an RRC message or an F1-AP message.

[0224] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, transmitting the indication of the one or more parameters comprises transmitting the indication of the one or more parameters via a DCI message or a MAC-CE message.

[0225] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, process 1700 includes determining a scheduling gap indicating an amount of time between an activation message for activating a periodic resource for an MT component associated with the different wireless node and the periodic resource, and transmitting an indication of the scheduling gap to the different wireless node.

[0226] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, process 1700 includes transmitting an activation message to the different wireless node to activate periodic resources associated with the MT component of the different wireless node.

[0227] In a ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, process 1700 includes transmitting communications to the different wireless node during periodic resources, wherein the communications are to be forwarded by the different wireless node to a subnode associated with the different wireless node.

[0228] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, process 1700 includes receiving communications from the different wireless node during periodic resources, wherein the communications are associated with communications to be forwarded by the different wireless node to the wireless node from a subnode associated with the different wireless node.

[0229] In an eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, transmitting an indication of the one or more parameters to the different wireless node includes transmitting an indication of the one or more parameters to a parent node associated with the different wireless node.

[0230] although Figure 17 Example blocks of process 1700 are shown, but in some aspects, process 1700 may include Figure 17 1700. In some embodiments, the process 1700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 1700 may be executed in parallel.

[0231] Figure 18 is a flow diagram illustrating an example process 1800, performed, for example, by a wireless node, in accordance with the present disclosure. The example process 1800 is an example in which a wireless node (e.g., IAB node 410, child node 810, or UE 120) performs operations associated with configuring downlink configured grants in an IAB network.

[0232] like Figure 18 As shown, in some aspects, process 1800 may include receiving a configuration from a control node indicating grant information for a downlink periodic resource, the grant information indicating a resource location associated with the downlink periodic resource (block 1810). For example, a wireless node (such as by using Figure 26 The receiving component 2602 depicted in FIG. 2 may receive a configuration indicating grant information for a downlink periodic resource from a control node, the grant information indicating a resource location associated with the downlink periodic resource, as described above.

[0233] like Figure 18 As further shown, in some aspects, process 1800 may include communicating downlink traffic using downlink periodic resources in accordance with the grant information (block 1820). For example, a wireless node (such as by using Figure 26 The receiving component 2602 or the transmitting component 2506 depicted in FIG. 2 can communicate downlink traffic using downlink periodic resources in accordance with the grant information, as described above.

[0234] Process 1800 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0235] In a first additional aspect, receiving a configuration indicating grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) includes receiving a configuration indicating full grant information, and wherein using the downlink periodic resources to convey downlink traffic in accordance with the grant information includes using the downlink periodic resources to convey downlink traffic without receiving or transmitting an activation message associated with the downlink periodic resources.

[0236] In a second additional aspect, either alone or in combination with the first aspect, the full grant information indicates at least a resource location associated with the downlink periodic resource, an MCS associated with the downlink periodic resource, a frequency domain resource block (RB) allocation associated with the downlink periodic resource, and an antenna port of the wireless node associated with the downlink periodic resource.

[0237] In a third additional aspect, alone or in combination with one or more of the first and second aspects, receiving a configuration indicating grant information for a downlink periodic resource (which indicates a resource location associated with the downlink periodic resource) includes receiving a configuration indicating partial grant information, which partial grant information indicates at least a resource location associated with the downlink periodic resource.

[0238] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, using downlink periodic resources to convey downlink traffic based on the grant information includes transmitting or receiving an activation message indicating remaining grant information associated with the downlink periodic resources, and using the downlink periodic resources to convey downlink traffic based on the partial grant information and the remaining grant information.

[0239] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the remaining grant information associated with the downlink periodic resource indicates at least one of: an MCS associated with the downlink periodic resource, a frequency domain RB allocation associated with the downlink periodic resource, an antenna port of a wireless node associated with the downlink periodic resource, or an RV associated with the downlink periodic resource.

[0240] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, the control node is a CU of an IAB donor.

[0241] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the wireless node is an IAB node and the downlink periodic resources are associated with an MT component of the IAB node, and wherein using the downlink periodic resources to convey downlink traffic according to the grant information includes using the downlink periodic resources to receive downlink traffic from a parent node associated with the IAB node.

[0242] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the wireless node is an IAB node and the downlink periodic resources are associated with a DU component of the IAB node, and wherein using the downlink periodic resources to convey downlink traffic according to the grant information includes using the downlink periodic resources to transmit downlink traffic to a child node associated with the IAB node.

[0243] In a ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, the configuration for receiving indication grant information comprises receiving an indication of a periodicity associated with a downlink periodic resource and an offset value associated with the downlink periodic resource.

[0244] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, process 1800 includes transmitting an indication of processing capabilities associated with the wireless node to a control node.

[0245] although Figure 18 Example blocks of process 1800 are shown, but in some aspects, process 1800 may include Figure 18 1800. In some embodiments, the process 1800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1800. Additionally or alternatively, two or more blocks of the process 1800 may be executed in parallel.

[0246] Figure 19 1900 is a flow diagram illustrating an example process 1900, performed, for example, by a control node, in accordance with the present disclosure. The example process 1900 is an example in which a control node (e.g., IAB donor 405, a CU of IAB donor 405, or base station 110) performs operations associated with configuring downlink configured grants in an IAB network.

[0247] like Figure 19 As shown, in some aspects, process 1900 may include determining grant information for downlink periodic resources for one or more wireless nodes included in a multi-hop network, the grant information indicating a resource location associated with the downlink periodic resources (block 1910). For example, a control node (such as by using Figure 27 The grant information determining component 2710 depicted in FIG. 2 may determine grant information for downlink periodic resources for one or more wireless nodes included in a multi-hop network, indicating a resource location associated with the downlink periodic resources, as described above.

[0248] like Figure 19 As further shown, in some aspects, process 1900 may include transmitting a configuration indicating the grant information to the one or more wireless nodes (block 1920). For example, a control node (such as by using Figure 27 The transmitting component 2706 depicted in can transmit a configuration indicating the grant information to the one or more wireless nodes, as described above.

[0249] Process 1900 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0250] In a first additional aspect, transmitting the configuration indicative of the grant information includes transmitting full grant information to each of the one or more wireless nodes, the full grant information enabling the wireless node to communicate periodic downlink communications using downlink periodic resources without requiring an activation message.

[0251] In a second additional aspect, alone or in combination with the first aspect, determining grant information for downlink periodic resources (which indicates resource locations associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining full grant information for each of the one or more wireless nodes.

[0252] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the configuration of transmitting the indication grant information includes transmitting to each of the one or more wireless nodes at least partial grant information indicating a resource location associated with a downlink periodic resource.

[0253] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining partial grant information for each of the one or more wireless nodes.

[0254] In a fifth additional aspect, determining partial grant information for each of the one or more wireless nodes, alone or in combination with one or more of the first to fourth aspects, includes determining at least one of: an MCS associated with a downlink periodic resource, a frequency domain RB allocation associated with the downlink periodic resource, an antenna port of the wireless node associated with the downlink periodic resource, or an RV associated with the downlink periodic resource.

[0255] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining, for each of the one or more wireless nodes, grant information for downlink periodic resources to be used by the wireless node.

[0256] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the one or more wireless nodes are included in a communication path for periodic multi-hop downlink communications.

[0257] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the communication path includes one or more RLC channels associated with low-latency traffic.

[0258] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, determining grant information for downlink periodic resources (indicating resource locations associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining, for each of the one or more wireless nodes, a resource location associated with the downlink periodic resources for the wireless node.

[0259] In a tenth additional aspect, determining, alone or in combination with one or more of the first to ninth aspects, a resource location associated with a downlink periodic resource for each of the one or more wireless nodes includes determining a periodicity associated with the downlink periodic resource, and determining an offset value associated with the downlink periodic resource.

[0260] In an eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, transmitting a configuration indicating the grant information includes transmitting an indication of a periodicity associated with a downlink periodic resource and an offset value associated with the downlink periodic resource to a wireless node among the one or more wireless nodes.

[0261] In a twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, determining grant information for downlink periodic resources (indicating a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes: determining the grant information for each of the one or more wireless nodes based at least in part on at least one of: a traffic pattern of the wireless node, a duplex communication mode capability of the wireless node, an IAB resource type pattern of the wireless node, an average link quality associated with the wireless node, a processing capability of the wireless node, or a waiting time requirement of the wireless node.

[0262] In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, process 1900 includes receiving, from a wireless node of the one or more wireless nodes, an indication of a processing capability of the wireless node.

[0263] In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, the control node is a CU of an IAB donor.

[0264] In a fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining grant information indicating a resource location for the downlink periodic resources for a wireless node among the one or more wireless nodes, which is associated with an MT component of the wireless node and used by the wireless node to receive periodic downlink communications.

[0265] In a sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining grant information indicating a resource location for the downlink periodic resources for a wireless node among the one or more wireless nodes, which is associated with a DU of the wireless node and is used by the wireless node to transmit periodic downlink communications.

[0266] although Figure 19 Example blocks of process 1900 are shown, but in some aspects, process 1900 may include Figure 19 1900. In some embodiments, the process 1900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 1900 may be executed in parallel.

[0267] Figure 20 is a flow diagram illustrating an example process 2000, performed, for example, by a wireless node, in accordance with the present disclosure. The example process 2000 is one in which a wireless node (eg, IAB node 410, child node 810, or UE 120) performs operations associated with priority flag signaling for periodic resources.

[0268] like Figure 20 As shown, in some aspects, process 2000 may include receiving a priority flag associated with a periodic resource set, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of resource types associated with individual resources included in the periodic resource set (block 2010). For example, the IAB node (e.g., by using Figure 28The receiving component 2802, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242 depicted in FIG; using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, or memory 282) can receive a priority flag associated with a periodic resource set, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set, as described above.

[0269] like Figure 20 As further shown, in some aspects, process 2000 may include performing communications with a child node of the IAB node or a parent node of the IAB node using the periodic resource set based at least in part on a priority flag associated with the periodic resource set (block 2020). For example, an IAB node (such as by using Figure 28 The receiving component 2802 or transmitting component 2806, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, scheduler 246 depicted in the embodiment; using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280 or memory 282) can use the periodic resource set to perform communication with a child node of the IAB node or a parent node of the IAB node based at least in part on a priority flag associated with the periodic resource set, as described above.

[0270] Process 2000 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0271] In a first additional aspect, receiving the priority flag includes receiving the priority flag via a radio resource control message from a central unit of an IAB donor associated with the IAB node.

[0272] In a second additional aspect, alone or in combination with the first aspect, receiving the priority flag comprises receiving the priority flag via an F1 Application Protocol message from a central unit of an IAB donor associated with the IAB node.

[0273] In a third additional aspect, alone or in combination with one or more of the first and second aspects, receiving the priority flag comprises receiving the priority flag via a media access control-control element from a distributed unit of a parent node of the IAB node.

[0274] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, receiving the priority flag comprises receiving the priority flag via an activation downlink control message from a distributed unit of a parent node of the IAB node.

[0275] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the periodic resource set comprises downlink resources allocated via downlink semi-persistent scheduling.

[0276] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, the periodic resource set comprises uplink resources allocated via an uplink configured grant.

[0277] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the periodic resource set may be used for a mobile terminal or a distributed unit of an IAB node.

[0278] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the resource type associated with the individual resource is a configured distributed unit resource type.

[0279] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the resource type associated with the individual resource is an NA resource type, a hard resource type, or a soft resource type.

[0280] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, the communication is associated with periodic low latency traffic.

[0281] In an eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, performing the communication comprises performing the communication using a periodic set of resources at a radio link control channel associated with the IAB node.

[0282] In a twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, process 2000 includes transmitting to a parent node information associated with a set of periodic resources available to the IAB node regardless of resource type to enable adjustment of resource allocation at the parent node.

[0283] although Figure 20 Example blocks of process 2000 are shown, but in some aspects, process 2000 may include Figure 20 2000. In some embodiments, the process 2000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 2000 may be executed in parallel.

[0284] Figure 21 is a flow diagram illustrating an example process 2100, performed, for example, by a control node, in accordance with the present disclosure. The example process 2100 is an example in which a control node (eg, an IAB donor) performs operations associated with priority flag signaling for periodic resources.

[0285] like Figure 21 As shown in , in some aspects, process 2100 may include associating a priority flag with a periodic resource set (block 2110). For example, an IAB donor (such as by using Figure 28 The associating component 2810 depicted in, using antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240 or memory 242; or using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280 or memory 282) can associate priority flags with periodic resource sets, as described above.

[0286] like Figure 21 As further shown, in some aspects, process 2100 may include transmitting, from the IAB donor to the IAB node, a priority flag associated with the periodic resource set, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of resource types associated with individual resources included in the periodic resource set (block 2120). For example, the IAB donor (such as by using Figure 28 246; or using antenna 252, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282) can communicate a priority flag associated with a periodic resource set from an IAB donor to an IAB node, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of resource types associated with individual resources included in the periodic resource set, as described above.

[0287] Process 2100 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0288] In a first additional aspect, transmitting the priority flag includes transmitting the priority flag via a radio resource control message from a central unit of the IAB donor.

[0289] In a second additional aspect, alone or in combination with the first aspect, transmitting the priority flag includes transmitting the priority flag via an F1 Application Protocol message from a central unit of the IAB donor.

[0290] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the periodic resource set comprises downlink resources allocated via downlink semi-persistent scheduling.

[0291] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, the periodic resource set comprises uplink resources allocated via an uplink configured grant.

[0292] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the periodic resource set may be used for a mobile terminal or a distributed unit of an IAB node.

[0293] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, the resource type associated with the individual resource is a configured distributed unit resource type.

[0294] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the resource type associated with the individual resource is an NA resource type, a hard resource type, or a soft resource type.

[0295] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the process 2100 includes transmitting, to a parent node of the IAB node, information associated with a set of periodic resources allocated to the IAB node with a priority flag.

[0296] although Figure 21 Example blocks of process 2100 are shown, but in some aspects, process 2100 may include Figure 21 21. In some embodiments, the process 2100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 2100 may be executed in parallel.

[0297] Figure 22 is a flow diagram illustrating an example process 2200 performed, for example, by a parent node, in accordance with the present disclosure. The example process 2200 is an example in which a control node (eg, an IAB node) performs operations associated with priority flag signaling for periodic resources.

[0298] like Figure 22 As shown in , in some aspects, process 2200 may include associating a priority flag with a periodic resource set (block 2210). For example, a parent node (such as by using Figure 28The associating component 2810 depicted in, using antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240 or memory 242; or using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280 or memory 282) can associate priority flags with periodic resource sets, as described above.

[0299] like Figure 22 As further shown, in some aspects, process 2200 may include transmitting, from the parent node to the IAB node, a priority flag associated with the periodic resource set, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of resource types associated with individual resources included in the periodic resource set (block 2220). For example, the parent node (such as by using Figure 28 The transmission component 2806 depicted in FIG, using the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antenna 234, the controller / processor 240, the memory 242, or the scheduler 246; or using the antenna 252, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282) can transmit a priority flag associated with a periodic resource set from a parent node to an IAB node, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set, as described above.

[0300] Process 2200 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0301] In a first additional aspect, transmitting the priority flag comprises transmitting the priority flag via a medium access control-control element from a distributed unit of the parent node.

[0302] In a second additional aspect, alone or in combination with the first aspect, transmitting the priority flag includes transmitting the priority flag via an activation downlink control message from a distributed unit of a parent node.

[0303] In a third additional aspect, alone or in combination with one or more of the first and second aspects, process 2200 includes receiving information from an IAB node associated with a set of periodic resources available to the IAB node regardless of resource type, and adjusting resource allocation based at least in part on the information received from the IAB node.

[0304] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, receiving the information comprises receiving the information from an IAB node via a medium access control-control element.

[0305] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, receiving the information comprises receiving the information from a central unit of the IAB donor via an F1 Application Protocol message or a Radio Resource Control message.

[0306] although Figure 22 Example blocks of process 2200 are shown, but in some aspects, process 2200 may include Figure 22 2200. In some embodiments, the process 2200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 2200 may be executed in parallel.

[0307] Figure 23 is a flow diagram illustrating an example process 2300, performed, for example, by a wireless node, in accordance with the present disclosure. The example process 2300 is an example in which a wireless node (eg, IAB node 410, child node 810, or UE 120) performs operations associated with enhancement of periodic resources in an IAB network.

[0308] like Figure 23 As shown, in some aspects, process 2300 may include receiving an indication of a first periodic resource associated with a wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource (block 2310). For example, the wireless node (such as by using Figure 29 The depicted communication manager 2904 or receiving component 2902) may receive an indication of a first periodic resource associated with a wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource, as described above.

[0309] like Figure 23 As further shown, in some aspects, process 2300 may communicate a message with a child node or another wireless node using a modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource (block 2320). For example, a wireless node (such as by using Figure 29The communication manager 2904, receiving component 2902, or transmitting component 2906 depicted in the figure can use the modified first periodic resource to communicate a message with a subnode or another wireless node, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource, as described above.

[0310] Process 2300 may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes described elsewhere herein.

[0311] In a first additional aspect, process 2300 includes transmitting an activation message associated with the first periodic resource to a child node, the activation message indicating a modified resource allocation associated with the first periodic resource.

[0312] In a second additional aspect, alone or in combination with the first aspect, a first periodic resource is associated with a DU of a wireless node, and wherein one or more parameters for coordinating the periodic resource are associated with coordinating the first periodic resource and a second periodic resource, the second periodic resource being associated with an MT component of the wireless node and corresponding to the first periodic resource, and wherein communicating using the modified first periodic resource is based at least in part on the first periodic resource not satisfying at least one of the one or more parameters.

[0313] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the one or more parameters include at least one of: a time gap between periodic resources associated with the MT component of the wireless node and periodic resources associated with the DU of the wireless node, or a range of time gaps between periodic resources associated with the MT component and periodic resources associated with the DU.

[0314] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, process 2300 includes receiving an indication of the one or more parameters from a control node or parent node, or determining the one or more parameters.

[0315] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the one or more parameters are based at least in part on at least one of: a processing capability of the wireless node, a waiting time requirement associated with the wireless node, or a PDB of an RLC channel associated with the first periodic resource or the second periodic resource.

[0316] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, process 2300 includes transmitting an indication of information to be used to determine the one or more parameters to a control node or parent node, and receiving an indication of the one or more parameters from the control node or parent node based at least in part on transmitting the indication of information to be used to determine the one or more parameters.

[0317] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, process 2300 includes receiving a priority flag from a control node or a parent node via at least one of a radio resource control message, an F1 application protocol message, a MAC-CE, or activation downlink control information.

[0318] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the first periodic resources include one or more downlink resources allocated via downlink semi-persistent scheduling or one or more uplink resources allocated via uplink configured grant.

[0319] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the resource type comprises a configured distributed unit resource type, a NA resource type, a hard resource type, or a soft resource type.

[0320] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, process 2300 includes transmitting to a control node or a parent node information associated with a first periodic resource available to the wireless node regardless of resource type to enable adjustment of resource allocation at the control node or the parent node.

[0321] In an eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, receiving an indication of a first periodic resource includes receiving a configuration indicating grant information for the first periodic resource from a control node, the grant information indicating a resource location associated with the first periodic resource.

[0322] In a twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, receiving a configuration indicating grant information for a first periodic resource (which indicates a resource location associated with the first periodic resource) includes receiving a configuration indicating full grant information.

[0323] In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, the full grant information indicates at least a resource location associated with the first periodic resource, an MCS associated with the first periodic resource, a frequency domain RB allocation associated with the first periodic resource, and an antenna port of the wireless node associated with the first periodic resource.

[0324] In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, receiving a configuration indicating grant information for a first periodic resource (which indicates a resource location associated with the first periodic resource) includes receiving a configuration indicating partial grant information, which partial grant information at least indicates the resource location associated with the first periodic resource.

[0325] although Figure 23 Example blocks of process 2300 are shown, but in some aspects, process 2300 may include Figure 23 2300. In some embodiments, the process 2300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 2300 may be executed in parallel.

[0326] Figure 24 24 is a block diagram of an example device 2400 for wireless communication according to the present disclosure. Device 2400 may be a wireless node, or a wireless node may include device 2400. In some aspects, device 2400 includes a receiving component 2402, a communication manager 2404, and a transmission component 2406, which may communicate with each other (e.g., via one or more buses). As shown, device 2400 may use receiving component 2402 and transmission component 2406 to communicate with another device 2408 (such as a UE, a base station, an IAB node, an IAB donor, or another wireless communication device).

[0327] In some aspects, the device 2400 may be configured to perform Figure 9-15 Additionally or alternatively, the device 2400 may be configured to perform one or more of the processes described herein (such as Figure 16 In some aspects, the apparatus 2400 may include the above combined Figure 2 One or more components of a wireless node are described.

[0328] The receiving component 2402 may receive communications (such as reference signals, control information, data communications, or a combination thereof) from the device 2408. The receiving component 2402 may provide the received communications to one or more other components of the device 2400, such as the communications manager 2404. In some aspects, the receiving component 2402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 2402 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described wireless nodes.

[0329] The transmission component 2406 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 2408. In some aspects, the communication manager 2404 may generate communications and may transmit the generated communications to the transmission component 2406 for transmission to the device 2408. In some aspects, the transmission component 2406 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and may transmit the processed signals to the device 2408. In some aspects, the transmission component 2406 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described wireless nodes. In some aspects, transmitting component 2406 can be co-located with receiving component 1002 in a transceiver.

[0330] The communication manager 2404 may receive or may cause the receiving component 2402 to receive an activation message for activating a first periodic resource associated with the MT component of the wireless node. The communication manager 2404 may identify one or more parameters for coordinating the periodic resources associated with the MT component of the wireless node, including the first periodic resource, with the periodic resources associated with the DU of the wireless node, including the second periodic resource. The communication manager 2404 may determine whether the second periodic resource satisfies the one or more parameters. The communication manager 2404 may modify the resource allocation associated with the second periodic resource based at least in part on determining that the second periodic resource does not satisfy at least one of the one or more parameters. In some aspects, the communication manager 2404 may include the above in combination with Figure 2 A controller / processor, memory, scheduler, communication unit, or combination thereof of the described wireless nodes.

[0331] In some aspects, the communication manager 2404 may include a component set, such as a parameter identification component 2410, a determination component 2412, a resource allocation modification component 2414, or a combination thereof. Alternatively, the component set may be separate and distinct from the communication manager 2404. In some aspects, one or more components in the component set may include or may be combined with the above. Figure 2 The described wireless node is implemented within a controller / processor, memory, scheduler, communication unit, or a combination thereof. Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in the memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0332] Parameter identifying component 2410 may identify one or more parameters for coordinating periodic resources associated with an MT component of a wireless node, including first periodic resources, with periodic resources associated with a DU of the wireless node, including second periodic resources. In some aspects, parameter identifying component 2410 may cause receiving component 2402 to receive an indication of the one or more parameters from a control node. In some aspects, parameter identifying component 2410 may cause receiving component 2402 to receive an indication of the one or more parameters from a parent node. In some aspects, parameter identifying component 2410 may cause determining component 2412 to determine the one or more parameters.

[0333] Determining component 2412 can determine whether the second periodic resource satisfies the one or more parameters. Resource allocation modifying component 2414 can modify a resource allocation associated with the second periodic resource based at least in part on determining that the second periodic resource does not satisfy at least one of the one or more parameters.

[0334] Transmitting component 2406 may transmit an activation message associated with the second periodic resource to the child node, the activation message indicating a modified resource allocation associated with the second periodic resource. Transmitting component 2406 may transmit an indication of the one or more parameters to a parent node associated with the wireless node. Transmitting component 2406 may transmit an indication of information to be used to determine the one or more parameters to a control node or parent node.

[0335] Receiving component 2402 can receive, from a control node or parent node, an indication of the one or more parameters based at least in part on information to be used to determine the one or more parameters. Receiving component 2402 can receive an indication of a scheduling gap indicating an amount of time between an activation message and a first periodic resource.

[0336] Receiving component 2402 can receive a first communication from a parent node using a first periodic resource via the MT component. Transmitting component 2406 can transmit a second communication associated with the first communication to a child node using a second periodic resource via the DU.

[0337] Receiving component 2402 can receive a first communication from the child node via the DU using the second periodic resource. Transmitting component 2406 can transmit a second communication associated with the first communication to the parent node via the MT component using the first periodic resource.

[0338] Figure 24 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 24 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 24Two or more components shown in the figure may be implemented in a single component, or Figure 24 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 24 The component set (e.g., one or more components) shown in FIG can perform the operations described as being performed by Figure 24 One or more functions performed by another set of components shown in .

[0339] Figure 25 2 is a block diagram of an example device 2500 for wireless communication according to the present disclosure. Device 2500 may be a wireless node, or a wireless node may include device 2500. In some aspects, device 2500 includes a receiving component 2502, a communication manager 2504, and a transmission component 2506, which may communicate with each other (e.g., via one or more buses). As shown, device 2500 may use receiving component 2502 and transmission component 2506 to communicate with another device 2508 (such as a UE, a base station, an IAB node, an IAB donor, or another wireless communication device).

[0340] In some aspects, the device 2500 may be configured to perform Figure 9-15 Additionally or alternatively, the device 2500 may be configured to perform one or more of the processes described herein (such as Figure 17 In some aspects, the apparatus 2500 may include the above combined Figure 2 One or more components of a wireless node are described.

[0341] The receiving component 2502 may receive communications (such as reference signals, control information, data communications, or a combination thereof) from the device 2508. The receiving component 2502 may provide the received communications to one or more other components of the device 2500 (such as the communications manager 2504). In some aspects, the receiving component 2502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 2502 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described wireless nodes.

[0342] The transmission component 2506 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 2508. In some aspects, the communication manager 2504 may generate communications and may transmit the generated communications to the transmission component 2506 for transmission to the device 2508. In some aspects, the transmission component 2506 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and may transmit the processed signals to the device 2508. In some aspects, the transmission component 2506 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described wireless nodes. In some aspects, transmitting component 2506 can be co-located with receiving component 2502 in a transceiver.

[0343] The communication manager 2504 may determine one or more parameters for coordinating periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with different wireless nodes. The communication manager 2504 may transmit, or may cause the transmission component 2506 to transmit, an indication of the one or more parameters to the different wireless nodes. In some aspects, the communication manager 2504 may include the above in combination with Figure 2 A controller / processor, memory, scheduler, communication unit, or combination thereof of the described wireless nodes.

[0344] In some aspects, the communication manager 2504 may include a component set, such as a parameter determination component 2510, etc. Alternatively, the component set may be separate and distinct from the communication manager 2504. In some aspects, one or more components in the component set may include or may be combined with the above. Figure 2 The described wireless node is implemented within a controller / processor, memory, scheduler, communication unit, or a combination thereof. Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in the memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0345] Parameter determining component 2510 may determine one or more parameters for coordinating periodic resources of MT components associated with different wireless nodes and periodic resources of DUs associated with different wireless nodes. In some aspects, parameter determining component 2510 may determine a time gap between the periodic resources of the MT components associated with the different wireless nodes and the periodic resources of the DUs associated with the different wireless nodes. In some aspects, parameter determining component 2510 may determine a time gap range between the periodic resources of the MT components associated with the different wireless nodes and the periodic resources of the DUs associated with the different wireless nodes.

[0346] Parameter determining component 2510 can determine the one or more parameters based at least in part on information comprising at least one of: processing capabilities of different wireless nodes, latency requirements associated with different wireless nodes, or PDBs of RLC channels associated with periodic resources of MT components associated with different wireless nodes or periodic resources of DUs associated with different wireless nodes. Receiving component 2502 can receive, from different wireless nodes, an indication of the processing capabilities of the different wireless nodes or the latency requirements associated with the different wireless nodes.

[0347] Transmitting component 2506 may transmit an indication of the one or more parameters via a DCI message or a MAC-CE message. Parameter determining component 2510 may determine a scheduling gap indicating an amount of time between an activation message for activating a periodic resource associated with an MT component of a different wireless node and the periodic resource. Transmitting component 2506 may transmit an indication of the scheduling gap to the different wireless node.

[0348] Transmitting component 2506 can transmit communications to the different wireless node during the periodic resources, wherein the communications are to be forwarded by the different wireless node to a child node associated with the different wireless node. Receiving component 2502 can receive communications from the different wireless node during the periodic resources, wherein the communications are associated with communications to be forwarded by the different wireless node from a child node associated with the different wireless node to the wireless node.

[0349] Transmitting component 2506 may communicate an indication of the one or more parameters to a parent node associated with the different wireless node.

[0350] Figure 25 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 25 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 25 Two or more components shown in the figure may be implemented in a single component, or Figure 25 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 25 The component set (e.g., one or more components) shown in FIG can perform the operations described as being performed by Figure 25 One or more functions performed by another set of components shown in .

[0351] Figure 26 26 is a block diagram of an example device 2600 for wireless communication according to the present disclosure. Device 2600 can be a wireless node (such as an IAB node), or a wireless node can include device 2600. In some aspects, device 2600 includes a receiving component 2602, a communication manager 2604, and a transmission component 2606, which can communicate with each other (e.g., via one or more buses). As shown, device 2600 can use receiving component 2602 and transmission component 2606 to communicate with another device 2608 (such as a UE, a base station, or another wireless communication device).

[0352] In some aspects, the device 2600 may be configured to perform Figure 9-15 Additionally or alternatively, the device 2600 may be configured to perform one or more of the processes described herein (such as Figure 18 In some aspects, the apparatus 2600 may include the above combined Figure 2 One or more components of a wireless node are described.

[0353] The receiving component 2602 may receive communications (such as reference signals, control information, data communications, or a combination thereof) from the device 2608. The receiving component 2602 may provide the received communications to one or more other components of the device 2600, such as the communications manager 2604. In some aspects, the receiving component 2602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 2602 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described wireless nodes.

[0354] The transmission component 2606 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 2608. In some aspects, the communication manager 2604 may generate communications and may transmit the generated communications to the transmission component 2606 for transmission to the device 2608. In some aspects, the transmission component 2606 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and may transmit the processed signals to the device 2608. In some aspects, the transmission component 2606 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described wireless nodes. In some aspects, transmitting component 2606 can be co-located with receiving component 2602 in a transceiver.

[0355] The communication manager 2604 may, or may cause the receiving component 2602 to, receive a configuration indicating grant information for downlink periodic resources from a control node, indicating a resource location associated with the downlink periodic resources. In some aspects, the communication manager 2604 may communicate (e.g., transmit or receive), or may cause the receiving component 2602 to receive, or may cause the transmitting component 2606 to transmit downlink traffic using the downlink periodic resources in accordance with the grant information. In some aspects, the communication manager 2604 may include the above in combination with Figure 2 A controller / processor, memory, scheduler, communication unit, or combination thereof of the described wireless nodes.

[0356] In some aspects, the communication manager 2604 may include a component set, such as a processing capability determination component 2610, or a grant information determination component 2612, etc. Alternatively, the component set may be separate and distinct from the communication manager 2604. In some aspects, one or more components in the component set may include or may be combined with the above. Figure 2 The described wireless node is implemented within a controller / processor, memory, scheduler, communication unit, or a combination thereof. Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in the memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0357] Processing capability determining component 2610 can determine the processing capability of the wireless node associated with processing or forwarding the communication to the next hop.

[0358] Receiving component 2602 can receive a configuration indicating full grant information. Receiving component 2602 can receive downlink traffic using the downlink periodic resources without receiving or transmitting an activation message associated with the downlink periodic resources. Transmitting component 2606 can transmit downlink traffic using the downlink periodic resources without receiving or transmitting an activation message associated with the downlink periodic resources.

[0359] Receiving component 2602 can receive a configuration indicating partial grant information indicating at least a resource location associated with a downlink periodic resource.

[0360] Receiving component 2602 may receive an activation message indicating remaining grant information associated with the downlink periodic resources. Transmitting component 2606 may transmit the activation message indicating remaining grant information associated with the downlink periodic resources. Grant information determining component 2612 may determine remaining grant information associated with the downlink periodic resources. Receiving component 2602 may receive downlink traffic using the downlink periodic resources based on the partial grant information and the remaining grant information. Transmitting component 2606 may transmit downlink traffic using the downlink periodic resources based on the partial grant information and the remaining grant information.

[0361] Receiving component 2602 can receive downlink traffic from a parent node associated with the IAB node using the downlink periodic resources.Transmitting component 2606 can transmit downlink traffic to a child node associated with the IAB node using the downlink periodic resources.

[0362] Receiving component 2602 may receive an indication of a periodicity associated with the downlink periodic resources and an offset value associated with the downlink periodic resources.Transmitting component 2606 may communicate an indication of a processing capability associated with the wireless node to a control node.

[0363] Figure 26 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 26 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 26 Two or more components shown in the figure may be implemented in a single component, or Figure 26 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 26 The component set (e.g., one or more components) shown in FIG can perform the operations described as being performed by Figure 26 One or more functions performed by another set of components shown in .

[0364] Figure 272 is a block diagram of an example device 2700 for wireless communication according to the present disclosure. The device 2700 can be a control node (such as an IAB donor or a CU of an IAB donor), or the control node can include the device 2700. In some aspects, the device 2700 includes a receiving component 2702, a communication manager 2704, and a transmission component 2706, which can communicate with each other (e.g., via one or more buses). As shown, the device 2700 can use the receiving component 2702 and the transmission component 2706 to communicate with another device 2708 (such as a UE, a base station, or another wireless communication device).

[0365] In some aspects, the device 2700 may be configured to perform Figure 9-15 Additionally or alternatively, the device 2700 may be configured to perform one or more of the processes described herein (such as Figure 19 In some aspects, the apparatus 2700 may include the above combined Figure 2 Describes one or more components of a control node.

[0366] The receiving component 2702 may receive communications (such as reference signals, control information, data communications, or a combination thereof) from the device 2708. The receiving component 2702 may provide the received communications to one or more other components of the device 2700 (such as the communication manager 2704). In some aspects, the receiving component 2702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 2702 may include a combination of the above. Figure 2 The described control node may include one or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0367] The transmission component 2706 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 2708. In some aspects, the communication manager 2704 may generate communications and may transmit the generated communications to the transmission component 2706 for transmission to the device 2708. In some aspects, the transmission component 2706 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and may transmit the processed signals to the device 2708. In some aspects, the transmission component 2706 may include a combination of the above. Figure 2The described control node's one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof. In some aspects, transmitting component 2706 can be co-located with receiving component 2702 in a transceiver.

[0368] The communication manager 2704 may determine grant information for downlink periodic resources for one or more wireless nodes included in the multi-hop network, the grant information indicating a resource location associated with the downlink periodic resources. In some aspects, the communication manager 2704 may or may cause the transmission component 2706 to transmit a configuration indicating the grant information to the one or more wireless nodes. In some aspects, the communication manager 2704 may include the above in combination with Figure 2 The described controller / processor, memory, scheduler, communication unit, or combination thereof, of a control node.

[0369] In some aspects, the communication manager 2704 may include a component set, such as a grant information determining component 2710, etc. Alternatively, the component set may be separate and distinct from the communication manager 2704. In some aspects, one or more components of the component set may include or may be combined with the above. Figure 2 The described control node is implemented within a controller / processor, memory, scheduler, communication unit, or a combination thereof. Additionally or alternatively, one or more components in the component set can be implemented at least in part as software stored in the memory. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0370] Grant information determining component 2710 can determine grant information for downlink periodic resources for one or more wireless nodes included in a multi-hop network, indicating a resource location associated with the downlink periodic resources.

[0371] Transmitting component 2706 can transmit full grant information to each of the one or more wireless nodes, which enables the wireless node to use downlink periodic resources to convey periodic downlink communications without the need for an activation message. Grant information determining component 2710 can determine full grant information for each of the one or more wireless nodes.

[0372] Transmitting component 2706 may transmit, to each of the one or more wireless nodes, partial grant information indicating at least a resource location associated with a downlink periodic resource. Grant information determining component 2710 may determine partial grant information for each of the one or more wireless nodes. Grant information determining component 2710 may determine, for each of the one or more wireless nodes, grant information for the downlink periodic resource to be used by the wireless node.

[0373] Grant information determining component 2710 can determine, for each of the one or more wireless nodes, a resource location associated with a downlink periodic resource for the wireless node. Grant information determining component 2710 can determine a periodicity associated with the downlink periodic resource. Grant information determining component 2710 can determine an offset value associated with the downlink periodic resource.

[0374] Transmitting component 2706 may transmit an indication of a periodicity associated with the downlink periodic resource and an offset value associated with the downlink periodic resource to a wireless node of the one or more wireless nodes.

[0375] Grant information determining component 2710 can determine grant information for each wireless node of the one or more wireless nodes based at least in part on at least one of a traffic pattern of the wireless node, a duplex communication mode capability of the wireless node, an IAB resource type pattern of the wireless node, an average link quality associated with the wireless node, a processing capability of the wireless node, or a latency requirement of the wireless node. Receiving component 2702 can receive, from a wireless node of the one or more wireless nodes, an indication of the processing capability of the wireless node.

[0376] Grant information determining component 2710 can determine, for a wireless node among the one or more wireless nodes, grant information indicating a resource location for downlink periodic resources associated with an MT component of the wireless node and to be used by the wireless node to receive periodic downlink communications. Grant information determining component 2710 can determine, for a wireless node among the one or more wireless nodes, grant information indicating a resource location for downlink periodic resources associated with a DU of the wireless node and to be used by the wireless node to transmit periodic downlink communications.

[0377] Figure 27 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 27 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 27Two or more components shown in the figure may be implemented in a single component, or Figure 27 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 27 The component set (e.g., one or more components) shown in FIG can perform the operations described as being performed by Figure 27 One or more functions performed by another set of components shown in .

[0378] Figure 28 2 is a block diagram of an example device 2800 for wireless communication according to the present disclosure. Device 2800 can be a node (such as an IAB node), or a node can include device 2800. The node can be an IAB node, an IAB donor, or a parent node. In some aspects, device 2800 includes a receiving component 2802, a communication manager 2804, and a transmission component 2806, which can communicate with each other (e.g., via one or more buses). As shown, device 2800 can use receiving component 2802 and transmission component 2806 to communicate with another device 2808 (such as a UE, a base station, or another wireless communication device).

[0379] In some aspects, the device 2800 may be configured to perform Figure 9-15 Additionally or alternatively, the device 2800 may be configured to perform one or more of the processes described herein (such as Figure 20 The process of 2000, Figure 21 Process 2100, Figure 22 In some aspects, the apparatus 2800 may include the above combined Figure 2 One or more components of a wireless node are described.

[0380] The receiving component 2802 may receive communications (such as reference signals, control information, data communications, or a combination thereof) from the device 2808. The receiving component 2802 may provide the received communications to one or more other components of the equipment 2800 (such as the communication manager 2804). In some aspects, the receiving component 2802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 2802 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described wireless nodes.

[0381] The transmission component 2806 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 2808. In some aspects, the communication manager 2804 may generate communications and may transmit the generated communications to the transmission component 2806 for transmission to the device 2808. In some aspects, the transmission component 2806 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and may transmit the processed signals to the device 2808. In some aspects, the transmission component 2806 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described wireless nodes. In some aspects, transmitting component 2806 can be co-located with receiving component 2802 in a transceiver.

[0382] The communication manager 2804 may receive, or may cause the receiving component 2802 to receive, a priority flag associated with a periodic resource set, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set. In some aspects, the communication manager 2804 may communicate (e.g., transmit or receive), or may cause the receiving component 2802 to receive, or may cause the transmitting component 2806 to transmit, communications with a child node of the IAB node or a parent node of the IAB node based at least in part on the priority flag associated with the periodic resource set. In some aspects, the communication manager 2804 may include the above in combination with Figure 2 A controller / processor, memory, scheduler, communication unit, or combination thereof of the described wireless nodes.

[0383] In some aspects, the communication manager 2804 may include a component set, such as an association component 2810 or an adjustment component 2812, etc. Alternatively, the component set may be separate and distinct from the communication manager 2804. In some aspects, one or more components in the component set may include or may be combined with the above. Figure 2 The described wireless node is implemented within a controller / processor, memory, scheduler, communication unit, or a combination thereof. Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in the memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0384] Receiving component 2802 may receive the priority flag via a radio resource control message from a central unit of an IAB donor associated with the IAB node. Receiving component 2802 may receive the priority flag via an F1 application protocol message from a central unit of an IAB donor associated with the IAB node. Receiving component 2802 may receive the priority flag via a media access control-control element from a distributed unit of a parent node of the IAB node. Receiving component 2802 may receive the priority flag via an activate downlink control message from a distributed unit of a parent node of the IAB node.

[0385] Transmitting component 2806 can perform the communication using a periodic resource set at a radio link control channel associated with the IAB node. Transmitting component 2806 can transmit information associated with a periodic resource set available to the IAB node regardless of resource type to the parent node to enable adjustment of resource allocation at the parent node. Transmitting component 2806 can transmit the information via a medium access control-control element.

[0386] The associating component 2810 can associate a priority flag with a periodic resource set. In some aspects, the associating component 2810 can include a combination of the above Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described nodes.

[0387] Transmitting component 2806 can transmit a priority flag associated with the periodic resource set from the IAB donor to the IAB node, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set. Transmitting component 2806 can transmit the priority flag via a radio resource control message from the central unit of the IAB donor. Transmitting component 2806 can transmit the priority flag via an F1 application protocol message from the central unit of the IAB donor. Transmitting component 2806 can transmit information associated with the periodic resource set allocated to the IAB node with the priority flag to a parent node of the IAB node.

[0388] Associating component 2810 can associate a priority flag with a periodic resource set. Transmitting component 2806 can transmit a priority flag associated with the periodic resource set from a parent node to an IAB node, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set. Transmitting component 2806 can transmit the priority flag via a media access control-control element from a distributed unit of the parent node. Transmitting component 2806 can transmit the priority flag via an activation downlink control message from a distributed unit of the parent node.

[0389] Receiving component 2802 can receive information associated with a periodic set of resources available to the IAB node regardless of resource type from the IAB node. Receiving component 2802 can receive the information from the IAB node via a medium access control-control element. Receiving component 2802 can receive the information from a central unit of the IAB donor via an F1 application protocol message or a radio resource control message.

[0390] Adjustment component 2812 can adjust resource allocation based at least in part on information received from the IAB node. In some aspects, adjustment component 2812 can include the above combination Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described nodes.

[0391] Figure 28 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 28 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 28 Two or more components shown in the figure may be implemented in a single component, or Figure 28 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 28 The component set (e.g., one or more components) shown in FIG can perform the operations described as being performed by Figure 28 One or more functions performed by another set of components shown in .

[0392] Figure 29 2 is a block diagram of an example device 2900 for wireless communication according to the present disclosure. Device 2900 can be a node (such as an IAB node), or a node can include device 2900. The node can be an IAB node, an IAB donor, or a parent node. In some aspects, device 2900 includes a receiving component 2902, a communication manager 2904, and a transmission component 2906, which can communicate with each other (e.g., via one or more buses). As shown, device 2900 can use receiving component 2902 and transmission component 2906 to communicate with another device 2908 (such as a UE, a base station, or another wireless communication device).

[0393] In some aspects, the device 2900 may be configured to perform Figure 9-15 Additionally or alternatively, the device 2900 may be configured to perform one or more of the processes described herein (such as Figure 23 In some aspects, the apparatus 2900 may include the above combined Figure 2 One or more components of a wireless node are described.

[0394] The receiving component 2902 may receive communications (such as reference signals, control information, data communications, or a combination thereof) from the device 2908. The receiving component 2902 may provide the received communications to one or more other components of the device 2900, such as the communications manager 2904. In some aspects, the receiving component 2902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 2902 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described wireless nodes.

[0395] The transmission component 2906 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 2908. In some aspects, the communication manager 2904 may generate communications and may transmit the generated communications to the transmission component 2906 for transmission to the device 2908. In some aspects, the transmission component 2906 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and may transmit the processed signals to the device 2908. In some aspects, the transmission component 2906 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described wireless nodes. In some aspects, the transmitting component 2906 can be co-located with the receiving component 2902 in a transceiver.

[0396] The communication manager 2904 may receive, or may cause the receiving component 2902 to receive, an indication of a first periodic resource associated with a wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. In some aspects, the communication manager 2904 may communicate (e.g., transmit or receive) using the modified first periodic resource, or may cause the receiving component 2902 to receive, or may cause the transmitting component 2906 to transmit, a message, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource. In some aspects, the communication manager 2904 may include the above in combination with Figure 2A controller / processor, memory, scheduler, communication unit, or combination thereof of the described wireless nodes.

[0397] In some aspects, the communication manager 2904 may include a component set, such as a resource modification component 2910, etc. Alternatively, the component set may be separate and distinct from the communication manager 2904. In some aspects, one or more components of the component set may include or may be combined with the above. Figure 2 The described wireless node is implemented within a controller / processor, memory, scheduler, communication unit, or a combination thereof. Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in the memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0398] Receiving component 2902 can receive an indication of a first periodic resource associated with a wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource. Receiving component 2902 or transmitting component 2906 can communicate (e.g., receive or transmit) a message using the modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

[0399] Resource modifying component 2910 can modify the first periodic resource based at least in part on the one or more parameters or priority flags.

[0400] Figure 29 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 29 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 29 Two or more components shown in the figure may be implemented in a single component, or Figure 29 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 29 The component set (e.g., one or more components) shown in FIG can perform the operations described as being performed by Figure 29 One or more functions performed by another set of components shown in .

[0401] The following provides an overview of some aspects of the disclosure:

[0402] Aspect 1: A wireless communication method performed by a wireless node, comprising: receiving an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters or a priority flag for coordinating periodic resources, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource; and using a modified first periodic resource to communicate a message with a child node or another wireless node, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

[0403] Aspect 2: The method of aspect 1 further comprises: transmitting an activation message associated with the first periodic resource to the child node, the activation message indicating a modified resource allocation associated with the first periodic resource.

[0404] Aspect 3: A method as in any of Aspects 1-2, wherein the first periodic resource is associated with a distributed unit (DU) of the wireless node, and wherein one or more parameters for coordinating the periodic resource are associated with coordinating the first periodic resource and a second periodic resource, the second periodic resource is associated with a mobile terminal (MT) component of the wireless node and corresponds to the first periodic resource, and wherein communicating using the modified first periodic resource is at least partially based on the first periodic resource not satisfying at least one of the one or more parameters.

[0405] Aspect 4: A method as described in any of Aspects 1-3, wherein the one or more parameters include at least one of the following: a time gap between periodic resources associated with a mobile terminal (MT) component of a wireless node and periodic resources associated with a distributed unit (DU) of the wireless node, or a time gap range between periodic resources associated with the MT component and periodic resources associated with the DU.

[0406] Aspect 5: The method according to any one of aspects 1-4, further comprising: receiving an indication of the one or more parameters from a control node or a parent node; or determining the one or more parameters.

[0407] Aspect 6: A method as in any of Aspects 1-5, wherein the one or more parameters are based at least in part on at least one of: a processing capability of the wireless node, a waiting time requirement associated with the wireless node, or a packet delay budget (PDB) of a radio link control (RLC) channel associated with the first periodic resource or the second periodic resource.

[0408] Aspect 7: The method of any of Aspects 1-6 further includes: transmitting an indication of information to be used to determine the one or more parameters to a control node or a parent node; and receiving an indication of the one or more parameters from the control node or the parent node based at least in part on transmitting the indication of information to be used to determine the one or more parameters.

[0409] Aspect 8: The method of any one of Aspects 1-7 further includes: receiving a priority flag from a control node or a parent node via at least one of a radio resource control message, an F1 application protocol message, a medium access control (MAC) control element (MAC-CE), or activation downlink control information.

[0410] Aspect 9: The method according to any one of aspects 1-8, wherein the first periodic resources include one or more downlink resources allocated via downlink semi-persistent scheduling or one or more uplink resources allocated via uplink configured grant.

[0411] Aspect 10: The method of any one of aspects 1-9, wherein the resource type comprises a configured distributed unit resource type, a not available (NA) resource type, a hard resource type, or a soft resource type.

[0412] Aspect 11: The method of any of aspects 1-10, further comprising: transmitting information associated with the first periodic resources available to the wireless node regardless of resource type to a control node or parent node to enable adjustment of resource allocation at the control node or parent node.

[0413] Aspect 12: The method according to any one of aspects 1-11, wherein receiving the indication of the first periodic resource comprises receiving a configuration indicating grant information for the first periodic resource from a control node, the grant information indicating a resource location associated with the first periodic resource.

[0414] Aspect 13: The method of aspect 12, wherein receiving a configuration indicating grant information for the first periodic resource (which indicates a resource location associated with the first periodic resource) includes receiving a configuration indicating full grant information.

[0415] Aspect 14: A method as in Aspect 13, wherein the full grant information indicates at least: a resource location associated with the first periodic resource, a modulation and coding scheme (MCS) associated with the first periodic resource, a frequency domain resource block (RB) allocation associated with the first periodic resource, and an antenna port of the wireless node associated with the first periodic resource.

[0416] Aspect 15: A method as described in any of Aspects 12-14, wherein receiving a configuration indicating grant information for a first periodic resource (which indicates a resource location associated with the first periodic resource) includes receiving a configuration indicating partial grant information, which partial grant information at least indicates a resource location associated with the first periodic resource.

[0417] Aspect 16: A wireless communication method performed by a wireless node, comprising: receiving an activation message for activating a first periodic resource associated with a mobile terminal (MT) component of the wireless node; identifying one or more parameters for coordinating periodic resources associated with the MT component of the wireless node, including the first periodic resource, with periodic resources associated with a distributed unit (DU) of the wireless node, including a second periodic resource; determining whether the second periodic resource satisfies the one or more parameters; and modifying a resource allocation associated with the second periodic resource based at least in part on determining that the second periodic resource does not satisfy at least one of the one or more parameters.

[0418] Aspect 17: The method of Aspect 16, further comprising: transmitting an activation message associated with the second periodic resource to the child node, the activation message indicating a modified resource allocation associated with the second periodic resource.

[0419] Aspect 18: The method of any one of aspects 16-17, wherein both the first periodic resource and the second periodic resource are downlink semi-persistent scheduling (SPS) resources or both are uplink configured grant resources.

[0420] Aspect 19: The method of any one of aspects 16-18, wherein the first periodic resource or the second periodic resource is associated with a radio link control (RLC) channel carrying low-latency traffic.

[0421] Aspect 20: A method as in any one of Aspects 16-19, wherein the one or more parameters include at least one of the following: a time gap between the periodic resources associated with the MT component and the periodic resources associated with the DU, or a time gap range between the periodic resources associated with the MT component and the periodic resources associated with the DU.

[0422] Aspect 21: The method of aspect 20, wherein the time gap is based at least in part on a processing capability of the wireless node.

[0423] Aspect 22: The method of any of Aspects 16-21, wherein identifying one or more parameters for coordinating periodic resources of an MT component associated with the wireless node and periodic resources of a DU associated with the wireless node comprises receiving an indication of the one or more parameters from a control node.

[0424] Aspect 23: The method of aspect 22, wherein receiving an indication of the one or more parameters from the control node comprises receiving an indication of the one or more parameters via a radio resource control (RRC) message or an F1 application protocol (F1-AP) message.

[0425] Aspect 24: The method according to any one of aspects 22-23, wherein the control node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor.

[0426] Aspect 25: The method of any of aspects 16-24, wherein identifying one or more parameters for coordinating periodic resources of an MT component associated with the wireless node and periodic resources of a DU associated with the wireless node comprises receiving an indication of the one or more parameters from a parent node.

[0427] Aspect 26: The method of Aspect 25, wherein receiving an indication of the one or more parameters from the parent node comprises receiving an indication of the one or more parameters via a downlink control information (DCI) message or a media access control (MAC) control element (MAC-CE) message.

[0428] Aspect 27: The method of any one of Aspects 25-26, wherein receiving an indication of the one or more parameters from the parent node comprises receiving an indication of the one or more parameters in an activation message.

[0429] Aspect 28: The method according to any one of aspects 25-27, wherein the parent node is a DU of an integrated access and backhaul (IAB) node.

[0430] Aspect 29: The method of any of Aspects 16-28, wherein identifying one or more parameters for coordinating periodic resources of an MT component associated with the wireless node and periodic resources of a DU associated with the wireless node comprises determining the one or more parameters.

[0431] Aspect 30: The method of aspect 29, further comprising: transmitting an indication of the one or more parameters to a parent node associated with the wireless node.

[0432] Aspect 31: A method as in Aspect 30, wherein transmitting an indication of the one or more parameters to a parent node associated with the wireless node includes transmitting an indication of the one or more parameters via a medium access control (MAC) control element (MAC-CE) message or an uplink control information (UCI) message.

[0433] Aspect 32: A method as in any of Aspects 29-31, wherein determining the one or more parameters comprises determining the one or more parameters based at least in part on at least one of: a processing capability of the wireless node, a waiting time requirement associated with the wireless node, or a packet delay budget (PDB) of a radio link control (RLC) channel associated with the first periodic resource or the second periodic resource.

[0434] Aspect 33: The method of any of Aspects 16-32, further comprising: transmitting an indication of information to be used to determine the one or more parameters to a control node or a parent node.

[0435] Aspect 34: A method as in Aspect 33, wherein the information used to determine the one or more parameters includes at least one of: a processing capability of the wireless node, a waiting time requirement associated with the wireless node, or a packet delay budget (PDB) of a radio link control (RLC) channel associated with the first periodic resource or the second periodic resource.

[0436] Aspect 35: The method of any of Aspects 33-34, further comprising: receiving an indication of the one or more parameters from a control node or a parent node, the one or more parameters being based at least in part on information to be used to determine the one or more parameters.

[0437] Aspect 36: The method of any of Aspects 16-35, wherein receiving an activation message for activating a first periodic resource associated with the MT component of the wireless node comprises identifying a second periodic resource corresponding to the first periodic resource.

[0438] Aspect 37: The method of any one of aspects 16-36, wherein determining whether the second periodic resource satisfies the one or more parameters comprises determining whether a resource allocation associated with the second periodic resource satisfies the one or more parameters.

[0439] Aspect 38: The method of any of Aspects 16-37, further comprising: receiving an indication of a scheduling gap indicating an amount of time between the activation message and the first periodic resource.

[0440] Aspect 39: The method of aspect 38, wherein determining whether the second periodic resource satisfies the one or more parameters comprises determining whether the second periodic resource satisfies the one or more parameters during a scheduling gap.

[0441] Aspect 40: A method as in any of Aspects 38-39, wherein receiving an indication of a scheduling gap indicating an amount of time between the activation message and the first periodic resource includes receiving an indication of the scheduling gap from a control node via a radio resource control (RRC) message or an F1 application protocol (F1-AP) message.

[0442] Aspect 41: A method as in any of Aspects 38-40, wherein receiving an indication of a scheduling gap indicating an amount of time between an activation message and a first periodic resource includes receiving an indication of the scheduling gap from a parent node via a downlink control information (DCI) message or a media access control (MAC) control element (MAC-CE) message.

[0443] Aspect 42: The method of any of Aspects 16-41, further comprising: receiving, by the MT component, a first communication from a parent node using a first periodic resource; and transmitting, by the DU, a second communication associated with the first communication to a child node using a second periodic resource.

[0444] Aspect 43: The method of any of Aspects 16-42, further comprising: receiving, by the DU, a first communication from the child node using the second periodic resource; and transmitting, by the MT component, a second communication associated with the first communication to the parent node using the first periodic resource.

[0445] Aspect 44: A wireless communication method performed by a wireless node, comprising: determining one or more parameters for coordinating periodic resources of a mobile terminal (MT) component associated with a different wireless node and periodic resources of a distributed unit (DU) associated with the different wireless node; and transmitting an indication of the one or more parameters to the different wireless node.

[0446] Aspect 45: The method of aspect 44, wherein the wireless node is a central unit (CU) of an integrated access and backhaul (IAB) donor or a DU of an IAB node.

[0447] Aspect 46: A method as described in any of Aspects 44-45, wherein determining one or more parameters for coordinating the periodic resources of the MT component associated with the different wireless node and the periodic resources of the DU associated with the different wireless node includes determining at least one of the following: a time gap between the periodic resources of the MT component associated with the different wireless node and the periodic resources associated with the DU of the different wireless node, or a time gap range between the periodic resources of the MT component associated with the different wireless node and the periodic resources associated with the DU of the different wireless node.

[0448] Aspect 47: A method as in any of Aspects 44-46, wherein determining one or more parameters for coordinating the periodic resources of the MT component associated with the different wireless node and the periodic resources of the DU associated with the different wireless node includes determining the one or more parameters based at least in part on information including at least one of: a processing capability of the different wireless node, a waiting time requirement associated with the different wireless node, or a packet delay budget (PDB) of a radio link control (REC) channel associated with the periodic resources of the MT component associated with the different wireless node or the periodic resources of the DU associated with the different wireless node.

[0449] Aspect 48: The method of any of Aspect 47, further comprising: receiving from the different wireless node an indication of at least one of: a processing capability of the different wireless node, or a latency requirement associated with the different wireless node.

[0450] Aspect 49: The method of any one of aspects 44-48, wherein transmitting the indication of the one or more parameters comprises transmitting the indication of the one or more parameters via a radio resource control (RRC) message or an F1 application protocol (F1-AP) message.

[0451] Aspect 50: The method of any one of aspects 44-48, wherein transmitting the indication of the one or more parameters comprises transmitting the indication of the one or more parameters via a downlink control information (DCI) message or a medium access control (MAC) control element (MAC-CE) message.

[0452] Aspect 51: The method of any of Aspects 44-50, further comprising: determining a scheduling gap indicating an amount of time between an activation message for activating a periodic resource of an MT component associated with the different wireless node and the periodic resource; and transmitting an indication of the scheduling gap to the different wireless node.

[0453] Aspect 52: The method of any of Aspects 44-51, further comprising: transmitting an activation message to the different wireless node for activating periodic resources associated with the MT component of the different wireless node.

[0454] Aspect 53: The method of Aspect 52, further comprising: transmitting communications to the different wireless node during the periodic resources, wherein the communications are to be forwarded by the different wireless node to a child node associated with the different wireless node.

[0455] Aspect 54: The method of any of Aspects 52-53, further comprising: receiving a communication from the different wireless node during the periodic resources, wherein the communication is associated with a communication to be forwarded by the different wireless node from a child node associated with the different wireless node to the wireless node.

[0456] Aspect 55: The method of any of Aspects 44-54, wherein transmitting an indication of the one or more parameters to the different wireless node comprises transmitting an indication of the one or more parameters to a parent node associated with the different wireless node.

[0457] Aspect 56: A wireless communication method performed by a wireless node, comprising: receiving a configuration indicating grant information for a downlink periodic resource from a control node, the grant information indicating a resource location associated with the downlink periodic resource; and using the downlink periodic resource to convey downlink traffic according to the grant information.

[0458] Aspect 57: A method as in Aspect 56, wherein receiving a configuration indicating grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) includes receiving a configuration indicating full grant information; and wherein using the downlink periodic resources to convey downlink traffic according to the grant information includes: using the downlink periodic resources to convey downlink traffic without receiving or transmitting an activation message associated with the downlink periodic resources.

[0459] Aspect 58: A method as in Aspect 57, wherein the full grant information indicates at least: a resource location associated with the downlink periodic resource, a modulation and coding scheme (MCS) associated with the downlink periodic resource, a frequency domain resource block (RB) allocation associated with the downlink periodic resource, and an antenna port of the wireless node associated with the downlink periodic resource.

[0460] Aspect 59: A method as described in any of Aspects 56-58, wherein receiving a configuration indicating grant information for a downlink periodic resource (which indicates a resource location associated with the downlink periodic resource) includes receiving a configuration indicating partial grant information, which partial grant information at least indicates a resource location associated with the downlink periodic resource.

[0461] Aspect 60: A method as in Aspect 59, wherein using downlink periodic resources to convey downlink traffic based on grant information includes: transmitting or receiving an activation message indicating remaining grant information associated with the downlink periodic resources; and using downlink periodic resources to convey downlink traffic based on partial grant information and remaining grant information.

[0462] Aspect 61: A method as in Aspect 60, wherein the remaining grant information associated with the downlink periodic resource indicates at least one of: a modulation and coding scheme (MCS) associated with the downlink periodic resource, a frequency domain resource block (RB) allocation associated with the downlink periodic resource, an antenna port of the wireless node associated with the downlink periodic resource, or a redundancy version (RV) associated with the downlink periodic resource.

[0463] Aspect 62: The method of any of Aspects 56-61, wherein the control node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor.

[0464] Aspect 63: A method as in any of Aspects 56-62, wherein the wireless node is an integrated access and backhaul (IAB) node and the downlink periodic resources are associated with a mobile terminal (MT) component of the wireless node; and wherein using the downlink periodic resources to convey downlink traffic according to the grant information includes: receiving the downlink traffic from a parent node associated with the wireless node using the downlink periodic resources.

[0465] Aspect 64: A method as in any of Aspects 56-62, wherein the wireless node is an integrated access and backhaul (IAB) node and the downlink periodic resources are associated with a distributed unit (DU) of the wireless node; and wherein using the downlink periodic resources to convey downlink traffic according to the grant information includes: using the downlink periodic resources to transmit the downlink traffic to a subnode associated with the wireless node.

[0466] Aspect 65: The method of any of Aspects 56-64, wherein receiving a configuration indicating grant information comprises receiving an indication of a periodicity associated with the downlink periodic resource and an offset value associated with the downlink periodic resource.

[0467] Aspect 66: The method of any of Aspects 56-65, further comprising: transmitting an indication of a processing capability associated with the wireless node to a control node.

[0468] Aspect 67: A wireless communication method performed by a control node, comprising: determining grant information for downlink periodic resources for one or more wireless nodes included in a multi-hop network, the grant information indicating a resource location associated with the downlink periodic resources; and transmitting a configuration indicating the grant information to the one or more wireless nodes.

[0469] Aspect 68: The method of aspect 67, wherein transmitting a configuration indicating the grant information comprises transmitting full grant information to each of the one or more wireless nodes, which enables the wireless node to use downlink periodic resources to convey periodic downlink communications without requiring an activation message.

[0470] Aspect 69: A method as in Aspect 68, wherein determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining full grant information for each wireless node in the one or more wireless nodes.

[0471] Aspect 70: The method of any of aspects 67-69, wherein transmitting the configuration indicative of the grant information comprises transmitting, to each of the one or more wireless nodes, partial grant information indicative of at least a resource location associated with the downlink periodic resource.

[0472] Aspect 71: A method as in Aspect 70, wherein determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining partial grant information for each wireless node in the one or more wireless nodes.

[0473] Aspect 72: A method as in Aspect 71, wherein determining partial grant information for each wireless node of the one or more wireless nodes includes determining at least one of: a modulation and coding scheme (MCS) associated with a downlink periodic resource, a frequency domain resource block (RB) allocation associated with the downlink periodic resource, an antenna port of the wireless node associated with the downlink periodic resource, or a redundancy version (RV) associated with the downlink periodic resource.

[0474] Aspect 73: A method as described in any of Aspects 67-72, wherein determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining grant information for downlink periodic resources to be used by each wireless node in the one or more wireless nodes.

[0475] Aspect 74: The method of any of Aspects 67-73, wherein the one or more wireless nodes are included in a communication path for periodic multi-hop downlink communication.

[0476] Aspect 75: The method of aspect 74, wherein the communication path comprises one or more radio link control (RLC) channels associated with low-latency traffic.

[0477] Aspect 76: A method as described in any of Aspects 67-75, wherein determining grant information (which indicates a resource location associated with the downlink periodic resource) for one or more wireless nodes included in a multi-hop network includes determining a resource location associated with the downlink periodic resource for each wireless node in the one or more wireless nodes.

[0478] Aspect 77: A method as in Aspect 76, wherein determining a resource location associated with a downlink periodic resource for each of the one or more wireless nodes includes: determining a periodicity associated with the downlink periodic resource; and determining an offset value associated with the downlink periodic resource.

[0479] Aspect 78: The method of aspect 77, wherein transmitting a configuration indicating the grant information comprises transmitting an indication of a periodicity associated with the downlink periodic resource and an offset value associated with the downlink periodic resource to a wireless node among the one or more wireless nodes.

[0480] Aspect 79: A method as in any of Aspects 67-78, wherein determining grant information for downlink periodic resources (indicating a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining the grant information for each of the one or more wireless nodes based at least in part on at least one of: a traffic pattern of the wireless node, a duplex communication mode capability of the wireless node, an integrated access and backhaul (IAB) resource type pattern of the wireless node, an average link quality associated with the wireless node, a processing capability of the wireless node, or a waiting time requirement of the wireless node.

[0481] Aspect 80: The method of aspect 79, further comprising: receiving an indication of a processing capability of a wireless node from the one or more wireless nodes.

[0482] Aspect 81: The method of any of aspects 67-80, wherein the control node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor.

[0483] Aspect 82: A method as described in any of Aspects 67-81, wherein determining grant information for downlink periodic resources (which indicates a resource location associated with the downlink periodic resources) for one or more wireless nodes included in a multi-hop network includes determining grant information indicating a resource location for the downlink periodic resources for a wireless node among the one or more wireless nodes, which is associated with a mobile terminal (MT) component of the wireless node and is used by the wireless node to receive periodic downlink communications.

[0484] Aspect 83: A method as described in any of Aspects 67-82, wherein determining grant information (which indicates a resource location associated with the downlink periodic resource) for one or more wireless nodes included in a multi-hop network includes determining grant information indicating a resource location for the downlink periodic resource for a wireless node among the one or more wireless nodes, which is associated with a distributed unit (DU) of the wireless node and is used by the wireless node to transmit periodic downlink communications.

[0485] Aspect 84: A wireless communication method performed by an integrated access and backhaul (IAB) node, comprising: receiving a priority flag associated with a periodic resource set, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set; and using the periodic resource set to perform communication with a child node of the IAB node or a parent node of the IAB node based at least in part on the priority flag associated with the periodic resource set.

[0486] Aspect 85: The method of aspect 84, wherein receiving the priority flag comprises receiving the priority flag via a radio resource control message from a central unit of an IAB donor associated with the IAB node.

[0487] Aspect 86: The method of any of Aspects 84-85, wherein receiving the priority flag comprises receiving the priority flag via an F1 Application Protocol message from a central unit of an IAB donor associated with the IAB node.

[0488] Aspect 87: The method according to any one of aspects 84-86, wherein receiving the priority flag comprises receiving the priority flag via a media access control-control element from a distributed unit of a parent node of the IAB node.

[0489] Aspect 88: The method according to any one of aspects 84-87, wherein receiving the priority flag comprises receiving the priority flag via an activation downlink control message from a distributed unit of a parent node of the IAB node.

[0490] Aspect 89: The method of any one of aspects 84-88, wherein the periodic resource set comprises downlink resources allocated via downlink semi-persistent scheduling.

[0491] Aspect 90: The method of any of aspects 84-89, wherein the periodic resource set comprises uplink resources allocated via an uplink configured grant.

[0492] Aspect 91: The method according to any one of aspects 84-90, wherein the periodic resource set is available to a mobile terminal or a distributed unit of an IAB node.

[0493] Aspect 92: The method of any of Aspects 84-91, wherein the resource type associated with the individual resource is a configured distributed unit resource type.

[0494] Aspect 93: The method of any of Aspects 84-92, wherein the resource type associated with the individual resource is a not available (NA) resource type, a hard resource type, or a soft resource type.

[0495] Aspect 94: The method of any of Aspects 84-93, wherein the communication is associated with periodic low-latency traffic.

[0496] Aspect 95: The method of any of aspects 84-94, wherein performing the communication comprises performing the communication using a periodic set of resources at a radio link control channel associated with the IAB node.

[0497] Aspect 96: The method of any of Aspects 84-95, further comprising: transmitting information associated with a set of periodic resources available to the IAB node regardless of resource type to a parent node of the IAB node to enable adjustment of resource allocation at the parent node.

[0498] Aspect 97: The method of Aspect 96, wherein transmitting the information comprises transmitting the information via a medium access control-control element.

[0499] Aspect 98: A wireless communication method performed by an integrated access and backhaul (IAB) donor, comprising: associating a priority flag with a periodic resource set; and transmitting the priority flag associated with the periodic resource set from the IAB donor to an IAB node, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set.

[0500] Aspect 99: The method of aspect 98, wherein transmitting the priority flag comprises transmitting the priority flag via a radio resource control message from a central unit of the IAB donor.

[0501] Aspect 100: The method of any of Aspects 98-99, wherein transmitting the priority flag comprises transmitting the priority flag via an F1 Application Protocol message from a central unit of the IAB donor.

[0502] Aspect 101: The method of any one of aspects 98-100, wherein the periodic resource set comprises downlink resources allocated via downlink semi-persistent scheduling.

[0503] Aspect 102: The method of any of aspects 98-101, wherein the periodic resource set comprises uplink resources allocated via an uplink configured grant.

[0504] Aspect 103: The method according to any one of aspects 98-102, wherein the periodic resource set is available to a mobile terminal or a distributed unit of an IAB node.

[0505] Aspect 104: The method of any one of Aspects 98-103, wherein the resource type associated with the individual resource is a configured distributed unit resource type.

[0506] Aspect 105: The method of any of Aspects 98-104, wherein the resource type associated with the individual resource is a not available (NA) resource type, a hard resource type, or a soft resource type.

[0507] Aspect 106: The method according to any one of aspects 98-105, further comprising: transmitting information associated with the periodic resource set with the priority flag allocated to the IAB node to a parent node of the IAB node.

[0508] Aspect 107: A wireless communication method performed by a parent node, comprising: associating a priority flag with a periodic resource set; and transmitting the priority flag associated with the periodic resource set from the parent node to an integrated access and backhaul (IAB) node, wherein the priority flag indicates that the periodic resource set is available to the IAB node regardless of the resource type associated with the individual resources included in the periodic resource set.

[0509] Aspect 108: The method of aspect 107, wherein transmitting the priority flag comprises transmitting the priority flag via a medium access control-control element from a distributed unit of a parent node.

[0510] Aspect 109: The method according to any one of aspects 107-108, wherein transmitting the priority flag comprises transmitting the priority flag via an activation downlink control message of a distributed unit from a parent node.

[0511] Aspect 110: The method of any of Aspects 107-109, further comprising: receiving from the IAB node information associated with a set of periodic resources available to the IAB node regardless of resource type; and adjusting resource allocation based at least in part on the information received from the IAB node.

[0512] Aspect 111: The method according to any one of aspects 107-110, wherein receiving the information comprises receiving the information from an IAB node via a medium access control-control element.

[0513] Aspect 112: The method according to any of aspects 107-111, wherein receiving the information comprises receiving the information from a central unit of the IAB donor via an F1 application protocol message or a radio resource control message.

[0514] Aspect 113: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as in one or more of Aspects 1-15, 16-43, 56-66, and 84-97.

[0515] Aspect 114: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-15, 16-43, 56-66, and 84-97.

[0516] Aspect 115: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-15, 16-43, 56-66, and 84-97.

[0517] Aspect 116: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-15, 16-43, 56-66, and 84-97.

[0518] Aspect 117: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 1-15, 16-43, 56-66, and 84-97.

[0519] Aspect 118: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as in one or more of Aspects 44-55, 67-83, and 98-106.

[0520] Aspect 119: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more aspects of aspects 44-55, 67-83, and 98-106.

[0521] Aspect 120: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 44-55, 67-83, and 98-106.

[0522] Aspect 121: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 44-55, 67-83, and 98-106.

[0523] Aspect 122: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 44-55, 67-83, and 98-106.

[0524] Aspect 123: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as in one or more aspects of aspects 107-112.

[0525] Aspect 124: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more aspects of aspects 107-112.

[0526] Aspect 125: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 107-112.

[0527] Aspect 126: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 107-112.

[0528] Aspect 127: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 107-112.

[0529] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0530] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware, firmware, or hardware and software. As used herein, processor hardware, firmware, or a combination of hardware and software is implemented. It will be apparent that the system or method described herein can be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods does not limit various aspects. Thus, the operation and behavior of these systems or methods are described herein without reference to specific software code---it will be appreciated that software and hardware can be designed to implement these systems or methods at least in part based on the description herein.

[0531] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, and the like, depending on the context.

[0532] Although specific feature combinations are described in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner not specifically described in the claims or not disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in this group of claims. As used herein, the phrase quoting "at least one of" a column item refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to encompass: a, b, c, ab, ac, bc, and abc, and any combination with multiple identical elements (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other sorting of a, b and c).

[0533] The elements, actions or instructions used herein should not be interpreted as key or necessary unless explicitly described as such. Moreover, as used herein, the articles "one" and "a" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more projects quoted in conjunction with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set (set)" and "group" are intended to include one or more projects (for example, related items, non-related items or a combination of related items and non-related items), and can be used interchangeably with "one or more". In the occasion where it is intended to have only one project, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "having", "containing", "comprising" and similar terms are intended to be open terms. In addition, the phrase "based on" is intended to mean "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a sequence is intended to be inclusive and can be used interchangeably with "and / or" unless expressly stated otherwise (e.g., when used in conjunction with "either of" or "only one of").

Claims

1. A wireless node for wireless communication, comprising: at least one processor; as well as at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to cause the wireless node to: receiving an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource; as well as A message is communicated with a subnode or another wireless node using the modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

2. The wireless node of claim 1 , wherein the at least one memory further stores processor-readable code configured to cause the wireless node to transmit an activation message associated with the first periodic resource to the child node, the activation message indicating the modified resource allocation associated with the first periodic resource.

3. The wireless node of claim 1 , wherein the first periodic resource is associated with a distributed unit (DU) of the wireless node, and wherein the one or more parameters for coordinating periodic resources are associated with coordinating the first periodic resource and a second periodic resource, the second periodic resource being associated with a mobile terminal (MT) component of the wireless node and corresponding to the first periodic resource, and wherein communicating using the modified first periodic resource is based at least in part on the first periodic resource not satisfying at least one of the one or more parameters.

4. The wireless node of claim 1 , wherein the one or more parameters include at least one of: a time gap between a periodic resource associated with a mobile terminal (MT) component of the wireless node and a periodic resource associated with a distributed unit (DU) of the wireless node, or The time gap range between the periodic resources associated with the MT component and the periodic resources associated with the DU.

5. The wireless node of claim 1 , wherein the at least one memory further stores processor readable code configured to cause the wireless node to: receiving an indication of the one or more parameters from a control node or a parent node; or The one or more parameters are determined.

6. The wireless node of claim 1 , wherein the one or more parameters are based at least in part on at least one of: the processing capability of the wireless node, a latency requirement associated with the wireless node, or A packet delay budget (PDB) of a radio link control (RLC) channel associated with the first periodic resource or the second periodic resource.

7. The wireless node of claim 1 , wherein the at least one memory further stores processor readable code configured to cause the wireless node to: transmitting to a control node or parent node an indication of information to be used to determine the one or more parameters; and An indication of the one or more parameters is received from the control node or the parent node based at least in part on transmitting the indication of information to be used to determine the one or more parameters.

8. The wireless node of claim 1 , wherein the at least one memory further stores processor readable code configured to cause the wireless node to: The priority flag is received from a control node or a parent node via at least one of a radio resource control message, an F1 application protocol message, a medium access control (MAC) control element (MAC-CE), or an activation downlink control message.

9. The wireless node of claim 1, wherein the first periodic resources comprise one or more downlink resources allocated via downlink semi-persistent scheduling or one or more uplink resources allocated via uplink configured grant.

10. The wireless node of claim 1, wherein the resource type comprises a configured distributed unit resource type, a not available (NA) resource type, a hard resource type, or a soft resource type.

11. The wireless node of claim 1 , wherein the at least one memory further stores processor-readable code configured to cause the wireless node to transmit information associated with the first periodic resource available to the wireless node regardless of the resource type to a control node or a parent node to enable adjustment of the resource allocation at the control node or the parent node.

12. The wireless node of claim 1, wherein: In order to cause the wireless node to receive an indication of the first periodic resource, the processor-readable code, when executed by the at least one processor, is configured to cause the wireless node to receive a configuration indicating grant information for the first periodic resource from a control node, the grant information indicating a resource location associated with the first periodic resource.

13. The wireless node of claim 12, wherein: In order to cause the wireless node to receive a configuration indicating grant information for the first periodic resource, the grant information indicating a resource location associated with the first periodic resource, the processor-readable code, when executed by the at least one processor, is configured to cause the wireless node to receive a configuration indicating full grant information.

14. The wireless node of claim 13 , wherein the full grant information indicates at least: the resource location associated with the first periodic resource, a modulation and coding scheme (MCS) associated with the first periodic resource, a frequency domain resource block (RB) allocation associated with the first periodic resource, and An antenna port of the wireless node associated with the first periodic resource.

15. The wireless node of claim 12, wherein: In order to cause the wireless node to receive a configuration indicating grant information for the first periodic resource, the grant information indicating a resource location associated with the first periodic resource, the processor-readable code, when executed by the at least one processor, is configured to cause the wireless node to receive a configuration indicating partial grant information, the partial grant information indicating at least the resource location associated with the first periodic resource.

16. A wireless communication method performed by a wireless node, comprising: receiving an indication of a first periodic resource associated with the wireless node, wherein the first periodic resource is associated with one or more parameters for coordinating periodic resources or a priority flag, the priority flag indicating that the first periodic resource is available to the wireless node regardless of a resource type associated with the first periodic resource; as well as A message is communicated with a subnode or another wireless node using the modified first periodic resource, wherein the modified first periodic resource includes a modified resource allocation associated with the first periodic resource or a modified resource type associated with the first periodic resource.

17. The method of claim 16, further comprising transmitting an activation message associated with the first periodic resource to the child node, the activation message indicating the modified resource allocation associated with the first periodic resource.

18. The method of claim 16 , wherein the first periodic resource is associated with a distributed unit (DU) of the wireless node, and wherein the one or more parameters for coordinating periodic resources are associated with coordinating the first periodic resource with a second periodic resource, the second periodic resource being associated with a mobile terminal (MT) component of the wireless node and corresponding to the first periodic resource, and wherein communicating using the modified first periodic resource is based at least in part on the first periodic resource not satisfying at least one of the one or more parameters.

19. The method of claim 16, wherein the one or more parameters include at least one of: a time gap between a periodic resource associated with a mobile terminal (MT) component of the wireless node and a periodic resource associated with a distributed unit (DU) of the wireless node, or The time gap range between the periodic resources associated with the MT component and the periodic resources associated with the DU.

20. The method of claim 16, further comprising: receiving an indication of the one or more parameters from a control node or a parent node; or The one or more parameters are determined.

21. The method of claim 16, wherein the one or more parameters are based at least in part on at least one of: the processing capability of the wireless node, a latency requirement associated with the wireless node, or A packet delay budget (PDB) of a radio link control (RLC) channel associated with the first periodic resource or the second periodic resource.

22. The method of claim 16, further comprising: transmitting, to a control node or a parent node, an indication of information to be used to determine the one or more parameters; as well as An indication of the one or more parameters is received from the control node or the parent node based at least in part on transmitting the indication of information to be used to determine the one or more parameters.

23. The method of claim 16, further comprising: The priority flag is received from a control node or a parent node via at least one of a radio resource control message, an F1 application protocol message, a medium access control (MAC) control element (MAC-CE), or an activation downlink control message.

24. The method of claim 16, wherein the first periodic resources comprise one or more downlink resources allocated via downlink semi-persistent scheduling or one or more uplink resources allocated via uplink configured grant.

25. The method of claim 16, wherein the resource type comprises a configured distributed unit resource type, a not available (NA) resource type, a hard resource type, or a soft resource type.

26. The method of claim 16, further comprising transmitting information associated with the first periodic resource available to the wireless node regardless of the resource type to a control node or a parent node to enable adjustment of the resource allocation at the control node or the parent node.

27. The method of claim 16, wherein receiving an indication of the first periodic resource comprises receiving a configuration from a control node indicating grant information for the first periodic resource, the grant information indicating a resource location associated with the first periodic resource.

28. The method of claim 27, wherein receiving a configuration indicating grant information for the first periodic resource comprises receiving a configuration indicating full grant information, the grant information indicating a resource location associated with the first periodic resource.

29. The method of claim 28, wherein the full grant information indicates at least: the resource location associated with the first periodic resource, a modulation and coding scheme (MCS) associated with the first periodic resource, a frequency domain resource block (RB) allocation associated with the first periodic resource, and An antenna port of the wireless node associated with the first periodic resource.

30. The method of claim 27, wherein receiving a configuration indicating grant information for the first periodic resource comprises receiving a configuration indicating partial grant information, the grant information indicating a resource location associated with the first periodic resource, the partial grant information indicating at least the resource location associated with the first periodic resource.

Images