Patent Description:
<NPL>et al, deals with resource allocation aspects between access and BH links.

After considering this discussion, and particularly after reading the section entitled "Detailed Description" one will understand how the features of this disclosure provide advantages that include improved communication in integrated access and backhaul systems.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for full-duplex slot configuration for integrated access and backhaul (IAB) communication systems. Specifically, the disclosure provides techniques for full-duplex communication in IAB systems, including modification, by IAB nodes, of slots and patterns of slots to full-duplex slot types and/or non-full duplex slot types. Accordingly, IAB systems are able to obtain improved channel capacity and flexible scheduling opportunities at each link to accommodate for backhaul and access traffic variances, and benefits both in eMBB and ultra-reliable low-latency communication (URLLC) services.

The teachings herein may be incorporated into (e.g., implemented within or performed by) a variety of wired or wireless apparatuses (e.g., nodes). In some aspects, a wireless node implemented in accordance with the teachings herein may comprise an access point or an access terminal.

An access point ("AP") may comprise, be implemented as, or known as a Node B, a Radio Network Controller ("RNC"), an evolved Node B (eNB), a Base Station Controller ("BSC"), a Base Transceiver Station ("BTS"), a Base Station ("BS"), a Transceiver Function ("TF"), a Radio Router, a Radio Transceiver, a Basic Service Set ("BSS"), an Extended Service Set ("ESS"), a Radio Base Station ("RBS"), an IAB node (e.g., an IAB donor node, an IAB parent node, and an IAB child node), or some other terminology.

An access terminal ("AT") may comprise, be implemented as, or known as a subscriber station, a subscriber unit, a mobile station, a remote station, a remote terminal, a user terminal, a user agent, a user device, user equipment, a user station, or some other terminology. In some implementations, an access terminal may comprise a cellular telephone, a cordless telephone, a Session Initiation Protocol ("SIP") phone, a wireless local loop ("WLL") station, a personal digital assistant ("PDA"), a handheld device having wireless connection capability, a Station ("STA"), or some other suitable processing device connected to a wireless modem (such as an AR/VR console and headset). Accordingly, one or more aspects taught herein may be incorporated into a phone (e.g., a cellular phone or smart phone), a computer (e.g., a laptop), a portable communication device, a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music or video device, or a satellite radio), a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. In some aspects, the node is a wireless node. Such wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link.

For example, the wireless communication network <NUM> may be a New Radio (NR) or <NUM> network. For example, as shown in <FIG>, an access point (AP) 110a includes a full-duplex (FD) configuration module 114a that may be configured for full-duplex slot configuration in integrated access and backhaul (IAB) communication systems, according to aspects described herein. In another example, a relay 110r also includes a full-duplex (FD) configuration module 114r configured for full-duplex slot configuration in integrated access and backhaul (IAB) communication systems. In certain aspects, the AP 110a may be an IAB donor and/or parent node, while the relay 110r is an IAB node that is a child node to the AP 110a. Accordingly, in some configurations, communications between the AP 110a and relay 110r may be facilitated by wireless backhaul link. Moreover, in some configurations, communications between the relay 110r and a user equipment 120r may be facilitated by a wireless access link.

As illustrated in <FIG>, the wireless communication network <NUM> may include a number of access points (APs) <NUM> and other network entities. An AP may be a station that communicates with user equipment (UEs). Each AP <NUM> may provide communication coverage for a particular geographic area. In NR systems, the term "cell" and next generation NodeB (gNB or gNodeB), NR AP, <NUM> NB, or transmission reception point (TRP) may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile AP. In some examples, the access points may be interconnected to one another and/or to one or more other access points or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

An AP may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells. An AP for a macro cell may be referred to as a macro AP. An AP for a pico cell may be referred to as a pico AP. An AP for a femto cell may be referred to as a femto AP or a home AP. In the example shown in <FIG>, the APs 110a, 110b and 110c may be macro APs for the macro cells 102a, 102b and 102c, respectively. The AP 110x may be a pico AP for a pico cell 102x. The APs 110y and 110z may be femto APs for the femto cells 102y and 102z, respectively. An AP may support one or multiple (e.g., three) cells.

A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., an AP or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or an AP). In the example shown in <FIG>, a relay station 110r may communicate with the AP 110a and a UE 120r in order to facilitate communication between the AP 110a and the UE 120r. A relay station may also be referred to as an IAB node, a relay AP, a relay, etc..

Wireless communication network <NUM> may be a heterogeneous network that includes APs of different types, e.g., macro AP, pico AP, femto AP, relays, etc. These different types of APs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless communication network <NUM>. For example, macro AP may have a high transmit power level (e.g., <NUM> Watts) whereas pico AP, femto AP, and relays may have a lower transmit power level (e.g., <NUM> Watt).

For synchronous operation, the APs may have similar frame timing, and transmissions from different APs may be approximately aligned in time. For asynchronous operation, the APs may have different frame timing, and transmissions from different APs may not be aligned in time.

A network controller <NUM> may couple to a set of APs and provide coordination and control for these APs. The network controller <NUM> may communicate with the APs <NUM> via a backhaul. The APs <NUM> may also communicate with one another (e.g., directly or indirectly) via wireless or wireline backhaul.

MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with an AP, another device (e.g., remote device), or some other entity.

Certain wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink (DL) and single-carrier frequency division multiplexing (SC-FDM) on the uplink (UL).

A scheduling entity (e.g., an AP) allocates resources for communication among some or all devices and equipment within its service area or cell. Access points are not the only entities that may function as a scheduling entity.

In <FIG>, a solid line with double arrows indicates desired transmissions between a UE and a serving AP, which is an AP designated to serve the UE on the downlink and/or uplink. A finely dashed line with double arrows indicates interfering transmissions between a UE and an AP.

<FIG> illustrates an example architecture of a distributed radio access network (RAN) <NUM> that includes an example IAB network <NUM>, which may be implemented in the wireless communication network <NUM> illustrated in <FIG>. As shown in <FIG>, the distributed RAN includes core network (CN) <NUM> and access node (AN) configured as an IAB donor <NUM>.

As shown, the IAB network <NUM> includes an IAB donor node <NUM>. The IAB donor node <NUM> is a RAN node (e.g., access point/gNB that terminates the NR Ng interface with the core network (e.g., next generation NG core)) and is generally connected to the core network via a wireline backhaul link. The CN <NUM> may host core network functions. CN <NUM> may be centrally deployed. CN <NUM> functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. The CN <NUM> may include the access and mobility management function (AMF) <NUM> and user plane function (UPF) <NUM>. The AMF <NUM> and UPF <NUM> may perform one or more of the core network functions.

The IAB donor <NUM> may communicate with the CN <NUM> (e.g., via a backhaul interface). The IAB donor <NUM> may communicate with the AMF <NUM> via an N2 (e.g., NG-C) interface. The IAB donor <NUM> may communicate with the UPF <NUM> via an N3 (e.g., NG-U) interface. The IAB donor <NUM> may include a central unit-control plane (CU-CP) <NUM>, one or more central unit-user plane (CU-UPs) <NUM>, one or more distributed units (DUs) <NUM>-<NUM>, and one or more antenna/remote radio units (AU/RRUs) (not shown). The CUs and DUs may also be referred to as gNB-CU and gNB-DU, respectively.

An IAB donor node <NUM> may also be referred to as an IAB anchor node and may include an IAB central unit (e.g., NR CU) or an IAB Distributed Unit (e.g., NR DU). The IAB network <NUM> further includes one or more non-donor IAB nodes (e.g., 220a-220e). Each IAB node (including donor and non-donor IAB nodes) may serve one or more UEs (e.g., 222a-222c) connected to an IAB node. As shown, the IAB nodes, including the donor IAB node <NUM>, may be connected via wireless backhaul links (e.g., NR wireless backhaul links or backup NR wireless backhaul links). Each IAB node connects to its served UEs via respective access links.

Each IAB node is a RAN node (e.g., access point/gNB) that provides IAB functionality with two roles including data unit function (DU-F) and a mobile termination function (MT-F). The DU-F of an IAB node is generally responsible for scheduling UEs (e.g., served by the IAB node) and other IAB nodes (e.g., that are connected as child nodes to the IAB node). The DU-F also controls both access and backhaul links under its coverage. The MT-F of an IAB node is controlled and scheduled by an IAB donor node or another IAB node as its parent IAB node. In an aspect, the IAB donor node <NUM> only includes DU-F and no MT-F.

The CU-CP <NUM> may be connected to one or more of the DUs <NUM>-<NUM>. The CU-CP <NUM> and DUs <NUM>-<NUM> may be connected via a wireline interface using F1-C protocols. As shown in <FIG>, the CU-CP <NUM> may be connected to multiple DUs, but the DUs may be connected to only one CU-CP. Although <FIG> only illustrates one CU-UP <NUM>, the IAB donor <NUM> may include multiple CU-UPs. The CU-CP <NUM> selects the appropriate CU-UP(s) for requested services (e.g., for a UE). The CU-UP(s) <NUM> may be connected to the CU-CP <NUM>. For example, the CU-UP(s) <NUM> and the CU-CP <NUM> may be connected via an E1 interface. The CU-CP(s) <NUM> may be connected to one or more of the DUs <NUM>, <NUM>. The CU-UP(s) <NUM> and DUs <NUM>, <NUM> may be connected via a F1-U interface. As shown in <FIG>, the CU-CP <NUM> may be connected to multiple CU-UPs, but the CU-UPs may be connected to only one CU-CP.

A DU, such as DUs <NUM> and/or <NUM>, may host one or more TRP(s) (transmit/receive points, which may include an Edge Node (EN), an Edge Unit (EU), a Radio Head (RH), a Smart Radio Head (SRH), or the like). A DU may be located at edges of the network with radio frequency (RF) functionality. A DU may be connected to multiple CU-UPs that are connected to (e.g., under the control of) the same CU-CP (e.g., for RAN sharing, radio as a service (RaaS), and service specific deployments). DUs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE. Each DU <NUM>, <NUM> may be connected with one of AU/RRUs.

The CU-CP <NUM> may be connected to multiple DU(s) that are connected to (e.g., under control of) the same CU-UP <NUM>. Connectivity between a CU-UP <NUM> and a DU may be established by the CU-CP <NUM>. For example, the connectivity between the CU-UP <NUM> and a DU may be established using Bearer Context Management functions. Data forwarding between CU-UP(s) <NUM> may be via a Xn-U interface.

The distributed RAN <NUM> may support fronthauling solutions across different deployment types. For example, the RAN <NUM> architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The distributed RAN <NUM> may share features and/or components with LTE. For example, IAB donor <NUM> may support dual connectivity with NR and may share a common fronthaul for LTE and NR. The distributed RAN <NUM> may enable cooperation between and among DUs <NUM>, <NUM>, for example, via the CU-CP <NUM>. An inter-DU interface may not be used.

Logical functions may be dynamically distributed in the distributed RAN <NUM>. As will be described in more detail with reference to <FIG>, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, Physical (PHY) layers, and/or Radio Frequency (RF) layers may be adaptably placed, in the AN and/or UE.

<FIG> illustrates an example IAB network <NUM> in which aspects of the present disclosure may be practiced. In this example, the IAB network <NUM> includes a parent node <NUM>, an IAB node <NUM>, a child node <NUM>, and a user equipment (UE) <NUM>. The terms "parent node" and "child node" are terms assigned to a node dependent on that node's position from the donor node relative to another node. For example, as shown in <FIG>, the parent node <NUM> is closer to a donor node (not shown) than the IAB node <NUM> or the child node <NUM>. Accordingly, the IAB node <NUM> is a child node relative to the parent node <NUM>, and a parent node relative to the child node <NUM>.

In this example, the IAB node <NUM> includes six types of links: a DL parent backhaul (BH) and an UL parent BH with its parent node <NUM>, a DL child BH and an UL child BH with its child node <NUM>, and a DL access and an UL access with the UE <NUM>.

<FIG> illustrates a diagram showing examples for implementing a communications protocol stack <NUM> in a RAN (e.g., such as the RAN <NUM>), according to aspects of the present disclosure. The illustrated communications protocol stack <NUM> may be implemented by devices operating in a wireless communication system, such as a <NUM> NR system (e.g., the wireless communication network <NUM>). In various examples, the layers of the protocol stack <NUM> may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device or a UE. As shown in <FIG>, the system may support various services over one or more protocols. One or more protocol layers of the protocol stack <NUM> may be implemented by an AN (e.g., AN <NUM> in <FIG>, or AP 110a in <FIG>) and/or the UE (e.g., UE <NUM>).

As shown in <FIG>, the protocol stack <NUM> is split in the AN. The RRC layer <NUM>, PDCP layer <NUM>, RLC layer <NUM>, MAC layer <NUM>, PHY layer <NUM>, and RF layer <NUM> may be implemented by the AN. For example, the CU-CP (e.g., CU-CP <NUM> in <FIG>) and the CU-UP e.g., CU-UP <NUM> in <FIG>) each may implement the RRC layer <NUM> and the PDCP layer <NUM>. A DU (e.g., DUs <NUM> and <NUM> in <FIG>) may implement the RLC layer <NUM> and the MAC layer <NUM>. However, the DU may also implement the PHY layer(s) <NUM> and the RF layer(s) <NUM> via an AU/RRU connected to the DU. The PHY layers <NUM> may include a high PHY layer and a low PHY layer.

The UE (e.g., UE 222a-222c) may implement the entire protocol stack <NUM> (e.g., the RRC layer <NUM>, the PDCP layer <NUM>, the RLC layer <NUM>, the MAC layer <NUM>, the PHY layer(s) <NUM>, and the RF layer(s) <NUM>).

Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or AP), even though the scheduling entity may be utilized for scheduling and/or control purposes.

Next generation (<NUM>) wireless networks are expected to provide ultra-high data rate and support wide scope of application scenarios. Wireless full-duplex (FD) communications are an emerging technique theoretically capable of doubling wireless link capacity. The main idea behind wireless full-duplex is to enable radio network nodes to transmit and receive simultaneously using the same time resources at the same time slot. This contrasts with conventional half duplex operation where transmission and reception differ in time.

In an IAB system without full-duplex, an IAB node (e.g., IAB node <NUM>) cannot perform transmission and reception of wireless data concurrently. For example, from the perspective of IAB node <NUM>, any reception link (e.g., DL parent BH, UL child BH, and/or UL access) and any transmission link (e.g., UL parent BH, DL child BH, and/or DL access) cannot have data communicated at the same time. Moreover, non-full-duplex communication reduces the IAB systems ability to accommodate the requirements of urgent data traffic (e.g., ultra-reliable low-latency communication (URLLC) data traffic). For example, the half-duplex mode restricts the radio resource spectrum efficiency and hence lowers down the system throughput.

As described above, some data may be characterized as URLLC data. In some configurations, URLLC data refers to data that has a relatively low or ultra-low latency requirement. For example, the latency requirement of URLLC data may be lower than the latency requirement of other data included in a subframe. Generally, latency refers to the delay associated with receipt of data at its intended destination. In some configurations, URLLC data refers to data that has a relatively high priority requirement. For example, the priority requirement of URLLC data may be higher than the priority requirement of other data included in the subframe. Generally, priority refers to the importance or time-sensitivity of the data. Data having relatively higher importance and/or relatively greater time-sensitivity should be received before other data having relatively lesser importance and/or relatively lesser time-sensitivity. In some configurations, URLLC data refers to data that has a relatively high reliability requirement. For example, the reliability requirement of URLLC data may be greater than the reliability requirement of other data included in that subframe. Generally, reliability refers to how consistently data is successfully received by the intended destination without errors. As used throughout the disclosure, a quality of service (QoS) may correspond to any one or more of a latency, priority, or reliability requirement.

Therefore, the disclosure describes techniques for utilizing full-duplex to enable concurrent transmission and reception at an IAB node to support dynamic traffic allocation, improved system capacity, and capability to fast deliver any-directional packet. For example, to enable efficient IAB system operation, a plurality of full-duplex slot types are defined. Based on the full-duplex slots, the nodes in an IAB system can determine the proper full-duplex slot configuration to adapt with the traffic status variance of all related links of an IAB node, and send signaling to other nodes for synchronization.

In certain aspects, an IAB node (or IAB donor) determines whether to use a full-duplex slot or a non-full-duplex slot (e.g., a half-duplex downlink or uplink slot) to communicate wireless data. The determination to use a full-duplex slot or a non-full-duplex slot is based on traffic parameters associated with the wireless data. For example, the wireless data being communicated by the IAB node may include enhanced mobile broadband (eMBB) data that requires a high data transmission rate and/or a high data reliability requirement. In another example, the wireless data being communicated by the IAB node may include URLLC data having an ultra-reliable and ultra-low latency requirement. In yet another example, the wireless data being communicated by the IAB node may include both eMBB data and URLLC data. Thus, in an example where a first link is communicating eMBB data, and a second link is communicating URLLC data at the same time, the IAB node may determine to use a full-duplex slot that communicates the eMBB data of the first link and the URLLC data of the second link using the same time resources. Accordingly, in this example, the IAB node may select a type of full-duplex slot on the basis of which links are communicating the eMBB and URLLC data, and on the basis of other traffic parameters (e.g., the data transmission rate of the eMBB data, and the latency and reliability requirements of the URLLC data).

<FIG> illustrates a first table showing an example full-duplex slot type index for full-duplex communication from the perspective of IAB node <NUM>. In this example, each column represents one slot type. In each slot type, two or three links are involved in the full duplex. It should be noted that additional or fewer slot types may be available for other nodes (e.g., a parent/donor node, or a child node) depending on the links available to those nodes.

In the example shown in <FIG>, the first table includes eleven full-duplex slot types. The first slot type is a slot for full-duplex communication of data received over a DL parent BH link and data transmitted over an UL parent BH link. The second slot type is a slot for full-duplex communication of data received over a DL parent BH link and data transmitted over a DL child BH link. The third slot type is a slot for full-duplex communication of data received over a DL parent BH link and data transmitted over a DL access link. The fourth slot type is a slot for full-duplex communication of data transmitted over an UL parent BH link and data received over an UL child BH link. The fifth slot type is a slot for full-duplex communication of data transmitted over an UL parent BH link and data received over an UL access link. The sixth slot type is a slot for full-duplex communication of data transmitted over a DL child BH link and data received over an UL child BH link. The seventh slot type is a slot for full-duplex communication of data transmitted over a DL child BH link and data received over an UL access link. The eighth slot type is a slot for full-duplex communication of data received over an UL child BH link and data transmitted over a DL access link. The ninth slot type is a slot for full-duplex communication of data transmitted over a DL access link and data received over an UL access link. The tenth slot type is a slot for full-duplex communication of data received over a DL parent BH link and data transmitted over a DL child BH link and a DL access link. The eleventh slot type is a slot for full-duplex communication of data transmitted over an UL parent BH link and data received over an UL child BH link and an UL access link.

In the example of the tenth slot type, data received over the DL parent BH link is paired with data transmitted over the DL child BH link and the DL access link in the same time-frequency resource. For example, the data transmitted over the DL child BH link and the DL access link can be multiplexed in different frequency subbands (FDM) or different spatial domains (SDM). In the example of the eleventh slot type, data transmitted over the UL parent BH link is paired with data received over the UL child BH link and the UL access link in the same time-frequency resource. For example, the UL child BH link and the UL access link can be multiplexed in different frequency subbands (FDM) or different spatial domains (SDM).

<FIG> illustrates a second table showing a list of reception link types and transmission link types associated with each slot type. It should be noted that additional or fewer slot types may be available for other nodes (e.g., a parent/donor node, or a child node) depending on the links available to those nodes.

Thus, in one example, if a first link is communicating eMBB data, and a second link is communicating URLLC data at the same time, the IAB node will determine to use a full-duplex slot. Then the IAB node will select a full-duplex slot based on the links communicating the eMBB and URLLC data. For example, if the first link is an UL parent BH link and the second link is an UL child BH link, then the IAB node will select the fourth slot type for full-duplex communication of the eMBB and URLLC data. Accordingly, determination by an IAB node to utilize a full-duplex slot and selection of the particular type of full-duplex slot may be based on, or a function of, one or more traffic parameters. As used herein, the term "traffic parameters" may relate to one or more requirements associated with different service categories with the introduction of a Services Based Architecture (SBA) and Control and User Plane Separation (CUPS), requirements of data being communicated over one or more links (e.g., latency, reliability, priority, data rate, etc.), a status of one or more of the links (e.g., amount of traffic on a link, traffic throughput, link bandwidth, etc.), and/or a variance of one or more traffic parameters over time or the status of the links.

It should be noted that the length of the slot can be a full slot, or a partial slot (e.g., a mini-slot) as shown in <FIG>.

In a full-duplex mode of communication, an IAB node (or IAB donor) utilizes a full-duplex slot pattern for communication of data between various other nodes. In one example, the full-duplex slot pattern includes a plurality of consecutive slots, each of which is one of a non-full-duplex slot or one of the plurality of full-duplex slot types. In some configurations, the IAB node can periodically apply the pattern to communicate data, and repeat the pattern at intervals. In other configurations, the IAB node can apply the pattern aperiodically (e.g., the pattern occurs only after triggered by a certain event, (e.g. link throughput change or urgent traffic occurrence)).

In some configurations, the IAB node (or IAB donor) determines an initial periodic full-duplex slot pattern containing one or more full-duplex slot types and, in some cases, one or more non-full-duplex slots. For example, the IAB node may initially determine a full-duplex slot pattern based on the traffic characteristics of all links. For example, the IAB node may monitor data traffic over all the links it communicates over. Monitoring may include tracking a status of each link (e.g., amount of traffic on each link, link bandwidth, one or more QoS parameters, etc.) to determine whether to implement a full-duplex slot pattern. If the IAB node determines to implement a full-duplex slot pattern, the IAB node will generate a full-duplex slot pattern including an arrangement of each slot type in the pattern to accommodate the determined status of one or more links. For example, the IAB node may determine a pattern configured to adjust a ratio of aggregated capacity of each link of a slot of a particular type in accordance with a ratio of the traffic amount on each link of that slot. For example, the throughput of two or three links in one full-duplex slot type may be summed in their individual capacity aggregations, respectively. In one example, if for one link (e.g., DL parent BH), the ratio of aggregated capacity is smaller than the ratio of the traffic amount, the percentage of FD slot types that include the this link (e.g., the first slot type, the second slot type, the third slot type, and the tenth slot type) in the slot pattern are increased. In other words, the number of FD slots in the pattern that are a first, second, third, or tenth slot type will increase. Conversely, if the ratio of aggregated capacity is larger than the ratio of the traffic amount, the percentage of the FD slot types involving the link in the slot pattern is decreased.

Moreover, the IAB node may adjust the full-duplex slot pattern based on continued monitoring of the status of the links. For example, when the IAB node detects a change of link status (e.g., a change in one or more traffic parameters), the IAB node will adjust a periodic slot pattern that includes the full-duplex slot types described above and in relation to <FIG>, or apply an aperiodic full-duplex slot pattern or single slot modification according to the variation. For example, if the data communicated over the two or three links using a particular full-duplex slot type is larger than or equal to a threshold amount (e.g., the aggregated amount of data on each link exceeds one common threshold, or the data amount of one or more links exceeds an individual threshold of that corresponding link), then the IAB node may determine to increase a frequency of use of a particular full-duplex slot type for the two or three links in order to accommodate particular traffic needs. Similarly, if the data communicated over the two or three links using a particular full-duplex slot type is smaller than or equal to a threshold amount (e.g., the aggregated amount of data on each link is smaller one common threshold, or the data amount of one or more links is smaller than an individual threshold of that corresponding link), then the IAB node may determine to decrease a frequency of use of a particular slot type for the two or three links.

<FIG> is a call flow diagram <NUM> illustrating example communication processes for modifying one or more slots types. In certain aspects, modifying the one or more slot types includes modifying a full-duplex slot to a non-full-duplex slot, changing a non-full-duplex slot to one of the plurality of full-duplex slot types, or changing a particular type of full-duplex slot to another type of full-duplex slot in a periodic or aperiodic pattern determined by the IAB node, or for modifying any particular slot not in a pattern. <FIG> includes a parent node <NUM> (e.g., parent node <NUM>) or a donor node, an IAB node <NUM> (e.g., IAB node <NUM>) which is a child node relative to the parent node <NUM>, and a child node <NUM> (e.g., child node <NUM>). The IAB node <NUM> can modify a slot to accommodate traffic parameters of one or more links and/or data requirements of data communicated over the links.

It should be noted that by modifying an IAB system for full-duplex communication and providing periodic/aperiodic slot type modification, the IAB system is able to realize an increase in channel capacity and flexible scheduling to accommodate different types of data being communicated, as well as variance in amounts of traffic. Accordingly, the systems and methods of the disclosure benefit both eMBB and URLLC services.

In certain aspects, the modification of a slot type by the IAB node <NUM> may be triggered by either the parent node <NUM>, the child node <NUM>, or the IAB node <NUM> itself. In one example, the parent node <NUM> may send a request message <NUM> configured to request that the IAB node <NUM> to initiate a modification of a slot. When the IAB node <NUM> receives the message, the IAB node <NUM> may determine which slot to modify and how to modify the slot based on the request, then modify the slot <NUM> according to the request.

In another example, the child node <NUM> may send a request message <NUM> to the IAB node <NUM> requesting to modify a slot type, which in this case a parent node relative to the child node <NUM>, to initiate a modification of a slot. When the IAB node <NUM> receives the message, the IAB node <NUM> may determine whether to accept or reject the request <NUM>, and may modify the slot according to the modification request <NUM> if accepted. The IAB node <NUM> determines whether to accept or reject the request <NUM> based on the traffic parameters of the links that are involved in the slot that the child node <NUM> wants to modify. In one example, if the links of a current slot type have a high traffic amount (e.g., eMBB data) or a high priority and/or high reliability (e.g., URLLC data) data traffic compared to the links of the requested slot type, the IAB node <NUM> may determine to reject the request <NUM>. However, if the links of the requested slot type have a higher amount of traffic and/or higher priority data than the links of the current slot type, then the IAB node <NUM> may determine to accept the request <NUM>.

The IAB node <NUM> may then transmit an accept/reject message <NUM> to the child node <NUM>. Optionally, the IAB node <NUM>, upon accepting the request, may forward the request message <NUM> to a parent node <NUM> or donor node for acceptance. The parent node <NUM> may accept/reject the modification request and transmit the acceptance/rejection <NUM> to the IAB node <NUM> in response to the modification request <NUM>. Once the IAB <NUM> node receives the acceptance/rejection <NUM>, the IAB node <NUM> may proceed to modify the slot according to the modification request <NUM>, and forward the acceptance/rejection <NUM> to the child node <NUM>. In some examples, the IAB node <NUM> and/or the parent node <NUM> may reject the request to modify a slot based on traffic parameters that the child node is unaware of.

It should be noted that in some examples, the IAB node <NUM> may determine the modification of the slot and executes the modification by itself, without notification or requesting an acceptance or a rejection.

In a first specific example, the IAB node <NUM> may determine to modify a slot. In this example, the determination to modify the slot may be based on monitoring, by the IAB node <NUM>, one or more traffic parameters associated with the DL Child BH link and/or the UL Child BH link. Based on the monitoring, the IAB node <NUM> may determine a slot type modification for the DL Child BH link and/or the UL Child BH link based on the traffic parameters (e.g., a variance of an amount of traffic on a link). For example, the IAB node <NUM> may select the seventh slot type and change the slot type to the seventh slot type for full-duplex communication if the DL child BH link and the UL access link have a high amount of traffic and/or URLLC data. Accordingly, the data communicated over the DL child BH link and the UL access link will be paired for full-duplex communication in the seventh slot type. In another example, the IAB node <NUM> may select the eighth slot type and change the slot type to the eighth slot type for full-duplex communication if the UL child BH link and the DL access link have high amount of traffic and/or URLLC data. Accordingly, the data communicated over the UL child BH link and the DL access link will be paired for full-duplex communication in the eighth slot type. In another example, the IAB node <NUM> may select the sixth the slot type and change the slot type to the sixth slot type for full duplex communication if the DL child BH and the UL child BH have high amount of traffic and/or URLLC data. Accordingly, the data communicated over the DL child BH and the UL child BH will be paired for full-duplex communication in the sixth slot type. The IAB node <NUM> may then notify the child node <NUM> of the modification to the slot.

In a second specific example, IAB node <NUM> may determine to modify a slot based on traffic parameters of one or more links. Similar to the previous example, the determination to modify the slot may be based on monitoring one or more traffic parameters of at least the DL parent BH link and/or the UL parent BH link. The IAB node <NUM> may then request the slot modification from the parent node <NUM> based on the traffic parameters. For example, the IAB node <NUM> may select one of a second slot type, a third slot type, or a tenth slot type and request to modify the slot accordingly if the DL parent BH link and the DL child BH link and/or DL access link have a high amount of traffic and/or URLLC data. Accordingly, if the parent node <NUM> accepts the requested modification, then data communicated over the DL parent BH link and one or more of the DL child BH link or DL access link will be paired for full-duplex communication. In another example, the IAB node <NUM> may request to modify the slot type to the fourth slot type, the fifth slot type, or the eleventh slot type if the UL Parent BH link and one or more of the UL Child BH link or the UL Access link have a high amount of traffic and/or URLLC data. Accordingly, if the parent node <NUM> accepts the requested modification, then data communicated over the UL Parent BH link and one or more of the UL Child BH link or the UL Access link will be paired for full-duplex communication. In another example, the IAB node <NUM> may request to modify the slot type to the first slot type if the DL Parent BH link and the UL Parent BH link have a high amount of traffic and/or URLLC data. Accordingly, if the parent node <NUM> accepts the requested modification, then data communicated over the DL Parent BH link and the UL Parent BH link will be paired for full-duplex communication.

In a third specific example, child node <NUM> may determine to modify a slot based on traffic parameters of one or more links. The child node <NUM> may then request the slot modification from the IAB node <NUM>. The IAB node <NUM> will determine whether to accept or reject the request, and send a response to the child node <NUM> indicating the acceptance or rejection. For example, the child node <NUM> may determine to modify a slot based on traffic parameters monitored over the DL child BH link or the UL child BH link. In one example, the child node <NUM> may request to modify a slot to the second slot type, the seventh slot type, or the tenth slot type if the DL child BH link has a high amount of traffic and/or URLLC data. In another example, the child node <NUM> may request to modify the slot to the fourth slot type, the eighth slot type, or the eleventh slot type if the UL child BH link has a high amount of traffic and/or URLLC data. In another example, the child node <NUM> may request to modify the slot to the sixth slot type if the DL child BH link and the UL child BH link have a high amount of traffic and/or URLLC data.

In a fourth specific example, the child node <NUM> may determine to modify a slot based on traffic parameters of one or more links. The child node <NUM> may then request the slot modification from the IAB node <NUM>. The IAB node <NUM> may then send the request for the slot modification to the parent node <NUM>. The parent node <NUM> then determines whether to accept to reject the request, and proceeds to communicate a response message to the IAB node <NUM> indicating the acceptance or rejection. The IAB node <NUM> may then communicate a response to the child node <NUM> indicating the acceptance or rejection of the parent node <NUM>. For example, the child node <NUM> may determine to modify the slot based on traffic parameters of at least the DL child BH link and/or the UL child BH link, and communicate a request for the slot modification to the IAB node <NUM>. Upon receiving the request, the IAB node <NUM> may determine whether to accept or reject the request modification based on traffic parameters of at least the DL parent BH link and/or the UL parent BH link. The IAB node <NUM> may then pass the requested slot modification to the parent node <NUM>, depending on traffic parameters of at least the DL parent BH link and/or the UL parent BH link. For example, the child node <NUM> and the IAB node <NUM> may request to modify the slot to the second slot type or the tenth slot type if the DL parent BH link and/or the DL child BH link have a high amount of traffic and/or URLLC data. In another example, the child node <NUM> and the IAB node <NUM> may request to modify the slot to the fourth slot type or the eleventh sloth type if the UL parent BH link and the UL child BH link have a high amount of traffic and/or URLLC data.

In a fifth specific example, the parent node <NUM> may determine to modify a slot based on traffic parameters of one or more links. Once a determination has been made, the parent node <NUM> notifies the IAB node <NUM> with a message requesting that the IAB node <NUM> modify the slot according to the determination. For example, the determination by the parent node <NUM> may be based on monitoring the traffic parameters of the DL parent BH link and/or the UL parent BH links. In one example, the parent node <NUM> may request to modify the slot to the second slot type, the third lot type, or the tenth slot type if the DL parent BH link has a high amount of traffic and/or URLLC data. In another example, the parent node <NUM> may request to modify the slot to the fourth slot type, the fifth slot type, or the eleventh slot type if the UL parent BH link has a high amount of traffic and/or URLLC data. In another example, the parent node <NUM> may request to modify the slot to the first slot type if the DL parent BH link and/or the UL parent BH link have a high amount of traffic and/or URLLC data.

In a sixth specific example, the parent node <NUM> determines the modification of a slot based on traffic parameters of one or more links. Once a determination has been made, the parent node <NUM> notifies the IAB node <NUM> with a message requesting that the IAB node <NUM> modify the slot according to the determination. Once the IAB node <NUM> receives the request message, the IAB node <NUM> determines the modification of the slot and notifies the child node <NUM> with a message requesting that the child node <NUM> modify the slot according to the parent node <NUM> determination. For example, the determination by the parent node <NUM> may be based on monitoring the traffic parameters of the DL parent BH link or the UL parent BH link. In one example, determination by the IAB node <NUM> to modify the slot is based on monitoring the traffic parameters of at least the DL child BH and/or the UL child BH link. In another example, the determined slot modification includes modifying the slot to the second slot type or the tenth slot type if the DL parent BH and DL child BH have a high amount of traffic and/or URLLC data. In another example, the determined slot modification includes modifying the slot to the fourth slot type or the eleventh slot type if the UL parent BH link and/or the UL child BH link have a high amount of traffic and/or URLLC data.

In a seventh specific example, the IAB node <NUM> determines the modification of the slot and executes the modification by itself. For example, the IAB node <NUM> may determine to modify the slot based on traffic parameters determined by monitoring the DL access link and/or the UL access link. In one example, the determined slot modification includes modifying the slot to the ninth slot type if one or more of the DL access link and/or the UL access link have a high amount of traffic and/or URLLC data.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a AP (e.g., such as a AP <NUM> in the wireless communication network <NUM>, and any one or more of the parent node <NUM>, the IAB node <NUM>, or the child node <NUM> of <FIG>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., processor <NUM> and processor <NUM> in relation to <FIG> and <FIG> described below). Further, the transmission and reception of signals by the AP in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antenna <NUM> and antennas 1034a-1024t in relation to <FIG> and <FIG>). In certain aspects, the transmission and/or reception of signals by the AP may be implemented via a bus interface (e.g., bus <NUM> in relation to <FIG>) of the one or more processors obtaining and/or outputting signals.

The operations <NUM> begin, at a first block <NUM>, by determining one or more parameters associated with data configured for communication over wireless links comprising at least one reception link and at least one transmission link.

The operations <NUM> proceed to a second block <NUM>, by selecting a full-duplex (FD) slot type for communication of the data over the wireless links, wherein the FD slot type is based on the one or more parameters.

The operations <NUM> proceed to a third block <NUM>, by communicating the data with one or more wireless nodes via the wireless links in accordance with the selected FD slot type.

In certain aspects, the operations include selecting the FD slot type from a plurality of FD slot types, wherein each of the plurality of FD slot types corresponds to a slot configured to communicate the data over the reception and transmission links. In some configurations, the plurality of FD slot types include a first slot associated with a first link paired with a second link and a third link. In some configurations, the first slot is configured to communicate data of the first link paired with data of the second link and data of the third link using a first time-frequency resource, and the wireless links comprise first, second and third links. In certain aspects, the first link is a downlink reception link, and the second link and the third link are downlink transmission links, or the first link is an uplink transmission link, and the second link and the third link are uplink reception links. In certain aspects, the second link and the third link are multiplexed in different frequency subbands or in different spatial domains.

In certain aspects, the plurality of FD slot types include a first slot associated with a first link paired with a second link, the first slot is configured to communicate data of the first link paired with data of the second link using a first time-frequency resource, and the wireless links comprise first and second links.

In certain aspects, the operations <NUM> include determining a slot pattern comprising a plurality of slots, wherein the plurality of slots are associated with at least one FD slot type or non-FD slot type, and communicating the data via the wireless links in accordance with the determined slot pattern. In certain aspects, the at least one FD slot type comprises the selected FD slot type. In certain aspects, the determination of the slot pattern is based on the one or more parameters associated with the data configured for communication via the wireless links. In certain aspects, the operations <NUM> include detecting a change in the one or more parameters, and modifying the determined slot pattern based on the change in the one or more parameters.

In some examples, the communications device <NUM> may correspond to an AP 110a or a relay 110r of <FIG>.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG>, or other operations for performing the various techniques discussed herein for FD communication and FD slot selection. In certain aspects, computer-readable medium/memory <NUM> stores code for determining parameters associated with data communication <NUM>. In certain aspects, computer-readable medium/memory <NUM> stores code for selecting an FD slot type <NUM>. In certain aspects, computer-readable medium/memory <NUM> stores code for communicating with wireless nodes <NUM>.

In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. For example, the processor <NUM> includes circuitry for determining parameters associated with data communication <NUM>. In certain aspects, the processor <NUM> includes circuitry for selecting a full-duplex (FD) slot type <NUM>. In certain aspects, the processor <NUM> includes circuitry for communicating with wireless nodes <NUM>.

<FIG> illustrates example components <NUM> of AP <NUM> and UE <NUM> (as depicted in <FIG>), which may be used to implement aspects of the present disclosure. For example, antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the AP <NUM> may be used to perform the various techniques and methods described herein. For example, as shown in <FIG>, the processor <NUM> includes an full-duplex (FD) slot configuration circuit <NUM> that may be configured for full-duplex slot configuration in integrated access and backhaul (IAB) communication systems, according to aspects described herein. In certain aspects, the full-duplex slot communication circuit <NUM> enables the processor <NUM> to detect a change in the one or more traffic parameters, and dynamically modify a slot pattern based on the change in the one or more traffic parameters. In certain aspects, the AP <NUM> may be an IAB donor and/or parent node, or an IAB child node.

At the AP <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 1032a through 1032t. Downlink signals from modulators 1032a through 1032t may be transmitted via the antennas 1034a through 1034t, respectively.

At the UE <NUM>, the antennas 1052a through 1052r may receive the downlink signals from the access point <NUM> and may provide received signals to the demodulators (DEMODs) in transceivers 1054a through 1054r, respectively. A MIMO detector <NUM> may obtain received symbols from all the demodulators in transceivers 1054a through 1054r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.

The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators in transceivers 1054a through 1054r (e.g., for SC-FDM, etc.), and transmitted to the access point <NUM>. At the AP <NUM>, the uplink signals from the UE <NUM> may be received by the antennas <NUM>, processed by the modulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE <NUM>.

The controllers/processors <NUM> and <NUM> may direct the operation at the AP <NUM> and the UE <NUM>, respectively. The processor <NUM> and/or other processors and modules at the AP <NUM> may perform or direct the execution of processes for the techniques described herein. The memories <NUM> and <NUM> may store data and program codes for AP <NUM> and UE <NUM>, respectively.

Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. §<NUM>, sixth paragraph, unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for.

Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components.

As an example, "at least one of: a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as combinations that include multiples of one or more members (aa, bb, and/or cc).

The steps of a method or algorithm described in connection with the present disclosure may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in any form of storage medium that is known in the art. Some examples of storage media that may be used include random access memory (RAM), read only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM and so forth. A storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium.

Means for receiving or means for obtaining may include a receiver (such as the receive processor <NUM>) or an antenna(s) <NUM> of the access point <NUM> or the receive processor <NUM> or antenna(s) <NUM> of the station <NUM> illustrated in <FIG>. Means for transmitting or means for outputting may include a transmitter (such as the transmit processor <NUM>) or an antenna(s) <NUM> of the access point <NUM> or the transmit processor <NUM> or antenna(s) <NUM> of the station <NUM> illustrated in <FIG>. Means for associating, means for determining, means for monitoring, means for deciding, means for providing, means for detecting, means for performing, and/or means for setting may include a processing system, which may include one or more processors, such as the receive processor <NUM>/<NUM>, the transmit processor <NUM>/<NUM>, the TX MIMO processor <NUM>/<NUM>, or the controller <NUM>/<NUM> of the access point <NUM> and station <NUM> illustrated in <FIG>.

In some cases, rather than actually transmitting a frame a device may have an interface to output a frame for transmission (a means for outputting). For example, a processor may output a frame, via a bus interface, to a radio frequency (RF) front end for transmission. Similarly, rather than actually receiving a frame, a device may have an interface to obtain a frame received from another device (a means for obtaining). For example, a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for reception.

The functions described may be implemented in hardware, software, firmware, or any combination thereof.

The processor may be responsible for managing the bus and general processing, including the execution of software stored on the machine-readable media. Machine-readable media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The computer-program product may comprise packaging materials.

In a hardware implementation, the machine-readable media may be part of the processing system separate from the processor. However, as those skilled in the art will readily appreciate, the machine-readable media, or any portion thereof, may be external to the processing system. By way of example, the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer product separate from the wireless node, all which may be accessed by the processor through the bus interface.

The processing system may be configured as a general-purpose processing system with one or more microprocessors providing the processor functionality and external memory providing at least a portion of the machine-readable media, all linked together with other supporting circuitry through an external bus architecture. Alternatively, the processing system may be implemented with an ASIC (Application Specific Integrated Circuit) with the processor, the bus interface, the user interface in the case of an access terminal), supporting circuitry, and at least a portion of the machine-readable media integrated into a single chip, or with one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gated logic, discrete hardware components, or any other suitable circuitry, or any combination of circuits that can perform the various functionality described throughout this disclosure.

The machine-readable media may comprise a number of software modules. The software modules include instructions that, when executed by the processor, cause the processing system to perform various functions.

A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

Further, it should be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or access point as applicable. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or access point can obtain the various methods upon coupling or providing the storage means to the device.

Claim 1:
An apparatus (<NUM>) for wireless communications in an integrated access and backhaul, IAB, node, comprising:
a processing system (<NUM>) configured to:
determine one or more traffic parameters associated with data configured for communication via wireless links comprising at least one reception link and at least one transmission link;
select a full-duplex, FD, slot type for communication of the data via the wireless links, wherein the selection of the FD slot type is based on the one or more traffic parameters;
determine, based on the one or more traffic parameters, a slot pattern comprising a plurality of slots, wherein the plurality of slots are associated with at least one FD slot type or non-FD slot type, wherein the at least one FD slot type comprises the selected FD slot type; and
communicate the data with one or more wireless nodes via the wireless links in accordance with the determined slot pattern.