Supporting IAB operation in paired spectrum

Abstract

Aspects relate to an integrated access backhaul (IAB) - distributed unit (DU) resource configuration framework for paired (e.g., frequency division duplex (FDD)) spectrum. For paired spectrum, two DU resource configurations per cell can be supported, including one for a first spectrum band (e.g., downlink band) of the paired spectrum and another for a second spectrum band (e.g., uplink band) of the paired spectrum. Each DU resource configuration can include a respective symbol pattern for a plurality of slots of a symbol type (e.g., downlink (DL), uplink (UL), flexible), and a corresponding availability attribute for each symbol type (e.g., hard, soft, or unavailable). A DU of an IAB node in an IAB network can receive the two DU resource configurations for the paired spectrum from a central unit (CU) of an IAB donor node in the IAB network.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to and the benefit of pending non-provisional application No. 17 / 225,909 filed in the U.S. Patent Office on April 8, 2021, and provisional application No. 63 / 008,636 filed in the U.S. Patent Office on April 10, 2020, which are assigned to the assignee of the present application and which are expressly incorporated by reference herein as if fully set forth in their entirety and for all applicable purposes. TECHNICAL FIELD

[0003] The technology discussed below relates generally to wireless communication systems, and more particularly, to techniques for supporting paired spectrum in an integrated access backhaul (IAB) network. BACKGROUND

[0004] In 5G New Radio wireless communication networks, resources can be shared between access networks and backhaul networks. For example, wireless spectrum can be used for both access links (e.g., between a base station and a user equipment (UE)) and backhaul links (e.g., between a base station and a core network). In such integrated access backhaul (IAB) networks, a shared wireless carrier can be time divided into multiple frames, subframes, and slots. In some IAB network configurations, one or more slots can be allocated for access communications, while other slots can be allocated for backhaul communications. Additionally, the wireless carrier can be a time division duplex (TDD) carrier, in which transmissions in different directions are separated from each other using time division multiplexing, or a frequency division duplex (FDD) carrier, in which transmissions in different directions are separated from each other using frequency division multiplexing. For example, an FDD carrier can include paired spectrum, in which one spectrum band (e.g., one frequency band) can be used for transmissions in one direction, and another spectrum band (e.g., another frequency band) can be used for transmissions in the other direction.

[0005] An IAB network can include a plurality of IAB nodes, each of which can be an access point, a base station (BS), or other node that utilizes the same wireless spectrum (e.g., radio frequency (RF) spectrum) to support access for one or more UEs located within a cell served by the IAB node and backhaul access traffic to / from a mobile backhaul network or mobile core network, such as a Fifth Generation (5G) core network. Within an IAB network, one of the IAB nodes can be an IAB donor node that includes functionality to control the IAB network. For example, the IAB donor node can include a central unit (CU) configured to operate as a centralized network node (or central entity) within the IAB network. Each of the IAB nodes, including the IAB donor node, can also include a distributed unit (DU) configured to schedule communications with child nodes, such as other child IAB nodes and UEs of the IAB node. Each child IAB node can also include a mobile termination (MT) unit configured to backhaul access traffic to / from a parent IAB node. The DU at the parent IAB node schedules backhaul downstream and upstream access traffic to / from the MT unit at the child IAB node. SUMMARY

[0006] The following presents a summary of one or more aspects of the disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form that is brief, so as to provide a conceptual presentation of the same as a prelude to the more detailed description that is presented later.

[0007] In one example, a method of wireless communication at an integrated access backhaul (IAB) node within an IAB network is provided. The method includes receiving a resource configuration for a distributed unit (DU) of the IAB node. The resource configuration can include a first DU resource configuration for a first spectrum band of a paired spectrum and a second DU resource configuration for a second spectrum band of the paired spectrum. The method further includes scheduling, with the resource configuration, at least one communication with a child node of the IAB node.

[0008] Another example provides an Integrated Access Backhaul (IAB) node configured for wireless communication. The IAB node includes a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory can be configured to receive resource configurations for distributed units (DUs) of the IAB node via the transceiver. These resource configurations may include a first DU resource configuration for a first spectrum band of paired spectrum and a second DU resource configuration for a second spectrum band of paired spectrum. The processor and the memory can also be configured to schedule communication with at least one child node of the IAB node using the resource configurations.

[0009] Another example provides a method for wireless communication at an IAB donor node within an Integrated Access Backhaul (IAB) network. The method includes generating a resource configuration for distributed units (DUs) of the IAB nodes within the IAB network. The resource configuration may include a first DU resource configuration for a first spectrum band of paired spectrum and a second DU resource configuration for a second spectrum band of paired spectrum. The method also includes transmitting the resource configuration to the DUs of the IAB nodes.

[0010] Another example provides an Integrated Access Backhaul (IAB) donor node configured for wireless communication. The IAB donor node includes a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory can be configured to generate resource configurations for distributed units (DUs) of IAB nodes within the IAB network. These resource configurations may include a first DU resource configuration for a first spectrum band of paired spectrum and a second DU resource configuration for a second spectrum band of paired spectrum. The processor and the memory can also be configured to transmit the resource configurations to the DUs of the IAB node via the transceiver.

[0011] These and other aspects of the invention will be more fully understood by reading the following detailed description. Other aspects, features, and embodiments of the invention will become clear to those skilled in the art by reading the following description of specific exemplary embodiments of the invention in conjunction with the accompanying drawings. While features of the invention may be discussed with respect to certain embodiments and the drawings below, all embodiments of the invention may include one or more advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used according to the various embodiments of the invention discussed herein. Similarly, while exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0012] Figure 1It is a schematic diagram of a wireless communication system based on some aspects.

[0013] Figure 2 This is a conceptual diagram illustrating examples of radio access networks based on certain aspects.

[0014] Figure 3 This is a schematic diagram illustrating the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.

[0015] Figure 4 It is a high-level diagram illustrating an example of a network configuration based on several aspects, including Integrated Access Backhaul (IAB) networks.

[0016] Figure 5 This is a diagram illustrating examples of the functions of IAB nodes within an IAB network, based on some aspects.

[0017] Figure 6 This diagram illustrates the allocation of resources in an IAB network based on several aspects.

[0018] Figure 7 This is a signaling notification diagram illustrating an exemplary signaling notification for the configuration of distributed unit (DU) resources in paired spectrum in an IAB network, based on some aspects.

[0019] Figure 8 This is a signaling notification diagram illustrating an exemplary signaling notification for scheduling communication on soft resources in a paired spectrum, based on several aspects.

[0020] Figure 9 This is a block diagram illustrating an example of a hardware implementation of an IAB node for a processing system, based on several aspects.

[0021] Figure 10 This is a flowchart of an exemplary method for configuring IAB-DU resources in a paired spectrum according to some aspects.

[0022] Figure 11 This is a flowchart of another exemplary method for configuring IAB-DU resources in the spectrum for pairing, based on some aspects.

[0023] Figure 12 This is a flowchart of another exemplary method for configuring IAB-DU resources in the spectrum for pairing, based on some aspects.

[0024] Figure 13 This is a flowchart of another exemplary method for configuring IAB-DU resources in the spectrum for pairing, based on some aspects. Detailed Implementation

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

[0026] The various aspects relate to an IAB Distributed Unit (DU) resource configuration framework for paired spectrum to support per-cell DU semi-static configuration for FDD carriers. For paired spectrum, two semi-static DU resource configurations per cell can be supported, including one semi-static DU resource configuration for a first spectrum band (e.g., downlink or downstream band) and another semi-static DU resource configuration for a second spectrum band (e.g., uplink or upstream band). Each DU resource configuration may include a corresponding symbol pattern for each time slot symbol type (e.g., downlink (DL), uplink (UL), flexible), and a corresponding availability attribute for each symbol type (e.g., hard, soft, or unavailable). For example, an uplink DU resource configuration may include symbol patterns for uplink symbols and / or flexible symbols, while a downlink DU resource configuration may include symbol patterns for downlink symbols and / or flexible symbols. For each symbol type in the DU resource configuration, the DU resource configuration may indicate whether the symbol type is a hard symbol type, a soft symbol type, or unavailable.

[0027] The CU of the IAB donor node can generate resource configurations for the DUs of the IAB node (which may be the DUs of the IAB donor node) and send the resource configurations to the IAB node. For example, the resource configurations can be sent within an F1-Application Protocol (F1-AP) message from the CU. These resource configurations may include a first DU resource configuration for a first spectrum band of the paired spectrum and a second DU resource configuration for a second spectrum band of the paired spectrum. The resource configurations can also be sent, for example, within an information element containing a list of active cells of the IAB node to be updated. Each cell in the list of active cells may include a corresponding cell resource configuration for the paired spectrum. Therefore, each cell resource configuration may include two DU resource configurations: one DU resource configuration for the uplink and one DU resource configuration for the downlink. In some examples, the CU of the IAB donor node may also send corresponding sub-DU resource configurations for each child node (e.g., a child IAB node) of the IAB node (e.g., a parent IAB node), including the corresponding sub-DU resource configuration for each cell served by the child node. Each sub-DU resource configuration may also include two DU resource configurations: one DU resource configuration for the uplink in the paired spectrum and one DU resource configuration for the downlink in the paired spectrum.

[0028] In some examples, soft symbols in each of the first DU resource configuration and / or the second DU resource configuration may be explicitly released by the IAB parent node to allow the child IAB-DU configuration to use soft symbols for UL communications in the UL spectrum and / or DL ​​communications in the DL spectrum. The parent IAB node may send a corresponding availability indicator for the soft symbols in each of the first and second DU resource configurations to the child IAB node. Each availability indicator may indicate the corresponding availability of a soft symbol in the first and second DU resource configurations for one or more time slots. For example, uplink and / or flexible symbols in the uplink DU resource configuration may be soft symbols, and the child IAB node may allocate one or more of the uplink and / or flexible symbols for UL communications upon receiving an uplink availability indicator from the parent IAB node indicating the availability of uplink and / or flexible soft symbols destined for the child IAB node. As another example, the downlink and / or flexible symbols in the downlink DU resource configuration can be soft symbols, and a child IAB node can allocate one or more of the downlink and / or flexible symbols for UL communication when it receives a downlink availability indicator from the parent IAB node indicating the availability of the downlink and / or flexible soft symbols leading to the child IAB node. In some examples, two availability indicators can be received within the downlink control information (DCI) (such as DCI format 2_5).

[0029] Additionally, protection symbols can be requested by the child IAB node and / or provided by the parent IAB node for use in the conversion between DU and MT modes within the child IAB node (e.g., MT Tx / Rx to / from DU Tx / Rx). In time slots with flexible symbols in the DU resource configuration of a child IAB node, the parent IAB node can treat the flexible resources (e.g., flexible symbols) of the child IAB node in the UL portion of the FDD band as UL resources and the flexible resources of the child IAB node in the DL portion of the FDD band as DL resources to identify the conversion type between MT and DU within the child IAB node.

[0030] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating frequency bands are designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes arise when referring to FR2, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it differs from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0031] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as the frequency range name FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4-a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0032] In light of the foregoing, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, it can be within FR1, or it can include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" as used herein, it can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or it can be within the EHF band.

[0033] While aspects and embodiments are described herein by way of illustration of some examples, those skilled in the art will understand that other implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented on many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses may be implemented via integrated chip embodiments and / or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). However, some examples may or may not be specifically targeted at use cases or applications, and a broad classification of the applicability of the described innovations may occur. The range of implementations can extend from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems that incorporate one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors(s), interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and constructions.

[0034] The various concepts presented throughout this disclosure can be implemented across multiple telecommunications systems, network architectures, and communication standards. Reference is now made to... Figure 1 As a non-limiting illustrative example, reference is made to a wireless communication system 100 to illustrate various aspects of this disclosure. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 can be enabled to communicate data with an external data network 110 (such as, but not limited to, the Internet).

[0035] RAN 104 can implement any suitable wireless communication technology or technology to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate under a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, commonly known as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0036] As shown in the figure, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to by those skilled in the art as a Base Transceiver Station (BTS), radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Access Point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), Transmit and Receive Point (TRP), or some other suitable terminology. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one base station may be an LTE base station, while the other may be a 5G NR base station.

[0037] The diagram also illustrates RAN 104, which supports wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a User Equipment (UE), but those skilled in the art may also refer to such a device as a Mobile Station (MS), Subscriber Station, Mobile Unit, Subscriber Unit, Radio Unit, Remote Unit, Mobile Device, Radio Equipment, Wireless Communication Equipment, Remote Equipment, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handset, Terminal, User Agent, Mobile Client, Client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides users with access to network services.

[0038] In this disclosure, a “mobile” device need not be mobile and may be stationary. The term mobile device or mobile equipment broadly refers to a wide array of devices and technologies. A UE may include multiple hardware structural components that are sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and, for example, a wide array of embedded systems corresponding to the “Internet of Things” (IoT).

[0039] Mobile devices can also be automobiles or other transportation vehicles, remote sensors or actuators, robots or robotic equipment, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-helicopters, quadcopters, remote control devices, consumer and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment for controlling electricity (e.g., smart grids), lighting, water, etc., industrial automation and enterprise equipment, logistics controllers, and / or agricultural equipment, etc. Furthermore, mobile devices can provide connected medical or telemedicine support, such as remote healthcare. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority processing or access over other types of information, for example, in terms of priority access for the delivery of critical service data, and / or in terms of relevant QoS aspects for the delivery of critical service data.

[0040] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions initiated at the base station (e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of this disclosure, the term uplink can refer to point-to-point transmissions initiated at the UE (e.g., UE 106).

[0041] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all of the devices and equipment within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UE 106). That is, for scheduled communication, multiple UEs 106, which may be scheduled entities, can utilize the resources allocated by the scheduling entity 108.

[0042] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0043] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling services in a wireless communication network, including downlink service 112, and in some examples, uplink service 116 from one or more scheduled entities (e.g., one or more UEs 106) to scheduling entity 108. On the other hand, a scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114, which includes, but is not limited to, scheduling information (e.g., authorization), synchronization or timing information, or other control information from another entity in the wireless communication network (such as scheduling entity 108).

[0044] Additionally, uplink and / or downlink control information and / or service information can be transmitted on a waveform that can be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in an Orthogonal Frequency Division Multiplexing (OFDM) waveform where each subcarrier carries a resource element (RE). A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within this disclosure, a frame can refer to a predetermined duration (e.g., 10 ms) for wireless transmission, where each frame, for example, consists of 10 subframes, each 1 ms long. Of course, these definitions are not mandatory, and any suitable scheme for organizing the waveform can be utilized, and various time divisions of the waveform can have any suitable duration.

[0045] Typically, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of wireless communication system 100. Backhaul section 120 may provide a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network may provide interconnection between the individual base stations 108. Various types of backhaul interfaces may be employed, such as direct physical connections, virtual networks, or the like using any suitable transport network.

[0046] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0047] Now for reference Figure 2 As an illustrative and not limiting example, a schematic diagram of a radio access network (RAN) 200 according to some aspects of this disclosure is provided. In some examples, the RAN 200 may be connected to the network as described above and... Figure 1 The same as RAN104 shown in the diagram.

[0048] The geographic area covered by RAN 200 can be divided into multiple cellular regions (cells), and user equipment (UE) can uniquely identify these cellular regions (cells) based on an identifier broadcast from an access point or base station in the geographic area. Figure 2Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by antenna groups, each antenna responsible for communicating with UEs within a portion of the cell.

[0049] Various base stations can be used for deployment. For example, in Figure 2 In the illustration, two base stations, base station 210 and base station 212, are shown in cells 202 and 204. A third base station, base station 214, is shown as a remote radio headend (RRH) 216 controlling cell 206. That is, the base station may have an integrated antenna or may be connected to an antenna or RRH 216 via a feed cable. In the illustrated example, cells 202, 204, and 206 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, a base station 218, which may overlap with one or more macro cells, is shown in cell 208. In this example, cell 208 can be referred to as a small cell (e.g., small cell, microcell, picocell, femtocell, home base station, home node B, home eNode B, etc.) because base station 218 supports cells with relatively small sizes. The cell size can be determined based on system design and component constraints.

[0050] It should be understood that RAN 200 can include any number of radio base stations and cells. Furthermore, relay nodes can be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 can be connected to the network as described above. Figure 1 The scheduling entity 108 shown in the figure is the same as or similar to that shown in the figure.

[0051] Figure 2 It also includes an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. The UAV 220 can be configured to function as a base station, or more specifically as a mobile base station. That is, in some examples, the cell does not have to be stationary, and the geographical area of ​​the cell can move depending on the location of the mobile base station (such as the UAV 220).

[0052] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see [link to core network]) to all UEs within the corresponding cell. Figure 1Access points. For example, UE 222 and UE 224 can communicate with base station 210; UE 226 and UE 228 can communicate with base station 212; UE 230 and UE 232 can communicate with base station 214 via RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base station 220. In some examples, UE 222, UE 224, UE 226, UE 228, UE 230, UE 232, UE 234, UE 236, UE 238, UE 240 and / or UE 242 can communicate with the access points described above and Figure 1 The UE / scheduled entity 106 illustrated herein is the same as or similar to that shown. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0053] In another aspect of RAN 200, sidelink signaling can be used between UEs without relying on scheduling or control information from the base station. For example, sidelink network communication can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For instance, two or more UEs (e.g., UE 238, UE 240, and UE 242) can communicate with each other using sidelink signaling 237 without relaying the communication through the base station. In some examples, UE 238, UE 240, and UE 242 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and transmit sidelink signaling 237 among themselves without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UE 226 and UE 228) within the coverage area of ​​a base station (e.g., base station 212) may also transmit sidelink signal 227 on a direct link (sidelink) without passing the communication through base station 212. In this example, base station 212 may allocate resources to UE 226 and UE 228 for sidelink communication.

[0054] To achieve a low block error rate (BLER) while still maintaining a very high data rate for transmission over the air interface, channel decoding can be used. That is, wireless communication can typically utilize appropriate error-correcting block codes. In a typical block code, the information message or sequence is divided into code blocks (CBs), and then an encoder (e.g., a CODEC) at the transmitting device mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message improves message reliability, enabling correction for any bit errors that may occur due to noise.

[0055] Data decoding can be implemented in several ways. In early 5G NR specifications, quasi-cyclic low-density parity-check (LDPC) was used to encode user data, employing two different base maps (one for large code blocks and / or high code rates, and the other for other cases). Polar coding was used to encode control information and the Physical Broadcast Channel (PBCH) based on nested sequences. For these channels, truncation, shortening, and repetition were used for rate matching.

[0056] Various aspects of this disclosure can be implemented using any suitable channel code. Various implementations of the base station and UE may include appropriate hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0057] In RAN 200, the ability of a UE to communicate independently of its location while on the move is referred to as mobility. Various physical channels between the UE and RAN 200 are typically established, maintained, and released under the control of the Access and Mobility Management Function (AMF). In some scenarios, the AMF may include a Security Context Management Function (SCMF) that performs authentication and a Security Anchor Function (SEAF). The SCMF can manage the security context for both control plane and user plane functionalities, either entirely or partially.

[0058] In various aspects of this disclosure, RAN 200 can utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the transfer of UE connectivity from one radio channel to another). In a network configured for DL-based mobility, during calls with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During the present time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given time, the UE can undertake a handover or transfer from the serving cell to a neighboring (target) cell. For example, UE 224 can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds the signal strength or quality from its serving cell 202 for a given time, UE 224 can send a report message indicating this condition to its serving base station 210. In response, UE 224 can receive a handover command and the UE can undergo handover in cell 206.

[0059] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a uniform synchronization signal (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, UE 224, UE 226, UE 228, UE 230, and UE 232 can receive the uniform synchronization signal, derive the carrier frequency and time slot timing from the synchronization signal, and transmit uplink pilot or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be simultaneously received by two or more cells within RAN 200 (e.g., base stations 210 and 214 / 216). Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. When UE 224 moves through RAN 200, RAN 200 can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, RAN 200 can switch UE 224 from the serving cell to a neighboring cell, with or without notifying UE 224.

[0060] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, the synchronization signals do not need to identify a specific cell. Instead, they can identify an area of ​​multiple cells at the same frequency and / or with the same timing. Using areas in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves the efficiency of both the UE and the network because it reduces the number of mobility messages that need to be exchanged between the UE and the network.

[0061] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically obtained by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-authorized license. While some technical rules are generally still required to access unlicensed spectrum, access is typically available to any operator or device. Shared spectrum can fall between licensed and unlicensed spectrum, where access may require technical rules or restrictions, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide a Licensed Shared Access (LSA) to share the spectrum with other parties, for example, by utilizing conditions determined by the appropriate licensee.

[0062] Devices communicating in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to achieve simultaneous communication between various devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes, but can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other suitable multiplexing schemes can be used to provide multiplexing for DL ​​transmissions from base station 210 to UEs 222 and 224.

[0063] Devices in the radio access network 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex simulations are frequently implemented for wireless links using Time Division Duplex (TDD). In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel. That is, in some scenarios, the channel is dedicated to transmissions in one direction, while at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels typically rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulations are often implemented for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions can operate on different carrier frequencies (e.g., within paired spectrum). In SDD, spatial division multiplexing (SDM) is used to separate transmissions in different directions on a given channel from each other. In other examples, full-duplex communication can be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as subband full-duplex (SBFD), also known as flexible duplex or half-duplex FDD.

[0064] Reference Figure 3 The OFDM waveforms illustrated herein are used to describe various aspects of this disclosure. Those skilled in the art will understand that various aspects of this disclosure can be applied to SC-FDMA waveforms in essentially the same manner as described below. That is, although some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0065] Now for reference Figure 3 The illustration shows an expanded view of exemplary subframe 302, illustrating the OFDM resource grid. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application can vary from the example described herein depending on any number of factors. Here, time is in the horizontal direction, in OFDM symbols; and frequency is in the vertical direction, in subcarriers or carriers.

[0066] Resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding number of resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE of 1 subcarrier × 1 symbol is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE can represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the parametric used. In some examples, depending on the parametric, an RB may include any suitable number of consecutive OFDM symbols in the time domain. In this disclosure, it is assumed that a single RB such as RB 308 corresponds exactly to a single direction of communication (transmission or reception for a given device).

[0067] A collection of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth portion (BWP). A collection of subbands or BWPs can span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWPs). Therefore, the UE typically utilizes only a subset of the resource grid 304. In some examples, an RB may be the smallest unit of resource that can be allocated to the UE. Therefore, the more RBs scheduled for the UE and the higher the modulation scheme selected for the air interface, the higher the data rate available for the UE. RBs can be scheduled by a scheduling entity (such as a base station (e.g., gNB, eNB, etc.)) or can be scheduled by the UE itself implementing D2D sidelink communication.

[0068] In this illustration, RB 308 is shown occupying less than the entire bandwidth of subframe 302, with some subcarriers illustrated above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RB 308. Furthermore, in this illustration, RB 308 is shown occupying less than the entire duration of subframe 302, although this is only one possible example.

[0069] Each 1ms subframe 302 can consist of one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, time slots can be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-slots with shorter durations (e.g., one to three OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). In some cases, these micro-slots or shortened transmission time intervals (TTIs) may be transmitted while occupying resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be used within a subframe or time slot.

[0070] An expanded diagram of one of the time slots 310 illustrates a time slot 310 including a control region 312 and a data region 314. Typically, the control region 312 may carry a control channel, and the data region 314 may carry a data channel. Of course, a time slot may contain all DLs, all ULs, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely exemplary and different time slot structures can be used, and may include one or more of each of the control region(s) and data region(s).

[0071] Although Figure 3 Although not shown, each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can be provided to the receiving equipment to perform channel estimation for the corresponding channel, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0072] In some examples, time slot 310 can be used for broadcast, multicast, groupcast, or unicast communication. For example, broadcast, multicast, or groupcast communication can refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast or groupcast communication is delivered to multiple intended receiving devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0073] In an example of cellular communication over a cellular carrier via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within control area 312) to one or more scheduled entities (e.g., UEs) to carry DL control information, including one or more DL control channels such as the Physical Downlink Control Channel (PDCCH). The PDCCH carries downlink control information (DCI), which includes, but is not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or the allocation of REs for DL ​​and UL transmissions. The PDCCH may also carry HARQ feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well known to those skilled in the art, whereby the integrity of packet transmissions can be checked for accuracy on the receiving side, for example, using any suitable integrity checking mechanism (such as checksums or cyclic redundancy check (CRC)). If the integrity of the transmission is acknowledged, an ACK can be sent; otherwise, a NACK can be sent. In response to NACK, the transmitting device can send HARQ retransmission, which can achieve catch-up merging, incremental redundancy, etc.

[0074] The base station can also allocate one or more REs 306 (e.g., in control area 312 or data area 314) to carry other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signals (PT-RS); channel state information (CSI) reference signals (CSI-RS); and synchronization signal blocks (SSBs). SSBs can be broadcast at regular intervals based on periodicity (e.g., 5, 10, 20, 30, 80, or 130 ms). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE can utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identifier (PCI) of the cell.

[0075] The PBCH in the SSB may also include a Master Information Block (MIB), which includes various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, a SystemInformationType 1 (SIB1) that may include various additional system information. Together, the MIB and SIB1 provide the minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameters), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell prohibition indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of residual minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information.

[0076] In UL transmission, the scheduled entity (e.g., the UE) may use one or more RE 306s to carry UL control information (UCI) to the scheduling entity. This UCL includes one or more UL control channels, such as the Physical Uplink Control Channel (PUCCH). The UCL can include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include Sounding Reference Signals (SRS) and Uplink DMRS. In some examples, the UCL may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the UCL, the scheduling entity may transmit Downlink Control Information (DCI), which can schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, Channel State Feedback (CSF) (such as CSI reports), or any other suitable UCL.

[0077] In addition to control information, one or more REs 306 (e.g., within data area 314) can be allocated for service data. Such services can be carried on one or more service channels, such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions, or the Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within data area 314 can be configured to carry other signals, such as one or more SIBs and DMRS.

[0078] In an example of sidelink communication on a sidelink carrier via the ProSe PC5 interface, the control area 312 of time slot 310 may include a physical sidelink control channel (PSCCH) comprising sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., Rx V2X devices or other Rx UEs). The data area 314 of time slot 310 may include a physical sidelink shared channel (PSSCH) comprising sidelink data traffic transmitted by the initiating (transmitting) sidelink device via the SCI within resources reserved on the sidelink carrier by the transmitting sidelink device. Other information may also be transmitted via the various REs 306 within time slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device via the physical sidelink feedback channel (PSFCH) within time slot 310. Additionally, one or more reference signals, such as lateral link SSB, lateral link CSI-RS, lateral link SRS, and / or lateral link positioning reference signal (PRS), can be transmitted within time slot 310.

[0079] These physical channels are typically multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transmit channel carries blocks of information called transmit blocks (TBs). The transmit block size (TBS) can correspond to the number of bits of information and can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0080] Figure 3 The channels or carriers illustrated herein may not be all channels or carriers that can be used between devices, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be used in addition to the channels or carriers illustrated herein.

[0081] Figure 4 This is a high-level schematic diagram providing an example of an Integrated Access Backhaul (IAB) network configuration 400 that can be utilized in some aspects of this disclosure. In this diagram, a communications network 402, such as an IAB network, is coupled to a remote network 404, such as a primary backhaul network or a mobile core network. In such an IAB network 402, radio spectrum can be used for both access links and backhaul links. In some examples, the radio spectrum can utilize millimeter wave (mmWave) or carrier frequencies below 6 GHz.

[0082] IAB network 402 can be similar to Figure 2The radio access network 200 shown can be divided into multiple cells 406, 408, 410, 412, and 414, each of which can be served by corresponding IAB nodes 416, 418, 420, 422, and 424. Each of the IAB nodes 416-424 can be an access point, base station (BS), eNB, gNB, or other node that utilizes radio spectrum (e.g., radio frequency (RF) spectrum) to support access to one or more UEs located within cells 406-414 served by the IAB nodes.

[0083] exist Figure 4 In the example shown, IAB node 416 communicates with UEs 426 and 428 via radio access links 430 and 432, IAB node 418 communicates with UE 434 via radio access link 436, and IAB node 422 communicates with UE 438 via radio access link 440. IAB nodes 416-424 are also interconnected via one or more radio backhaul links 442, 444, 446, 448, 450, and 452. Each radio backhaul link 442-452 can utilize the same radio spectrum (e.g., radio frequency (RF) spectrum) as access links 430-440 to backhaul access traffic to / from remote network 404. This can be referred to as wireless self-backhaul. Such wireless self-backhaul enables rapid and easy deployment of high-density small cell networks. That is, instead of requiring each new gNB deployment to be equipped with its own hardwired backhaul connection, the radio spectrum used for communication between the gNB and the UE can be used to perform backhaul communication between any number of IAB nodes to form an IAB network 402.

[0084] exist Figure 4 In the example shown, IAB node 416 communicates with IAB node 420 via wireless backhaul link 442; IAB node 420 communicates with IAB node 422 via wireless backhaul link 444; IAB node 422 communicates with IAB node 424 via wireless backhaul link 446; IAB node 424 communicates with IAB node 418 via wireless backhaul link 448; IAB node 418 communicates with IAB node 416 via wireless backhaul link 450; and IAB node 418 communicates with IAB node 420 via wireless backhaul link 452. Figure 4 As shown, each IAB node 416-424 can connect to two or more other IAB nodes via its own wireless backhaul link 442-452 to achieve robustness.

[0085] Some or all of IAB nodes 416-424 can also be connected via wired backhaul links (e.g., fiber optic, coaxial cable, Ethernet, copper wire, etc.) and / or microwave backhaul links. Therefore, IAB network 402 can support wired / microwave and wireless backhaul services. At least one of the IAB nodes (e.g., IAB node 424) can be a border IAB node, also referred to herein as an IAB donor node, which also provides a communication link 454 to the remote network 404. For example, IAB donor node 424 may include wired (e.g., fiber optic, coaxial cable, Ethernet, copper wire), microwave, or other suitable links 454 to the remote network 404.

[0086] To facilitate wireless communication between IAB nodes 416-424 and between IAB nodes 416-424 and the UEs served by IAB nodes 416-424, each IAB node 416-424 can be configured to operate as both a scheduling entity and a scheduled entity. Therefore, IAB nodes (e.g., IAB node 416) can use the same radio spectrum to transmit access traffic to / from the UE and then backhaul access traffic to / from the remote network 404. For example, for backhaul access traffic to / from IAB node 418, IAB node 418 can communicate with IAB node 420 to transmit the backhaul access traffic via radio backhaul link 442, IAB node 420 can communicate with IAB node 422 to transmit the backhaul access traffic via radio backhaul link 444, and IAB node 422 can communicate with IAB node 424 to transmit the backhaul access traffic via radio backhaul link 446. In this example, both IAB nodes 420 and 422 can operate as both scheduling entities and scheduled entities to backhaul access services to / from IAB node 416. Thus, communication between a pair of IAB nodes can be scheduled independently by one of the IAB nodes in the pair.

[0087] In other examples, IAB nodes can schedule wireless backhaul communication between other IAB node pairs. For instance, IAB node 424 can operate as a scheduling entity for IAB network 402, while IAB nodes 416, 420, and 422 each operate as scheduled entities to backhaul access traffic to / from IAB node 416. In this example, IAB node 424 can schedule wireless backhaul communication between each pair of IAB nodes (e.g., between IAB nodes 416 and 420, between IAB nodes 420 and 422, and between IAB nodes 422 and 424). As another example, IAB node 422 can operate as a scheduling entity to schedule wireless backhaul communication between IAB nodes 416 and 420, and between IAB nodes 420 and 422. IAB node 422 can then operate as a scheduled entity to allow IAB node 424 to schedule the wireless backhaul communication therebetween.

[0088] Figure 5 This is a schematic diagram illustrating an example of the functionality of IAB nodes within an IAB network of 500. Figure 5 In the example shown, IAB node 502 is depicted as coupled to core network 504 via a wired connection. This IAB node 502 may be referred to herein as an IAB donor node, which, for example, may be an enhanced gNB including functions for controlling IAB network 500. In some examples, IAB donor node 502 may include a central unit (CU) 506 and a distributed unit (DU) 508. CU 506 is configured to operate as a centralized network node (or central entity) within IAB network 500. For example, CU 506 may include Radio Resource Control (RRC) layer functions and Packet Data Convergence Protocol (PDCP) layer functions to control / configure other nodes (e.g., IAB nodes and UEs) within IAB network 500 via an F1 interface.

[0089] DU 508 is configured to operate as a scheduling entity to schedule scheduled entities (e.g., other IAB nodes and UEs) of IAB donor node 502. For example, DU 508 of IAB donor node 502 can operate as a scheduling entity to schedule IAB nodes 510 and 512, as well as UEs 514 and UE 516. Therefore, DU 508 of IAB donor node 502 can schedule communication with IAB nodes 510 and 512 via the corresponding backhaul links, and schedule communication with UEs 514 and UE 516 via the corresponding access links. In some examples, DU 508 may include Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layer functions to enable operation as a scheduling entity.

[0090] Each of IAB nodes 510 and 512 can be configured as a Layer 2 (L2) relay node including a corresponding DU 520 and a mobile terminal (MT) unit 518, such that each of the L2 relay IAB nodes 510 and 512 can operate as a scheduling entity and a scheduled entity. For example, the MT unit 518 within each of the L2 relay IAB nodes 510 and 512 is configured to operate as a scheduled entity that can be scheduled by the IAB donor node 502. Each MT unit 518 within the L2 relay IAB nodes 510 and 512 is also facilitated to communicate with the IAB donor node 502 via a corresponding backhaul link. Additionally, the DU 520 within each of the L2 relay IAB nodes 510 and 512 operates similarly to the DU 508 within the IAB donor node 502 to function as a scheduling entity to schedule one or more corresponding scheduled entities (e.g., other IAB nodes and / or UEs) of the L2 relay IAB nodes 510 and 512.

[0091] For example, DU 520 of L2 relay IAB node 512 serves as a scheduling entity to schedule communication with UE 522 via the access link, while DU 520 of L2 relay IAB node 510 serves as a scheduling entity to schedule communication with MT unit 518 of L2 relay IAB nodes 526 and 526 via the corresponding backhaul link and with UE 528 via the access link. Each of L2 relay IAB nodes 524 and 526 also includes its own DU 520, which serves as a scheduling entity to communicate with their respective UEs 530 and 532. Therefore, in Figure 5 In the network topology shown, since IAB donor node 502 is configured to control each of the other nodes in the IAB network, IAB donor node 502 is the parent IAB node of child IAB nodes 510, 512, 524, and 526. Additionally, IAB node 510 is also the parent IAB node of child IAB nodes 524 and 526. For example, CU 506 and DU 508 within IAB donor node 502 can be used as parent IAB nodes of child IAB nodes 510, 512, 524, and 526, while DU 520 within IAB node 510 can be used as the parent IAB node of child IAB nodes 524 and 526. MT unit 518 within IAB nodes 510, 512, 524, and 526 can also be used as a child IAB node.

[0092] Figure 6 This diagram illustrates resource allocation within the IAB Network 600 based on several aspects. Figure 6In the example shown, parent IAB node 604 wirelessly communicates with child IAB node 602 via a first (e.g., backhaul) link. Child IAB node 602 also wirelessly communicates with child node 606 (e.g., another IAB node or UE) via a second (e.g., backhaul or access) link. Each IAB node 602 and 604 may correspond to, for example, Figure 4 or Figure 5 Any of the IAB nodes shown.

[0093] IAB network 600 can coordinate resource allocation between parent IAB node 604 and child IAB node 602 in a time-division multiplexing configuration. For example, IAB network 600 can utilize time-division duplex (TDD) radio carriers (e.g., unpaired spectrum) in FR2 (or higher frequency bands), which can be time-divided into multiple frames, subframes, and time slots. Within a frame, subframe, or time slot, for each IAB node DU, the IAB donor node CU (e.g., ...) Figure 5 (As shown) Different types of resources in the time domain can be allocated, such as hard downlink (DL) resources, hard uplink (UL) resources, soft DL resources, soft UL resources, or unavailable (NA) resources. Hard DL and hard UL resources allocated to an IAB node DU are resources that the IAB node DU can utilize, regardless of whether the IAB node includes MT units located in the same location. Soft DL and soft UL resources allocated to an IAB node DU are resources that the IAB node DU can share with co-located MT units, and are therefore available when not used by MT units (e.g., based on scheduling by the parent IAB-DU). Unavailable (NA) resources are resources that the IAB node DU cannot utilize except for cell-specific signals, such as SSB, CSI-RS, Physical Random Access Channel (PRACH), and SR.

[0094] exist Figure 6In the example shown, resources are illustrated as three sets 608a, 608b, and 608c, time-divided into resources. Each set 608a, 608b, and 608c may correspond to a frame, subframe, time slot, or a portion of a frame, subframe, or time slot. The first set 608a of resources is shown as allocated as a hard DL resource to the parent IAB node DU 604 and as unavailable to the child IAB node DU 602. The second set 608b of resources is shown as unavailable to the parent IAB node DU 604 and allocated as a hard DL resource to the child IAB node DU 602. The third set 608c of resources is shown as allocated as a hard UL resource to the parent IAB node DU 604 and as unavailable to the child IAB node DU 602. Therefore, the parent IAB node DU 604 can use the first set 608a of resources to transmit downlink information (e.g., downlink control and / or data) to the MT unit of the child IAB node 602 via a first link. Then, child IAB node DU 602 can use the second set of resources 608b to send downlink information (e.g., downlink control and / or data) to child node 606 via the second link. Then, the third set of resources 608c can be used by parent IAB node DU 604 to receive uplink information (e.g., uplink control and / or data) from the MT unit of child IAB node 602 via the first link.

[0095] The IAB donor node (CU) can generate a corresponding per-cell DU resource configuration for a TDD carrier and send it to each IAB-DU (including the DU of the IAB donor node). For example, the DU resource configuration can be sent in an F1 Application Protocol (F1-AP) message on the F1 interface between the CU and the IAB-DU. Each DU resource configuration can be, for example, a semi-static configuration, including symbol patterns for UL symbols, DL symbols, and / or flexible symbols for each time slot, and corresponding availability attributes (e.g., hard, soft, or NA) for each symbol type (e.g., UL, DL, and flexible). For example, the DU resource configuration for a cell served by parent IAB node 604 can include symbol patterns for DL ​​symbol 608a, flexible symbol 608b, and UL symbol 608c. DL symbol 608a and UL symbol 608b can each be configured as hard symbols, while flexible symbol 608b can be configured as unavailable.

[0096] In some examples, the DU resource configuration for a cell may be included within the information elements of the F1-AP message. For instance, the F1-AP message may include an Activated Cells to be UpdatedList information element (IE) that includes a list of activated cells served by the IAB-DU (e.g., parent IAB node 604), for which the F1-AP message includes the updated DU resource configuration of the IAB-DU. For each cell in the Activated Cells to be UpdatedList IE, the F1-AP message may also include an IAB-DU Cell Resource Configuration IE that includes the DU resource configuration for that cell. The F1-AP message may also include a Child-Node List IE that includes a list of child IAB nodes (e.g., child IAB node 602) of the IAB-DU (parent IAB node 604). For each sub-IAB node and each cell served by the sub-IAB node, the F1-AP message may also include the corresponding IAB-DU cell resource configuration IE for the cell served by the sub-IAB node. The parent IAB node (e.g., parent IAB node 604) may utilize the DU resource configuration of parent IAB node 604 and sub-IAB node 602 in scheduling communications (UL / DL) with sub-IAB node 602.

[0097] In various aspects of this disclosure, the DU resource configuration framework for cells communicating on unpaired (e.g., TDD) spectrum can be extended to cells communicating on paired (e.g., FDD) spectrum in FR1 or FR2 (or other bands). In some examples, half-duplex constraints between upstream and downstream links can be applied to IAB-DUs communicating via paired (e.g., FDD) spectrum. For example, on the uplink (UL) portion of the FDD band, the MT unit of the child IAB node can operate only in transmit mode, and the DU unit of the parent IAB node can operate only in receive mode. Similarly, on the downlink (DL) portion of the FDD band, the MT unit of the child IAB node can operate only in receive mode, and the DU unit of the parent IAB node can operate only in transmit mode. Thus, in some examples, when the corresponding cell operates in FDD spectrum, the DU resource configuration of the IAB node can follow the existing TDD resource configuration framework by adding a second instance of the existing DU resource configuration to the DU resource configuration information element.

[0098] Figure 7This is a signaling notification diagram illustrating an exemplary signaling notification of distributed unit (DU) resource configuration in paired spectrum within an IAB network, based on some aspects. Figure 7 In the example shown, IAB donor node 702 (e.g., the CU of the IAB donor node) wirelessly communicates with IAB node 704 (e.g., the DU of the IAB node, including the DU of the IAB donor node) via a backhaul link. IAB-DU 704 can be the parent IAB node of one or more child nodes 706; one of the child nodes is shown for convenience. IAB donor-CU 702 may correspond to, for example, Figure 4 and / or Figure 5 Any IAB donor node illustrated in the diagram. IAB-DU 704 may correspond to, for example, Figure 4 and / or Figure 5 Any IAB node illustrated in the diagram. Child node 706 may correspond to, for example, Figure 1 , Figure 2 , Figure 4 and / or Figure 5 Any of the IAB sub-nodes, UEs, or other scheduled entities shown.

[0099] At 708, the IAB donor-CU 702 can generate a DU resource configuration for the IAB-DU 704 in the paired spectrum and send the DU resource configuration to the IAB-DU 704. The DU resource configuration may include, for example, two semi-static DU resource configurations, each for a corresponding spectrum band (e.g., UL or DL ​​portion) of the paired spectrum. For example, the DU resource configuration may include a first DU resource configuration for a first spectrum band of the paired spectrum and a second DU resource configuration for a second spectrum band of the paired spectrum. In some examples, the first DU resource configuration may include an uplink DU resource configuration for the uplink portion of the paired spectrum, while the second DU resource configuration may include a downlink DU resource configuration for the downlink portion of the paired spectrum.

[0100] In some examples, the uplink DU resource configuration includes uplink symbol patterns for multiple uplink time slots, and the downlink DU resource configuration includes downlink symbol patterns for multiple downlink time slots. In some examples, the uplink symbol pattern includes a corresponding symbol type for each of the multiple symbols in each uplink time slot. For example, the symbol type for the uplink symbol pattern may include an uplink symbol type (U) or a flexible symbol type (F). Thus, the uplink symbol pattern includes a U / F pattern for the UL portion of the paired spectrum. In some examples, the downlink symbol pattern also includes a corresponding symbol type for each of the multiple symbols in each downlink time slot. For example, the symbol type for the downlink symbol pattern may include a downlink symbol type (D) or a flexible symbol type (F). Thus, the downlink symbol pattern includes a D / F pattern for the DL portion of the paired spectrum. Flexible symbols in the UL and / or DL ​​resource configurations can provide operability with existing scheduling constraints. For example, there may be scheduling constraints to cancel periodic (semi-permanently scheduled) transmissions on flexible resources (e.g., for power saving purposes). Therefore, configuring flexible resources on paired spectrum can enable paired spectrum cells to meet this scheduling constraint.

[0101] Each of the uplink and downlink DU resource configurations can also include a corresponding availability attribute (e.g., a hard symbol attribute (H), a soft symbol attribute (S), or an unavailability attribute (NA)) for each symbol type. For example, the uplink DU resource configuration can include a corresponding availability attribute for each of the U and F symbol types. Additionally, the downlink DU resource configuration can include a corresponding availability attribute for each of the D and F symbol types. In this example, the H / S / NA granularity can be per spectrum band. Therefore, the availability attribute (H / S / NA) for the U symbol type in the uplink DU resource configuration can be applied to all U symbols in the uplink DU resource configuration. Similarly, the availability attribute (H / S / NA) for the F symbol type in the uplink DU resource configuration can be applied to all F symbols in the uplink DU resource configuration. Different availability attribute options provide flexibility in configuring resources in shared spectrum pairs (e.g., multiple IAB-DUs across serving neighboring cells and / or multiple neighboring cells sharing a single IAB-DU). For example, the IAB donor-CU 702 can configure a set of resources in the uplink portion of the paired spectrum as flexible NA resources for one IAB-DU (e.g., IAB-DU 704) and the same set of resources as uplink soft or hard resources for another IAB-DU.

[0102] In some examples, DU resource configurations may include flexible time slots (e.g., time slots including all flexible symbols) or flexible symbols within time slots that can be aligned across the DL and UL portions of the paired spectrum. In this example, H / S / NA availability attributes for flexible symbols can be applied across both spectrum bands (e.g., uplink and downlink portions) of the paired spectrum. Therefore, a single common availability configuration for U / D / F symbols can be generated for both spectrum bands, avoiding the need for duplicate availability configurations between uplink and downlink DU resource configurations.

[0103] In some examples, flexible symbols (if any) can be configured in both uplink and downlink DU resource configurations, or only in one of the uplink or downlink DU resource configurations, for a given time slot. Such configurations can support, for example, half-duplex FDD (HD-FDD). In examples where flexible symbols can be configured for a given time slot in both uplink and downlink DU resource configurations, the flexible symbols may partially overlap or not overlap. Additionally, in examples where flexible symbols can be configured only for one of the downlink or uplink DU resource configurations, a single common availability configuration of the corresponding availability attributes of the U / D / F symbols can be generated for both the uplink and downlink DU resource configurations.

[0104] In some examples, the DU resource configuration for the paired spectrum may not be included in any flexible resource within either the DL or UL portion of the paired spectrum. In this example, the TDD DU resource configuration may be optional. Additionally, the H / S / NA granularity may be each time slot within a specific spectral band (e.g., frequency band) of the paired spectrum to provide sufficient flexibility when configuring DU resources across cells and / or across IAB-DUs. Furthermore, a single common availability configuration may be used to generate corresponding availability attributes for U / D symbols for both uplink and downlink DU resource configurations.

[0105] Other symbol patterns used for DU resource configuration are also within the scope of this disclosure, including patterns of both UL symbols and DL symbols in a single spectrum band comprising paired spectra.

[0106] In some examples, DU resource configurations may include a corresponding DU resource configuration for each cell served by IAB-DU 704. Each DU resource configuration for each cell may include, for example, two semi-static DU resource configurations, where one semi-static DU resource configuration is used for each spectrum band of the paired spectrum.

[0107] In some examples, the IAB donor-CU 702 may send an F1-AP message including DU resource configuration to the IAB-DU 704. In this example, the F1-AP message may include an Information Element (IE) that includes a list of active cells for the IAB-DU to be updated. For example, the F1-AP message may include an IE listing active cells to be updated, which includes a list of active cells served by the IAB-DU 704, for which the updated DU resource configuration is included in the F1-AP message. For each cell in the list of active cells to be updated, the F1-AP message may also include an IAB-DU cell resource configuration IE, which includes cell resource configurations for the paired spectrum (e.g., DU resource configurations for each spectrum band in that cell). Thus, each cell resource configuration includes two DU resource configurations, one of which is for each spectrum band of the paired spectrum (e.g., uplink and downlink portions).

[0108] The IAB donor-CU 702 can also send the corresponding sub-DU resource configuration for each sub-IAB node (e.g., sub-node 706) of IAB-DU 704. Each sub-DU resource configuration may include two DU resource configurations for sub-node 706, one of which is configured for each spectrum band of the paired spectrum (e.g., uplink and downlink). For example, the F1-AP message may also include a sub-node list IE that includes a list of sub-IAB nodes (e.g., sub-node 706) of IAB-DU 704. For each sub-IAB node and each cell served by the sub-IAB node, the F1-AP message may also include a corresponding IAB-DU cell resource configuration IE for the cell served by the sub-IAB node. The IAB-DU cell resource configuration IE may include two DU resource configurations for the sub-IAB node cell (e.g., one for uplink and one for downlink).

[0109] At 710, IAB-DU 704 may store DU resource configurations received from IAB donor-CU 702, including any child IAB node DU resource configurations, and send DU resource configuration acknowledgment messages to IAB donor-CU 702. At 712, IAB-DU 704 may utilize the DU resource configurations, including any and multiple DU resource configurations of child node 706, to schedule communication (UL / DL) with child node 706. IAB-DU 704 may then send scheduling information based on the DU resource configurations, indicating downlink allocation or uplink granting for resources on the paired spectrum for child node 706. For example, IAB-DU 704 may schedule downlink transmissions to child node 706 on hard DL resources in the downlink portion of the paired spectrum, and schedule uplink transmissions from child node 706 on hard UL resources in the uplink portion of the paired spectrum.

[0110] As another example, IAB-DU 704 can also schedule downlink transmissions in the downlink portion of the paired spectrum or on flexible soft resources, and uplink transmissions in the uplink portion of the paired spectrum or on flexible soft resources, based on the availability of soft resources. In some examples, IAB-DU 704 can determine the availability of soft resources based on scheduling information received from its parent IAB node (not shown). For example, soft resources can be configured for co-located MT units of IAB-DU 704 and IAB-DU 704. In this example, in response to the parent IAB node determining that the co-located MT units of IAB-DU 704 have not yet scheduled any communication with MT units on these soft resources, IAB-DU 704 can utilize the soft resources to schedule communication with child node 706.

[0111] In other examples, the parent IAB node of IAB-DU 704 can send an availability indicator to IAB-DU 704, which explicitly indicates the availability of one or more soft symbol types for IAB-DU 704. For example, the availability indicator may indicate whether soft uplinks, soft downlinks, and / or soft flexible symbols in one or more time slots (e.g., the next N time slots) are available for scheduling by IAB-DU 704. In TDD operations, a single availability indicator can be provided, indicating the availability of each symbol type (DL, UL, and flexible). The availability indicator may indicate, for example, that all soft symbol types are available for scheduling by IAB-DU 704, no soft symbol types are available for scheduling by IAB-DU 704, or one or more soft symbol types are available for scheduling by IAB-DU 704.

[0112] For FDD operations, according to the aspects described herein, two separate availability indicators can be sent from the IAB parent node to the IAB-DU 704 to allow for additional flexibility in releasing soft resources between the two spectrum bands of a paired spectrum. Figure 8 This is a signaling notification diagram illustrating an exemplary signaling notification for scheduling communication on soft resources in paired spectrum, based on several aspects. Figure 8 In the example shown, the parent IAB node 802 (e.g., the DU of the IAB node) wirelessly communicates with the child IAB node 804 (e.g., the MT unit of the IAB node) via a backhaul link. The child IAB node 804 can also wirelessly communicate with one or more child nodes 806; one of these child nodes is shown for convenience. The parent IAB node 802 and the child IAB node 804 may each correspond to, for example, Figures 4-7 Any of the IAB nodes illustrated. Child node 806 may correspond to, for example, Figure 1 , Figure 2 and / or Figures 4-7 The IAB sub-node UE or any other scheduled entity shown.

[0113] At 808, parent IAB node 802 may generate two availability indicators and send them to child IAB node 804. Each availability indicator may be associated with a corresponding spectrum band of the paired spectrum (e.g., a corresponding DU configuration for the spectrum band). For example, a first availability indicator may be associated with a first spectrum band of the paired spectrum (e.g., an uplink spectrum band), and a second availability indicator may be associated with a second spectrum band of the paired spectrum (e.g., a downlink spectrum band). The first availability indicator may indicate, for example, the availability of a corresponding symbol type in a first DU resource configuration (e.g., an uplink DU resource configuration) with soft symbol attributes in one or more time slots (e.g., the next N time slots). The second availability indicator may indicate, for example, the availability of a corresponding symbol type in a second DU resource configuration (e.g., a downlink DU resource configuration) with soft symbol attributes in one or more time slots (e.g., the next N time slots or a different number of time slots than the first availability indicator).

[0114] The first availability indicator may indicate, for example, that all symbol types with soft symbol attributes (e.g., U and F) are available for scheduling by child IAB node 804, none of the symbol types with soft symbol attributes (e.g., U and F) are available for scheduling by child IAB node 804, or one of the symbol types (e.g., U or F) is available for scheduling by child IAB node 804. The second availability indicator may indicate, for example, that all symbol types with soft symbol attributes (e.g., D and F) are available for scheduling by child IAB node 804, none of the symbol types with soft symbol attributes (e.g., D and F) are available for scheduling by child IAB node 804, or one of the symbol types (e.g., D or F) is available for scheduling by child IAB node 804.

[0115] In some examples, the first and second availability indicators may, for example, be sent from the parent IAB node 802 to the child IAB node 804 within the downlink control information (DCI). For example, the availability indicators may be carried in DCI format 2_5. Therefore, in various aspects, DCI format 2_5 can be extended to include two availability indicators for paired spectrum. This extension may follow, for example, the same framework used in DCI format 2_0, to extend the slot format indicator (SFI) carried in DCI format 2_0 to paired spectrum.

[0116] At 810, child IAB node 804 can schedule communication with child node 806 on available resources, including available soft resources indicated by two availability indicators. For example, child IAB node 804 can schedule uplink communication from child node 806 to child IAB node 804 on hard uplink resources and soft uplink and / or soft flexible resources, indicated as available by a first availability indicator. Additionally, child IAB node 804 can schedule downlink communication from child IAB node 804 to child node 806 on hard downlink resources and soft downlink and / or soft flexible resources, indicated as available by a second availability indicator. At 812, child IAB node 804 can generate scheduling information indicating resources for uplink and / or downlink communication scheduling and send this scheduling information to child node 806.

[0117] In some examples, child IAB node 804 and parent IAB node 802 may also exchange information regarding the number of protection symbols to be used during the transition between MT unit communication and DU communication. For example, refer again... Figure 6The child IAB node 602 can switch from an MT unit to a DU unit between the first set of resources 608a and the second set of resources 608b, and then switch back from a DU unit to an MT unit between the second set of resources 608b and the third set of resources 608c. Each switch may involve the child IAB node 602 performing a hardware handover and / or modifying the analog beamwidth used for transmission or reception between transmit and receive. Additionally, due to the propagation delay between the parent IAB node 604 and the child IAB node 602, downlink transmissions from the parent IAB node 604 within the first set of resources 608a can be received at the child IAB node 602 during the second set of resources 608b. Furthermore, the child IAB node 602 can initiate uplink transmissions to the parent IAB node 604 within the second set of resources 608b, associated with the third set of resources 608c, based on a timing advance (TA) value provided by the parent IAB node 604 to the child IAB node 602.

[0118] To facilitate handover at sub-IAB node 602 (e.g., between transmit and receive and / or analog beamwidth) and further avoid or minimize resource overlap between MT unit transmit / receive and DU transmit / receive due to TA or propagation delay, gaps can be provided at the edges (e.g., start or end) of resources where the transition between the MT unit and DU of sub-IAB node 602 occurs. For example, a first gap can be provided at the transition between a first set 608a of resources and a second set 608b of resources, and a second gap can be provided between the second set 608b of resources and a third set 608c of resources. Each gap may include one or more protection symbols (e.g., OFDM or SC-FDMA symbols) within a set of resources not used for transmit or receive. Sub-IAB node 602 may request and / or parent IAB node 604 may provide multiple protection symbols at each transition.

[0119] In TDD bands, the number of guard symbols can differ for each conversion type (e.g., MT Tx / Rx to / from DU Tx / Rx). Therefore, a corresponding number of guard symbols can be assigned for each of the eight different conversion types. For FDD bands, some conversion types may be irrelevant. For example, in the UL portion of a paired spectrum, the MT unit can only be in transmit (Tx) mode, and the DU can only be in receive (Rx) mode. Therefore, the only conversion type in the UL portion of the paired spectrum is MT Tx to / from DU Rx. Similarly, in the DL portion of a paired spectrum, the MT unit can only be in Rx mode, and the DU can only be in Tx mode. Therefore, the only conversion type in the DL portion of the paired spectrum is MTRx to / from DU Tx.

[0120] In TDD bands, when flexible symbols are provided in the sub-DU resource configuration at the transition edge, the transition type may not be easily identifiable at the parent IAB node 604. However, for FDD bands, such ambiguity may not exist. For example, flexible resources in the UL portion of a paired spectrum can be changed only to UL, and flexible resources in the DL portion of a paired spectrum can be changed only to DL.

[0121] Therefore, in all aspects, for the FDD band, the parent IAB node (e.g., Figure 8 The parent IAB node 802 shown can be used for child IAB nodes (e.g., Figure 8 When selecting multiple protection symbols for the transition type between the MT and DU operations of the child IAB node 804 (shown), the flexible resource (flexible symbol) is considered as an uplink symbol in the uplink symbol pattern of the paired spectrum's uplink portion. Additionally, the parent IAB node 802 can also consider the flexible resource (flexible symbol) as a downlink symbol in the downlink symbol pattern of the paired spectrum's downlink portion when selecting multiple protection symbols for the transition type between the MT and DU operations of the child IAB node 804.

[0122] Figure 9 This is a block diagram illustrating an example of a hardware implementation of an IAB node 900 using a processing system 914. For example, the IAB node 900 can be a child IAB node, a parent IAB node, or an IAB donor node, such as... Figures 4-9 The illustration of one or more of them.

[0123] IAB node 900 may be implemented using a processing system 914 including one or more processors 904. Examples of processors 904 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, IAB node 900 may be configured to perform any or more of the functions described herein. That is, the processor 904 used in IAB node 900 may be used to implement any or more of the procedures and programs described below.

[0124] In some instances, processor 904 may be implemented via a baseband or modem chip, and in other implementations, processor 904 may include multiple devices that are different from and distinct from the baseband or modem chip (e.g., in scenarios where they can work together to implement the examples discussed herein). As described above, various hardware arrangements and components other than the baseband modem processor can be used in implementations including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0125] In the examples herein, the processing system 914 can be implemented using a bus architecture, typically represented by bus 902. Depending on the specific application and overall design constraints of the processing system 914, bus 902 may include any number of interconnect buses and bridges. Bus 902 communicatively couples together various circuits including one or more processors (typically represented by processor 904), memory 905, and computer-readable media (typically represented by computer-readable media 906). Bus 902 may also link various other circuits known in the art (such as timing sources, peripherals, voltage regulators, and power management circuits), and therefore will not be described further.

[0126] Bus interface 908 provides an interface between bus 902 and transceiver 910. Transceiver 910 provides a communication interface or component for communicating with various other devices via a transmission medium (e.g., air). Depending on the nature of the device, a user interface 912 (e.g., keypad, display, touchscreen, speaker, microphone, control knob, etc.) may also be provided. Of course, such a user interface 912 is optional and may be omitted in some examples.

[0127] Processor 904 is responsible for managing bus 902 and general-purpose processing, including the execution of software stored on computer-readable medium 906. When executed by processor 904, this software causes processing system 914 to perform various functions for any particular device. Computer-readable medium 906 and memory 905 can also be used to store data manipulated by processor 904 during software execution. For example, memory 905 may store multiple DU resource configurations 915 and availability indicators (AI) 916 that can be used by processor 904.

[0128] One or more processors 904 in the processing system can execute software. Software, whether it involves software, firmware, middleware, microcode, hardware description languages, or others, should be broadly interpreted as representing instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. Software may reside on computer-readable media 906.

[0129] Computer-readable medium 906 may be a non-transitory computer-readable medium. As an example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 906 may reside in processing system 914, be outside of processing system 914, or be distributed across multiple entities including processing system 914. Computer-readable medium 906 may be included in a computer program product. For example, a computer program product may include a computer-readable medium within encapsulation material. In some examples, computer-readable medium 906 may be part of memory 905. Those skilled in the art will recognize that the best implementation of the functions described throughout this disclosure depends on the specific application and the overall design constraints imposed on the system.

[0130] In some aspects of this disclosure, processor 904 may include circuitry configured for various functions. In an example where IAB node 900 includes an IAB-DU (e.g., IAB node 900 is a child IAB node, parent IAB node, or IAB donor node), processor 904 may include resource allocation and scheduling circuitry 942 configured to generate, schedule, and modify resource allocations or authorizations for time-frequency resources (e.g., a set of one or more resource elements) to a set of one or more child nodes (e.g., UEs or child IAB nodes) of IAB node 900. For example, resource allocation and scheduling circuitry 942 may schedule time-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) time slots to carry user data services and / or control information to and / or from a set of one or more child nodes (e.g., UEs or child IAB nodes).

[0131] In an example where IAB node 900 is an IAB donor node including a CU, resource allocation and scheduling circuitry 942 can be configured to schedule resources for transmission of DU resource configuration 915 to another IAB node in the IAB network (e.g., the DU of the other IAB node). For example, resource allocation and scheduling circuitry 942 can be configured to schedule resources for transmission of an F1-AP message including DU resource configuration 915 to the other IAB node. In this example, when the other IAB node operates in an FDD band, DU resource configuration 915 can include a first DU resource configuration for a first spectrum band (e.g., an uplink band) of paired spectrum and a second DU resource configuration for a second spectrum band (e.g., a downlink band) of paired spectrum. DU resource configuration 915 can be associated with a single cell served by the other IAB node. In an example where other IAB nodes serve multiple cells, the F1-AP message can also include a corresponding additional DU resource configuration 915 for each cell served by the other IAB node. Additionally, the F1-AP message may include additional DU resource configurations 915 (e.g., sub-DU resource configurations) for one or more child IAB nodes of another IAB node.

[0132] In the example where IAB node 900 is the parent IAB node, resource allocation and scheduling circuitry 942 can be configured to schedule resources for transmission of AI 916 to the child IAB node. AI 916 may include, for example, a first AI 916 for a first spectrum band (e.g., the uplink portion) of paired spectrum and a second AI 916 for a second spectrum band (e.g., the downlink portion) of paired spectrum. For example, AI 916 can be transmitted within a DCI. The DCI may, for example, have DCI format 2_5.

[0133] The resource allocation and scheduling circuit 942 can also be configured to use DU resource configuration 915 associated with a cell serving one or more sub-nodes to schedule resources for communication (e.g., uplink or downlink communication) with one or more sub-nodes (e.g., UE or sub-IAB node). For example, the resource allocation and scheduling circuit 942 can be configured to use uplink DU resource configuration in DU resource configuration 915 to schedule uplink spectrum bands for paired spectrum for uplink communication with one or more sub-nodes. The resource allocation and scheduling circuit 942 can also be configured to use downlink DU resource configuration in DU resource configuration 915 to schedule downlink spectrum bands for paired spectrum for downlink communication with one or more sub-nodes. The resource allocation and scheduling circuit 942 can further utilize the corresponding sub-DU resource configuration of the sub-IAB node to schedule communication with the sub-IAB node.

[0134] Additionally, the resource allocation and scheduling circuit 942 can be configured to utilize AI 916 received from the parent IAB node 900 when scheduling uplink and / or downlink communication with one or more child nodes. For example, the resource allocation and scheduling circuit 942 can be configured to schedule uplink communication on soft uplink or flexible symbols based on AI 916 for uplink spectrum bands. The resource allocation and scheduling circuit 942 can also be configured to schedule downlink communication on soft downlink or flexible symbols based on AI 916 for downlink spectrum bands.

[0135] In some examples, the resource allocation and scheduling circuit 942 may also consider flexible symbols in the sub-DU resource configuration as uplink symbols in the uplink symbol pattern of the sub-IAB node or downlink symbols in the downlink symbol pattern of the sub-IAB node. The resource allocation and scheduling circuit 942 may then select the number of protection symbols at the transition type between the MT unit operation and the DU operation of the sub-IAB node based on considering flexible symbols as uplink symbols in the uplink symbol pattern or downlink symbols in the downlink symbol pattern. The resource allocation and scheduling circuit 942 may also be configured to execute resource allocation and scheduling instructions (software) 952 included on the computer-readable medium 906 to implement one or more of the functions described herein.

[0136] The processor 904 may also include communication and processing circuitry 944 configured to communicate with other IAB nodes and / or UEs in the IAB network. In some examples, the communication and processing circuitry 944 may include one or more hardware components that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuitry 944 may include one or more transmit / receive chains.

[0137] In some implementations of communication involving the reception of information, communication and processing circuitry 944 may obtain information from components of wireless communication device 900 (e.g., a transceiver 910 receiving information via radio frequency signaling notification or some other type of signaling notification suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 944 may output information to another component of processor 904, memory 905, or bus interface 908. In some examples, communication and processing circuitry 944 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 944 may receive information via one or more channels. In some examples, communication and processing circuitry 944 may include the functionality of receiving components. In some examples, communication and processing circuitry 944 may include the functionality of processing components, including demodulation components, decoding components, etc.

[0138] In some implementations of communication involving the transmission (e.g., sending) of information, communication and processing circuitry 944 may acquire information (e.g., from another component of processor 904, memory 905, or bus interface 908), process (e.g., modulate, encode, etc.) that information, and output the processed information. For example, communication and processing circuitry 944 may output information to transceiver 910 (e.g., which transmits information via radio frequency signaling notification or some other type of signaling notification suitable for the applicable communication medium). In some examples, communication and processing circuitry 944 may transmit one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 944 may transmit information via one or more channels. In some examples, communication and processing circuitry 944 may include the functionality of components for transmission (e.g., components for sending). In some examples, communication and processing circuitry 944 may include the functionality of components for generation, including components for modulation, components for encoding, etc.

[0139] In an example where IAB node 900 is an IAB donor node including a CU, communication and processing circuitry 944 can be configured to transmit one or more DU resource configurations 915 to another IAB node in the IAB network (e.g., a DU of another IAB node) via transceiver 910. For example, communication and processing circuitry 944 can be configured to generate an F1-AP message including the DU resource configurations(s)915 and send the message to the other IAB node (IAB-DU). In this example, when the other IAB node operates in an FDD band, each DU resource configuration 915 can include a first DU resource configuration for a first spectrum band (e.g., an uplink band) for pairing spectrum and a second DU resource configuration for a second spectrum band (e.g., a downlink band) for pairing spectrum. For example, each DU resource configuration 915 can be associated with a corresponding cell served by the other IAB node. As an example, an F1-AP message may include an IE (Active Cell List) to be updated, which includes a list of active cells served by the IAB-DU, and for each cell, the F1-AP message includes the updated DU resource configuration. For each cell in the IE, the F1-AP message may also include an IAB-DU cell resource configuration IE, which includes the cell resource configuration for the paired spectrum (e.g., uplink and downlink DU resource configuration for that cell).

[0140] Additionally, the DU resource configuration 915 included in the F1-AP message may also include sub-DU resource configurations for one or more sub-IAB nodes of other IAB nodes. For example, the F1-AP message may also include a sub-node list IE, which includes a list of sub-IAB nodes of the IAB-DU. For each sub-IAB node and each cell served by the sub-IAB node, the F1-AP message may also include a corresponding IAB-DU cell resource configuration IE for the cell served by the sub-IAB node. The IAB-DU cell resource configuration IE may include two DU resource configurations for the sub-IAB node cell (e.g., one for uplink and one for downlink).

[0141] In an example where IAB node 900 is a parent or child IAB node, communication and processing circuitry 944 can be configured to receive (multiple) DU resource configurations 915 from the CU of the IAB donor node (e.g., via F1-AP messages) via transceiver 910 and store (multiple) DU resource configurations 915 in memory 905. In an example where IAB node 900 is a parent IAB node, communication and processing circuitry 944 can also be configured to generate an AI 916 for the child IAB node and send it to the child IAB node via transceiver 910. For example, AI 916 can be sent within a DCI having format 2_5. Additionally, in an example where IAB node 900 is a child IAB node, communication and processing circuitry 944 can be configured to receive AI 916 from the parent IAB node via transceiver 910 and store AI 916 in, for example, memory 905.

[0142] In the example where IAB node 900 is the parent IAB node, the communication and processing circuitry 944 can also be configured to generate scheduling information and send it to one or more child nodes for uplink or downlink communication with one or more child nodes (e.g., UE or child IAB node) via transceiver 910. The resource allocation and scheduling circuitry 942 can determine the scheduling information using multiple DU resource configurations 915 associated with the cell serving one or more child nodes, the child DU resource configurations 915 of the child IAB node, and AI 916 received from the parent IAB node of IAB node 900. The communication and processing circuitry 944 can also be configured to execute communication and processing instructions (software) 954 included on computer-readable medium 906 to implement one or more of the functions described herein.

[0143] In an example where IAB node 900 is an IAB donor node including a CU, processor 904 may further include DU resource configuration generation circuitry 946, configured to generate one or more DU resource configurations 915 for one or more FDD cells served by IAB node 900 and / or one or more FDD cells served by one or more other IAB nodes in the IAB network. Each DU configuration 915 may include two semi-static DU resource configurations, each for a corresponding spectrum band (e.g., UL or DL ​​portion) of the paired spectrum. For example, each DU resource configuration 915 may include a first DU resource configuration for a first spectrum band of the paired spectrum and a second DU resource configuration for a second spectrum band of the paired spectrum. In some examples, the first DU resource configuration may include an uplink DU resource configuration for the uplink portion of the paired spectrum, while the second DU resource configuration may include a downlink DU resource configuration for the downlink portion of the paired spectrum.

[0144] In some examples, the uplink DU resource configuration includes uplink symbol styles for multiple uplink time slots, and the downlink DU resource configuration includes downlink symbol styles for multiple downlink time slots. In some examples, the uplink symbol style includes a corresponding symbol type for each of the multiple symbols in each uplink time slot. For example, the symbol type of the uplink symbol style may include an uplink symbol type (U) or a flexible symbol type (F). Thus, the uplink symbol style includes a U / F style for the UL portion of the paired spectrum. In some examples, the downlink symbol style also includes a corresponding symbol type for each of the multiple symbols in each downlink time slot. For example, the symbol type of the downlink symbol style may include a downlink symbol type (D) or a flexible symbol type (F). Thus, the downlink symbol style includes a D / F style for the DL portion of the paired spectrum. Each of the uplink and downlink DU resource configurations may also include a corresponding availability attribute (e.g., a hard symbol attribute (H), a soft symbol attribute (S), or an unavailable attribute (NA)) for each symbol type. For example, the uplink DU resource configuration may include corresponding availability attributes for each of the U and F symbol types. Additionally, the downlink DU resource configuration may also include corresponding availability attributes for each of the D and F symbol types. The DU resource configuration generation circuitry 946 may also be configured to execute DU resource configuration instructions (software) 956 contained on the computer-readable medium 906 to implement one or more of the functions described herein.

[0145] Figure 10 This is a flowchart of an exemplary method for configuring IAB-DU resources in a paired spectrum according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be necessary for all implementations of the embodiments. In some examples, the method may be as described above and Figure 9 The IAB node 900 shown in the diagram is executed by a processor or processing system, or by any suitable component used to implement the functions described herein.

[0146] In box 1002, the IAB node may receive resource configurations for its Distributed Unit (DU), which include a first DU resource configuration for a first spectrum band of the spectrum to be paired and a second DU resource configuration for a second spectrum band of the spectrum to be paired. In some examples, the first DU resource configuration includes an uplink DU resource configuration, and the second DU resource configuration includes a downlink DU resource configuration. The IAB node may receive an F1-Application Protocol (F1-AP) message including the resource configuration from the Central Unit (CU) of the IAB donor node.

[0147] In some examples, the uplink DU resource configuration includes an uplink symbol style for each of a plurality of uplink time slots, and the downlink DU resource configuration includes a downlink symbol style for each of a plurality of downlink time slots. The uplink symbol style may include a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots. The corresponding first symbol type may include an uplink symbol type or a flexible symbol type. The downlink symbol style may include a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink time slots. The corresponding second symbol type may include a downlink symbol type or a flexible symbol type. In some examples, the uplink DU resource configuration also includes a corresponding first availability attribute for each of the first symbol types in the plurality of uplink time slots, and the downlink DU resource configuration also includes a corresponding second availability attribute for each of the second symbol types in the plurality of downlink time slots. Each of the corresponding first availability attribute and each of the corresponding second availability attribute may include one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

[0148] In some examples, the resource configuration is associated with a first cell served by the IAB node. In this example, the IAB node may also receive an information element that includes a list of activated cells to be updated. The list of activated cells may include the first cell. Each cell in the list of activated cells may include a corresponding cell resource configuration for the spectrum used for pairing. Each cell resource configuration may include uplink DU resource configuration and downlink DU resource configuration for that cell.

[0149] In some examples, the IAB node may also receive sub-resource configurations (e.g., sub-DU resource configurations) for child nodes. The sub-resource configurations include a first sub-DU resource configuration for a first spectrum band and a second sub-DU resource configuration for a second spectrum band. The first sub-resource configuration may include uplink symbol patterns for each of a plurality of uplink time slots, and the second sub-resource configuration may include downlink symbol patterns for each of a plurality of downlink time slots. In some examples, the IAB node may also receive multiple sub-resource configurations including sub-resource configurations. Each of the multiple sub-resource configurations may be associated with a different corresponding child node of the IAB node or a different corresponding cell associated with a child node. For example, the above combined... Figure 9 The communication and processing circuitry 944 and transceiver 910 shown and described provide components for receiving DU resource configurations.

[0150] In box 1004, an IAB node can utilize resource configuration to schedule at least one communication with its child nodes. In some examples, an IAB node can utilize the resource configuration of its child nodes and sub-resource configurations to schedule at least one communication with its child nodes. For example, the above combined... Figure 9 The resource allocation and scheduling circuit 942 shown and described can provide a component for scheduling at least one communication.

[0151] Figure 11 This is a flowchart of another exemplary method for configuring IAB-DU resources in a paired spectrum according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be necessary for all implementations of the embodiments. In some examples, the method may be as described above and... Figure 9 The IAB node 900 shown in the diagram is executed by a processor or processing system, or by any suitable component used to implement the functions described herein.

[0152] In box 1102, the IAB node may receive resource configurations for its Distributed Unit (DU), which include a first DU resource configuration for a first spectrum band of the spectrum to be paired and a second DU resource configuration for a second spectrum band of the spectrum to be paired. In some examples, the first DU resource configuration includes an uplink DU resource configuration, and the second DU resource configuration includes a downlink DU resource configuration. The IAB node may receive an F1-Application Protocol (F1-AP) message including the resource configuration from the Central Unit (CU) of the IAB donor node.

[0153] In some examples, the uplink DU resource configuration includes an uplink symbol style for each of a plurality of uplink time slots, and the downlink DU resource configuration includes a downlink symbol style for each of a plurality of downlink time slots. The uplink symbol style may include a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots. The corresponding first symbol type may include an uplink symbol type or a flexible symbol type. The downlink symbol style may include a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink time slots. The corresponding second symbol type may include a downlink symbol type or a flexible symbol type. In some examples, the uplink DU resource configuration also includes a corresponding first availability attribute for each of the first symbol types in the plurality of uplink time slots, and the downlink DU resource configuration also includes a corresponding second availability attribute for each of the second symbol types in the plurality of downlink time slots. Each of the corresponding first availability attribute and each of the corresponding second availability attribute may include one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

[0154] In some examples, the resource configuration is associated with the first cell served by the IAB node. In this example, the IAB node may also receive an information element including a list of activated cells to be updated. The list of activated cells may include the first cell. Each cell in the list of activated cells may include a corresponding cell resource configuration for the spectrum used for pairing. Each cell resource configuration may include uplink DU resource configuration and downlink DU resource configuration for that cell.

[0155] In some examples, the IAB node may also receive sub-resource configurations (e.g., sub-DU resource configurations) for child nodes. The sub-resource configurations include a first sub-DU resource configuration for a first spectrum band and a second sub-DU resource configuration for a second spectrum band. The first sub-resource configuration may include uplink symbol patterns for each of a plurality of uplink time slots, and the second sub-resource configuration may include downlink symbol patterns for each of a plurality of downlink time slots. In some examples, the IAB node may also receive multiple sub-resource configurations including sub-resource configurations. Each of the multiple sub-resource configurations may be associated with a different corresponding child node of the IAB node or a different corresponding cell associated with a child node. For example, the above combined... Figure 9 The communication and processing circuitry 944 and transceiver 910 shown and described provide components for receiving DU resource configurations.

[0156] At 1104, the IAB node can receive a first availability indicator for a first spectrum band and a second availability indicator for a second spectrum band. The first availability indicator can indicate the availability of one or more first symbol types with soft symbol attributes in one or more uplink time slots out of a plurality of uplink time slots. The second availability indicator can indicate the availability of one or more second symbol types with soft symbol attributes in one or more downlink time slots out of a plurality of downlink time slots. The first and second availability indicators can be received, for example, from the parent IAB node of the IAB node. In some examples, the IAB node can receive downlink control information (DCI) including the first and second availability indicators. The DCI can have DCI format 2_5. For example, the above combined... Figure 9 The communication and processing circuitry 944 and transceiver 910 shown and described may provide components for receiving a first availability indicator and a second availability indicator.

[0157] In box 1106, an IAB node may utilize resource configuration, a first availability attribute, and a second availability attribute to schedule at least one communication with a child node of the IAB node. In some examples, an IAB node may utilize the resource configuration and sub-resource configuration of a child node to schedule at least one communication with a child node. For example, the above combined... Figure 9 The resource allocation and scheduling circuit 942 shown and described can provide a component for scheduling at least one communication.

[0158] Figure 12 This is a flowchart of another exemplary method for configuring IAB-DU resources in a paired spectrum according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be necessary for all implementations of the embodiments. In some examples, the method may be as described above and Figure 9 The IAB node 900 shown herein is executed by a processor or processing system, or by any suitable component for implementing the functions described herein.

[0159] In box 1202, an IAB node may receive a sub-resource configuration for the distributed unit (DU) of its child IAB nodes. This resource configuration may include a first DU resource configuration for a first spectrum band of paired spectrum and a second DU resource configuration for a second spectrum band of paired spectrum. In some examples, the first DU resource configuration includes an uplink DU resource configuration, and the second DU resource configuration includes a downlink DU resource configuration. The IAB node may receive an F1-Application Protocol (F1-AP) message including the sub-resource configuration from the central unit (CU) of the IAB donor node.

[0160] In some examples, the uplink DU resource configuration includes an uplink symbol style for each of a plurality of uplink time slots, and the downlink DU resource configuration includes a downlink symbol style for each of a plurality of downlink time slots. The uplink symbol style may include a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots. The corresponding first symbol type may include an uplink symbol type or a flexible symbol type. The downlink symbol style may include a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink time slots. The corresponding second symbol type may include a downlink symbol type or a flexible symbol type. In some examples, the uplink DU resource configuration also includes a corresponding first availability attribute for each of the first symbol types in the plurality of uplink time slots, and the downlink DU resource configuration also includes a corresponding second availability attribute for each of the second symbol types in the plurality of downlink time slots. Each of the corresponding first availability attribute and each of the corresponding second availability attribute may include one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute. For example, the above combined... Figure 9 The communication and processing circuitry 944 and transceiver 910 shown and described provide components for receiving DU resource configurations.

[0161] In 1204, an IAB node can consider flexible symbols as either uplink symbols in the uplink symbol pattern of the first DU resource configuration of a sub-IAB node or downlink symbols in the downlink symbol pattern of the second DU resource configuration. For example, the above combined Figure 9 The resource allocation and scheduling circuit 942 shown and described can provide components for considering flexible symbols as uplink symbols in an uplink symbol pattern or downlink symbols in a downlink symbol pattern.

[0162] In box 1206, the IAB node can select multiple protection symbols for the conversion type between MT unit operations and DU operations of the sub-IAB nodes. For example, the above combined Figure 9 The resource allocation and scheduling circuit 942 shown and described can provide components for selecting the number of protection symbols.

[0163] In one configuration, the IAB node 900 includes means for receiving resource configurations for a distributed unit (DU) of the IAB node, the resource configurations including a first DU resource configuration for a first spectrum band of paired spectrum and a second DU resource configuration for a second spectrum band of paired spectrum, as described herein. The IAB node 900 also includes components for scheduling communication with at least one child node of the IAB node using the resource configurations, as described herein. In one aspect, the aforementioned components may be...Figure 9 The processor 904 shown is configured to perform the functions listed by the foregoing components. Alternatively, the foregoing components may be circuits or any means configured to perform the functions listed by the foregoing components.

[0164] Of course, in the above example, the circuitry included in processor 904 is provided merely as an example, and other components for implementing the described functions may be included in various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 906, or in Figure 1 , Figure 3 and / or Figures 4-8 The description and use of any of them, for example, in this article concerning Figures 10-12 Any other suitable device or component of the described processing and / or algorithm.

[0165] Figure 13 This is a flowchart of another exemplary method for configuring IAB-DU resources in a paired spectrum according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be necessary for all implementations of the embodiments. In some examples, the method may be provided by the method described above and Figure 9 The IAB node 900 shown in the diagram is executed by a processor or processing system, or by any suitable component used to implement the functions described herein.

[0166] In box 1302, an IAB node (e.g., an IAB donor node) may generate resource configurations for distributed units (DUs) of IAB nodes within the IAB network. The resource configurations may include a first DU resource configuration for a first spectrum block of paired spectrum and a second DU resource configuration for a second spectrum block of paired spectrum. In some examples, the first DU resource configuration includes an uplink DU resource configuration, and the second DU resource configuration includes a downlink DU resource configuration.

[0167] In some examples, the uplink DU resource configuration includes an uplink symbol style for each of a plurality of uplink time slots, and the downlink DU resource configuration includes a downlink symbol style for each of a plurality of downlink time slots. The uplink symbol style may include a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots. The corresponding first symbol type may include an uplink symbol type or a flexible symbol type. The downlink symbol style may include a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink time slots. The corresponding second symbol type may include a downlink symbol type or a flexible symbol type. In some examples, the uplink DU resource configuration also includes a corresponding first availability attribute for each of the first symbol types in the plurality of uplink time slots, and the downlink DU resource configuration also includes a corresponding second availability attribute for each of the second symbol types in the plurality of downlink time slots. Each of the corresponding first availability attribute and each of the corresponding second availability attribute may include one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute. For example, the above combined... Figure 9 The DU resource configuration generation circuit 946 shown and described provides components for generating DU resource configurations for IAB nodes.

[0168] In box 1304, an IAB node can send resource configurations to its DU. For example, an IAB donor node can send an F1-Application Protocol (F1-AP) message, which includes resource configurations, from its CU to the IAB node.

[0169] In some examples, the resource configuration is associated with a first cell served by the IAB node. In this example, the IAB donor node may also send an information element that includes a list of activated cells to be updated. The list of activated cells may include the first cell. Each cell in the list of activated cells may include a corresponding cell resource configuration for the spectrum used for pairing. Each cell resource configuration may include uplink DU resource configuration and downlink DU resource configuration for that cell.

[0170] In some examples, the IAB donor node may also transmit sub-resource configurations (e.g., sub-DU resource configurations) of its child nodes (e.g., sub-IAB nodes). The sub-resource configurations include a first sub-DU resource configuration for a first spectrum band and a second sub-DU resource configuration for a second spectrum band. The first sub-resource configuration may include uplink symbol patterns for each of a plurality of uplink time slots, and the second sub-resource configuration may include downlink symbol patterns for each of a plurality of downlink time slots. In some examples, the IAB donor node may also transmit multiple sub-resource configurations including sub-resource configurations. Each of the multiple sub-resource configurations may be associated with a different corresponding child node of the IAB node or a different corresponding cell associated with a child node. For example, the communication and processing circuit 944, in conjunction with the above... Figure 9 The transceiver 910 shown and described together provides a component for sending resource configurations to the DU of the IAB node.

[0171] In one configuration, IAB node 900 includes components for generating resource configurations for distributed units (DUs) of IAB nodes within the IAB network. These resource configurations include a first DU resource configuration for a first spectrum band of paired spectrum and a second DU resource configuration for a second spectrum band of paired spectrum, as described herein. IAB node 900 also includes components for sending the resource configurations to the DUs of the IAB nodes, as described herein. In one aspect, the aforementioned components may be… Figure 9 The processor 904 shown is configured to perform the functions listed by the foregoing components. Alternatively, the foregoing components may be circuits or any means configured to perform the functions listed by the foregoing components.

[0172] Of course, in the above example, the circuitry included in processor 904 is provided merely as an example, and other components for implementing the described functions may be included in various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 906, or in Figure 1 , Figure 3 and / or Figures 4-8 The description and use of any of them, for example, in this article concerning Figure 13 Any other suitable device or component of the described processing and / or algorithm.

[0173] Figures 10-13 The processor shown may include additional aspects, such as any single aspect or any combination of aspects of one or more other processes described below and / or in conjunction with one or more other processes described elsewhere herein.

[0174] Aspect 1: A method for wireless communication at an IAB node within an Integrated Access Backhaul (IAB) network, the method comprising: receiving a resource configuration for a distributed unit (DU) of the IAB node, the resource configuration including a first DU resource configuration for a first spectrum band of a paired spectrum and a second DU resource configuration for a second spectrum band of the paired spectrum; and utilizing the resource configuration to schedule at least one communication with a child node of the IAB node.

[0175] Aspect 2: According to the method of aspect 1, wherein the first DU resource configuration includes an uplink DU resource configuration and the second DU resource configuration includes a downlink DU resource configuration.

[0176] Aspect 3: According to the method of Aspect 2, wherein: the uplink DU resource configuration includes an uplink symbol pattern for each of a plurality of uplink time slots, and the downlink DU resource configuration includes a downlink symbol pattern for each of a plurality of downlink time slots, the uplink symbol pattern including a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots, wherein the corresponding first symbol type includes an uplink symbol type or a flexible symbol type, and the downlink symbol pattern including a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink time slots, wherein the corresponding second symbol type includes a downlink symbol type or the flexible symbol type.

[0177] Aspect 4: According to the method of aspect 3, the uplink DU resource configuration further includes a corresponding first availability attribute for each of the first symbol types in the plurality of uplink slots, and the downlink DU resource configuration further includes a corresponding second availability attribute for each of the second symbol types in the plurality of downlink slots.

[0178] Aspect 5: According to the method of aspect 4, each of the corresponding first availability attributes and each of the corresponding second availability attributes may include one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

[0179] Aspect 6: According to the method of aspect 5, the method further includes: receiving a first availability indicator for the first spectrum band and a second availability indicator for the second spectrum band, the first availability indicator indicating the availability of one or more of a first symbol type including the soft symbol attribute in one or more of the plurality of uplink time slots, and the second availability indicator indicating the availability of one or more of the second symbol type including the soft symbol attribute in one or more of the plurality of downlink time slots, and wherein scheduling at least one communication with the child node further includes: scheduling at least one communication with the child node using the resource configuration, the first availability indicator and the second availability indicator.

[0180] Aspect 7: According to the method of aspect 6, receiving the first availability indicator and the second availability indicator further includes: receiving downlink control information (DCI) including the first availability indicator and the second availability indicator, wherein the DCI includes DCI format 2_5.

[0181] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the resource configuration is associated with a first cell served by the IAB node, and wherein receiving the resource configuration further includes: receiving an information element including a list of activated cells to be updated, wherein the list of activated cells includes the first cell, and wherein each cell in the list of activated cells includes a corresponding cell resource configuration for the spectrum of the pair.

[0182] Aspect 9: The method according to any one of aspects 1 to 8, further comprising: receiving a sub-resource configuration for the child node, wherein the sub-resource configuration includes a first sub-DU resource configuration for the first spectrum band and a second sub-DU resource configuration for the second spectrum band, and wherein scheduling at least one communication with the child node further comprises: scheduling at least one communication with the child node using the resource configuration and the sub-resource configuration.

[0183] Aspect 10: According to the method of aspect 9, wherein the first sub-DU resource configuration includes an uplink symbol pattern for each of the plurality of uplink slots, and the second sub-DU resource configuration includes a downlink symbol pattern for each of the plurality of downlink slots.

[0184] Aspect 11: According to the method of aspect 10, the method further includes: when selecting multiple protection symbols for the conversion type between the moving termination (MT) unit operation and the DU operation of the sub-node, considering the flexible symbol as an uplink symbol in the uplink symbol pattern or a downlink symbol in the downlink symbol pattern.

[0185] Aspect 12: According to the method of any one of Aspects 9 to 11, receiving the sub-resource configuration for the sub-node further includes: receiving a plurality of sub-DU resource configurations including the sub-resource configuration, each of the plurality of sub-DU resource configurations being associated with a different corresponding sub-node of the IAB node or a different corresponding cell associated with the sub-node.

[0186] Aspect 13: According to the method of any one of Aspects 1 to 12, receiving the resource configuration further includes: receiving an F1-Application Protocol (F1-AP) message including the resource configuration from the central unit (CU) of the IAB donor node.

[0187] Aspect 14: A method for wireless communication at an IAB donor node within an Integrated Access Backhaul (IAB) network, the method comprising: generating a resource configuration for a Distributed Unit (DU) of an IAB node within the IAB network, the resource configuration including a first DU resource configuration for a first spectrum band of a paired spectrum and a second DU resource configuration for a second spectrum band of the paired spectrum; and transmitting the resource configuration to the DU of the IAB node.

[0188] Aspect 15: According to the method of aspect 14, wherein the first DU resource configuration includes an uplink DU resource configuration and the second DU resource configuration includes a downlink DU resource configuration.

[0189] Aspect 16: The method of Aspect 15, wherein: the uplink DU resource configuration includes an uplink symbol pattern for an uplink timeslot, and the downlink DU resource configuration includes a downlink symbol pattern for a downlink timeslot, the uplink symbol pattern including a corresponding first symbol type for each of a plurality of first symbols in the uplink timeslot, wherein the corresponding first symbol type includes an uplink symbol type or a flexible symbol type, and the downlink symbol pattern including a corresponding second symbol type for each of a plurality of second symbols in the downlink timeslot, wherein the corresponding second symbol type includes a downlink symbol type or a flexible symbol type.

[0190] Aspect 17: The method according to aspect 16, wherein the uplink DU resource configuration further includes a corresponding first availability attribute for each of the first symbol types in the uplink time slot, and the downlink DU resource configuration further includes a corresponding second availability attribute for each of the second symbol types in the downlink time slot.

[0191] Aspect 18: According to the method of aspect 17, each of the corresponding first availability attributes and each of the corresponding second availability attributes may include one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

[0192] Aspect 19: The method according to any one of Aspects 14 to 18, wherein the resource configuration is associated with a first cell served by the IAB node, and wherein sending the resource configuration further includes: sending an information element including a list of activated cells to be updated, wherein the list of activated cells includes the first cell, and wherein each cell in the list of activated cells includes a corresponding cell resource configuration.

[0193] Aspect 20: The method according to any one of aspects 14 to 19 further includes: sending a sub-resource configuration for a child node of the IAB node, wherein the sub-resource configuration includes a first sub-DU resource configuration for the first spectrum band and a second sub-DU resource configuration for the second spectrum band.

[0194] Aspect 21: According to the method of aspect 20, sending the sub-resource configuration for the sub-node further includes sending a plurality of sub-DU resource configurations including the sub-resource configuration, each of the plurality of sub-DU resource configurations being associated with a different corresponding sub-node of the IAB node or a different corresponding cell associated with the sub-node.

[0195] Aspect 22: According to the method of any one of aspects 14 to 21, the sending of resource configuration further includes: sending an F1-Application Protocol (F1-AP) message including the resource configuration from the central unit (CU) of the IAB donor node to the IAB node.

[0196] Aspect 23: An apparatus configured for wireless communication, the apparatus comprising a transceiver, a memory, and a processor coupled to the wireless transceiver and the memory, the processor and the memory being configured to perform the method of any one of aspects 1 to 13 or aspects 14 to 22.

[0197] Aspect 24: An apparatus in a wireless communication network, the apparatus comprising at least one component for performing a method of any one of aspects 1 to 13 or aspects 14 to 22.

[0198] Aspect 25: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium including code for causing a device in a wireless communication network to perform the methods of any one of aspects 1 to 13 or aspects 14 to 22.

[0199] Several aspects of wireless communication networks have been described with reference to exemplary implementations. As will be readily understood by those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0200] As an example, various aspects can be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0201] Within this disclosure, the term “exemplary” is used to mean “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the invention. Similarly, the term “aspect” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term “coupled” is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other—even if they are not in direct physical contact with each other. For instance, even if the first object never directly physically contacts the second object, the first object can be coupled to the second object. The terms “circuit” and “circuit system” are used broadly and are intended to include, but are not limited to, hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in this disclosure, as well as software implementations that, when executed by a processor, enable the execution of information and instructions to perform the functions described in this disclosure.

[0202] Figures 1-13 One or more components, steps, features, and / or functions shown may be rearranged and / or combined into a single component, step, feature, or function, or included in several components, steps, or functions. Additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. Figure 1 , 2 The devices, apparatuses, and / or components shown in 4-9 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0203] It should be understood that the specific order or hierarchy of steps in the disclosed method is an illustrative representation of the process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the method may be rearranged. The appended method claims present elements of various steps in an exemplary order and are not intended to limit one to the presented specific order or hierarchy, unless specifically stated herein.

[0204] The preceding description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, these claims are not intended to be limited to the aspects shown herein, but rather to conform to the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, reference to an element in the singular does not mean “one and only one,” but rather “one or more.” Unless expressly stated otherwise, the term “some” means one or more. The phrase “at least one of” referring to a list of items refers to any combination of these items, including a single member. As an example, “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; all structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will be known by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims.

Claims

1. A method for wireless communication at an IAB node within an Integrated Access Backhaul (IAB) network, the method comprising: Receive resource configuration for the distributed unit (DU) of the IAB node, the resource configuration including uplink DU resource configuration for a first spectrum band of the paired spectrum and downlink DU resource configuration for a second spectrum band of the paired spectrum; as well as The resource configuration is used to schedule communication with at least one child node of the IAB node, wherein: The uplink DU resource configuration includes uplink symbol patterns for each of the multiple uplink time slots; The uplink symbol style includes a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots, wherein the corresponding first symbol type includes an uplink symbol type or a flexible symbol type; The uplink DU resource configuration further includes a corresponding first availability attribute for each of the uplink symbol type or flexible symbol type, the first availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute; The downlink DU resource configuration includes downlink symbol patterns for each of the multiple downlink time slots; The downlink symbol pattern includes a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink slots, wherein the corresponding second symbol type includes a downlink symbol type or the flexible symbol type; and The downlink DU resource configuration also includes a corresponding second availability attribute for each of the downlink symbol types or flexible symbol types, the second availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

2. The method according to claim 1, further comprising: Receiving a first availability indicator for the first spectrum band and a second availability indicator for the second spectrum band, the first availability indicator indicating the availability of one or more of the first symbol types including the soft symbol attribute in one or more of the plurality of uplink time slots, and the second availability indicator indicating the availability of one or more of the second symbol types including the soft symbol attribute in one or more of the plurality of downlink time slots, wherein scheduling the at least one communication with the child node further includes: The resource configuration, the first availability indicator, and the second availability indicator are used to schedule the at least one communication with the child node.

3. The method according to claim 2, wherein, The step of receiving the first availability indicator and the second availability indicator further includes: Receive downlink control information (DCI) including the first availability indicator and the second availability indicator, wherein the DCI includes DCI format 2_5.

4. The method according to claim 1, wherein, The resource configuration is associated with a first cell served by the IAB node, and wherein receiving the resource configuration further includes: The system receives an information element that includes a list of activated cells to be updated, wherein the list of activated cells includes the first cell, and wherein each cell in the list of activated cells includes a corresponding cell resource configuration for the spectrum of the pair.

5. The method according to claim 1, further comprising: Receiving sub-resource configurations for the child node, wherein the sub-resource configurations include a first sub-DU resource configuration for the first spectrum band and a second sub-DU resource configuration for the second spectrum band, and wherein the scheduling communication with the at least one child node further includes: The resource configuration and the sub-resource configuration are used to schedule the at least one communication with the child node.

6. The method according to claim 5, wherein, The first sub-DU resource configuration includes uplink symbol patterns for each of the multiple uplink time slots, and the second sub-DU resource configuration includes downlink symbol patterns for each of the multiple downlink time slots.

7. The method according to claim 6, further comprising: When selecting multiple protection symbols for the conversion type between the mobile terminal MT unit operation and DU operation for the sub-node, the flexible symbol is considered as either the uplink symbol in the uplink symbol pattern or the downlink symbol in the downlink symbol pattern.

8. The method according to claim 5, wherein, The receiving of the sub-resource configuration for the child node further includes: Receive a plurality of sub-DU resource configurations including the sub-resource configuration, each of the plurality of sub-DU resource configurations being associated with a different corresponding sub-node of the IAB node or a different corresponding cell associated with the sub-node.

9. The method according to claim 1, wherein, The process of receiving the resource configuration also includes: Receive the F1-AP message containing the resource configuration from the central unit (CU) of the IAB donor node.

10. An Integrated Access Backhaul (IAB) node configured for wireless communication, comprising: transceiver; At least one memory containing instructions; and At least one processor is configured to execute the instructions such that the node: The transceiver receives resource configurations for the distributed unit (DU) of the IAB node, the resource configurations including uplink DU resource configurations for a first spectrum band of the paired spectrum and downlink DU resource configurations for a second spectrum band of the paired spectrum. as well as The resource configuration is used to schedule communication with at least one child node of the IAB node, wherein: The uplink DU resource configuration includes uplink symbol patterns for each of the multiple uplink time slots; The uplink symbol style includes a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots, wherein the corresponding first symbol type includes an uplink symbol type or a flexible symbol type; The uplink DU resource configuration further includes a corresponding first availability attribute for each of the uplink symbol type or flexible symbol type, the first availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute; The downlink DU resource configuration includes downlink symbol patterns for each of the multiple downlink time slots; The downlink symbol pattern includes a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink slots, wherein the corresponding second symbol type includes a downlink symbol type or the flexible symbol type; and The downlink DU resource configuration also includes a corresponding second availability attribute for each of the downlink symbol types or flexible symbol types, the second availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

11. The IAB node according to claim 10, wherein, The processor and the memory are further configured to: The transceiver receives a first availability indicator for the first spectrum band and a second availability indicator for the second spectrum band. The first availability indicator indicates the availability of one or more of the first symbol types including the soft symbol attribute in one or more of the plurality of uplink time slots, and the second availability indicator indicates the availability of one or more of the second symbol types including the soft symbol attribute in one or more of the plurality of downlink time slots. The resource configuration, the first availability indicator, and the second availability indicator are used to schedule the at least one communication with the child node.

12. The IAB node according to claim 11, wherein, The first availability indicator and the second availability indicator are received within downlink control information (DCI), wherein the DCI includes DCI format 2_5.

13. A method for wireless communication at an IAB donor node within an integrated access backhaul IAB network, the method comprising: Generate resource configurations for distributed units (DUs) of IAB nodes within the IAB network, the resource configurations including uplink DU resource configurations for a first spectrum band of the paired spectrum and downlink DU resource configurations for a second spectrum band of the paired spectrum; as well as The resource configuration is sent to the DU of the IAB node, wherein: The uplink DU resource configuration includes uplink symbol patterns for each of the multiple uplink time slots; The uplink symbol style includes a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots, wherein the corresponding first symbol type includes an uplink symbol type or a flexible symbol type; The uplink DU resource configuration further includes a corresponding first availability attribute for each of the uplink symbol type or flexible symbol type, the first availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute; The downlink DU resource configuration includes downlink symbol patterns for each of the multiple downlink time slots; The downlink symbol pattern includes a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink slots, wherein the corresponding second symbol type includes a downlink symbol type or the flexible symbol type; and The downlink DU resource configuration also includes a corresponding second availability attribute for each of the downlink symbol types or flexible symbol types, the second availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

14. The method according to claim 13, wherein, The resource configuration is associated with a first cell served by the IAB node, and the sending of the resource configuration further includes: Sending an information element that includes a list of activated cells to be updated, wherein the list of activated cells includes the first cell, and wherein each cell in the list of activated cells includes a corresponding cell resource configuration.

15. The method of claim 13, further comprising: Send sub-resource configurations for the child nodes of the IAB node, wherein the sub-resource configurations include a first sub-DU resource configuration for the first spectrum band and a second sub-DU resource configuration for the second spectrum band.

16. The method according to claim 15, wherein, Sending the sub-resource configuration for the child node further includes: Send a plurality of sub-DU resource configurations including the sub-resource configuration, each of the plurality of sub-DU resource configurations being associated with a different corresponding sub-node of the IAB node or a different corresponding cell associated with the sub-node.

17. The method according to claim 13, wherein, Sending the resource configuration also includes: The F1-Application Protocol (F1-AP) message, which includes the resource configuration, is sent from the central unit (CU) of the IAB donor node to the IAB node.

18. An Integrated Access Backhaul (IAB) donor node configured for wireless communication, comprising: transceiver; At least one memory containing instructions; and At least one processor is configured to execute the instructions such that the node: Generate resource configurations for distributed units (DUs) of IAB nodes within the IAB network, the resource configurations including uplink DU resource configurations for a first spectrum band of the paired spectrum and downlink DU resource configurations for a second spectrum band of the paired spectrum; as well as The resource configuration is sent to the DU of the IAB node via the transceiver, wherein: The uplink DU resource configuration includes uplink symbol patterns for each of the multiple uplink time slots; The uplink symbol style includes a corresponding first symbol type for each of a plurality of first symbols in each of the plurality of uplink time slots, wherein the corresponding first symbol type includes an uplink symbol type or a flexible symbol type; The uplink DU resource configuration further includes a corresponding first availability attribute for each of the uplink symbol type or flexible symbol type, the first availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute; The downlink DU resource configuration includes downlink symbol patterns for each of the multiple downlink time slots; The downlink symbol pattern includes a corresponding second symbol type for each of a plurality of second symbols in each of the plurality of downlink slots, wherein the corresponding second symbol type includes a downlink symbol type or the flexible symbol type; and The downlink DU resource configuration also includes a corresponding second availability attribute for each of the downlink symbol types or flexible symbol types, the second availability attribute including one of a hard symbol attribute, a soft symbol attribute, or an unavailable symbol attribute.

19. An apparatus for performing wireless communication at an IAB node within an IAB network, the apparatus comprising components for performing the method according to any one of claims 1-9.

20. An apparatus for wireless communication performed at an IAB donor node within an IAB network, the apparatus comprising components for performing the method according to any one of claims 13-17.

21. A computer-readable medium having computer-executable code stored thereon, including code for causing IAB nodes within an IAB network to perform the method according to any one of claims 1-11.

22. A computer-readable medium having computer-executable code stored thereon, including code for causing IAB donor nodes within an IAB network to perform the method according to any one of claims 13-17.

Images