Uplink preemption indication for full-duplex based IAB

Abstract

Various aspects of the present disclosure provide techniques for sending an uplink preemption indication in an integrated access and backhaul (IAB) system, which identifies resources or symbols that can be punctured by the IAB in order to minimize self-interference at the IAB node in the following circumstances: during an ongoing uplink transmission from the IAB node to a parent backhaul node, an ultra-reliable low-latency communication (URLLC) packet is received at the IAB node from one of a child IAB node or a user equipment (UE).

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly, to uplink preemption indication for a full-duplex based integrated access and backhaul (IAB) node in a wireless communication system. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. For example, it is envisioned that the fifth generation (5G) wireless communication technology (which may be referred to as New Radio (NR)) extends and supports different usage scenarios and applications with respect to the current mobile network generation. In one aspect, 5G communication technology may include: enhanced mobile broadband that addresses people-centric use cases for accessing multimedia content, services, and data; ultra-reliable-low latency communications (URLLC) with specifications for latency and reliability; and massive machine type communications, which may allow for very large numbers of connected devices and the transmission of relatively small amounts of non-delay sensitive information. However, as the demand for mobile broadband access continues to grow, further improvements in NR communication technology and beyond may be expected.

[0004] For example, with NR communication technology and beyond, current backhaul solutions may not provide the desired speeds or customization levels for efficient operation. Therefore, improvements in wireless communication operations may be expected. Summary of the invention

[0005] Various aspects of the present disclosure provide techniques for sending uplink preemption indications in an integrated access and backhaul (IAB) system, where the uplink preemption indications identify resources or symbols that can be punctured by the IAB so as to minimize self-interference at the IAB node in the following circumstances: during an ongoing uplink transmission from the IAB node to a parent backhaul node, an ultra-reliable low-latency communication (URLLC) packet is received at the IAB node from one of a child IAB node or a user equipment (UE).

[0006] In one example, a method for wireless communication is disclosed. The method may include: during a first time slot, sending uplink traffic from a first node to a second node via a physical uplink shared channel (PUSCH). The method may also include: at the first node during the first time slot, on resources that conflict with uplink traffic transmission from the first node to the parent backhaul node, receiving emergency URLLC traffic from a third node. The method may also include: based on the reception of the emergency URLLC traffic at the first node, puncturing at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node during the first time slot. The method may also include: sending an uplink preemption indication from the first node to the second node identifying at least a portion of the resources punctured by the first node.

[0007] In another example, an apparatus for wireless communication. The apparatus may include a memory having instructions and a processor configured to execute the instructions to perform the following operations: sending uplink traffic from a first node to a second node via a PUSCH during a first time slot. The processor may be further configured to execute instructions to perform the following operations: receiving URLLC traffic from a third node on resources that conflict with uplink traffic transmission from the first node to the second node during a first time slot at the first node. The processor may also be configured to execute instructions to perform the following operations: based on the reception of emergency URLLC traffic at the first node, puncturing at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node during the first time slot. The processor may also be configured to execute instructions to perform the following operations: sending an uplink preemption indication from the first node to the second node identifying at least a portion of the resources punctured by the first node.

[0008] In some aspects, a non-transitory computer-readable medium includes instructions stored thereon, which, when executed by a processor, cause the processor to perform the following steps: sending uplink traffic from a first node to a second node via a PUSCH during a first time slot. The computer-readable medium may also include instructions for performing the following operations: receiving emergency URLLC traffic from a third node at a first node during a first time slot on resources that conflict with uplink traffic transmission from the first node to the second node. The computer-readable medium may also include instructions for performing the following operations: based on the reception of emergency URLLC traffic at the first node, puncturing at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node during the first time slot. The computer-readable medium may also include instructions for performing the following operations: sending an uplink preemption indication from the first node to the parent backhaul node identifying at least a portion of the resources punctured by the first node.

[0009] In certain aspects, the apparatus includes: a unit for transmitting uplink traffic from a first node to a second node via a PUSCH during a first time slot. The apparatus may also include: a unit for receiving emergency URLLC traffic from a third node at the first node during the first time slot on resources that conflict with uplink traffic transmission from the first node to the second node. The apparatus may also include: a unit for puncturing at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node during the first time slot based on reception of the emergency URLLC traffic at the first node. The apparatus may also include: a unit for sending an uplink preemption indication from the first node to the second node identifying at least a portion of the resources punctured by the first node.

[0010] In some examples, another method, apparatus, and computer-readable medium are disclosed. The method may include: receiving uplink traffic from a first node via a PUSCH during a first time slot. The method may also include: receiving an uplink preemption indication from the first node at a second node, the uplink preemption indication identifying that at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node is punctured by the first node due to the following situation: receiving an emergency URLLC service at the first node during a first time slot on at least a portion of the resources that conflict with the uplink traffic transmission from the first node to the second node. The method may also include: decoding the uplink preemption indication to identify at least a portion of the resources corresponding to the punctured service.

[0011] To accomplish the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying 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 basic principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The disclosed aspects will hereinafter be described in conjunction with the accompanying drawings, which are provided to illustrate the disclosed aspects rather than to limit the disclosed aspects, wherein like numerals indicate like elements, and wherein:

[0013] Figure 1 is a schematic diagram of an example of a wireless communication system according to aspects of the present disclosure;

[0014] Figure 2 is an example of a schematic diagram for sending an uplink preemption indication in an IAB system according to aspects of the present disclosure;

[0015] Figure 3Ais an example technique for sending an uplink preemption indication on resources reserved in a PUCCH indicated in a previously transmitted DCI in accordance with aspects of the present disclosure;

[0016] Figure 3B is an example of another technique for sending an uplink preemption indication in a reserved resource element of a PUSCH for which an IAB node has punctured resources in accordance with aspects of the present disclosure;

[0017] Figure 3C is an example of another technique for sending an uplink preemption indication in a reserved resource element of a retransmitted or repeated PUSCH transmission in accordance with aspects of the present disclosure;

[0018] Figure 4 is a schematic diagram of an example implementation of various components of an IAB node according to various aspects of the present disclosure;

[0019] Figure 5 is a flowchart of an example of a wireless communication method implemented by an IAB node according to aspects of the present disclosure; and

[0020] Figure 6 is a flow chart of an example of a wireless communication method implemented by an IAB parent node according to aspects of the present disclosure. DETAILED DESCRIPTION

[0021] One aspect of 5G NR communication technology includes the use of high spectrum bands above 24 GHz (which may be referred to as mmW). The use of these frequency bands enables extremely high data rates and a significant increase in data processing capabilities. However, compared to LTE, mmW bands are susceptible to rapid channel changes and suffer from severe free space path loss and atmospheric absorption. In addition, millimeter wave bands are extremely susceptible to blockage (e.g., hands, heads, bodies, leaves, building penetration). In particular, at mmW frequencies, even small changes in the environment (such as turning of the head, movement of the hand, or a passing car) may change the channel conditions between the base station (BS) and the user equipment (UE), and thereby affect communication performance.

[0022] Current mmW 5G NR systems utilize the small wavelengths of mmW at higher frequencies to utilize multiple-input multiple-output (MIMO) antenna arrays to create highly directional beams that concentrate the transmitted radio frequency (RF) energy in an attempt to overcome the propagation and path loss challenges in both the uplink and downlink. However, the isodirectional path loss and propagation characteristics of the mmWave environment require dense deployment of next-generation node base stations (gNBs) (i.e., base stations using NR technology) to guarantee line-of-sight links at any given time and reduce the probability of outages. In such deployments, it may not be feasible to equip each such gNB with a wired backhaul link (e.g., optical fiber) due to the high costs involved. Therefore, network operators have considered using wireless backhaul as a more cost-effective alternative solution for high-density deployment scenarios. However, the use of wireless backhaul communications introduces additional implementation challenges, including interference management.

[0023] Facilitating wireless backhaul communications may include utilizing IAB nodes (which may include "relay nodes"), which may have both base station (gNB) type and user equipment (UE) type functionality. IAB nodes provide wireless communication system flexibility such that only a small portion of gNBs may be equipped with traditional wired backhaul capabilities (e.g., using cables or optical fibers), while the remaining gNBs (or IAB nodes) may have a wireless connection to the wired backhaul, either directly or indirectly (e.g., via relay nodes), for example, via multiple hops through one or more relay nodes. According to the 3GPP protocol, an NR cellular network with IAB functionality may have the following features: (i) the possibility of using mmWave spectrum; (ii) integration of access and backhaul technologies (i.e., using the same spectrum resources and infrastructure to serve mobile terminals in access and NR gNBs in backhaul); and (iii) the possibility of deploying plug-and-play IAB nodes that are capable of self-configuration and self-optimization.

[0024] To this end, the IAB node may include a gNB type function that allows signals to be sent to and received from a child node (e.g., a UE or another IAB node) over an access link. In addition, the IAB node may also include a UE type function that allows signals to be sent to and received from a parent node (e.g., a gNB or another IAB node) over a backhaul link. By utilizing the IAB node, a common architecture, waveform, and process may be shared for the access link and the backhaul link, thereby reducing system complexity. For example, the IAB node may share the same radio resources (e.g., via TDM or FDM) between the access link and the backhaul link.

[0025] In a full-duplex time slot, a full-duplex IAB node can simultaneously (using the same time slot and shared resources) send uplink traffic to a parent backhaul node and receive uplink traffic from one or more of the IAB child nodes or UEs. Conversely, a full-duplex IAB node can also simultaneously send downlink traffic to a child node while receiving downlink packets from a parent node during the same time slot. In some systems, the 3GPP protocol provides downlink preemption indications for enhanced mobile broadband (eMBB) multiplexing. Specifically, for an eMBB UE, if URLLC data is transmitted (e.g., URLLC data is preferentially transmitted) during a regularly scheduled downlink, the serving cell indicates downlink preemption to the UE in a subsequent group common DCI (GC-DCI), and the GC-DCI is monitored by one or more UEs using an interrupted radio network temporary identifier (RNTI) configured by a radio resource control (RRC). However, in instances of uplink communications that may be affected by uplink URLLC traffic, group common DCI is not available.

[0026] Accordingly, various aspects of the present disclosure provide techniques for sending uplink preemption indications in an IAB system, the uplink preemption indications identifying resources or symbols that may be punctured by the IAB so as to minimize self-interference at the IAB node in the following circumstances: during an ongoing uplink transmission from the IAB node to the parent backhaul node, a URLLC packet is received at the IAB node from one of the child IAB nodes or the UE.

[0027] For example, during an ongoing slot-level scheduled uplink transmission from an IAB node to a parent node (wherein the slot may also be used by the IAB node to receive uplink traffic from a UE or one or more of the IAB child nodes), the reception of emergency URLLC uplink traffic with micro-slot scheduling (e.g., partial subframe overlap) at the IAB node may cause the IAB to experience self-interference (e.g., transmissions on overlapping resources may be affected or interfered with). To remedy this situation, the IAB node may, based on one or more of the techniques outlined below, puncture the PUSCH to the parent return node for one or more symbols (or resources) used by the UE or IAB child node in the transmission of emergency URLLC traffic to the IAB node. Puncturing is the process of deleting one or more check bits in the check bits after encoding with an error correction code. Puncturing can also be used in wireless communications in the rate matching process.

[0028] For example, according to the first technique, the uplink preemption indication resource configuration may rely on the resources of a subsequently sent physical uplink control channel to transmit the uplink preemption indication. Specifically, in some instances, when a DCI is used to schedule a PUSCH transmission from an IAB node to a parent return node, the IAB node may additionally indicate in the same DCI the PUCCH resources that may be used by the IAB node for preemption indication. Thus, if during a first time slot, one or more symbols of the PUSCH associated with an uplink service from the IAB node to the parent return node are punctured by the IAB node to accommodate receiving emergency URLLC uplink services from a child node / UE on overlapping resources (e.g., in portions of time slots and resources that may be shared for simultaneous uplink transmission to a parent node and reception from a child node), the IAB node may signal the parent node with an uplink preemption indication to indicate the punctured or affected symbols. As discussed, in one example, such an uplink preemption indication may be sent in the resources of a PUCCH sent during the second time period, the resources being reserved in the DCI for scheduling PUSCH transmissions previously during the first time period. In some examples, the uplink preemption indication may include both a PUCCH resource set ID and a PUCCH resource ID. In other examples, the uplink preemption indication may include only a PUCCH resource ID, where the PUCCH resource set ID may be provided or RRC configured. In some examples, the indicated PUCCH resource may also have a time domain offset from the last symbol of the PUSCH to the first symbol of the PUCCH resource. In such an example, the time domain offset may also be indicated by an uplink grant, predetermined in the standard, or RRC configured. In a further example, the uplink preemption indication may be a slot level at the transport block level (e.g., for a PUCCH format with a small payload), or a symbol level and / or frequency range level indication (e.g., for a PUCCH format with a large payload).

[0029] In another example, according to various aspects of the second technology, the uplink preemption indication can be a resource configured with a reserved resource element in a PUSCH punctured by an IAB node. Specifically, in some instances, the scheduling resources for PUSCH transmission (e.g., uplink traffic from an IAB node to a parent backhaul node) may include one or more reserved resource elements that can be used for uplink preemption indication. In some instances, a resource element may be located in one or more last symbols of a resource for PUSCH, and the one or more last symbols may not be used for emergency URLLC services (e.g., may not be punctured to accommodate uplink traffic from a child node). Although various aspects of the present disclosure discuss that the reserved resource element is located in one or more last symbols, it should be understood by those skilled in the art that the reserved resource element for carrying the uplink preemption indication in PUSCH may be located in any or part of the symbols of PUSCH. In some instances, the existence, quantity, and position of the reserved resource element may be configured or indicated by a parent node, or may be predetermined in a standard. In some instances, the preemption indication may be based on a digital payload and / or sequence. For example, as noted above, the uplink preemption indication may be a timeslot level indication at a transport block level (eg, for a small number of reserved resource elements), or a symbol level and / or frequency range level indication (eg, for a large number of reserved resource elements).

[0030] In yet another example, according to aspects of the third technique, a preemption indication regarding a previous PUSCH transmission / repetition may be included in one or more resource elements of a subsequent PUSCH retransmission / repetition sent from the IAB node to the parent backhaul node during the second time period. In such an instance, the uplink preemption indication may indicate which previously transmitted RV, repetition, or symbol is affected by puncturing.

[0031] In another example, according to aspects of the fourth technique, a preemption indication resource configuration may be included in a medium access control (MAC) control element (MAC-CE) message that includes a subsequent PUSCH with a hybrid automatic repeat request (HARQ)-ID. In some examples, the MAC-CE-based preemption indication may include an indication of which previously transmitted RV or repetition is affected and which symbol is affected relative to a particular RV / repetition.

[0032] Additionally or alternatively, aspects of the present disclosure also include techniques for determining whether a preemption indication is needed. For example, when a scheduling request (SR) is sent from an IAB node to a parent node, the IAB node may use one / several bits to indicate whether resources for preemption indication are needed, based at least in part on whether the IAB node believes that the corresponding resources can be used by the UE / child node for emergency UL URLLC services. In some examples, the type of uplink preemption indication may be a slot level or a symbol level, and may further identify a technology selected from a plurality of technologies identified above for sending preemption indications. To this end, the IAB node may identify the number and position of reserved resource elements to be used for preemption indications, as well as the PUCCH format and / or payload size, based at least in part on the type of uplink preemption indication. In addition, the IAB node may send an SR to a second node to indicate a puncturing technique applied by a first node from a plurality of available puncturing techniques. Specifically, the SR may indicate a specific solution in the above solution for applying an uplink preemption indication.

[0033] Now refer to Figure 1-6 To describe various aspects in more detail. In the following description, for the sake of illustration, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it is apparent that such aspects may be implemented without these specific details. In addition, the term "component" as used herein may be a component of a component that constitutes a system, may be hardware, firmware, and / or software stored on a computer-readable medium, and may be divided into other components.

[0034] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of protection of the present disclosure. Various examples may omit, replace, or add various processes or components as needed. For example, the described method may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, the features described with respect to certain examples may be combined in other examples.

[0035] Figure 11 is a schematic diagram showing an example of a wireless communication system and an access network 100 for uplink preemption indication in an IAB system. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network, such as an evolved packet core (EPC) 180 and / or a 5G core (5GC) 190. One or more base stations 102 and / or UEs 104 may operate according to millimeter wave (mmW or mmWave) technology. For example, mmW technology includes transmission in mmW frequencies and / or near mmW frequencies. Specifically, extremely high frequency (EHF) is a part of radio frequency (RF) in the electromagnetic spectrum, wherein EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this frequency band may be referred to as millimeter waves. Near mmW may extend downward to a frequency of 3 GHz with a wavelength of 100 mm. For example, the super high frequency (SHF) band extends between 3 GHz and 30 GHz and may also be referred to as centimeter waves.

[0036] As noted above, communications using mmW and / or near-mmW radio frequency bands have extremely high path losses and short ranges. Therefore, the propagation characteristics of the mmW environment require the deployment of dense gNBs 102 (i.e., base stations 102 using NR technology) to ensure line-of-sight links at any given time and reduce the probability of interruptions. However, it may not be economically feasible to provide a wired backhaul link 132 for each such gNB 102. Therefore, alternative wireless backhauls 164 that utilize IAB nodes 150 to facilitate 5G communications have been considered.

[0037] In some examples, the IAB node 150 can include both gNB type functionality and UE type functionality. The IAB node 150 provides flexibility to the wireless communication system 100 so that only a small portion of the gNBs (e.g., base stations 102-a, 102-b) can be equipped with traditional fiber-like wired 132 backhaul capabilities, while the remaining gNBs (e.g., IAB nodes 150) can act as relays that may be wirelessly connected to the fiber infrastructure 164 through multiple hops. In some examples, one or more IAB nodes 150 may include an uplink preemption indication component 450 (see Figure 4 ) for sending an uplink preemption indication in the IAB system, the uplink preemption indication identifying resources or symbols that can be punctured by the IAB so as to minimize self-interference at the IAB node 150 in the following circumstances: during an ongoing uplink transmission from the IAB node to the parent backhaul node, a URLLC packet is received at the IAB node 150 from one of the child IAB nodes or the UE.

[0038] The EPC 180 and / or 5GC 190 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connections, and other access, routing or mobility functions. The base station 102 may 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, RAN information management (RIM), paging, positioning and transmission of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 180 or 5GC 190) via backhaul links 132, 134 (e.g., Xn, X1 or X2 interfaces), which may be wired or wireless communication links.

[0039] The base stations 102 may communicate wirelessly with the UEs 104 via one or more base station antennas. Each of the base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In some examples, the base stations 102 may be referred to as base transceiver stations, radio base stations, access points, access nodes, radio transceivers, node Bs, eNodeBs (eNBs), gNBs, home node Bs, home eNodeBs, gNodeBs (gNBs), relays, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmission reception points (TRPs), or some other appropriate terminology. The geographic coverage area 110 for the base stations 102 may be divided into sectors or cells (not shown) that constitute only a portion of the coverage area. The wireless communication network 100 may include different types of base stations 102 (e.g., macro base stations 102 or small cell base stations 180 described below).

[0040] In some examples, the wireless communication network 100 may be or include one or any combination of communication technologies, including NR or 5G technology, long term evolution (LTE) or improved LTE (LTE-A) or MuLTEfire technology, Wi-Fi technology, Bluetooth technology, or any other long-range or short-range wireless communication technology. The wireless communication network 100 may be a heterogeneous technology network in which different types of base stations provide coverage for various geographic areas. For example, each base station 102 may provide communication coverage for a macro cell, a small cell, or other types of cells. Depending on the context, the term "cell" is a 3GPP term that can be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., a sector, etc.) of a carrier or base station.

[0041] A macro cell may generally cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 104 that has a service subscription with a network provider. A small cell may include a relatively low transmit power base station compared to a macro cell, which may operate in the same or different frequency band (e.g., licensed, unlicensed, etc.) compared to a macro cell. According to various examples, a small cell may include a pico cell, a femto cell, and a micro cell. For example, a pico cell may cover a small geographic area and may allow unrestricted access by a UE 104 that has a service subscription with a network provider. A femto cell may also cover a small geographic area (e.g., a residence) and may provide restricted access and / or unrestricted access by a UE 104 associated with the femto cell (e.g., in a restricted access case, a UE 104 in a closed subscriber group (CSG) of a base station 102, which may include a UE 104 for users in a home, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (eg, two, three, four, etc.) cells (eg, component carriers).

[0042] The communication network that can adapt to some examples in various disclosed examples can be a packet-based network that operates according to a layered protocol stack, and the data in the user plane can be based on IP. The user plane protocol stack (e.g., Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, etc.) can perform packet segmentation and reorganization to communicate through logical channels. For example, the MAC layer can perform priority processing, and multiplexing of logical channels to transport channels. The MAC layer can also use hybrid automatic repeat / request (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration and maintenance of the RRC connection between the UE 110 and the base station 105. The RRC protocol layer can also be used in the core network 115 to support radio bearers for user plane data. At the physical (PHY) layer, transport channels can be mapped to physical channels.

[0043] UE 104 may be dispersed throughout the wireless communication network 100, and each UE 104 may be stationary or mobile. UE 104 may also include or be referred to by those skilled in the art as a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. UE 104 may be a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a smart watch, a wireless local loop (WLL) station, an entertainment device, a vehicle component, a customer premises equipment (CPE), or any device capable of communicating in the wireless communication network 100. Some non-limiting examples of UE 104 may include a Session Initiation Protocol (SIP) phone, a satellite radio unit, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functional device. In addition, UE 104 may be an Internet of Things (IoT) and / or Machine-to-Machine (M2M) type device that may not frequently communicate with the wireless communication network 100 or other UEs in some aspects, such as a low-power, low-data rate (e.g., relative to a wireless phone) type device. UE 104 is capable of communicating with various types of base stations 102 and network devices including macro eNBs, small cell eNBs, macro gNBs, small cell gNBs, gNBs, relay base stations, etc.

[0044] UE 104 may be configured to establish one or more wireless communication links 120 with one or more base stations 102. The wireless communication links 120 shown in the wireless communication network 100 may carry uplink (UL) transmissions from UE 104 to base station 102, or downlink (DL) transmissions from base station 102 to UE 104. Each wireless communication link 120 may include one or more carriers, where each carrier may be a signal composed of multiple subcarriers (e.g., waveform signals of different frequencies) modulated according to the various radio technologies described above. Each modulated signal may be sent on a different subcarrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. In one aspect, the wireless communication link 120 may use frequency division duplex (FDD) (e.g., using paired spectrum resources) or time division duplex (TDD) operation (e.g., using non-paired spectrum resources) to transmit bidirectional communications. A frame structure for FDD (e.g., frame structure type 1) and a frame structure for TDD (e.g., frame structure type 2) may be defined. Moreover, in some aspects wireless communication link 120 may represent one or more broadcast channels.

[0045] In some aspects of the wireless communication network 100, the base station 102 or the UE 104 may include multiple antennas to employ an antenna diversity scheme to improve the communication quality and reliability between the base station 102 and the UE 104. Additionally or alternatively, the base station 102 or the UE 104 may employ multiple-input multiple-output (MIMO) technology, which may utilize a multipath environment to transmit multiple spatial layers carrying the same or different encoded data.

[0046] The wireless communication network 100 may also support operation on multiple cells or carriers, a feature that may be referred to as carrier aggregation (CA) or multi-carrier operation. A carrier may also be referred to as a component carrier (CC), layer, channel, etc. The terms "carrier," "component carrier," "cell," and "channel" may be used interchangeably herein. The UE 104 may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation. Carrier aggregation may be used with both FDD component carriers and TDD component carriers. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The base station 105 and / or the UE 110 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 30, 50, 100, 200, 400, etc. MHz) bandwidth per carrier allocated in a total of up to Yx MHz (x=number of component carriers) for transmission in each direction. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). A component carrier may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell), and a secondary component carrier may be referred to as a secondary cell (SCell).

[0047] Some UEs 110 may communicate with each other using a device-to-device (D2D) communication link 138. The D2D communication link 138 may use DL / UL WWAN spectrum. The D2D communication link 138 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed via various wireless D2D communication systems (e.g., FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR).

[0048] The wireless communication network 100 may also include a base station 102 (e.g., a Wi-Fi access point) operating in accordance with Wi-Fi technology, which communicates with a UE 110 (e.g., a Wi-Fi station (STA)) operating in accordance with Wi-Fi technology via a communication link in an unlicensed spectrum (e.g., 5 GHz). When communicating in an unlicensed spectrum, the STA and the AP may perform a clear channel assessment (CCA) or a listen-before-talk (LBT) procedure before communicating to determine whether a channel is available.

[0049] Small cells can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cells can adopt NR and use the same 5 GHz unlicensed spectrum used by Wi-Fi APs. Small cells that adopt NR in unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network.

[0050] In a non-limiting example, the EPC 180 may include a mobile management entity (MME) 181, other MMEs 182, a serving gateway 183, a multimedia broadcast multicast service (MBMS) gateway 184, a broadcast multicast service center (BM-SC) 185, and a packet data network (PDN) gateway 186. The MME 181 may communicate with a home subscriber server (HSS) 187. The MME 181 is a control node that handles signaling between the UE 110 and the EPC 180. Typically, the MME 181 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 183, which itself is connected to the PDN gateway 186. The PDN gateway 186 provides UE IP address allocation and other functions. The PDN gateway 186 and the BM-SC 185 are connected to IP services 188. The IP services 188 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 185 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 185 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 to schedule MBMS transmissions. The MBMS Gateway 184 may be used to distribute MBMS services to base stations 105 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collect charging information related to eMBMS.

[0051] 5GC 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. AMF 192 may communicate with unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 110 and 5GC 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.

[0052] refer to Figure 2 , schematic diagram 200 includes an example of a wireless communication system that employs mmW communications in accordance with various aspects of the present disclosure. Diagram 200 also illustrates one or more base stations 102, in addition to one or more IAB nodes 205 (such as IAB node 205 and IAB node 215), which may include traditional wired (e.g., via cable or optical fiber) backhaul capabilities 132, which may not have wired backhaul capabilities 132 and therefore utilize wireless communications 164 with the base stations 102 to define wireless backhaul capabilities. In some aspects, the IAB node 205 may be a reference Figure 1 Examples of one or more IAB nodes 150 are discussed.

[0053] The base station 102 and / or the IAB nodes 205 and 210 may serve one or more UEs 104 via corresponding wireless communication links 154. In some cases, the IAB node 205 may be referred to as a relay node based on the IAB node 205 wirelessly connecting the IAB child node 210 to the wired backhaul capability 132 of the base station 102. As discussed above, one or more IAB nodes 205 and 215 may provide both UE-type functionality and gNB-type functionality. The UE-type functionality of the IAB node 205 or 215 may allow signals to be sent to and received from the parent node 102 (e.g., gNB 102 or another IAB node) over a backhaul link. Conversely, the gNB-type functionality of the IAB node 205 may allow signals to be sent to and received from a child node (e.g., UE 104 or another IAB child node 215) over an access link. As noted above, the IAB functionality of IAB nodes 205 and 215 may have the following features: (i) use of mmWave spectrum; (ii) integration of access technology and backhaul technology (i.e., using the same spectrum resources and infrastructure to provide services to mobile terminals in access and NR gNBs in backhaul); and (iii) the possibility of deploying plug-and-play IAB nodes that are capable of self-configuration and self-optimization.

[0054] In some examples, the IAB node 205 may be a full-duplex IAB node such that in a full-duplex timeslot, the IAB node 205 may simultaneously or concurrently send uplink traffic 220 to the parent backhaul node 102 and receive uplink traffic 225 from one or more of the IAB child nodes 215 or UEs 104. For example, during an ongoing timeslot-level scheduled uplink transmission 220 from the IAB node 205 to the parent node 102 (where the timeslot may also be used by the IAB node 205 to receive uplink traffic 225 from the UE 104 or one or more of the IAB child nodes 215), receiving emergency URLLC uplink traffic with mini-slot scheduling at the IAB node 205 from the UE 104 or one or more of the IAB child nodes 215 may cause the IAB node 205 to experience self-interference (e.g., transmissions on overlapping resources may be affected or interfered). To remedy this situation, the IAB node 205 may puncture the PUSCH to the parent backhaul node 102 for one or more symbols (or resources) used by the UE 104 or the IAB child node 215 in the transmission of the emergency URLLC traffic 225 to the IAB node 205, based on one or more techniques outlined below.

[0055] Figure 3A 3 is a timing diagram 300 of a first technique for sending an uplink preemption indication on resources reserved in a PUCCH 320 indicated in a previously transmitted DCI 305 in accordance with aspects of the present disclosure. Specifically, in some instances, to schedule a PUSCH transmission 310, the IAB node 205 may send a DCI 305 to the parent node 102 to identify resources for the PUSCH 310. In accordance with aspects of the present disclosure, the DCI 305 may additionally indicate in the same DCI 305 PUCCH resources 320, which may be used by the IAB node 205 for preemption indications for any symbols 315 that may be punctured in the PUSCH 310 that may be sent by the IAB node 205 during the first time period.

[0056] Thus, if during the first time slot, one or more symbols of the PUSCH associated with uplink traffic from the IAB node to the parent backhaul node are punctured 315 (e.g., symbol 4) by the IAB node 205 to accommodate reception of emergency URLLC uplink traffic from the child node 215 / UE 104 on overlapping resources, the IAB node 205 may signal to the parent node 102 an uplink preemption indication for the punctured or affected one or more symbols 315.

[0057] As discussed, in one instance, such an uplink preemption indication may be sent in resources of a PUCCH 320 sent during the second time period, the resources being previously reserved in a DCI 305 for scheduling PUSCH 310 transmissions during the first time period. In some examples, the uplink preemption indication may include both a PUCCH resource set ID and a PUCCH resource ID. In other instances, the uplink preemption indication may include only a PUCCH resource ID, where the PUCCH resource set ID may be given or RRC configured. In some instances, the indicated PUCCH resource may also have a time domain offset from the last symbol of the PUSCH to the first symbol of the PUCCH resource. In such instances, the time domain offset may also be indicated by an uplink grant, predetermined in the standard, or RRC configured. In a further example, the uplink preemption indication may be a timeslot level at a transport block level (e.g., for a PUCCH format with a small payload), or a symbol level and / or frequency range level indication (e.g., for a PUCCH format with a large payload).

[0058] Figure 3B 3 is an example of another technique for sending an uplink preemption indication in accordance with aspects of the present disclosure. Specifically, once the IAB node 205 punctures one or more symbols 315 of an uplink transmission PUSCH 310 from the IAB node 205 to the parent node 102 to accommodate an emergency URLLC uplink packet from one of the child node 215 or the UE 104, the IAB node 205 may utilize one or more reserved resource elements 355 of the PUSCH 310 for which the IAB node identifies the punctured resources to the parent node 102.

[0059] In particular, in some instances, the scheduled resources for PUSCH transmission 310 (e.g., uplink traffic from IAB node 205 to parent backhaul node 102) may include one or more reserved resource elements 355 that may be used for uplink preemption indication. In some instances, resource element 355 may be located in one or more last symbols of the resources for PUSCH 310, and the one or more last symbols may not be used for emergency URLLC services (e.g., not punctured to accommodate uplink traffic from child nodes). In addition, in some examples, the presence, quantity, and position of reserved resource elements 355 may be configured or indicated by parent node 102, or predetermined in the standard. In some instances, the preemption indication may be based on digital payload and / or sequence. For example, as indicated above, the uplink preemption indication may be a time slot level at a transport block level (e.g., for a small number of reserved resource elements), or a symbol level and / or frequency range level indication (e.g., for a large number of reserved resource elements).

[0060] Figure 3C is another example of a technique for sending an uplink preemption indication in accordance with aspects of the present disclosure. Specifically, in some instances, a preemption indication regarding a previous PUSCH transmission 380 may be included in one or more resource elements 395 of a subsequent PUSCH 390 retransmission / repetition sent from the IAB node 205 to the parent backhaul node 102 during the second time period. In such an instance, the uplink preemption indication may indicate which previously transmitted RV, repetition, or symbol is affected by puncturing.

[0061] In addition, although not shown, additional techniques for sending uplink preemption indication resource configuration may include a MAC-CE message that is included with a subsequent PUSCH with a HARQ-ID. In some examples, the MAC-CE based preemption indication may include an indication of which previously transmitted RV or repetition is affected and which symbol is affected relative to a particular RV / repetition.

[0062] Additionally or alternatively, aspects of the present disclosure also include techniques for determining whether a preemption indication is needed. For example, when an SR is sent from an IAB node to a parent node, the IAB node may use one / several bits to indicate whether resources for preemption indication are needed, based at least in part on whether the IAB node believes that the corresponding resources can be used by the UE / child node for emergency UL URLLC services. In some examples, the type of uplink preemption indication may be a timeslot level or a symbol level, and may further identify a technique selected from the multiple techniques identified above for sending preemption indications. To this end, the IAB node may identify the number and location of reserved resource elements to be used for preemption indications, as well as the PUCCH format and / or payload size, based at least in part on the type of uplink preemption indication.

[0063] Figure 4 The hardware components and subcomponents of a device that may be an IAB node 150 or 205 for various aspects of implementing one or more methods described herein (e.g., method 500) according to the present disclosure are shown. For example, one example of an implementation of the IAB node 205 may include a variety of components, some of which have been described above, but may include components that may operate in conjunction with the uplink preemption indication component 450 to perform the functions described herein in connection with one or more methods (e.g., 500) including the present disclosure, such as one or more processors 412, memory 416, and transceiver 402 in communication via one or more buses 444.

[0064] In some examples, the uplink preemption indication component 450 may include a resource punching component 455, which punches at least a portion of the resources of the PUSCH for uplink traffic from the IAB to the parent backhaul node during the first time slot based on receiving the emergency URLLC traffic at the IAB node. The uplink preemption indication component 450 may also include an uplink preemption generation component 460 to generate an uplink preemption indication identifying at least a portion of the resources punched by the IAB node, and send the uplink preemption indication from the IAB node to the parent backhaul node.

[0065] One or more processors 412, modem 414, memory 416, transceiver 402, RF front end 488 and one or more antennas 465 can be configured to support voice and / or data calls (simultaneously or non-simultaneously) in one or more radio access technologies. In one aspect, one or more processors 412 can include a modem 414 using one or more modem processors. Various functions related to uplink preemption indication component 450 can be included in modem 414 and / or processor 412, and in one aspect, can be performed by a single processor, while in other aspects, different functions of the functions can be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 412 can include any one or any combination of the following: modem processor, or baseband processor, or digital signal processor, or transmit processor, or receiver processor, or transceiver processor associated with transceiver 402. In other aspects, some features associated with timing management component 850 in the features of one or more processors 412 and / or modem 414 can be performed by transceiver 402. The one or more antennas 465 may include individual antennas and / or antenna arrays.

[0066] The memory 416 may be configured to store data used herein, and / or a local version of the application 475, or one or more subcomponents of the uplink preemption indication component 450 and / or its subcomponents executed by at least one processor 412. The memory 416 may include any type of computer-readable medium that can be used by a computer or at least one processor 412, such as a random access memory (RAM), a read-only memory (ROM), a tape, a disk, an optical disk, a volatile memory, a non-volatile memory, and any combination thereof. For example, in one aspect, when the IAB node 150 operates at least one processor 412 to execute one or more subcomponents of the timing management component 850 and / or its subcomponents, the memory 416 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes and / or data associated therewith for defining the uplink preemption indication component 450 and / or its subcomponents.

[0067] The transceiver 402 may include at least one receiver 406 and at least one transmitter 408. The receiver 406 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code including instructions and stored in a memory (e.g., a computer-readable medium). For example, the receiver 406 may be a radio frequency (RF) receiver. In one aspect, the receiver 406 may receive a signal transmitted by at least one UE 104. In addition, the receiver 406 may process such received signals and may also obtain measurements of the signals, such as but not limited to Ec / Io, SNR, RSRP, RSSI, etc. The transmitter 408 may include hardware, firmware, and / or software code executable by a processor for transmitting data, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 408 may include, but are not limited to, an RF transmitter.

[0068] In addition, in an aspect, the transmitting device may include an RF front end 488, which may operate in communication with one or more antennas 865 and the transceiver 802 to receive and send radio transmissions, such as wireless communications sent by at least one base station 102, other IAB nodes 150, or wireless transmissions sent by and to the UE 104. The RF front end 888 may be connected to the one or more antennas 465 and may include one or more low noise amplifiers (LNAs) 490, one or more switches 492, one or more power amplifiers (PAs) 498, and one or more filters 496 for sending and receiving RF signals.

[0069] In one aspect, the LNA 490 can amplify the received signal at a desired output level. In one aspect, each LNA 490 can have a specified minimum and maximum gain value. In one aspect, the RF front end 488 can use one or more switches 492 to select a specific LNA 490 and its specified gain value based on the desired gain value for a particular application.

[0070] In addition, for example, the RF front end 488 can use one or more PAs 498 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 498 can have a specified minimum and maximum gain value. In one aspect, the RF front end 488 can use one or more switches 492 to select a particular PA 498 and its specified gain value based on the desired gain value for a particular application.

[0071] In addition, for example, the RF front end 488 can use one or more filters 496 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, a corresponding filter 496 can be used to filter the output from the corresponding PA 498 to produce an output signal for transmission. In one aspect, each filter 496 can be connected to a specific LNA 490 and / or PA 498. In one aspect, the RF front end 488 can use one or more switches 492 to select a transmit path or a receive path using a specified filter 496, LNA 490, and / or PA 498 based on a configuration as specified by the transceiver 402 and / or the processor 412.

[0072] As such, the transceiver 402 may be configured to transmit and receive wireless signals via the RF front end 488 through the one or more antennas 465. In an aspect, the transceiver 402 may be tuned to operate at a specified frequency so that the transmitting device may communicate, for example, with one or more base stations 102 or one or more cells associated with one or more base stations 102. In an aspect, the modem 414 may configure the transceiver 402 to operate at a specified frequency and power level, for example, based on the configuration of the transmitting device and the communication protocol used by the modem 414.

[0073] In one aspect, the modem 414 can be a multi-band multi-mode modem that can process digital data and communicate with the transceiver 402 so that the digital data is sent and received using the transceiver 402. In one aspect, the modem 414 can be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, the modem 414 can be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 414 can control one or more components of the transmitting device (e.g., RF front end 488, transceiver 402) to achieve the transmission and / or reception of signals from the network based on the specified modem configuration. In one aspect, the modem configuration can be based on the mode of the modem 414 and the frequency band in use. In another aspect, the modem configuration can be based on the UE configuration information associated with the transmitting device as provided by the network during cell selection and / or cell reselection.

[0074] Figure 5 is a flow chart of an example method 500 for wireless communication according to aspects of the present disclosure. Figure 1 and Figure 2The IAB node 150 or 205 discussed above may be used to perform the method 500. Although the method 500 is described below with respect to elements of an IAB node, other components may also be used to implement one or more of the steps described herein. The IAB node may include both base station type functionality that allows sending to and receiving from child nodes, and UE type functionality that allows sending to and receiving from parent nodes.

[0075] At block 505, method 500 may optionally include: sending DCI from the first node to the second node, the DCI for scheduling resources for transmitting uplink traffic via the PUSCH during the first time slot. In some examples, the DCI may also include a resource indication of a PUCCH resource that the first node will use to send an uplink preemption indication during the second time period. Aspects of block 505 may be referred to as Figure 4 The modem 450 of the IAB node 150 may generate DCI and send the DCI to the transceiver 402 or transmitter 408 of the IAB node 150. The transceiver 402 or transmitter 408 may convert data into electrical signals. The RF front end 488 may filter and / or amplify the electrical signals into electromagnetic signals. One or more antennas 465 of the IAB node 150 may send electromagnetic signals associated with the DCI to the parent node 102. Therefore, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412, and / or the IAB node 150, or one of its subcomponents, may define a unit for sending DCI from a first node to a second node, the DCI being used to schedule resources for transmitting uplink traffic over a PUSCH during a first time slot.

[0076] At block 510, method 500 may include sending uplink traffic from a first node to a second node via a PUSCH during a first time slot. Aspects of block 510 may be referred to as Figure 4The modem 450 of the IAB node 150 may generate data for transmission to the transceiver 402 or the transmitter 408 of the IAB node 150. The transceiver 402 or the transmitter 408 may convert the data into an electrical signal. The RF front end 488 may filter and / or amplify the electrical signal into an electromagnetic signal. One or more antennas 465 of the IAB node 150 may send electromagnetic signals associated with uplink traffic to the parent node 102 via the PUSCH. Therefore, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412 and / or the IAB node 150 or one of its subcomponents may define a unit for sending uplink traffic from a first node to a second node via the PUSCH during a first time slot.

[0077] At block 515, method 500 may include receiving emergency URLLC traffic from a third node during a first time slot at the first node on resources that conflict with uplink traffic transmission from the IAB node to the parent backhaul node. In some examples, the first node may be an IAB node, the second node may be an IAB parent backhaul node, and the third node may be one or more of a child IAB node or a UE. Aspects of block 515 may be referred to as Figure 4 The described transceiver 402 and more specifically the receiver 406 are performed. For example, one or more antennas 465 of the IAB node 150 can receive electromagnetic signals associated with URLLC services. The RF front end 488 of the IAB node 150 can filter, amplify and / or extract the electrical signals carried by the electromagnetic signals. The transceiver 402 or the receiver 406 of the IAB node 150 can digitize and convert the electrical signals into data (such as URLLC services from subnodes) and send them to the modem 450 of the IAB node 150. Therefore, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412 and / or the IAB node 150 or one of its subcomponents can be defined for receiving an emergency URLLC service from a third node on resources that conflict with the uplink service transmission from the first node to the second node during the first time slot at the first node.

[0078] At block 520, method 500 may include, based on receiving the emergency URLLC traffic at the IAB node, puncturing at least a portion of the resources of a PUSCH for uplink traffic from the first node to the second node during the first time slot. Aspects of block 520 may be as described with reference to Figure 4The described resource puncturing component 455 is performed in conjunction with the transceiver 402. For example, the resource puncturing component 455 can identify that one or more symbols of the uplink service from the first node to the second node are affected by the reception of the emergency URLLC from the third node. Based on this determination, the resource puncturing component 455, the uplink preemption indication component 450, the modem 414 and / or the processor 412 can puncture one or more resource elements or symbols used by the subnode / UE for URLLC. Therefore, the resource puncturing component 455, the uplink preemption indication component 450, the modem 414, the processor 412 and / or the IAB node 150 or a subcomponent thereof can define a unit for puncturing at least a portion of the resources of the PUSCH for the uplink service from the first node to the second node during the first time slot based on the reception of the emergency URLLC service at the first node.

[0079] At block 525, method 500 may include sending an uplink preemption indication from the first node to the second node that identifies at least a portion of the resources punctured by the first node. In some examples, the uplink preemption indication may be one of a time slot level or a transport block level indication. In other examples, the uplink preemption indication may be one of a symbol level or a frequency range level indication. The modem 450 of the IAB node 150 may generate an uplink preemption indication (e.g., a message or signal) for transmission to the transceiver 402 or transmitter 408 of the IAB node 150. The transceiver 402 or transmitter 408 may convert the uplink preemption indication into an electrical signal. The RF front end 488 may filter and / or amplify the electrical signal into an electromagnetic signal. One or more antennas 465 of the IAB node 150 may send an electromagnetic signal associated with the uplink preemption indication to the parent node 102. Thus, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412 and / or the IAB node 150, or one of its subcomponents, may define a unit for sending an uplink preemption indication from a first node to a second node identifying at least a portion of the resources punctured by the first node.

[0080] In some examples, as described in sub-block 530, method 500 may optionally include: sending an uplink preemption indication about a previous PUSCH in a subsequently sent PUCCH on a resource identified in the DCI. Specifically, as indicated above with reference to block 505, the DCI may schedule resources for transmitting uplink traffic over the PUSCH during a first time slot. In some examples, the DCI may also include a resource indication of a PUCCH resource that the first node may use to send an uplink preemption indication during a second time period. In some examples, the resource indication may include both an identification of a PUCCH resource set ID and a PUCCH resource ID within the PUCCH resource set ID. In other instances, the resource indication may include only an identification of a PUCCH resource ID within the PUCCH resource set ID. In such a case, a PUCCH resource set ID predetermined between the first node and the second node may be omitted from the resource indication. In some examples, the resource indication identifies a time domain offset from the last symbol of the punctured PUSCH to the first symbol of the PUCCH resource that the IAB node will use to send an uplink preemption indication.

[0081] At sub-block 535, method 500 may optionally or alternatively include: sending an uplink preemption indication in one or more reserved resource elements located in the last OFDM symbol of the PUSCH punctured by the first node during the first time slot. In some examples, the PUSCH may be rate matched based on the one or more reserved resource elements (e.g., for the reserved resource element method, the IAB node may rate match around the reserved resource elements when sending the PUSCH). However, if there is no uplink preemption indication to include, then in some examples, the reserved resource elements may be used for the PUSCH. In addition, the one or more reserved resource elements that may be used are selected from a plurality of resource element sequences (or different digital payloads) that may each identify a different puncturing situation.

[0082] At sub-block 540, method 500 may optionally or alternatively include: sending an uplink preemption indication corresponding to an uplink traffic transmission of a PUSCH during a first time slot in one or more reserved resource elements located in the last OFDM symbol of a second PUSCH sent to a second node during a second time period, wherein the second PUSCH transmission is a retransmission or repetition of the first PUSCH sent from the first node to the second node. As noted above, in some examples, the PUSCH may be rate matched based on one or more reserved resource elements (e.g., for the reserved resource element method, the IAB node may rate match around the reserved resource elements when sending the PUSCH). However, if there is no uplink preemption indication to be included, then in some examples, the reserved resource elements may be used for the PUSCH. In addition, the one or more reserved resource elements that may be used are selected from a plurality of resource element sequences (or different digital payloads) that may each identify different puncturing situations.

[0083] Furthermore, the method 500 may optionally include sending an uplink preemption indication corresponding to uplink traffic transmission of the PUSCH during the first time slot in a MAC-CE message sent to the parent backhaul node during the second time period through the second PUSCH.

[0084] Additionally or alternatively, in some examples, an uplink preemption indication may be sent via a demodulation reference signal (DMRS) sent to a second node, wherein the DMRS is selected from a plurality of DMRS sequences each indicating a different puncturing technique. In other words, DMRS may be used instead of using reserved resource elements for UL-PI. If UL preemption is not encountered, a conventional DMRS sequence may be used. However, if UL preemption is encountered, other DMRS sequences may be used to identify UL-PI details (e.g., what symbols are punctured). In some aspects, a DMRS-based solution may also be based on the current PUSCH, or a retransmitted / repeated PUSCH, or a PUSCH of another HARQ process.

[0085] Finally, in some examples, the method may further include: sending a configuration associated with multiple DMRS sequences in a scheduling request from the first node to the second node or from the second node to the first node. Specifically, the meaning of the DMRS sequence, the DMRS sequence that may be allowed, and the specific configuration of the specific method may be transmitted in the scheduling request from the IAB node to the parent node, and / or configured / indicated from the parent node to the IAB node.

[0086] In some examples, method 500 may also include: at the first node, at least in part based on determining whether the resources for the uplink preemption indication can be used by at least one of the child IAB node or the UE for uplink transmission of emergency URLLC services, determining whether the resources are needed. Method 500 may also include: based on the determination, sending a scheduling request from the IAB node to the parent backhaul node to indicate whether resources for the uplink preemption indication are allocated. In some aspects, the uplink preemption indication may indicate whether the preemption is at the time slot level or the symbol level, and additionally identifies a technique that the parent node in the technology discussed above will use to receive and decode the uplink preemption indication. The first node may further identify the number and position of reserved resource elements for the preemption indication.

[0087] Figure 6 is a flow chart of an example method 600 for wireless communication according to aspects of the present disclosure. Figure 1 and Figure 2 The method 600 is performed by an IAB parent node (e.g., parent node 102) discussed below. Although the method 600 is described below with respect to elements of an IAB parent node, other components may also be used to implement one or more of the steps described herein. The IAB parent node may include both base station type functions that allow sending to and receiving from child nodes, and UE type functions that allow sending to and receiving from the parent node.

[0088] At block 605, method 600 may optionally include receiving a DCI from a first node to a second node, the DCI being used to schedule resources for transmitting uplink traffic via a PUSCH during a first time slot. In some examples, the DCI may also include a resource indication of a PUCCH resource that the first node will use to send an uplink preemption indication during a second time period. Aspects of block 605 may be referred to as Figure 4 The modem 450 of the IAB node 150 may generate DCI and send the DCI to the transceiver 402 or transmitter 408 of the IAB node 150. The transceiver 402 or transmitter 408 may convert data into electrical signals. The RF front end 488 may filter and / or amplify the electrical signals into electromagnetic signals. One or more antennas 465 of the IAB node 150 may send electromagnetic signals associated with the DCI to the parent node 102. Therefore, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412, and / or the IAB node 150 or one of its subcomponents may define a unit for receiving DCI from a first node to a second node, the DCI being used to schedule resources for transmitting uplink traffic over a PUSCH during a first time slot.

[0089] At block 610, method 600 may include: receiving, at the second node, an uplink preemption indication from the first node, the uplink preemption indication identifying that at least a portion of resources of a PUSCH for uplink traffic from the first node to the second node are punctured by the first node due to: receiving, at the first node, emergency URLLC traffic on at least a portion of the resources that conflicts with transmission of uplink traffic from the first node to the second node during a first time slot. Aspects of block 610 may be referred to by reference Figure 4 The transceiver 402 and more specifically the receiver 406 described are performed. For example, one or more antennas 465 of the IAB node 150 can receive electromagnetic signals associated with uplink traffic. The RF front end 488 of the IAB node 150 can filter, amplify and / or extract the electrical signals carried by the electromagnetic signals. The transceiver 402 or the receiver 406 of the IAB parent node 150 can digitize and convert the electrical signals into data (such as uplink traffic from the IAB node) and send them to the modem 450 of the IAB node 150. Therefore, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412 and / or the IAB node 150 or one of its subcomponents may define a unit for receiving an uplink preemption indication from the first node at the second node, the uplink preemption indication identifying that at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node are punctured by the first node due to the following situation: emergency URLLC traffic is received at the first node during a first time slot on at least a portion of the resources that conflict with the transmission of uplink traffic from the first node to the second node.

[0090] In some examples, as described in sub-block 620, method 600 may optionally include: receiving an uplink preemption indication about a previous PUSCH in a PUCCH subsequently sent on resources identified in the DCI. Specifically, as indicated above with reference to block 605, the DCI may schedule resources for transmitting uplink traffic via PUSCH during a first time slot. In some examples, the DCI may further include a resource indication of PUCCH resources that the first node may use to send an uplink preemption indication during a second time period. In some examples, the resource indication may include both an identification of a PUCCH resource set ID and a PUCCH resource ID within the PUCCH resource set ID. In other instances, the resource indication may include only an identification of a PUCCH resource ID within the PUCCH resource set ID. In such a case, the PUCCH resource set ID omitted from the resource indication may be predetermined between the first node and the second node. In some examples, the resource indication identifies a time domain offset from a last symbol of a punctured PUSCH to a first symbol of a PUCCH resource that the IAB node will use to send an uplink preemption indication.

[0091] At sub-block 625, method 500 may optionally or alternatively include: receiving an uplink preemption indication in one or more reserved resource elements located in the last OFDM symbol of the PUSCH punctured by the first node during the first time slot. In some examples, the PUSCH may be rate matched based on the one or more reserved resource elements (e.g., for the reserved resource element method, the IAB node may rate match around the reserved resource elements when sending the PUSCH). However, if there is no uplink preemption indication to include, in some examples, the reserved resource elements may be used for the PUSCH. In addition, the one or more reserved resource elements that may be used are selected from a plurality of resource element sequences (or different digital payloads) that may each identify a different puncturing situation.

[0092] At sub-block 630, method 600 may optionally or alternatively include: receiving an uplink preemption indication corresponding to an uplink traffic transmission of a PUSCH during a first time slot in one or more reserved resource elements located in the last OFDM symbol of a second PUSCH sent to a second node during a second time period, wherein the second PUSCH transmission is a retransmission or repetition of the first PUSCH sent from the first node to the second node. Similarly, as noted above, in some examples, the PUSCH may be rate matched based on one or more reserved resource elements (e.g., for the reserved resource element method, the IAB node may rate match around the reserved resource elements when sending the PUSCH). However, if there is no uplink preemption indication to be included, then in some examples, the reserved resource elements may be used for the PUSCH. In addition, the one or more reserved resource elements that may be used are selected from a plurality of resource element sequences (or different digital payloads) that may each identify different puncturing situations.

[0093] Furthermore, the method 600 may optionally include receiving an uplink preemption indication corresponding to uplink traffic transmission of the PUSCH during the first time slot in a MAC-CE message sent to the parent backhaul node during the second time period over the second PUSCH.

[0094] Additionally or alternatively, in some examples, an uplink preemption indication may be received via a demodulation reference signal (DMRS) sent to the second node, wherein the DMRS is selected from a plurality of DMRS sequences identifying at least a portion of the resources punctured by the first node. In other words, DMRS may be used instead of using reserved resource elements for UL-PI. If UL preemption is not encountered, a conventional DMRS sequence may be used. However, if UL preemption is encountered, other DMRS sequences may be used to identify UL-PI details (e.g., what symbols are punctured). In some aspects, a DMRS-based solution may also be based on the current PUSCH, or a retransmitted / repeated PUSCH, or a PUSCH of another HARQ process.

[0095] Finally, in some examples, the method may further include: receiving a configuration associated with a plurality of DMRS sequences in a scheduling request from one of the first node to the second node or the second node to the first node. Specifically, the meaning of the DMRS sequence, the possible allowed DMRS sequence, and the specific configuration of the specific method may be transmitted in the scheduling request from the IAB node to the parent node, and / or configured / indicated from the parent node to the IAB node.

[0096] At block 640, method 600 may include decoding the uplink preemption indication to identify at least a portion of the resources corresponding to the punctured traffic. In some examples, the first node may be an IAB node, the second node may be an IAB parent backhaul node, and the third node may be one or more of a child IAB node or a UE. Aspects of block 640 may be as described in reference to Figure 4 The described transceiver 402 and more specifically the receiver 406 are performed. For example, one or more antennas 465 of the IAB node 150 can receive an electromagnetic signal associated with a preemption indication. The RF front end 488 of the IAB node 150 can filter, amplify and / or extract the electrical signal carried by the electromagnetic signal. The transceiver 402 or the receiver 406 of the IAB node 150 can digitize, decode and convert the electrical signal into data (such as an uplink preemption indication from the IAB node) and send it to the modem 450 of the IAB parent node 150. Therefore, the modem 450, the transceiver 402, the transmitter 408, the RF front end 488, the one or more antennas 465, the one or more processors 412 and / or the IAB node 150 or one of its subcomponents can define a unit for decoding the uplink preemption indication to identify at least a portion of the resources corresponding to the punched service.

[0097] Some further example embodiments

[0098] In one example, an aspect of the present disclosure includes a method for wireless communication, comprising: sending uplink traffic from a first node to a second node via a physical uplink shared channel (PUSCH) during a first time slot; receiving, at the first node during the first time slot, an emergency ultra-reliable low-latency communication (URLLC) service from a third node on resources that conflict with the uplink traffic transmission from the first node to the second node; based on reception of the emergency URLLC service at the first node, puncturing at least a portion of the resources of the PUSCH used for the uplink traffic from the first node to the second node during the first time slot; and sending an uplink preemption indication from the first node to the second node identifying at least a portion of the resources punctured by the first node.

[0099] The above example method also includes: sending downlink control information (DCI) from the first node to the second node, the DCI being used to schedule resources for transmitting uplink services via the PUSCH during a first time slot, wherein the DCI also includes a resource indication of a physical uplink control channel (PUCCH) resource that the first node will use to send an uplink preemption indication during a second time period.

[0100] Any of the above example methods, wherein the resource indication comprises an identification of both a PUCCH resource set identification (ID) and a PUCCH resource ID within the PUCCH resource set ID.

[0101] Any of the above example methods, wherein the resource indication comprises an identification of a PUCCH resource set identification (ID) within a PUCCH resource set ID, wherein the PUCCH resource set ID is omitted from the resource indication and is predetermined between the first node and the second node.

[0102] Any of the above example methods, wherein the resource indication identifies a time domain offset from a last symbol of the punctured PUSCH to a first symbol of a PUCCH resource to be used by the first node to send an uplink preemption indication.

[0103] Any of the above example methods, wherein an uplink preemption indication identifying at least a portion of the resources punctured by the first node is sent from a first node to a parent return node, comprising: during a first time slot, sending an uplink preemption indication in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of a PUSCH punctured by the first node.

[0104] Any of the above example methods, wherein an uplink preemption indication identifying at least a portion of the resources punctured by the IAB node is sent from a first node to a second node, comprising: sending an uplink preemption indication corresponding to an uplink service transmission of the PUSCH during a first time slot in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of a second PUSCH sent to a parent return node during a second time period, wherein the second PUSCH transmission is a retransmission or repetition of the first PUSCH sent from the first node to the second node.

[0105] Any of the above example methods, wherein an uplink preemption indication identifying at least a portion of the resources perforated by the IAB node is sent from a first node to a second node, comprising: sending an uplink preemption indication corresponding to an uplink traffic transmission of a PUSCH during a first time slot in a medium access control address control element (MAC-CE) message sent to a parent return node via a second PUSCH during a second time period.

[0106] Any of the above example methods, wherein the uplink preemption indication is one of a slot level or a transport block level indication.

[0107] Any of the above example methods, wherein the uplink preemption indication is one of a symbol level or a frequency range level indication.

[0108] Any of the above example methods also includes: at the first node, determining whether resources for uplink preemption indication are needed based at least in part on determining whether the resources can be used by a third node for uplink transmission of emergency URLLC services; and based on the determination, sending a scheduling request from the first node to the second node to indicate whether resources for uplink preemption indication are allocated.

[0109] Any of the above example methods, wherein the first node is an integrated access and backhaul (IAB) node, wherein the second node is a parent backhaul node, and wherein the third node is at least one of a child IAB node or a user equipment (UE).

[0110] In another example, aspects of the present disclosure include an apparatus for wireless communication, comprising: a memory configured to store instructions; a processor communicatively coupled to the memory, the processor configured to execute the instructions to perform the following operations: during a first time slot, sending uplink traffic from a first node to a second node via a physical uplink shared channel (PUSCH); at the first node during the first time slot, receiving emergency ultra-reliable low-latency communication (URLLC) traffic from a third node on resources that conflict with uplink traffic transmission from the first node to a parent return node; based on reception of the emergency URLLC traffic at the first node, puncturing at least a portion of the resources of the PUSCH for uplink traffic from the first node to the second node during the first time slot; and sending an uplink preemption indication from the first node to the second node identifying at least a portion of the resources punctured by the first node.

[0111] The above example apparatus, wherein the processor is further configured to execute instructions for: sending downlink control information (DCI) from the first node to the second node, the DCI being used to schedule resources for transmitting uplink services via the PUSCH during a first time slot, wherein the DCI also includes a resource indication of a physical uplink control channel (PUCCH) resource that the IAB node will use to send an uplink preemption indication during a second time period.

[0112] Any of the above example apparatuses, wherein the resource indication comprises an identification of both a PUCCH resource set identification (ID) and a PUCCH resource ID within the PUCCH resource set ID.

[0113] Any of the above example apparatuses, wherein the resource indication comprises an identification of a PUCCH resource set identification (ID) within a PUCCH resource set ID, wherein the PUCCH resource set ID is omitted from the resource indication and is predetermined between the IAB node and the parent backhaul node.

[0114] Any of the above example apparatuses, wherein the resource indication identifies a time domain offset from a last symbol of a punctured PUSCH to a first symbol of a PUCCH resource to be used by the IAB node to send an uplink preemption indication.

[0115] Any of the above example devices, wherein the instruction for sending an uplink preemption indication identifying at least a portion of the resources punctured by the IAB node from the IAB node to the parent return node can also be executed by the processor to perform the following operations: during a first time slot, in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of the PUSCH punctured by the IAB node, sending the uplink preemption indication.

[0116] Any of the above example devices, wherein the instruction for sending an uplink preemption indication from an IAB node to a parent backhaul node identifying at least a portion of the resources punctured by the IAB node, may also be executed by a processor to perform the following operations: sending an uplink preemption indication corresponding to an uplink service transmission of a PUSCH during a first time slot in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of a second PUSCH sent to the parent backhaul node during a second time period, wherein the second PUSCH transmission is a retransmission or repetition of the first PUSCH transmitted from the IAB node to the parent backhaul node.

[0117] Any of the above example devices, wherein the instruction for sending an uplink preemption indication identifying at least a portion of the resources punctured by the IAB node from the IAB node to the parent backhaul node can also be executed by the processor to perform the following operations: sending an uplink preemption indication corresponding to the uplink service transmission of the PUSCH during the first time slot in a medium access control address control element (MAC-CE) message sent to the parent backhaul node via the second PUSCH during the second time period.

[0118] Any of the above example apparatus, wherein the uplink preemption indication is one of a slot level or a transport block level indication.

[0119] Any of the above example apparatus, wherein the uplink preemption indication is one of a symbol level or a frequency range level indication.

[0120] In another example, aspects of the present disclosure include a non-transitory computer-readable medium storing instructions for wireless communication that can be executed by a processor, the instructions including instructions for performing the following operations: sending uplink traffic from a first node to a second node via a physical uplink shared channel (PUSCH) during a first time slot; receiving emergency ultra-reliable low-latency communication (URLLC) traffic from a third node at the first node during the first time slot on resources that conflict with uplink traffic transmission from the first node to a parent return node; based on reception of the emergency URLLC traffic at the first node, puncturing at least a portion of the resources of the PUSCH used for uplink traffic from the first node to the second node during the first time slot; and sending an uplink preemption indication from the first node to the parent return node identifying at least a portion of the resources punctured by the first node.

[0121] The above example non-temporary computer-readable medium also includes instructions for performing the following operations: sending downlink control information (DCI) from the IAB node to the parent return node, the DCI being used to schedule resources for transmitting uplink services via the PUSCH during a first time slot, wherein the DCI also includes a resource indication of a physical uplink control channel (PUCCH) resource that the IAB node will use to send an uplink preemption indication during a second time period.

[0122] Any of the above example non-transitory computer-readable media, wherein the resource indication comprises an identification of both a PUCCH resource set identification (ID) and a PUCCH resource ID within the PUCCH resource set ID.

[0123] Any of the above example non-transitory computer-readable media, wherein the resource indication includes an identification of a PUCCH resource set identification (ID) within a PUCCH resource set ID, wherein the PUCCH resource set ID is omitted from the resource indication and is predetermined between the IAB node and the parent backhaul node.

[0124] Any of the above example non-transitory computer-readable media, wherein the resource indication identifies a time domain offset from a last symbol of a punctured PUSCH to a first symbol of a PUCCH resource that the IAB node is to use to send an uplink preemption indication.

[0125] Any of the above example non-transitory computer-readable media, wherein the instructions for sending an uplink preemption indication identifying at least a portion of the resources punctured by the IAB node from the IAB node to the parent return node also include instructions for performing the following operations: during a first time slot, sending an uplink preemption indication in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of the PUSCH punctured by the IAB node.

[0126] Any of the above example non-transitory computer-readable media, wherein the instructions for sending an uplink preemption indication from an IAB node to a parent return node identifying at least a portion of the resources punctured by the IAB node also include instructions for performing the following operations: sending an uplink preemption indication corresponding to an uplink service transmission of a PUSCH during a first time slot in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of a second PUSCH sent to the parent return node during a second time period, wherein the second PUSCH transmission is a retransmission or repetition of the first PUSCH sent from the IAB node to the parent return node.

[0127] Any of the above example non-transitory computer-readable media, wherein the instructions for sending an uplink preemption indication identifying at least a portion of the resources perforated by the IAB node from the IAB node to the parent return node also include instructions for performing the following operations: sending an uplink preemption indication corresponding to the uplink service transmission of the PUSCH during the first time slot in a medium access control address control element (MAC-CE) message sent to the parent return node via a second PUSCH during a second time period.

[0128] Any of the above example non-transitory computer readable media, wherein the uplink preemption indication is one of a slot level or a transport block level indication.

[0129] Any of the above example non-transitory computer readable media, wherein the uplink preemption indication is one of a symbol level or a frequency range level indication.

[0130] In another example, aspects of the present disclosure may include an apparatus for wireless communication, comprising: a unit for sending uplink traffic from an IAB node to a parent return node via a physical uplink shared channel (PUSCH) during a first time slot; a unit for receiving, at the IAB node, an emergency ultra-reliable low-latency communication (URLLC) service from at least one of a child IAB node or a user equipment (UE) on resources that conflict with the transmission of uplink traffic from the IAB node to the parent return node during the first time slot; a unit for puncturing at least a portion of the resources of the PUSCH for uplink traffic from the IAB node to the parent return node during the first time slot based on reception of the emergency URLLC service at the IAB node; and a unit for sending an uplink preemption indication from the IAB node to the parent return node identifying at least a portion of the resources punctured by the IAB node.

[0131] The above exemplary apparatus further includes: a unit for sending downlink control information (DCI) from the IAB node to the parent return node, the DCI being used to schedule resources for transmitting uplink services via the PUSCH during a first time slot, wherein the DCI also includes a resource indication of a physical uplink control channel (PUCCH) resource that the IAB node will use to send an uplink preemption indication during a second time period.

[0132] Any of the above example apparatuses, wherein the resource indication comprises an identification of both a PUCCH resource set identification (ID) and a PUCCH resource ID within the PUCCH resource set ID.

[0133] Any of the above example apparatuses, wherein the resource indication comprises an identification of a PUCCH resource set identification (ID) within a PUCCH resource set ID, wherein the PUCCH resource set ID is omitted from the resource indication and is predetermined between the IAB node and the parent backhaul node.

[0134] Any of the above example apparatuses, wherein the resource indication identifies a time domain offset from a last symbol of a punctured PUSCH to a first symbol of a PUCCH resource to be used by the IAB node to send an uplink preemption indication.

[0135] Any of the above example devices, wherein the unit for sending an uplink preemption indication identifying at least a portion of the resources punctured by the IAB node from the IAB node to the parent return node also includes: a unit for sending the uplink preemption indication in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of the PUSCH punctured by the IAB node during the first time slot.

[0136] Any of the above example devices, wherein the unit for sending an uplink preemption indication identifying at least a portion of the resources punctured by the IAB node from the IAB node to the parent return node further includes: a unit for sending an uplink preemption indication corresponding to an uplink service transmission of the PUSCH during the first time slot in one or more reserved resource elements located in the last orthogonal frequency division multiplexing (OFDM) symbol of a second PUSCH sent to the parent return node during a second time period, wherein the second PUSCH transmission is a retransmission or repetition of the first PUSCH sent from the IAB node to the parent return node.

[0137] Any of the above example devices, wherein the unit for sending an uplink preemption indication identifying at least a portion of the resources perforated by the IAB node from the IAB node to the parent return node also includes: a unit for sending an uplink preemption indication corresponding to the uplink service transmission of the PUSCH during the first time slot in a medium access control address control element (MAC-CE) message sent to the parent return node via the second PUSCH during the second time period.

[0138] Any of the above example apparatus, wherein the uplink preemption indication is one of a slot level or a transport block level indication.

[0139] Any of the above example apparatus, wherein the uplink preemption indication is one of a symbol level or a frequency range level indication.

[0140] The specific embodiments described above in conjunction with the accompanying drawings describe some examples and do not represent the only examples that can be implemented, nor do they represent the only examples within the scope of the claims. When used in this specification, the term "example" means "used as an example, instance, or illustration" and is not "preferred" or "advantageous" over other examples. The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques can be implemented without these specific details. In some instances, in order to avoid obscuring the concepts of the described examples, well-known structures and devices are shown in block diagram form.

[0141] Information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer executable codes or instructions stored on a computer-readable medium, or any combination thereof.

[0142] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a specially programmed device designed to perform the functions described herein, such as, but not limited to, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof. The specially programmed processor may be a microprocessor, but in an alternative, the processor may also be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such structure.

[0143] The functions described herein can be implemented with hardware, software executed by a processor, firmware, or any combination thereof. When implemented with software executed by a processor, the functions can be stored as one or more instructions or codes on a non-transitory computer-readable medium, or transmitted by a non-transitory computer-readable medium. Other examples and implementations are also within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software, hardware, firmware, hard wiring, or any combination thereof executed by a specially programmed processor. The features used to implement the functions can also be physically distributed in different locations, including being distributed so that the parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), "or" used in a list of items ending with "at least one of" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0144] Computer readable medium includes computer storage medium and communication medium, and communication medium includes any medium that promotes to transmit computer program from one place to another place. Storage medium can be any available medium that can be accessed by general or special purpose computer. By way of example and not limitation, computer readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used for carrying or storing the program code unit with the expectation of instruction or data structure form and can be accessed by general or special purpose computer or general or special purpose processor any other medium. In addition, any connection is appropriately referred to as computer readable medium. For example, if software is to use coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, from website, server or other remote source transmission, so coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of described medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0145] The specific embodiments described above in conjunction with the accompanying drawings are intended to be descriptions of various configurations, and are not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, in order to avoid blurring such concepts, known structures and components are illustrated in the form of block diagrams.

[0146] Some aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the detailed description and depicted 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.

[0147] For 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, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, separate hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

[0148] It should be noted that the techniques described herein can be used in various wireless communication networks, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA 2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 version 0 and version A are commonly referred to as CDMA 2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement, for example, Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 902.11 (Wi-Fi), IEEE 902.16 (WiMAX), IEEE 902.20, Flash-OFDM TMRadio technologies such as LTE and UTRA. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Improved LTE (LTE-A) are new versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the systems and radio technologies mentioned above and other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio spectrum bands. However, the following description describes LTE / LTE-A and / or 5G New Radio (NR) systems for example purposes, and LTE or 5G NR terms are used in most of the following descriptions, but the techniques are applicable outside of LTE / LTE-A and 5G NR applications (e.g., to other next generation communication systems).

[0149] The previous description of the present disclosure is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the spirit or scope of the present disclosure. In addition, although the elements of the various aspects and / or embodiments described are described or claimed in the singular, the plural form is contemplated unless explicitly stated to be limited to the singular. In addition, unless otherwise stated, all or part of any aspect and / or embodiment can be used together with all or part of any other aspect and / or embodiment. Therefore, the present disclosure is not limited to the examples and design schemes described herein, but is to be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication implemented by an integrated access and backhaul (IAB) node, comprising: During the first time slot, sending uplink traffic to the second node via a physical uplink shared channel (PUSCH); receiving, during the first time slot, emergency ultra-reliable low-latency communication (URLLC) traffic from a third node on resources that conflict with uplink traffic transmission from the IAB node to the second node; Based on reception of the emergency URLLC traffic at the IAB node, puncturing at least a portion of resources of the PUSCH used for the uplink traffic from the IAB node to the second node during the first time slot; as well as An uplink preemption indication identifying at least the portion of the resources punctured by the IAB node is sent to the second node.

2. The method according to claim 1, further comprising: sending downlink control information (DCI) to the second node, the DCI being used to schedule resources for transmitting the uplink traffic over the PUSCH during a first time slot, The DCI further includes a resource indication of a physical uplink control channel (PUCCH) resource that the IAB node will use to send the uplink preemption indication during the second time period.

3. The method according to claim 2, wherein: The resource indication includes both a PUCCH resource set identifier (ID) and a PUCCH resource ID within the PUCCH resource set ID.

4. The method according to claim 2, wherein: The resource indication includes an identifier of a PUCCH resource ID in a PUCCH resource set identifier (ID), The PUCCH resource set ID is omitted from the resource indication and is predetermined between the IAB node and the second node.

5. The method according to claim 2, wherein: The resource indication identifies a time domain offset from a last symbol of the punctured PUSCH to a first symbol of the PUCCH resource that the IAB node will use to send the uplink preemption indication.

6. The method according to claim 1, wherein: Sending the uplink preemption indication identifying at least the portion of the resources punctured by the IAB node to the second node comprises: During the first time slot, sending the uplink preemption indication in one or more reserved resource elements located in a last orthogonal frequency division multiplexing (OFDM) symbol of the PUSCH punctured by the IAB node, The PUSCH is rate matched based on the one or more reserved resource elements.

7. The method according to claim 6, wherein: During the first time slot, sending the uplink preemption indication in one or more reserved resource elements located in the last OFDM symbol of the PUSCH punctured by the IAB node, further comprising: A signal included by the reserved resource element is encoded based at least in part on selecting from a plurality of coding sequences each indicating a different puncturing technique.

8. The method according to claim 1, wherein: Sending the uplink preemption indication identifying at least the portion of the resources punctured by the IAB node to the second node comprises: transmitting, in one or more reserved resource elements located in a last orthogonal frequency division multiplexing (OFDM) symbol of a second PUSCH transmitted to the second node during a second time period, the uplink preemption indication corresponding to the uplink traffic transmission of the PUSCH during the first time slot, The second PUSCH transmission is a retransmission or repetition of a first PUSCH sent from the IAB node to the second node, and The PUSCH is rate matched around the one or more reserved resource elements.

9. The method according to claim 8, wherein: transmitting the uplink preemption indication corresponding to the uplink traffic transmission of the PUSCH during the first time slot in one or more reserved resource elements located in the last OFDM symbol of a second PUSCH sent to the second node during a second time period, further comprising: A signal included by the reserved resource element is encoded based at least in part on selecting from a plurality of coding sequences each indicating a different puncturing technique.

10. The method according to claim 1, wherein: Sending the uplink preemption indication identifying at least the portion of the resources punctured by the IAB node to the second node comprises: The uplink preemption indication corresponding to the uplink traffic transmission of the PUSCH during the first time slot is sent in a Medium Access Control Address Control Element (MAC-CE) message sent to the second node during a second time period over a second PUSCH.

11. The method according to claim 1, wherein: Sending the uplink preemption indication identifying at least the portion of the resources punctured by the IAB node to the second node comprises: The uplink preemption indication is sent via a demodulation reference signal (DMRS) sent to the second node, wherein the DMRS is selected from a plurality of DMRS sequences each indicating a different puncturing technique.

12. The method according to claim 11, further comprising: The transmission configuration associated with the plurality of DMRS sequences is transmitted in a scheduling request from one of the IAB node to the second node or the second node to the IAB node.

13. The method according to claim 1, wherein: The uplink preemption indication is one of a timeslot level indication, a transport block level indication, a symbol level indication or a frequency range level indication.

14. The method according to claim 1, further comprising: determining, at the IAB node, whether resources are needed for the uplink preemption indication based at least in part on determining whether the resources can be used by the third node for uplink transmission of the emergency URLLC service; as well as Based on the determination, a scheduling request is sent to the second node to indicate whether the resources for the uplink preemption indication are allocated.

15. The method according to claim 1, further comprising: A scheduling request is sent to the second node to indicate a puncturing technique to be applied by the IAB node from among a plurality of available puncturing techniques.

16. The method according to claim 1, wherein: The second node is a parent backhaul node, and The third node is at least one of a sub-IAB node or a user equipment (UE).

17. An apparatus for wireless communication, comprising: a memory configured to store instructions; a processor communicatively coupled to the memory, the processor configured to execute the instructions to: During a first time slot, uplink traffic is transmitted from an integrated access and backhaul (IAB) node to a second node via a physical uplink shared channel (PUSCH); receiving, during the first time slot, emergency ultra-reliable low-latency communication (URLLC) traffic from a third node on resources that conflict with uplink traffic transmission to the second node; Based on reception of the emergency URLLC traffic at the IAB node, puncturing at least a portion of resources of the PUSCH used for the uplink traffic from the IAB node to the second node during the first time slot; as well as An uplink preemption indication identifying at least the portion of the resources punctured by the IAB node is sent from the IAB node to the second node.

18. The device according to claim 17, wherein: The processor is further configured to execute the instructions to perform the method according to claims 1-16.

19. A non-transitory computer readable medium storing instructions for wireless communications, the instructions executable by a processor of an integrated access and backhaul (IAB) node, comprising instructions for: During a first time slot, transmitting uplink traffic from the IAB node to a second node via a physical uplink shared channel (PUSCH); receiving, during the IAB node being in the first time slot, an emergency ultra-reliable low-latency communication (URLLC) service from a third node on resources that conflict with uplink service transmission from the IAB node to the second node; Based on reception of the emergency URLLC traffic at the IAB node, puncturing at least a portion of resources of the PUSCH used for the uplink traffic from the IAB node to the second node during the first time slot; as well as An uplink preemption indication identifying at least the portion of the resources punctured by the IAB node is sent from the IAB node to the second node.

20. The non-transitory computer readable medium of claim 19, wherein: The instructions execute the method according to claims 1-16.

21. An apparatus for wireless communication, comprising: means for transmitting uplink traffic from an integrated access and backhaul (IAB) node to a second node via a physical uplink shared channel (PUSCH) during a first time slot; means for receiving, during the time when the IAB node is at the first time slot, emergency ultra-reliable low-latency communication (URLLC) traffic from a third node on resources that conflict with uplink traffic transmission from the IAB node to the second node; means for puncturing at least a portion of resources of the PUSCH for the uplink traffic from the IAB node to the second node during the first time slot based on reception of the emergency URLLC traffic at the IAB node; as well as Means for sending, from the IAB node to the second node, an uplink preemption indication identifying at least the portion of the resources punctured by the IAB node.

22. The apparatus according to claim 21, further comprising means for performing the method according to claims 1-16.

23. A method for wireless communication implemented by an integrated access and backhaul (IAB) node, comprising: receiving uplink traffic from the first node via a physical uplink shared channel (PUSCH) during a first time slot; receiving an uplink preemption indication from the first node, the uplink preemption indication identifying that at least a portion of resources of the PUSCH used for the uplink traffic from the first node to the IAB node are punctured by the first node due to: receiving, at the first node during the first time slot, an emergency ultra-reliable low-latency communication (URLLC) traffic on at least the portion of the resources that conflicts with transmission of uplink traffic from the first node to the IAB node; as well as The uplink preemption indication is decoded to identify at least the portion of the resources corresponding to punctured traffic.

24. The method according to claim 23, further comprising: receiving, at the IAB node, downlink control information (DCI) from the first node, the DCI being used to schedule resources for transmitting the uplink traffic over the PUSCH during a first time slot, The DCI further includes a resource indication of a physical uplink control channel (PUCCH) resource that the first node will use to send the uplink preemption indication during a second time period.

25. The method according to claim 24, wherein: The resource indication includes both a PUCCH resource set identifier (ID) and a PUCCH resource ID within the PUCCH resource set ID.

26. The method according to claim 24, wherein: The resource indication includes an identifier of a PUCCH resource ID in a PUCCH resource set identifier (ID), The PUCCH resource set ID is omitted from the resource indication and is predetermined between the first node and the IAB node.

27. The method according to claim 24, wherein: The resource indication identifies a time domain offset from a last symbol of the punctured PUSCH to a first symbol of the PUCCH resource that the first node will use to send the uplink preemption indication.

28. The method of claim 23, wherein: Receiving, at the IAB node from the first node, the uplink preemption indication identifying at least the portion of the resources punctured by the first node, comprises: receiving, during the first time slot, the uplink preemption indication in one or more reserved resource elements located in a last orthogonal frequency division multiplexing (OFDM) symbol of the PUSCH punctured by the first node, The PUSCH is rate matched around the one or more reserved resource elements.

29. The method according to claim 28, wherein: The one or more reserved resource elements for transmitting the uplink preemption indication are selected from a plurality of resource element sequences each indicating a different puncturing technique.

30. The method of claim 23, wherein: Receiving the uplink preemption indication from the first node to the IAB node identifying at least the portion of the resources punctured by the first node, comprises: receiving, in one or more reserved resource elements located in a last orthogonal frequency division multiplexing (OFDM) symbol of a second PUSCH sent to the IAB node during a second time period, the uplink preemption indication corresponding to the uplink traffic transmission of the PUSCH during the first time slot, The second PUSCH transmission is a retransmission or repetition of a first PUSCH sent from the first node to the IAB node, and The PUSCH is rate matched around the one or more reserved resource elements.

31. The method according to claim 30, wherein: The one or more reserved resource elements for transmitting the uplink preemption indication are selected from a plurality of resource element sequences each indicating a different puncturing technique.

32. The method of claim 23, wherein: Receiving the uplink preemption indication from the first node to the IAB node identifying at least the portion of the resources punctured by the first node, comprises: The uplink preemption indication is received via a demodulation reference signal (DMRS) sent to the IAB node, wherein the DMRS is selected from a plurality of DMRS sequences identifying at least the portion of the resources punctured by the first node.

33. The method of claim 32, further comprising: The reception configuration associated with the plurality of DMRS sequences is sent in a scheduling request from one of the first node to the IAB node or the IAB node to the first node.

34. The method of claim 23, wherein: Receiving the uplink preemption indication from the first node to the IAB node identifying at least the portion of the resources punctured by the first node, comprises: The uplink preemption indication corresponding to the uplink traffic transmission of the PUSCH during the first time slot is received in a medium access control address control element (MAC-CE) message sent to the IAB node during a second time period over a second PUSCH.

35. The method of claim 23, wherein: The uplink preemption indication is one of a timeslot level indication, a transport block level indication, a symbol level indication or a frequency range level indication.

36. The method of claim 23, wherein: The first node is an integrated access and backhaul (IAB) node, wherein the IAB node is a parent backhaul node, and The third node is at least one of a sub-IAB node or a user equipment (UE).

37. An apparatus for wireless communication, comprising: a memory configured to store instructions; a processor communicatively coupled to the memory, the processor configured to execute the instructions to: receiving uplink traffic from the first node via a physical uplink shared channel (PUSCH) during a first time slot; receiving, at an integrated access and backhaul (IAB) node from the first node, an uplink preemption indication, the uplink preemption indication identifying that at least a portion of resources of the PUSCH used for the uplink traffic from the first node to the IAB node are punctured by the first node due to: receiving, at the first node, during the first time slot, an emergency ultra-reliable low-latency communication (URLLC) traffic on at least the portion of the resources that conflicts with transmission of uplink traffic from the first node to the IAB node; as well as The uplink preemption indication is decoded to identify at least the portion of the resources corresponding to punctured traffic.

38. The device according to claim 37, wherein The processor is further configured to execute the instructions to perform the method according to claims 23-36.

Images