Repeated Transmissions with Overlapping Resources

Abstract

Aspects presented herein relate to methods and apparatus (including devices such as nodes or base stations) for wireless communication. In one aspect, the device may receive a communication including at least one data packet via a first resource set, the first resource set being allocated for a receiving entity of the node. The device may also decode at least one data packet at the receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time. Additionally, the device may send a communication including at least one data packet to a next-hop node via a second resource set, the second resource set being allocated for a forwarding entity of the node, and at least one first resource overlaps with at least one second resource.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit and priority of the following applications: U.S. Provisional Application Serial No. 63 / 077,499, filed on September 11, 2020, and entitled "METHODS AND APPARATUS FOR REPETITION TRANSMISSIONS WITH OVERLAPPING RESOURCES"; and U.S. Patent Application No. 17 / 471,088, filed on September 9, 2021, and entitled "REPETITION TRANSMISSIONS WITH OVERLAPPING RESOURCES", the entire contents of which are hereby incorporated by reference in their entirety. Field of the Invention

[0003] Broadly speaking, the present disclosure relates to communication systems, and more particularly, to repetition transmissions in wireless communication systems. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple - access technologies that are capable of supporting communication with multiple users by sharing the available system resources. 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, and time - division synchronous code - division multiple - access (TD - SCDMA) systems.

[0005] These multiple - access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced (PC) mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. There is a need for further improvement in 5G NR technology. These improvements may also be applicable to other multiple - access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] A brief overview of one or more aspects is given below to provide a basic understanding of such aspects. This overview is not an extensive review of all the expected aspects and is not intended to identify key or important elements of all aspects nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a node or a base station. The apparatus may receive UL or DL communication including at least one data packet via a first UL or DL resource set allocated for a receiving entity of the node. The apparatus may also decode at least one data packet at the receiving entity during a decoding period that includes a decoding start time and a decoding completion time. Additionally, the apparatus may send an acknowledgement (ACK) or a negative ACK (NACK) when decoding at least one data packet at the receiving entity of the node. The apparatus may also stop receiving at least one remaining first repetition unit among one or more first repetition units when at least one data packet is successfully decoded, wherein the reception of at least one remaining first repetition unit is stopped at an early termination instance. Further, the apparatus may encode at least one data packet at a forwarding entity of the node, and after at least one data packet is encoded, at least one data packet is sent to a next-hop node via one or more second repetition units, wherein one or more second repetition units overlap with at least one remaining first repetition unit. The apparatus may also send UL or DL communication including at least one data packet to the next-hop node via a second UL or DL resource set allocated for the forwarding entity of the node, wherein at least one first resource in the first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set. The apparatus may receive a notification flag from a last-hop node indicating one or more potentially skipped resources that are skipped by the last-hop node at the start of a first uplink (UL) or downlink (DL) resource set, wherein the received UL or DL communication is based on the notification flag. In some examples, the notification flag may be initiated or generated by the last-hop node. In some examples, the notification flag may be initiated by a central unit (CU) of the network and delivered to the apparatus via the last-hop node. The apparatus may also send a notification flag indicating one or more potentially skipped resources that are skipped by the forwarding entity at the start of a second UL or DL resource set to the next-hop node.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a node or a base station. The apparatus may send UL or DL communication including at least one data packet to a second node via a first uplink (UL) or downlink (DL) resource set, and the first UL or DL resource set is allocated for a receiving entity of the second node. The apparatus may also receive an acknowledgment (ACK) or a negative ACK (NACK) from the second node based on at least one data packet being decoded at the receiving entity of the second node. The apparatus may also send a notification flag indicating one or more potential skipped resources to the second node, where the one or more potential skipped resources are skipped by a first node at the start of the first UL or DL resource set, and wherein the sent UL or DL communication is based on the notification flag.

[0009] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a node or a base station. The apparatus may receive a notification flag indicating one or more potential skipped resources from a second node, where the one or more potential skipped resources are skipped by a forwarding entity of the second node at the start of a first uplink (UL) or downlink (DL) resource set. The apparatus may also receive UL or DL communication including at least one data packet from the second node via the first UL or DL resource set, and the first UL or DL resource set is allocated for the forwarding entity of the second node, wherein at least one second resource in the second UL or DL resource set overlaps with at least one first resource in the first UL or DL resource set.

[0010] To achieve the foregoing and related purposes, one or more aspects include the features described fully hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0012] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0013] Figure 2B is a diagram illustrating an example of a DL channel within a subframe according to various aspects of the present disclosure.

[0014] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0015] Figure 2D It is a diagram showing an example of the UL channel within a subframe according to various aspects of the present disclosure.

[0016] Figure 3 It is a diagram showing an example of a base station and a user equipment (UE) in an access network.

[0017] Figure 4 It is a diagram showing an example integrated access and backhaul (IAB) network.

[0018] Figure 5A It is a diagram showing an example node.

[0019] Figure 5B It is a diagram showing an example node.

[0020] Figure 6A It is a diagram showing an example of repeated transmission.

[0021] Figure 6B It is a diagram showing an example of repeated transmission

[0022] Figure 7 It is a diagram showing an example of repeated transmission.

[0023] Figure 8 It is a diagram showing an example of repeated transmission.

[0024] Figure 9A It is a diagram showing an example of repeated transmission.

[0025] Figure 9B It is a diagram showing an example of repeated transmission.

[0026] Figure 10 It is a diagram showing an example of repeated transmission.

[0027] Figure 11 It is a diagram showing an example of repeated transmission.

[0028] Figure 12 It is a diagram showing an example of repeated transmission.

[0029] Figure 13 It is a diagram showing an example of communication between nodes.

[0030] Figure 14 It is a flowchart of a method for wireless communication.

[0031] Figure 15 It is a flowchart of a method for wireless communication.

[0032] Figure 16 It is a flowchart of a method for wireless communication.

[0033] Figure 17 It is a flowchart of a method for wireless communication.

[0034] Figure 18 It is a diagram showing an example of the hardware implementation of an example device.

[0035] Figure 19 It is a diagram showing an example of the hardware implementation of an example device.

[0036] Figure 20 It is a diagram showing an example of the hardware implementation of an example device. Detailed Implementation Modes

[0037] The detailed implementation modes described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations and are not intended to represent the only configuration in which the concepts described herein can be practiced. For the purpose of providing a comprehensive understanding of the various concepts, the detailed implementation modes include specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0038] Certain aspects of a telecommunications system will now be presented with reference to various devices and methods. These devices and methods will be described in the detailed implementation modes below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0039] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, executing threads, processes, functions, etc.

[0040] Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded on a computer-readable medium as one or more instructions or code. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0041] Figure 1 FIG. 4 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.

[0042] The base station 102 configured for 4G LTE (collectively referred to as evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., the S1 interface). The base station 102 configured for 5G NR (collectively referred to as next-generation RAN (NG-RAN)) may interface with the core network 190 via a second backhaul link 184. In addition to other functions, the base station 102 may also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly with each other (e.g., via the EPC 160 or the core network 190) on a third backhaul link 134 (e.g., the X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0043] Base station 102 can communicate wirelessly with UE 104. Each base station 102 in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. There can be overlapping geographical coverage areas 110. For example, small cell 102' can have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network can also include a home evolved Node B (eNB) (HeNB), and the HeNB can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple-input multiple-output (MIMO) antenna technology, which includes spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be over one or more carriers. Base station 102 / UE 104 can use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) per carrier allocated in carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction. The carriers can be adjacent to each other or can be non-adjacent to each other. The allocation of carriers can be asymmetric with respect to DL and UL (e.g., more or fewer carriers can be allocated for DL compared to UL). The component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell), and the secondary component carriers can be referred to as secondary cells (SCell).

[0044] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and the physical sidelink control channel (PSCCH). D2D communication can be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0045] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, e.g., in a 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0046] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may adopt NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may enhance the coverage of the access network and / or increase the capacity of the access network.

[0047] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as the frequency range name FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Similar naming issues sometimes occur with respect to FR2. Although FR2 is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz), it is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, and the EHF band is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0048] In view of the above aspects, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz", etc. (if used herein) may generally represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that the term "millimeter wave", etc. (if used herein) may generally represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0049] Base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in the traditional sub 6GHz spectrum, at millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When gNB 180 operates at millimeter wave or near millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short distances. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0050] Base station 180 may transmit the beamformed signal to UE 104 in one or more transmission directions 182'. UE 104 may receive the beamformed signal from base station 180 in one or more reception directions 182". UE 104 may also transmit the beamformed signal to base station 180 in one or more transmission directions. Base station 180 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission direction and reception direction for base station 180 may be the same or may be different. The transmission direction and reception direction for UE 104 may be the same or may be different.

[0051] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transported through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to an IP service 176. The IP service 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used for scheduling MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular service being broadcast, and may be responsible for session management (start / stop) and for collecting charging information related to eMBMS.

[0052] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management Unit (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transported through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services.

[0053] The base station may include and / or be referred to as a gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission and reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of the UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with a similar function. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, cardiac monitors, etc.). The UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0054] Refer again to Figure 1, in some aspects, the base station 180 may include a transmitting component 199 configured to: receive from a last-hop node a notification flag indicating one or more potentially skipped resources that are skipped by the last-hop node at the start of a first uplink (UL) or downlink (DL) resource set, wherein the received UL or DL communication is based on the notification flag. The transmitting component 199 may also be configured to: receive a UL or DL communication including at least one data packet via the first UL or DL resource set, the first UL or DL resource set being allocated for a receiving entity of the node. The transmitting component 199 may also be configured to: decode at least one data packet at the receiving entity during a decoding period that includes a decoding start time and a decoding completion time. The transmitting component 199 may also be configured to: transmit an acknowledgment (ACK) or a negative ACK (NACK) when decoding at least one data packet at the receiving entity of the node. The transmitting component 199 may also be configured to: stop receiving at least one remaining first repetition unit in one or more first repetition units when at least one data packet is successfully decoded, wherein the receiving of the at least one remaining first repetition unit is stopped at an early termination instance. The transmitting component 199 may also be configured to: send to a next-hop node a notification flag indicating one or more potentially skipped resources that are skipped by a forwarding entity at the start of a second UL or DL resource set. The transmitting component 199 may also be configured to: encode at least one data packet at a forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is sent to the next-hop node via one or more second repetition units, wherein the one or more second repetition units overlap with at least one remaining first repetition unit. The transmitting component 199 may also be configured to: send a UL or DL communication including at least one data packet to the next-hop node via the second UL or DL resource set, the second UL or DL resource set being allocated for a forwarding entity of the node, and at least one first resource in the first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set.

[0055] Referring again to Figure 1, in some aspects, the base station 180 may include a transmitting component 198 configured to: transmit a UL or DL communication including at least one data packet to a second node via a first set of uplink (UL) or downlink (DL) resources, the first set of UL or DL resources being allocated for a receiving entity of the second node. The transmitting component 198 may also be configured to: receive an acknowledgment (ACK) or negative ACK (NACK) from the second node based on at least one data packet being decoded at the receiving entity of the second node. The transmitting component 198 may also be configured to: transmit a notification flag indicating one or more potentially skipped resources to the second node, the one or more potentially skipped resources being skipped by a first node at the start of the first set of UL or DL resources, wherein the transmitted UL or DL communication is based on the notification flag.

[0056] Referring again to Figure 1 , in certain aspects, the base station 180 may include a receiving component 191 configured to: receive a notification flag indicating one or more potentially skipped resources from the second node, the one or more potentially skipped resources being skipped by a forwarding entity of the second node at the start of a first set of uplink (UL) or downlink (DL) resources. The receiving component 191 may also be configured to: receive a UL or DL communication including at least one data packet from the second node via the first set of UL or DL resources, the first set of UL or DL resources being allocated for the forwarding entity of the second node, wherein at least one second resource in the second set of UL or DL resources overlaps with at least one first resource in the first set of UL or DL resources.

[0057] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0058] Figure 2A is a schematic diagram 200 showing an example of a first subframe within a 5G NR frame structure. Figure 2B is a schematic diagram 230 showing an example of a DL channel within a 5G NR subframe. Figure 2C is a schematic diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D is a schematic diagram 280 showing an example of a UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexing (FDD) (wherein, for a specific set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to DL or UL), or may be time division duplexing (TDD) (wherein, for a specific set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL). In passing through Figure 2A ,Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly available between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all-DL and all-UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format by the received Slot Format Indicator (SFI) (configured dynamically by Downlink Control Information (DCI) or semi-statically / statically by Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0059] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini-slots, which can include 7, 4, or 2 symbols. Each slot can include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot can include 14 symbols, while for slot configuration 1, each slot can include 7 symbols. The symbols on the DL can be Cyclic Prefix (CP) OFDM (CP - OFDM) symbols. The symbols on the UL can be CP - OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) spread OFDM (DFT - s - OFDM) symbols (also known as Single - Carrier Frequency - Division Multiple Access (SC - FDMA) symbols) (for power - limited scenarios; limited to single - stream transmission). The number of slots within a subframe is based on the slot configuration and numerology. For slot configuration 0, different numerologies μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe respectively. For slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 slots per subframe respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2 μ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the numerology. The subcarrier spacing can be equal to 2 μ *15 kHz, where μ is numerology 0 to 4. Thus, numerology μ = 0 has a subcarrier spacing of 15 kHz, and numerology μ = 4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A - 2DProvide an example of time slot configuration 0 (with 14 symbols per time slot) and digital scheme μ = 2 (with 4 time slots per subframe). The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there can be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a specific digital scheme.

[0060] A resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also referred to as physical RBs (PRBs)), and a PRB spans 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] As shown in Figure 2A , some of the REs carry reference (pilot) signals (RSs) for the UE. The RS can include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration, but other DM-RS configurations are possible) and channel state information reference signal (CSI-RS). The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0062] Figure 2BAn example of various DL channels within a subframe of a frame is shown. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes six Resource Element groups (REGs), and each REG includes 12 consecutive Resource Elements in one OFDM symbol of one Resource Block. The PDCCH within a Bandwidth Part (BWP) can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be in symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be in symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the above-mentioned DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of Resource Blocks in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0063] As shown in Figure 2C some of the Resource Elements carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can send DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be sent in the previous one or two symbols of the PUSCH. The PUCCH DM-RS can be sent in different configurations according to whether a short PUCCH or a long PUCCH is sent and according to the specific PUCCH format used. The UE can send a Sounding Reference Signal (SRS). The SRS can be sent in the last symbol of a subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the combs in the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0064] Figure 2D An example of various UL channels within a subframe of a frame is shown. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0065] Figure 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding on the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 can be used to determine the encoding and modulation schemes and for spatial processing. The channel estimates can be derived based on reference signals transmitted by the UE 350 and / or channel status feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier using the corresponding spatial stream for transmission.

[0067] At the UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functions.

[0068] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0069] Similar to the functions described in connection with DL transmissions performed by the base station 310, the controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functions associated with: mapping between the logical channel and the transport channel, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0070] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0071] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functions at the UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0072] The controller / processor 375 can be associated with a memory 376 that stores program code and data. The memory 376 can be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. The IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0073] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 can be configured to perform aspects related to Figure 1 191, 198, and / or 199 of

[0074] Some aspects of wireless communication can include an integrated access and backhaul (IAB) network. In an IAB network, a portion of the wireless spectrum can be used for the backhaul connection of nodes or base stations. This utilization of the wireless spectrum can be used instead of another type of connection, e.g., a fiber optic connection. IAB networks can be beneficial as they can make the high-density deployment of wireless networks more economically viable. Based on this, some aspects of wireless communication increasingly utilize multi-hop IAB networks.

[0075] An IAB network can include several different nodes or base stations, such as an IAB donor and IAB nodes. An IAB donor is an enhanced base station node with the function of controlling the IAB network. The IAB donor can include a central unit (CU), which is a central entity that controls the entire IAB network through configuration. Additionally, the CU can include several functions, e.g., radio resource control (RRC) protocol or packet data convergence protocol (PDCP) layer functions. The IAB donor can also include a distributed unit (DU), which is a scheduling node that can schedule the sub-nodes of the IAB donor. The DU can also include several functions, e.g., radio link control (RLC), media access control (MAC), and / or physical (PHY) layer functions.

[0076] An IAB node can be a layer 2 (L2) relay node that includes several functions, e.g., a mobile terminal (MT) unit and DU functions. In some aspects, the MT of the IAB node can be a scheduled node similar to a UE. Additionally, the MT can be scheduled by its parent IAB node or the IAB donor. Furthermore, the DU can be a scheduling node that schedules the sub-nodes of the IAB node.

[0077] Figure 4 is FIG. 400 showing an exemplary IAB network. As Figure 4As shown, Figure 400 includes a core network 410, an IAB donor 422, and IAB nodes 432 / 434 / 436 / 438. Figure 4 Also shown are several UEs, child nodes of the IAB node 432, radio access links, and radio backhaul links. As described above, the IAB donor 422 includes a CU and a DU. Additionally, the IAB nodes 432 / 434 / 436 / 438 include an MT and a DU.

[0078] Some aspects of the IAB network may include resource management solutions that handle different constraints (e.g., half-duplex constraints). A half-duplex constraint is a node that cannot perform both transmit (TX) and receive (RX) functions simultaneously on the same frequency band. One solution to the half-duplex constraint can be time-division multiplexing (TDM) and space-division multiplexing (SDM) TX, frequency-division multiplexing (FDM) TX, SDM RX, or FDM RX.

[0079] Figure 5A and Figure 5B Figures 500 and 550 respectively show example nodes. As Figure 5A shown, Figure 500 includes parent nodes 502 / 512, IAB nodes 504 / 514, child IAB nodes 506 / 516, and UEs 508 / 518. Figure 5A An example of a TDM solution between different nodes is shown. As Figure 5B shown, Figure 550 includes parent nodes 552 / 562, IAB nodes 554 / 564, child IAB nodes 556 / 566, and UEs 558 / 568. Figure 5B An example of an SDM RX or FDM RX solution between different nodes and an SDM TX or FDM TX solution between different nodes is shown.

[0080] An IAB node may include several DU resource attributes, such as hard (H) resources, unavailable (NA) resources, and soft (S) resources. The DU can use H resources unconditionally, but it does not have to use H resources. The DU cannot use NA resources, except when the DU matches the allocation for several cell-specific signals or channels. For example, this exception can apply to synchronization signal block (SSB) transmissions (both cell-defined SSB (CD-SB) and non-CD SSB), RACH reception, periodic CSI-RS transmissions, and SR reception. If the conditions are met or are true, the DU can use S resources. For example, these conditions can include an explicit indication (i.e., where the parent node sends an indication to release the resources), an implicit determination (i.e., where the node determines that the use of the DU resources has no impact on what is expected of the MT), and the same exception as for the NA case for cell-specific signals or channels described above.

[0081] Some aspects of wireless communication (e.g., 5G NR communication) may include several repetition schemes. For example, the repetition scheme may include slot aggregation or multi-transmit receive point (TRP) or multi-TRP TDM repetition. In slot aggregation, a single DCI may schedule a PDSCH or PUSCH that may span multiple consecutive slots (e.g., N slots). In some cases, the same set of symbols on the N slots may be used for data transmission. Additionally, the number of aggregated slots may be configured semi-statically via RRC signaling (e.g., the pdsch-AggregationFactor parameter in pdsch-config). In one case, based on the TDD slot configuration, the UE may determine that the symbols allocated for receiving the PDSCH (or transmitting the PUSCH) are UL (or DL), and determine that there is no transmission in the slot.

[0082] In multi-TRP TDM repetition, aspects of wireless communication may include support for slot or mini-slot repetition. Multi-TRP TDM repetition may also include TCI state or redundancy version (RV) pattern cross-repetition. Additionally, multi-TRP TDM repetition may include a dynamic indication of the number of repetitions via DCI, e.g., time domain resource assignment. In some cases, the DCI may point to an entry in a table configured via RRC (e.g., the PDSCH-TimeDomainResourceAllocation parameter). Further, the RepNumR16 parameter for multi-TRP repetition may be part of the configuration for the PDSCH-TimeDomainResourceAllocation parameter.

[0083] Moreover, some aspects of wireless communication may include a work item description (WID) for an IAB network. For example, an IAB network may include several enhancements such as topology, routing, and transmission enhancements. An IAB network may also include enhancement specifications, e.g., to improve fairness of topology scope, multi-hop latency, and / or congestion mitigation.

[0084] Figure 6A and Figure 6B are FIGS. 600 and 650 respectively showing example repeated transmissions. Figure 6A and Figure 6B show that aspects of wireless communication may include repetitions with non-overlapping resources and overlapping resources across an IAB network. As Figure 6A shown, FIG. 600 includes a parent node 602, an IAB node 604, and a child node 606. Figure 6A also includes multiple repeated resources. For example, the repeated resources corresponding to the MT of the IAB node 604 are white in Figure 6A which includes K1 repetitions. The repeated resources corresponding to the DU of the IAB node 604 are inFigure 6A has diagonals therein, which include K2 repetitions. Figure 6A depicts repetitions where the IAB MT across the IAB node 604 and the IAB DU of the IAB node 604 have non - overlapping resources.

[0085] As Figure 6B shown, FIG. 650 includes a parent node 652, an IAB node 654, and a child node 656. Figure 6B depicts repetitions where the IAB MT across the IAB node 654 and the IAB DU of the IAB node 654 have overlapping resources. Figure 6B also includes multiple repeated resources. For example, the repeated resources corresponding to the MT of the IAB node 654 are white in Figure 6B and include K1 repetitions. The repeated resources corresponding to the DU of the IAB node 654 have diagonals in Figure 6B and include K2 repetitions. Figure 6B also depicts that there are multiple overlapping repeated resources. As Figure 6B indicated, the repetitions with overlapping resources can include improved latency on a multi - hop IAB network. Additionally, the repetition scheme can refer to slot aggregation or multi - TRP TDM repetition.

[0086] Based on the above, including repeated transmissions across IAB nodes with overlapping resources may be beneficial. For example, the repetitions with overlapping resources can provide various enhancements such as latency enhancement. Therefore, including repetitions across the IAB MT and IAB DU with overlapping resources may be beneficial to improve latency issues.

[0087] Aspects of the present disclosure may include repeated transmissions across IAB nodes with overlapping resources. For example, aspects of the present disclosure may utilize repetitions with overlapping resources in order to provide various enhancements such as latency enhancement. Aspects of the present disclosure may also include repetitions across the IAB MT and IAB DU with overlapping resources to optimize latency issues.

[0088] Figure 7 is FIG. 700 showing an example repeated transmission. As Figure 7 shown, FIG. 700 includes a parent node 702, an IAB node 704, and a child node 706. Figure 7 depicts repetitions where the IAB MT across the IAB node 704 and the IAB DU of the IAB node 704 have overlapping resources. Figure 7 includes multiple repeated resources corresponding to the MT and DU. For example, the repeated resources corresponding to the MT of the IAB node 704 are white in Figure 7 and include K1 repetitions. The repeated resources corresponding to the DU of the IAB node 704 are in Figure 7has a diagonal, which includes K2 repetitions. Figure 7 Also depicted are overlapping resources with multiple repeating resources. Additionally, Figure 7 includes early termination instances as well as DCI and ACK / NACK.

[0089] As Figure 7 shown, some aspects of the present disclosure may know the early termination instances at the scheduling time. In some cases, the overlapping resources allocated for the next hop may start after the early termination instance of that hop. As Figure 7 shown, DL repeated TX can be sent via dynamic DCI, where the IAB DU (e.g., the forwarding entity) can perform dynamic scheduling for the next hop when knowing the early termination at the co-located IAB MT (e.g., the receiving entity).

[0090] Figure 8 is FIG. 800 showing an example repeated transmission. As Figure 8 shown, FIG. 800 includes a parent node 802, an IAB node 804, and a child node 806. Figure 8 Depicts a repetition where the IAB MT across the IAB node 804 and the IAB DU of the IAB node 802 have overlapping resources. Figure 8 Includes multiple repeating resources corresponding to the MT and DU. For example, the repeating resources corresponding to the DU of the IAB node 804 are white in Figure 8 which includes K1 repetitions. The repeating resources corresponding to the MT of the IAB node 804 have a diagonal in Figure 8 which includes K2 repetitions. Figure 8 Also depicted are overlapping resources with multiple repeating resources. Additionally, Figure 8 includes early termination instances as well as DCI and a preemption buffer status report (BSR).

[0091] As Figure 8 shown, some aspects of the present disclosure may not know the early termination instances at the scheduling time. In some aspects, the overlapping resources allocated for the next hop can start before the early termination instance of that hop. As Figure 8 shown, UL repeated TX can be sent via dynamic DCI, where the parent DU is the scheduling node for the next hop TX by the IAB MT (e.g., the forwarding entity). The scheduling node may not know the early termination instances at the IAB DU (e.g., the receiving entity).

[0092] Figure 9A and Figure 9B are FIG. 900 and 950 showing example repeated transmissions respectively. As Figure 9A shown, FIG. 900 includes a parent node 902, an IAB node 904, and a child node 906.Figure 9A Depicts a repetition where the IAB MT across the IAB node 904 and the IAB DU of the IAB node 904 have overlapping resources. Figure 9A Includes multiple repetitive resources corresponding to the MT and DU. For example, the repetitive resources corresponding to the MT of the IAB node 904 are white in Figure 9A and include K1 repetitions. The repetitive resources corresponding to the DU of the IAB node 904 have diagonals in Figure 9A and include K2 repetitions. Figure 9A Also depicts overlapping resources where there are multiple repetitive resources. Figure 9A Also includes early termination instances and ACK / NACK. Figure 9A Depicts that aspects of the present disclosure may correspond to DL semi-persistent scheduling (SPS).

[0093] As Figure 9B shown, FIG. 950 includes a parent node 952, an IAB node 954, and a child node 956. Figure 9B Also depicts a repetition where the IAB MT across the IAB node 954 and the IAB DU of the IAB node 954 have overlapping resources. Figure 9B Includes multiple repetitive resources corresponding to the MT and DU. For example, the repetitive resources corresponding to the DU of the IAB node 904 are white in Figure 9B and include K1 repetitions. The repetitive resources corresponding to the MT of the IAB node 954 have diagonals in Figure 9B and include K2 repetitions. Figure 9B Also depicts overlapping resources where there are multiple repetitive resources and early termination instances. Figure 9B Depicts that aspects of the present disclosure may correspond to UL-configured grants with repetitions.

[0094] As Figure 9A and Figure 9B shown, examples of the present disclosure may correspond to DL SPS and / or UL-configured grants with repetitions. For these cases, resources may be pre-periodically allocated via activation DCI or by RRC configuration. The starting resources for the forwarding entity may be determined based on the earliest possible successful decoding time at the receiving entity. The actual successful decoding time at the receiving entity may occur after the start time of the resources allocated for the forwarding entity.

[0095] Figure 10 FIG. 1000 is a diagram showing an example of repetitive transmission. As Figure 10 shown, FIG. 1000 includes a parent node 1002, an IAB node 1004, and a child node 1006. Figure 10Depicts a repetition where the IAB MT across IAB node 1004 and the IAB DU of IAB node 1004 have overlapping resources. Figure 10 Includes multiple repeating resources corresponding to the MT and DU. For example, the repeating resources corresponding to the MT of IAB node 1004 are white in Figure 10 and include K1 repetitions. The repeating resources corresponding to the DU of IAB node 1004 have diagonals in Figure 10 and include K2 repetitions. Figure 10 Also depicts that there are multiple soft types of overlapping resources. Figure 10 Also includes early termination instances, DCI, and ACK / NACK.

[0096] Figure 10 Shows that the overlapping resources allocated for the forwarding entity can start after the early termination instance at the receiving entity. As Figure 10 depicted, the receiving entity (e.g., IAB MT for DL) can stop RX (i.e., early termination instance) when it successfully decodes at least one packet before the end of the repetition. In this case, although the parent node may not be aware of the early termination at the IAB MT and may continue to transmit, the IAB MT can stop RX and allow the co-located IAB DU to use the remaining resources. As Figure 10 shown, once the receiving entity stops RX upon successful reception, the co-located forwarding entity (e.g., IAB DU for DL) can allocate resources with repetitions overlapping the remaining unused resources of the receiving entity for TX towards the next-hop node. Additionally, the overlapping resources can be of soft type. According to the principle of implicit determination of soft resources, the IAB DU can use the remaining soft resources after the IAB MT stops RX upon successful reception.

[0097] Figure 11 Is FIG. 1100 showing an example of repeated transmission. As Figure 11 shown, FIG. 1100 includes a parent node 1102, an IAB node 1104, and a child node 1106. Figure 11 Depicts a repetition where the IAB MT across IAB node 1104 and the IAB DU of IAB node 1104 have overlapping resources. Figure 11 Includes multiple repeating resources corresponding to the MT and DU. For example, the repeating resources corresponding to the MT of IAB node 1104 are white in Figure 11 and include K1 repetitions. The repeating resources corresponding to the DU of IAB node 1104 have diagonals in Figure 11 and include K2 repetitions. Figure 11 Also depicts the noise (which includes a dotted pattern) between resources and the early termination instance.

[0098] Figure 11 It is shown that the overlapping resources allocated for the forwarding entity can start before the early termination instance at the receiving entity. As Figure 11 shown, the overlapping resources allocated for the forwarding entity (e.g., IAB DU for DL or IAB MT for UL) can start before the early termination instance at the receiving entity (e.g., IAB MT for DL or IAB DU for UL). In this case, the forwarding entity may not always be able to use the full resource allocation for packet forwarding. The forwarding entity may have to skip some start repetition units (in a time slot or a mini-slot) until the early termination instance and start forwarding the packet to the next-hop node near the middle of the repetition unit.

[0099] As Figure 11 shown, there may be an impact on the receiving entity at the next-hop node. For an unknown start time for effective reception, the first few allocated resources for reception may contain noise. For a sub-optimized redundancy version (RV) mode, the existing RV mode defined for the repetition may not be optimized for the case of skipped transmissions. For example, the first received signal after the skip may not have an RV with sufficient systematic bits for decoding. In addition, due to the skipped TX, there may be a reduced number of repetitions compared to the target value.

[0100] As pointed out above, in some aspects, the overlapping resources may start before the early termination instance. For a resource allocation with repetitions spanning multiple time slots or mini-slots, a flag can be associated with the resource allocation to enable or disable the operation of the floating start time. The flag can be indicated to the TX node and / or RX node of the resource allocation as part of the RRC configuration associated with the resource allocation by the IAB donor CU or as part of the DCI grant for scheduling the resource allocation by the scheduling node. The DCI grant can be a grant for dynamic scheduling or an activation grant for SPS or a UL-configured grant. In some cases, the forwarding entity can also indicate additional information (such as the number of skipped repetition units) to the next-hop node via a medium access control (MAC) control element (MAC-CE), DCI, or UCI for more efficient reception at the next-hop node.

[0101] If the enable flag is indicated, the RX node may assume that the TX node can start TX near the middle of the repetition unit (e.g., in a time slot or a mini-slot), and optimize its reception process accordingly. For example, the RX node may perform a certain hypothesis test on the starting time slot or mini-slot within the allocated resources during reception. For the case of enabling a floating start time, a separate RV mode may be indicated. For example, this may include an RV mode that includes certain RV versions (e.g., RV0 and / or RV3) with sufficient system bits. If additional information (such as the number of skipped repetition units) is also indicated to the RX node, the RX node may also skip these repetition units during the reception and / or decoding process.

[0102] If the enable flag is indicated for a resource allocation and the forwarding entity starts TX near the middle of the repetition unit, the forwarding entity may adopt one or more of the options. In some aspects, the number of TXs may be equal to the remaining number of repetitions, i.e., the total number of allocated repetitions minus the number of skipped repetitions. In these aspects, the number of TXs may vary according to the start time. Additionally, the forwarding entity may schedule additional TXs via another dynamic DCI to meet the target reliability.

[0103] In other cases, a fixed number of TXs may be indicated for a resource allocation regardless of the start time. In these cases, the total number of allocated repetitions may be equal to the latest start TX plus the indicated number of TXs. Additionally, the latest start TX at the forwarding entity of the IAB node may correspond to the end of the allocation at the co-located receiving entity of the IAB node.

[0104] Figure 12 FIG. 1200 shows an example of repeated transmissions. As Figure 12 shown, FIG. 1200 includes a parent node 1202, an IAB node 1204, and a child node 1206. Figure 12 Depicts a repetition where the IAB MT of the IAB node 1204 and the IAB DU of the IAB node 1204 have overlapping resources. Figure 12 Includes multiple repeated resources corresponding to the MT and DU. For example, the repeated resources corresponding to the DU of the IAB node 1204 are white in Figure 12 and include K1 repetitions. The repeated resources corresponding to the MT of the IAB node 1204 have diagonals in Figure 12 and include K2 repetitions. Figure 12 Also depicts an early termination instance, DCI, and a preemptive BSR.

[0105] As Figure 12As shown, for UL communication, the parent DU can utilize some information about the resource allocation of the child DU (e.g., the starting time slot or mini-slot index) to determine the overlapping resources for the IAB MT. This can be the case for dynamic UL scheduling and / or periodic allocation via a configured grant (e.g., a type 2 configured grant). In both cases, the child IAB MT can indicate the information about the resource allocation of the child DU (e.g., the starting time slot or mini-slot index) to the parent DU. Signaling overhead can also be a concern for dynamic UL scheduling. For periodic allocation via a configured grant (e.g., a type 2 configured grant), signaling overhead may not be a concern because the information can be indicated for one allocation and applied periodically. This information may not be used for periodic allocation via a type 1 configured grant because the complete resource allocation can be determined by the donor CU via RRC configuration, and the donor CU can align the overlapping resources.

[0106] In some aspects, for an IAB node, a first set of resources with repetition spanning multiple time slots or mini-slots can be allocated to a receiving entity of the IAB node to receive at least one packet. Additionally, a second set of resources with repetition spanning multiple time slots or mini-slots can be allocated to a forwarding entity of the IAB node to forward the received packet to the next-hop node, where there are overlapping resources between the first set of resources and the second set of resources. The number of repetition units in the first set of resources can be different from that in the second set of resources. For DL, the receiving entity can be the MT of the IAB node, the forwarding entity can be the DU of the IAB node, and the next-hop node can be a child node of the IAB node. For UL, the receiving entity can be the DU of the IAB node, the forwarding entity can be the MT of the IAB node, and the next-hop node can be the parent node of the IAB node. In some cases, the overlapping resources at the forwarding entity can start after the packet has been successfully received at the co-located receiving node. Additionally, the overlapping resources at the forwarding entity can start before the packet has been successfully received at the co-located receiving node.

[0107] In some cases, one or more second repeating units can belong to a second UL or DL resource set assigned to a forwarding entity of a node for communication with a next-hop node. Additionally, at least one first resource in the first UL or DL resource set can overlap with at least one second resource in the second UL or DL resource set. Resources with repeating units can be allocated for communication based on average or worst-case channel conditions in order to achieve a target reliability. Due to the varying channel conditions in a wireless network, in some cases with more favorable channel conditions, a receiving entity may be able to decode a data packet near the middle of the assigned repeating units. By allowing overlapping resources between the first resource set assigned for the receiving entity and the second resource set assigned for the forwarding entity, the packet can be forwarded to the next-hop node immediately after an early termination instance at the receiving entity. Thus, latency can be significantly improved over a multi-hop network.

[0108] In some aspects, a second resource set can be allocated for a forwarding entity after an early termination instance at a receiving entity. For example, in dynamic DL scheduling via DCI, the scheduling node for allocating the second resource set can correspond to the forwarding entity. In this case, the forwarding entity can allocate the second resource set to the next-hop node via dynamic DCI after an early termination instance at a co-located receiving entity. In this case, the starting position of the second resource set can be determined dynamically, which can be after the early termination instance at the receiving entity. Additionally, in this case, both the forwarding entity and the next-hop node can perform normal communication based on the allocation.

[0109] In other aspects, a second resource set can be allocated for a forwarding entity before an early termination instance at a receiving entity. For example, the second resource set can be allocated semi-persistently via DL SPS or UL-configured grants. In another example, in dynamic UL scheduling, the scheduling node for allocating the second resource set can be another node that may not know the early termination instance of the node. In this case, the second resource set can start before the early termination instance at the receiving entity, and the forwarding entity can skip some of the starting repeating units in the second resource set and send the data packet to the next-hop node via the second resource after the early termination instance at the receiving entity.

[0110] Additionally, as noted above, a node may receive from a last-hop node a notification flag indicating one or more potential skipped resources that are skipped by the last-hop node at the start of a first UL or DL resource set, wherein the received UL or DL communication is based on the notification flag. In some examples, the notification flag may be initiated or generated by the last-hop node. In some examples, the notification flag may be initiated by a CU of the network and delivered via the last-hop node. A node herein may also send to a next-hop node a notification flag indicating one or more potential skipped resources that are skipped by a forwarding entity at the start of a second UL or DL resource set.

[0111] Figure 13 FIG. 1300 is a diagram illustrating an example communication between a first node 1302 (e.g., an IAB node), at least one second node 1304 (e.g., a last-hop node), and at least one third node 1306 (e.g., a next-hop node).

[0112] At 1310, the second node 1304 may send a notification flag (e.g., notification flag 1314) indicating one or more potential skipped resources. At 1312, the first node 1302 may receive from the last-hop node a notification flag (e.g., notification flag 1314) indicating one or more potential skipped resources that are skipped by the last-hop node at the start of a first uplink (UL) or downlink (DL) resource set, wherein the received UL or DL communication is based on the notification flag.

[0113] In some aspects, the node may be an IAB node associated with an integrated access and backhaul (IAB) network, the receiving entity corresponds to a mobile terminal (MT) of the node or a distributed unit (DU) of the node, and the forwarding entity corresponds to the DU of the node or the MT of the node. When the UL or DL communication is UL communication, the receiving entity may correspond to the DU of the node, and the forwarding entity may correspond to the MT of the node, and the next-hop node corresponds to a parent IAB node or an IAB donor. When the UL or DL communication is DL communication, the receiving entity may correspond to the MT of the node, and the forwarding entity may correspond to the DU of the node, and the next-hop node corresponds to a child IAB node or a child user equipment (UE).

[0114] In some cases, upon receiving a notification flag, a receiving entity may apply a hypothesis test to the starting position of a first resource in a first UL or DL resource set, where the first resource is sent by a last-hop node and the hypothesis test is applied when receiving UL or DL communication from the last-hop node. Additionally, upon receiving a notification flag, the receiving entity may apply a pattern of redundancy versions (RVs) on one or more repeated resource units, which are different when the notification flag is not received. The notification flag may be received from an integrated access and backhaul (IAB) donor central unit (CU) via a radio resource control (RRC) message or an F1 application protocol (F1-AP) message, or from the last-hop node via a media access control (MAC) control element (MAC-CE) or downlink control information (DCI). The last-hop node may be a parent node of a node for DL communication or a child node of a node for UL communication.

[0115] At 1320, a second node 1304 may send a UL or DL communication including at least one data packet, e.g., communication 1324. At 1322, a first node 1302 may receive a UL or DL communication including at least one data packet (e.g., communication 1324) via a first UL or DL resource set allocated for a receiving entity of the node.

[0116] At 1330, the first node 1302 may decode at least one data packet at a receiving entity during a decoding period, which includes a decoding start time and a decoding completion time.

[0117] At 1340, when decoding at least one data packet at a receiving entity of the node, the first node 1302 may send an acknowledgement (ACK) or a negative ACK (NACK), e.g., ACK / NACK 1344. At 1342, the second node 1304 may receive the ACK / NACK, e.g., ACK / NACK 1344.

[0118] At 1350, the first node 1302 may stop receiving at least one remaining first repeat unit in one or more first repeat units when successfully decoding at least one data packet, where the receiving of the at least one remaining first repeat unit is stopped at an early termination instance. In some aspects, the receiving entity may attempt to decode at least one data packet upon receiving each first repeat unit in the one or more first repeat units.

[0119] At 1360, the first node 1302 may send a notification flag indicating one or more potentially skipped resources, e.g., (notification flag 1364), to the next-hop node, where one or more potentially skipped resources are skipped by a forwarding entity at the start of a second UL or DL resource set. At 1362, the third node 1306 may receive the notification flag indicating one or more potentially skipped resources, e.g., notification flag 1364.

[0120] At 1370, the first node 1302 may encode at least one data packet at a forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is sent to the next-hop node via one or more second repeating units, where the one or more second repeating units overlap with at least one remaining first repeating unit.

[0121] At 1380, the first node 1302 may send a UL or DL communication (e.g., communication 1384) including at least one data packet to the next-hop node via a second UL or DL resource set, where the second UL or DL resource set is allocated for a forwarding entity of the node, and at least one first resource in a first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set. At 1382, the third node 1306 may receive the UL or DL communication including at least one data packet, e.g., communication 1384. The first UL or DL resource set may include one or more first repeating units, and the second UL or DL resource set includes one or more second repeating units. Additionally, the number of one or more first repeating units may be different from the number of one or more second repeating units.

[0122] In some aspects, the second UL or DL resource set may be allocated after a decoding completion time. The allocated second UL or DL resource set may overlap with one or more remaining first resources in the first UL or DL resource set, and the receiving entity does not use the one or more remaining first resources. Additionally, the second UL or DL resource set may be allocated before the decoding completion time. The second UL or DL resource set may be allocated based on an assumption of an earliest possible decoding completion time. Further, at least one second resource in the second UL or DL resource set may start before the decoding completion time, where the forwarding entity may skip at least one second resource, and the forwarding entity may send at least one data packet to the next-hop node via a portion of the second UL or DL resource set that starts after the decoding completion time.

[0123] In some cases, the number of repeated transmissions performed by the forwarding entity may be equal to the difference between the total number of allocated repetition units in the second UL or DL resource set and the number of skipped repetition units before the decoding completion time. The number of repeated transmissions performed by the forwarding entity may also be equal to a fixed number. The fixed number may be equal to the difference between the total number of allocated repetition units and the maximum number of skipped repetition units.

[0124] Additionally, the first UL or DL resource set may include one or more first time slots or mini-slots, and the second UL or DL resource set may include one or more second time slots or mini-slots. At least one data packet may be associated with one or more data packet repetitions or one or more data packet retransmissions. Further, at least one of the first UL or DL resource set or the second UL or DL resource set may be configured via DL semi-persistent scheduling (SPS), configured via UL-configured grants, or scheduled via dynamic downlink control information (DCI).

[0125] Figure 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a node or a base station or a component of a node or a base station (e.g., base stations 102, 180, 310, nodes 604, 654, 704, 804, 904, 954, 1004, 1104, 1204, 1302; device 1802; a processing system, which may include a memory 376 and may be an entire base station or a component of a base station, such as an antenna 320, a receiver 318RX, an RX processor 370, a controller / processor 375, etc.). The methods described herein may provide many benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0126] At 1404, the device may receive UL or DL communication including at least one data packet via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the node, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 For example, node 1302 may receive UL or DL communication including at least one data packet via a first UL or DL resource set, the first UL or DL resource set being allocated for a receiving entity of the node, as combined with Figure 13described in 1322 of. In addition, 1404 may be performed by determination component 1840.

[0127] At 1406, the apparatus may decode at least one data packet at a receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time, as described in the examples combined in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 For example, node 1302 may decode at least one data packet at a receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time, as described in 1330 combined in Figure 13 In addition, 1406 may be performed by determination component 1840.

[0128] At 1416, the apparatus may send a UL or DL communication including at least one data packet to a next-hop node via a second UL or DL resource set, the second UL or DL resource set being allocated for a forwarding entity of the node, at least one first resource in the first UL or DL resource set overlapping with at least one second resource in the second UL or DL resource set, as described in the examples combined in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 For example, node 1302 may send a UL or DL communication including at least one data packet to a next-hop node via a second UL or DL resource set, the second UL or DL resource set being allocated for a forwarding entity of the node, at least one first resource in the first UL or DL resource set overlapping with at least one second resource in the second UL or DL resource set, as described in 1380 combined in Figure 13 In addition, 1416 may be performed by determination component 1840. The first UL or DL resource set may include one or more first repeating units, and the second UL or DL resource set includes one or more second repeating units, as described in the examples combined in Figure 4 , Figure 5A, Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 described in the examples of Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 described in the examples of

[0129] Figure 15 is a flowchart 1500 of a method for wireless communication. This method can be executed by a node or a base station or a component of a node or a base station (e.g., base stations 102, 180, 310, nodes 604, 654, 704, 804, 904, 954, 1004, 1104, 1204, 1302; device 1802; a processing system, which may include a memory 376 and may be the entire base station or a component of the base station, such as antenna 320, receiver 318RX, RX processor 370, controller / processor 375, etc.). The methods described herein can provide many benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0130] At 1502, the device can receive from the last-hop node a notification flag indicating one or more potentially skipped resources, where the one or more potentially skipped resources are skipped by the last-hop node at the beginning of a first uplink (UL) or downlink (DL) resource set, and wherein the received UL or DL communication is based on the notification flag, as described in the examples of Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13described in the example of. For example, node 1302 may receive from the last-hop node a notification flag indicating one or more potential skipped resources, where the one or more potential skipped resources are skipped by the last-hop node at the start of a first uplink (UL) or downlink (DL) resource set, and wherein the received UL or DL communication is based on the notification flag, as described in conjunction with Figure 13 described in 1312 of. Additionally, 1502 may be performed by determination component 1840.

[0131] In some aspects, the node may be an IAB node associated with an integrated access and backhaul (IAB) network, the receiving entity corresponding to a mobile terminal (MT) of the node or a distributed unit (DU) of the node, and the forwarding entity corresponding to the DU of the node or the MT of the node, as described in the examples of Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 When the UL or DL communication is UL communication, the receiving entity may correspond to the DU of the node, and the forwarding entity may correspond to the MT of the node, and the next-hop node corresponds to the parent IAB node or IAB donor, as described in the examples of Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 When the UL or DL communication is DL communication, the receiving entity may correspond to the MT of the node, and the forwarding entity may correspond to the DU of the node, and the next-hop node corresponds to a child IAB node or a child user equipment (UE), as described in the examples of Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13as described in the example in

[0132] In some cases, upon receiving a notification flag, the receiving entity may apply a hypothesis test to the starting position of the first resource in the first UL or DL resource set, where the first resource is sent by the last-hop node, and apply the hypothesis test when receiving UL or DL communication from the last-hop node, as combined in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the example in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , ​ , ​ and ​ as described in the example in ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ and ​ as described in the example in ​ , ​ , ​ , ​ ,​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ and ​ described in the examples of

[0133] At 1504, the device may receive UL or DL communication including at least one data packet via a first UL or DL resource set, where the first UL or DL resource set is allocated for the receiving entity of the node, as described in the examples of ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ and ​ described in the examples of ​ For example, node 1302 may receive UL or DL communication including at least one data packet via a first UL or DL resource set, where the first UL or DL resource set is allocated for the receiving entity of the node, as described in 1322 of

[0134] At 1506, the device may decode at least one data packet at the receiving entity during a decoding period, where the decoding period includes a decoding start time and a decoding completion time, as described in the examples of ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ and ​ described in the examples of ​ For example, node 1302 may decode at least one data packet at the receiving entity during a decoding period, where the decoding period includes a decoding start time and a decoding completion time, as described in 1330 of

[0135] At 1508, the device may send an acknowledgement (ACK) or a negative ACK (NACK) when decoding at least one data packet at the receiving entity of the node, as described in​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ and ​ described in the examples of ​ . For example, node 1302 may send an acknowledgment (ACK) or a negative ACK (NACK) when decoding at least one data packet at the receiving entity of the node, as described by 1340 in

[0136] At 1510, the device may stop receiving at least one remaining first repetition unit in one or more first repetition units when successfully decoding at least one data packet, wherein the receiving of at least one remaining first repetition unit is stopped at an early termination instance, as combined in ​ , ​ , ​ , ​ , ​ , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 described in the examples. For example, node 1302 may stop receiving at least one remaining first repetition unit in one or more first repetition units when successfully decoding at least one data packet, wherein the receiving of at least one remaining first repetition unit is stopped at an early termination instance, as combined with Figure 13 described by 1350 in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 described in the examples.

[0137] At 1512, the device may send a notification flag indicating one or more potentially skipped resources to the next-hop node, where the one or more potentially skipped resources are skipped by the forwarding entity at the start of a second UL or DL resource set, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the examples in Figure 13 . For example, node 1302 may send a notification flag indicating one or more potentially skipped resources to the next-hop node, where the one or more potentially skipped resources are skipped by the forwarding entity at the start of a second UL or DL resource set, as described in

[0138] At 1514, the device may encode at least one data packet at the forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is sent to the next-hop node via one or more second repetition units, where the one or more second repetition units overlap with at least one remaining first repetition unit, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the examples in Figure 13 . For example, node 1302 may encode at least one data packet at the forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is sent to the next-hop node via one or more second repetition units, where the one or more second repetition units overlap with at least one remaining first repetition unit, as described in

[0139] At 1516, the apparatus may send an UL or DL communication including at least one data packet to a next-hop node via a second UL or DL resource set, where the second UL or DL resource set is allocated for a forwarding entity of the node, and at least one first resource in the first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 . For example, node 1302 may send an UL or DL communication including at least one data packet to a next-hop node via a second UL or DL resource set, where the second UL or DL resource set is allocated for a forwarding entity of the node, and at least one first resource in the first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set, as described in 1380 in Figure 13 . In addition, 1516 may be performed by determination component 1840. The first UL or DL resource set may include one or more first repeating units, and the second UL or DL resource set includes one or more second repeating units, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 . In addition, the number of one or more first repeating units may be different from the number of one or more second repeating units, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 .

[0140] In some aspects, a second UL or DL resource set can be allocated after the decoding completion time, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 . The allocated second UL or DL resource set can overlap with one or more remaining first resources in the first UL or DL resource set, and the receiving entity does not use the one or more remaining first resources, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 . Additionally, a second UL or DL resource set can be allocated before the decoding completion time, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 . The second UL or DL resource set can be allocated based on the assumption of the earliest possible decoding completion time, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13described in the examples in. In addition, at least one second resource in the second UL or DL resource set may start before the decoding completion time, where the forwarding entity may skip at least one second resource, and the forwarding entity may send at least one data packet to the next-hop node via a part of the second UL or DL resource set that starts after the decoding completion time, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 described in the examples in.

[0141] In some cases, the number of repeated transmissions performed by the forwarding entity may be equal to the difference between the total number of allocated repetition units in the second UL or DL resource set and the number of skipped repetition units before the decoding completion time, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 described in the examples in. The number of repeated transmissions performed by the forwarding entity may also be equal to a fixed number, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、 Figure 10 、 Figure 11 、 Figure 12 and Figure 13 described in the examples in. The fixed number may be equal to the difference between the total number of allocated repetition units and the maximum number of skipped repetition units, as described in the examples in Figure 4 、 Figure 5A 、 Figure 5B 、 Figure 6A 、 Figure 6B 、 Figure 7 、 Figure 8 、 Figure 9A 、 Figure 9B 、Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the examples of

[0142] Additionally, the first UL or DL resource set may include one or more first time slots or mini-slots, and the second UL or DL resource set may include one or more second time slots or mini-slots, as described in the examples incorporated in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the examples of Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 Furthermore, at least one of the first UL or DL resource set or the second UL or DL resource set may be configured via DL semi-persistent scheduling (SPS), configured via UL-configured grants, or scheduled via dynamic downlink control information (DCI), as described in the examples incorporated in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the examples of

[0143] Figure 16FIG. 1600 is a flow chart of a method of wireless communication. The method may be performed by a node or a base station or a component of a node or a base station (e.g., base stations 102, 180, 310, nodes 604, 654, 704, 804, 904, 954, 1004, 1104, 1204, 1304; apparatus 1902; a processing system that may include a memory 376 and may be an entire base station or a component of a base station such as an antenna 320, a receiver 318RX, an RX processor 370, a controller / processor 375, etc.). The methods described herein may provide a number of benefits such as improved communication signaling, resource utilization, and / or power savings.

[0144] At 1602, the apparatus may send a notification flag indicating one or more potentially skipped resources to a second node, the one or more potentially skipped resources being skipped by a first node at the start of a first UL or DL resource set, wherein the UL or DL communication sent is based on the notification flag, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 . For example, node 1304 may send a notification flag indicating one or more potentially skipped resources to a second node, the one or more potentially skipped resources being skipped by a first node at the start of a first UL or DL resource set, wherein the UL or DL communication sent is based on the notification flag, as described in 1310 in Figure 13 . Additionally, 1602 may be performed by a determination component 1940.

[0145] At 1604, the apparatus may send a UL or DL communication including at least one data packet to a second node via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the second node, as described in the examples in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13as described in the example of. For example, node 1304 may send a UL or DL communication including at least one data packet to a second node via a first set of uplink (UL) or downlink (DL) resources, the first set of UL or DL resources being allocated for a receiving entity of the second node, as combined with Figure 13 described in 1320 of. In addition, 1604 may be performed by determination component 1940.

[0146] At 1606, the device may receive an acknowledgment (ACK) or negative ACK (NACK) from the second node based on at least one data packet being decoded at a receiving entity of the second node, as combined in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 , Figure 8 , Figure 9A , Figure 9B , Figure 10 , Figure 11 , Figure 12 and Figure 13 as described in the example of. For example, node 1304 may receive an acknowledgment (ACK) or negative ACK (NACK) from the second node based on at least one data packet being decoded at a receiving entity of the second node, as combined with Figure 13 described in 1342 of. In addition, 1606 may be performed by determination component 1940.

[0147] Figure 17 is a flowchart 1700 of a method of wireless communication. The method may be performed by a node or a base station or a component of a node or a base station (e.g., base stations 102, 180, 310, nodes 604, 654, 704, 804, 904, 954, 1004, 1104, 1204, 1306; device 2002; a processing system that may include a memory 376 and may be an entire base station or a component of a base station, such as an antenna 320, a receiver 318RX, an RX processor 370, a controller / processor 375, etc.). The methods described herein may provide many benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0148] At 1702, the device may receive a notification flag from the second node indicating one or more potentially skipped resources, the one or more potentially skipped resources being skipped by a forwarding entity of the second node at the start of a first set of uplink (UL) or downlink (DL) resources, as combined in Figure 4 , Figure 5A , Figure 5B , Figure 6A , Figure 6B , Figure 7 ,Figure 8 , Figure , ​ , ​ , ​ , ​ and ​ as described in the examples of ​ . For example, node 1306 may receive a notification flag indicating one or more potentially skipped resources from a second node, where one or more potentially skipped resources are skipped by a forwarding entity of the second node at the start of a first uplink (UL) or downlink (DL) resource set, as described in connection with

[0149] At 1704, the device may receive a UL or DL communication including at least one data packet from the second node via a first UL or DL resource set, where the first UL or DL resource set is allocated for a forwarding entity of the second node, and where at least one second resource in a second UL or DL resource set overlaps with at least one first resource in the first UL or DL resource set, as described in the examples of ​ , in ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ and ​ . For example, node 1306 may receive a UL or DL communication including at least one data packet from the second node via a first UL or DL resource set, where the first UL or DL resource set is allocated for a forwarding entity of the second node, and where at least one second resource in a second UL or DL resource set overlaps with at least one first resource in the first UL or DL resource set, as described in connection with ​ . In addition, 1704 may be performed by determination component 2040.

[0150] ​FIG. 1800 is a diagram illustrating an example of a hardware implementation for apparatus 1802. Apparatus 1802 is a base station and includes a baseband unit 1804. The baseband unit 1804 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1804 may include a computer-readable medium / memory. The baseband unit 1804 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory. When executed by the baseband unit 1804, the software causes the baseband unit 1804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 1804 when executing the software. The baseband unit 1804 also includes a receiving component 1830, a communication manager 1832, and a transmitting component 1834. The communication manager 1832 includes one or more of the components shown. The components within the communication manager 1832 may be stored in the computer-readable medium / memory and / or configured as hardware within the baseband unit 1804. The baseband unit 1804 may be a component of the BS 310 and may include a memory 376 and / or at least one of the following: a TX processor 316, an RX processor 370, and a controller / processor 375.

[0151] The communication manager 1832 includes a determination component 1840 configured to: receive, from a last-hop node, a notification flag indicating one or more potentially skipped resources that are skipped by the last-hop node at the start of a first UL or DL resource set, wherein the received UL or DL communication is based on the notification flag, e.g., as described above in connection with step 1502. The determination component 1840 may also be configured to: receive a UL or DL communication including at least one data packet via a first uplink (UL) or downlink (DL) resource set that is allocated for a receiving entity of the node, e.g., as described above in connection with step 1504. The determination component 1840 may also be configured to: decode at least one data packet at the receiving entity during a decoding period that includes a decoding start time and a decoding completion time, e.g., as described above in connection with step 1506. The determination component 1840 may also be configured to: transmit an acknowledgement (ACK) or a negative ACK (NACK) when decoding at least one data packet at the receiving entity of the node, e.g., as described above in connection with step 1508. The determination component 1840 may also be configured to: stop receiving at least one remaining first repetition unit in one or more first repetition units when at least one data packet is successfully decoded, wherein the receiving of the at least one remaining first repetition unit is stopped at an early termination instance, e.g., as described above in connection with step 1510. The determination component 1840 may also be configured to: send a notification flag indicating one or more potentially skipped resources to a next-hop node that are skipped by a forwarding entity at the start of a second UL or DL resource set, e.g., as described above in connection with step 1512. The determination component 1840 may also be configured to: encode at least one data packet at a forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is sent to the next-hop node via one or more second repetition units, wherein the one or more second repetition units overlap with at least one remaining first repetition unit, e.g., as described above in connection with step 1514. The determination component 1840 may also be configured to: send a UL or DL communication including at least one data packet to the next-hop node via a second UL or DL resource set that is allocated for a forwarding entity of the node, wherein at least one first resource in the first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set, e.g., as described above in connection with step 1516.

[0152] The apparatus may include additional components that perform each of the blocks of the algorithm in the above-described flowchart at ​ Thus, the blocks may be performed by components at ​each block in the above flowchart, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0153] In one configuration, apparatus 1802 (and specifically baseband unit 1804) includes: a unit for receiving UL or DL communication including at least one data packet via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the node. Apparatus 1802 may further include: a unit for decoding at least one data packet at the receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time. Apparatus 1802 may further include: a unit for transmitting UL or DL communication including at least one data packet to a next-hop node via a second UL or DL resource set, the second UL or DL resource set being allocated for a forwarding entity of the node, at least one first resource in the first UL or DL resource set overlapping with at least one second resource in the second UL or DL resource set. Apparatus 1802 may further include: a unit for receiving from a last-hop node a notification flag indicating one or more potentially skipped resources, the one or more potentially skipped resources being skipped by the last-hop node at the start of the first UL or DL resource set, wherein the received UL or DL communication is based on the notification flag. Apparatus 1802 may further include: a unit for sending an acknowledgment (ACK) or negative ACK (NACK) when decoding at least one data packet at the receiving entity of the node. Apparatus 1802 may further include: a unit for stopping receiving at least one remaining first repetition unit among one or more first repetition units when at least one data packet is successfully decoded, wherein the receiving of at least one remaining first repetition unit is stopped at an early termination instance. Apparatus 1802 may further include: a unit for sending a notification flag indicating one or more potentially skipped resources to a next-hop node, the one or more potentially skipped resources being skipped by the forwarding entity at the start of the second UL or DL resource set. Apparatus 1802 may further include: a unit for encoding at least one data packet at the forwarding entity of the node, after the at least one data packet is encoded, the at least one data packet being sent to a next-hop node via one or more second repetition units, wherein the one or more second repetition units overlap with at least one remaining first repetition unit. The above units may be one or more components among the above components of apparatus 1802 configured to perform the functions recited by the above units. As described above, apparatus 1802 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the above units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions recited by the above units.

[0154] ​FIG. 1900 is a diagram illustrating an example of a hardware implementation for apparatus 1902. Apparatus 1902 is a base station and includes a baseband unit 1904. The baseband unit 1904 can communicate with a UE 104 via a cellular RF transceiver. The baseband unit 1904 can include a computer-readable medium / memory. The baseband unit 1904 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory. When executed by the baseband unit 1904, the software causes the baseband unit 1904 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1904 when executing the software. The baseband unit 1904 also includes a receiving component 1930, a communication manager 1932, and a transmitting component 1934. The communication manager 1932 includes one or more of the components shown. The components within the communication manager 1932 can be stored in the computer-readable medium / memory and / or configured as hardware within the baseband unit 1904. The baseband unit 1904 can be a component of BS 310 and can include a memory 376 and / or at least one of the following: a TX processor 316, an RX processor 370, and a controller / processor 375.

[0155] The communication manager 1932 includes a determination component 1940 that is configured to: send a notification flag indicating one or more potential skipped resources to a second node, the one or more potential skipped resources being skipped by a first node at the start of a first UL or DL resource set, wherein the UL or DL communication sent is based on the notification flag, e.g., as described above in connection with step 1602. The determination component 1940 can also be configured to: send a UL or DL communication including at least one data packet to the second node via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the second node, e.g., as described above in connection with step 1604. The determination component 1940 can also be configured to: receive an acknowledgment (ACK) or negative ACK (NACK) from the second node based on at least one data packet being decoded at the receiving entity of the second node, e.g., as described above in connection with step 1606.

[0156] The apparatus can include additional components that execute each of the blocks of the algorithms in the above flowcharts in ​ and ​ Thus, the algorithms in ​ and ​each block in the above flowchart, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0157] In one configuration, apparatus 1902 (and specifically baseband unit 1904) includes: a unit for sending to a second node a notification flag indicating one or more potentially skipped resources, the one or more potentially skipped resources being skipped by a first node at the start of a first UL or DL resource set, wherein the UL or DL communication transmitted is based on the notification flag. Apparatus 1902 may further include: a unit for transmitting to the second node a UL or DL communication including at least one data packet via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the second node. Apparatus 1902 may further include: a unit for receiving an acknowledgment (ACK) or negative ACK (NACK) from the second node based on at least one data packet being decoded at a receiving entity of the second node. The above units may be one or more components among the above components of apparatus 1902 configured to perform the functions recited by the above units. As described above, apparatus 1902 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the above units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions recited by the above units.

[0158] ​FIG. 2000 is a diagram illustrating an example of a hardware implementation for apparatus 2002. Apparatus 2002 is a base station and includes a baseband unit 2004. The baseband unit 2004 can communicate with a UE 104 via a cellular RF transceiver. The baseband unit 2004 can include a computer-readable medium / memory. The baseband unit 2004 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory. When executed by the baseband unit 2004, the software causes the baseband unit 2004 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 2004 when executing the software. The baseband unit 2004 also includes a receiving component 2030, a communication manager 2032, and a transmitting component 2034. The communication manager 2032 includes the one or more components shown. The components within the communication manager 2032 can be stored in the computer-readable medium / memory and / or configured as hardware within the baseband unit 2004. The baseband unit 2004 can be a component of BS310 and can include a memory 376 and / or at least one of the following: a TX processor 316, an RX processor 370, and a controller / processor 375.

[0159] The communication manager 2032 includes a determination component 2040 configured to: receive from a second node a notification flag indicating one or more potential skipped resources, where the one or more potential skipped resources are skipped by a forwarding entity of the second node at the start of a first uplink (UL) or downlink (DL) resource set, e.g., as described above in connection with step 1702. The determination component 2040 can also be configured to: receive from the second node via the first UL or DL resource set a UL or DL communication including at least one data packet, where the first UL or DL resource set is allocated for the forwarding entity of the second node, and where at least one second resource in a second UL or DL resource set overlaps at least one first resource in the first UL or DL resource set, e.g., as described above in connection with step 1704.

[0160] The apparatus can include additional components that perform each block of the algorithms in the above ​ and ​ flowcharts. Thus, each block in the above ​ and ​ flowcharts can be performed by a component, and the apparatus can include one or more of those components. The components can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0161] In one configuration, apparatus 2002 (and specifically baseband unit 2004) includes: a unit for receiving, from a second node, a notification flag indicating one or more potentially skipped resources, the one or more potentially skipped resources being skipped by a forwarding entity of the second node at the start of a first uplink (UL) or downlink (DL) resource set. Apparatus 2002 may further include: a unit for receiving, via the first UL or DL resource set, a UL or DL communication including at least one data packet from the second node, the first UL or DL resource set being allocated for the forwarding entity of the second node, wherein at least one second resource in a second UL or DL resource set overlaps with at least one first resource in the first UL or DL resource set. The above units may be one or more components among the above components of apparatus 2002 configured to perform the functions recited by the above units. As described above, apparatus 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the above units may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the above units.

[0162] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. Additionally, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0163] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the literal claims, wherein the mention of an element in the singular is not intended to mean "one and only one" but "one or more" unless explicitly stated otherwise. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise explicitly stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "any combination of A, B, C, or the like" include any combination of A, B, and / or C and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "any combination of A, B, C, or the like" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination can include one or more members or several members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure are expressly incorporated herein by reference and are intended to be encompassed by the claims, which are known or will be known to those of ordinary skill in the art. Further, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The words "module", "mechanism", "element", "device", etc. are not intended to be substitutes for the word "unit". Thus, no claim element is to be construed as a unit plus function unless the element is expressly recited using the phrase "means for...".

[0164] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limited thereto.

[0165] Aspect 1 is a device for wireless communication performed at a node, the device comprising at least one processor coupled to a memory and configured to: receive UL or DL communication comprising at least one data packet via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the node; decode the at least one data packet at the receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time; and transmit the UL or DL communication comprising the at least one data packet to a next-hop node via a second UL or DL resource set, the second UL or DL resource set being allocated for a forwarding entity of the node, at least one first resource in the first UL or DL resource set overlapping at least one second resource in the second UL or DL resource set.

[0166] Aspect 2 is the device according to aspect 1, wherein the first UL or DL resource set comprises one or more first repeating units, and the second UL or DL resource set comprises one or more second repeating units.

[0167] Aspect 3 is the device according to any one of aspects 1 and 2, wherein the number of the one or more first repeating units is different from the number of the one or more second repeating units.

[0168] Aspect 4 is the device according to any one of aspects 1 to 3, wherein the receiving entity attempts to decode the at least one data packet when each of the one or more first repeating units is received, and wherein the at least one processor is further configured to: stop receiving at least one remaining first repeating unit among the one or more first repeating units when the at least one data packet is successfully decoded, and wherein the receiving of the at least one remaining first repeating unit is stopped at an early termination instance.

[0169] Aspect 5 is the device according to any one of aspects 1 to 4, wherein the at least one processor is further configured to: encode the at least one data packet at the forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is transmitted to the next-hop node via the one or more second repeating units, and wherein the one or more second repeating units overlap the at least one remaining first repeating unit.

[0170] Aspect 6 is the apparatus according to any one of Aspects 1 to 5, wherein the node is an IAB node associated with an integrated access and backhaul (IAB) network, the receiving entity corresponds to a mobile terminal (MT) of the node or a distributed unit (DU) of the node, and the forwarding entity corresponds to the DU of the node or the MT of the node.

[0171] Aspect 7 is the apparatus according to any one of Aspects 1 to 6, wherein the UL or DL communication is UL communication, the receiving entity corresponds to the DU of the node, and the forwarding entity corresponds to the MT of the node, and the next-hop node corresponds to a parent IAB node or an IAB donor.

[0172] Aspect 8 is the apparatus according to any one of Aspects 1 to 7, wherein the UL or DL communication is DL communication, the receiving entity corresponds to the MT of the node, and the forwarding entity corresponds to the DU of the node, and the next-hop node corresponds to a child IAB node or a child user equipment (UE).

[0173] Aspect 9 is the apparatus according to any one of Aspects 1 to 8, wherein the second UL or DL resource set is allocated after the decoding completion time.

[0174] Aspect 10 is the apparatus according to any one of Aspects 1 to 9, wherein the allocated second UL or DL resource set overlaps with one or more remaining first resources in the first UL or DL resource set, and the receiving entity does not use the one or more remaining first resources.

[0175] Aspect 11 is the apparatus according to any one of Aspects 1 to 10, wherein the second UL or DL resource set is allocated before the decoding completion time.

[0176] Aspect 12 is the apparatus according to any one of Aspects 1 to 11, wherein the second UL or DL resource set is allocated based on an assumption of the earliest possible decoding completion time.

[0177] Aspect 13 is the apparatus according to any one of Aspects 1 to 12, wherein at least one second resource in the second UL or DL resource set starts before the decoding completion time, and the forwarding entity skips the at least one second resource, wherein the forwarding entity sends the at least one data packet to the next-hop node via a part of the second UL or DL resource set that starts after the decoding completion time.

[0178] Aspect 14 is the apparatus according to any one of Aspects 1 to 13, wherein the at least one processor is further configured to: send a notification flag indicating one or more potentially skipped resources to the next-hop node, the one or more potentially skipped resources being skipped by the forwarding entity at the start of the second UL or DL resource set.

[0179] Aspect 15 is the apparatus according to any one of Aspects 1 to 14, wherein the at least one processor is further configured to: receive a notification flag indicating one or more potentially skipped resources from the last-hop node, the one or more potentially skipped resources being skipped by the last-hop node at the start of the first UL or DL resource set, wherein the received UL or DL communication is based on the notification flag.

[0180] Aspect 16 is the apparatus according to any one of Aspects 1 to 15, wherein upon receiving the notification flag, the receiving entity applies a hypothesis test to the starting position of the first resource in the first UL or DL resource set, the first resource being sent by the last-hop node, the hypothesis test being applied when receiving the UL or DL communication from the last-hop node.

[0181] Aspect 17 is the apparatus according to any one of Aspects 1 to 16, wherein upon receiving the notification flag, the receiving entity applies a pattern of redundancy versions (RVs) on one or more repeated resource units, the one or more repeated resource units being different when the notification flag is not received.

[0182] Aspect 18 is the apparatus according to any one of Aspects 1 to 17, wherein the notification flag is received from an integrated access and backhaul (IAB) donor central unit (CU) via a radio resource control (RRC) message or an F1 application protocol (F1-AP) message, or the notification flag is received from the last-hop node via a media access control (MAC) control element (MAC-CE) or downlink control information (DCI).

[0183] Aspect 19 is the apparatus according to any one of Aspects 1 to 18, wherein the last-hop node is the parent node of the node for DL communication or the child node of the node for UL communication.

[0184] Aspect 20 is the apparatus according to any one of Aspects 1 to 19, wherein the number of repeated transmissions performed by the forwarding entity is equal to the difference between the total number of allocated repeated units in the second UL or DL resource set and the number of skipped repeated units before the decoding completion time.

[0185] Aspect 21 is the apparatus according to any one of aspects 1 to 20, wherein the number of retransmissions performed by the forwarding entity is equal to a fixed number.

[0186] Aspect 22 is the apparatus according to any one of aspects 1 to 21, wherein the fixed number is equal to the difference between the total number of allocated repetition units and the maximum number of skipped repetition units.

[0187] Aspect 23 is the apparatus according to any one of aspects 1 to 22, wherein the at least one processor is further configured to: send an acknowledgement (ACK) or a negative ACK (NACK) when decoding the at least one data packet at the receiving entity of the node.

[0188] Aspect 24 is the apparatus according to any one of aspects 1 to 23, wherein the first UL or DL resource set includes one or more first time slots or mini - slots, and the second UL or DL resource set includes one or more second time slots or mini - slots.

[0189] Aspect 25 is the apparatus according to any one of aspects 1 to 24, wherein the at least one data packet is associated with one or more data packet repetitions or one or more data packet retransmissions.

[0190] Aspect 26 is the apparatus according to any one of aspects 1 to 25, wherein at least one of the first UL or DL resource set or the second UL or DL resource set is configured via DL semi - persistent scheduling (SPS), is configured via UL - configured grant, or is scheduled via dynamic downlink control information (DCI).

[0191] Aspect 27 is the apparatus according to any one of aspects 1 to 26, further comprising: a transceiver or an antenna coupled to the at least one processor.

[0192] Aspect 28 is a device for wireless communication performed at a first node, the device comprising at least one processor coupled to a memory and configured to: send UL or DL communication including at least one data packet to a second node via a first uplink (UL) or downlink (DL) resource set allocated for a receiving entity of the second node; and receive an acknowledgement (ACK) or a negative ACK (NACK) from the second node based on the at least one data packet being decoded at the receiving entity of the second node.

[0193] Aspect 29 is the apparatus according to aspect 28, wherein the at least one processor is further configured to: send a notification flag indicating one or more potentially skipped resources to the second node, the one or more potentially skipped resources being skipped by the first node at the start of the first UL or DL resource set, wherein the UL or DL communication transmitted is based on the notification flag.

[0194] Aspect 30 is an apparatus for wireless communication at a first node, the apparatus including at least one processor coupled to a memory and configured to: receive a notification flag indicating one or more potentially skipped resources from a second node, the one or more potentially skipped resources being skipped by a forwarding entity of the second node at the start of a first uplink (UL) or downlink (DL) resource set; and receive the UL or DL communication including at least one data packet from the second node via the first UL or DL resource set, the first UL or DL resource set being allocated for the forwarding entity of the second node, wherein at least one second resource in a second UL or DL resource set overlaps at least one first resource in the first UL or DL resource set.

[0195] Aspect 31 is a method for wireless communication implementing any one of aspects 1 to 30.

[0196] Aspect 32 is an apparatus for wireless communication, including units for implementing any one of aspects 1 to 30.

[0197] Aspect 33 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 30.

Claims

1. An apparatus for wireless communication performed at a node, comprising: a memory; and at least one processor coupled to the memory and configured to: receive UL or DL communication including at least one data packet via a first uplink (UL) or downlink (DL) resource set allocated for a receiving entity of the node; decode the at least one data packet at the receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time; and send the UL or DL communication including the at least one data packet to a next-hop node via a second UL or DL resource set allocated for a forwarding entity of the node, at least one first resource in the first UL or DL resource set overlapping with at least one second resource in the second UL or DL resource set.

2. The apparatus according to claim 1, wherein the first UL or DL resource set includes one or more first repeating units, and the second UL or DL resource set includes one or more second repeating units.

3. The apparatus according to claim 2, wherein the number of the one or more first repeating units is different from the number of the one or more second repeating units.

4. The apparatus according to claim 2, wherein the receiving entity attempts to decode the at least one data packet when each first repeating unit in the one or more first repeating units is received, and the at least one processor is further configured to: stop receiving at least one remaining first repeating unit in the one or more first repeating units when the at least one data packet is successfully decoded, wherein the receiving of the at least one remaining first repeating unit is stopped at an early termination instance.

5. The apparatus according to claim 4, wherein the at least one processor is further configured to: encode the at least one data packet at the forwarding entity of the node, and after the at least one data packet is encoded, the at least one data packet is sent to the next-hop node via the one or more second repeating units, wherein the one or more second repeating units overlap with the at least one remaining first repeating unit.

6. The apparatus according to claim 1, wherein the node is an IAB node associated with an integrated access and backhaul (IAB) network, the receiving entity corresponds to a mobile terminal (MT) of the node or a distributed unit (DU) of the node, and the forwarding entity corresponds to the DU of the node or the MT of the node.

7. The apparatus according to claim 6, wherein the UL or DL communication is UL communication, the receiving entity corresponds to the DU of the node, the forwarding entity corresponds to the MT of the node, and the next-hop node corresponds to a parent IAB node or an IAB donor.

8. The apparatus according to claim 6, wherein The UL or DL communication is DL communication, the receiving entity corresponds to the MT of the node, and the forwarding entity corresponds to the DU of the node, and the next-hop node corresponds to a sub-IAB node or a sub-user equipment (UE).

9. The apparatus according to claim 1, wherein, the second UL or DL resource set is allocated after the decoding completion time.

10. The apparatus according to claim 9, wherein, the second UL or DL resource set overlaps with one or more remaining first resources in the first UL or DL resource set, and the receiving entity does not use the one or more remaining first resources.

11. The apparatus according to claim 1, wherein, the second UL or DL resource set is allocated before the decoding completion time.

12. The apparatus according to claim 11, wherein, the second UL or DL resource set is allocated based on an assumption of the earliest possible decoding completion time.

13. The apparatus according to claim 12, wherein, at least one second resource in the second UL or DL resource set starts before the decoding completion time, and the forwarding entity skips the at least one second resource, wherein the forwarding entity sends the at least one data packet to the next-hop node via a part of the second UL or DL resource set that starts after the decoding completion time.

14. The apparatus according to claim 13, wherein, the at least one processor is further configured to: send a notification flag indicating one or more potentially skipped resources to the next-hop node, the one or more potentially skipped resources being skipped by the forwarding entity at the start of the second UL or DL resource set.

15. The apparatus according to claim 13, wherein, the at least one processor is further configured to: receive, from the last-hop node, a notification flag indicating one or more potentially skipped resources, the one or more potentially skipped resources being skipped by the last-hop node at the start of the first UL or DL resource set, wherein the received UL or DL communication is based on the notification flag.

16. The apparatus according to claim 15, wherein, upon receiving the notification flag, the receiving entity applies a hypothesis test to the starting position of the first resources in the first UL or DL resource set, the first resources being sent by the last-hop node, and the hypothesis test is applied when receiving the UL or DL communication from the last-hop node.

17. The apparatus according to claim 15, wherein, upon receiving the notification flag, the receiving entity applies a pattern of redundancy versions (RVs) on one or more repeated resource units, and the one or more repeated resource units are different when the notification flag is not received.

18. The apparatus according to claim 15, wherein, The notification flag is received from an integrated access and backhaul (IAB) donor central unit (CU) via a radio resource control (RRC) message or an F1 application protocol (F1-AP) message, or the notification flag is received from the last-hop node via a media access control (MAC) control element (MAC-CE) or downlink control information (DCI).

19. The apparatus according to claim 15, wherein, the last-hop node is a parent node of a node for DL communication or a child node of a node for UL communication.

20. The apparatus according to claim 13, wherein, the number of repeated transmissions performed by the forwarding entity is equal to the difference between the total number of allocated repetition units in the second UL or DL resource set and the number of skipped repetition units before the decoding completion time.

21. The apparatus according to claim 13, wherein, the number of repeated transmissions performed by the forwarding entity is equal to a fixed number.

22. The apparatus according to claim 21, wherein, the fixed number is equal to the difference between the total number of allocated repetition units and the maximum number of skipped repetition units.

23. The apparatus according to claim 1, wherein, the at least one processor is further configured to: send an acknowledgement (ACK) or a negative ACK (NACK) when decoding the at least one data packet at the receiving entity of the node.

24. The apparatus according to claim 1, wherein, the first UL or DL resource set includes one or more first time slots or mini-slots, and the second UL or DL resource set includes one or more second time slots or mini-slots.

25. The apparatus according to claim 1, wherein, the at least one data packet is associated with one or more data packet repetitions or one or more data packet retransmissions.

26. The apparatus according to claim 1, further comprising: a transceiver or an antenna coupled to the at least one processor, wherein at least one of the first UL or DL resource set or the second UL or DL resource set is configured via DL semi-persistent scheduling (SPS), is configured via a UL-configured grant, or is scheduled via dynamic downlink control information (DCI).

27. A method for wireless communication at a node, comprising: receiving UL or DL communication including at least one data packet via a first uplink (UL) or downlink (DL) resource set, the first UL or DL resource set being allocated for a receiving entity of the node; decoding the at least one data packet at the receiving entity during a decoding period, the decoding period including a decoding start time and a decoding completion time; and Send the UL or DL communication including the at least one data packet to a next-hop node via a second UL or DL resource set, where the second UL or DL resource set is allocated for a forwarding entity of the node, and at least one first resource in the first UL or DL resource set overlaps with at least one second resource in the second UL or DL resource set.

Images